Module 11 – Runtime Configuration

Options
Runtime Configuration Options

• At the end of this module you will be able to:

– Stop and start servers using Node Manager
– Configure managed server independence
– Route Network requests using network
channels
– Install Startup and shutdown classes
Roadmap

1. Node Manager
– Node Manager Architecture
– Configure Node Manager
– Server Self-health
2. Managed Servers Independence
3. Network Channels
4. Startup and Shutdown Classes
Node Manager

• Node Manager (NM):

– Lets you start and kill managed servers
remotely: one server, a domain, a cluster
– Is an independent Java program
– Monitors and acts on server health
– Runs on the same computers as the managed
servers
– Receives its requests from the administration
server through the console or weblogic.Admin
– Can be run automatically in the background, as a
Windows service or a Unix daemon
Node Manager Architecture

• <Gráfico de la página 546>

Startup With Node Manager

• The interacctions among the Admin Server, Node

Manager and managed servers, when starting a
managed server, are as follows:

• <Gráfico de la página 547>

Shutdown With Node Manager

• The interacctions among the Admin Server, Node

Manager and managed servers, when shutting down
a managed server, are as follows:

• <Gráfico de la página 548>

Set Up Node Manager

• To set up Node Manager on a whole domain:

1. Configure trusted hosts.
2. Define and configure machines.
3. Specify server start information.
4. Start Node Manager.
1. Configure Trusted Hosts

• On each machine running managed servers, edit the file

%WL_HOME%\common\nodemanager\nodemanager.hosts.
• This file is created when Node Manager is started the first
time in the Managed Server
• Add the IP address of the administration server
• Alternatively, you can use the Admin Server’s DNS name
with Node Manager, using this
parameter:Dweblogic.nodemanager.reverseDNSenabled=t
rue
• This is used in firewall environments.
2. Define and Configure Machines …

• Each server must be tied to a machine.

• If necessary, creates new machines

• <Pantalla de la página 551>

… 2. Define and Configure Machines

• <Pantalla de la página 552>

3. Especify Server Start Information

• For each server, specify the startup configuration:

• <Pantalla de la página 553>

4. Start Node Manager

• You can start Node Manager in these ways:

– At the command line
– Using a start script
– As a Window service or Unix daemon
• The last method is preferred, because Node
Manager should always be running.
Command Line

• <Gráfico de la página 555>

Start Script

• WLS comes with a start script for node Manager

• Modify this script for your configuration,
particularly these elements:
– Listen address
– Port number
– Location of trusted hosts files
– Location of Java home

• <Gráfico de la página 556>

The nodemanager.properties File

• You can specify the Node Manager configuration on

the command line when you start the Node
Manager, or in the nodemanager.properties file.
• This file:
– Can be created as a text file with NM
configurations as key-value pairs
– Is automatically created in the directory from
which you starty Node Manager for the first time
after WLS installation, using the command line or
script
• Values specified on the command line override the
values in the file
Configure Node Manager as a Window Service

• The default script to install or uninstall Node

Manager as a service for Windows Platform is
located in this directory:
WL_HOME\server\bin\instalNodeMgrSvc.cmd
WL_HOME\server\bin\uninstalNodeMgrSvc.cmd
• By default, the service installer configures Node
Manager to run on localhost:5555
• Edit the install file to change the host address and
port number.
Start and Stop Managed Servers Remotely

• When Node Manager is set up and running on a

machine, you can start and stop WLS:

• <Pantalla de página 559>

Monitor Server Status

• When starting managed servers from console, the

task status can be monitored.

• <Pantalla de página 560>

Server stdout

• You can display managed server stdout, stderr and

log messages from the console, if the serverr was
started with NM.

• <Pantalla de página 561>

Starting an Entire Domain

• You can start all managed servers in a domain as

follows.

• <Pantalla de página 562>

Node Manager Log Files

• The Node Manager saves logs in the

NodeManagerLogs directory, located where the
Node Manager was started from.
• The NodeManagerLogs directory contains files that
keep track of this data:
– Managed servers process ID
– Startup configurations for each managed server
– Startup messages for each managed server
– Startup error messages for each managed server
• More logs for managed servers are stored in
NodeManagerClientLogs.
Server Self-health

• Server self-health improves availability of servers in

a domain.
• Selected subsystems in each server:
– Monitor their own health status according to
specific criteria
– Register health state as “failed” if the criteria
are exceeded
• A server registers its own health state as “failed” if
any registered subsystems have status as failed
Using Self-health with Node Manager

• Node Manager can automatically reboot failed

servers, if so configured.
• Manual intervention by the Administrator is not
required
• The health state is not visible through the console.
• The health state of a server can be
programmatically checked by JMX.
Configuring Server Self-health Monitoring

• <Pantalla de la Página 567>

Node Manager and Server States

• Node Manager defines internal states, for use when

restarting a server:
FAILED_RESTARTING
ACTIVATE_LATER
FAILED_NOT_RESTARTABLE

• <Pantalla de la Página 568>

Section Review

In this section, we learned how to:

– Configure Node Manager
– Setup Node Manager as a service
– Monitor server health
Exercise

Start ans Stop Servers with Node Manager

– For details on the exercise, refer to the Lab Guide.
– If questions arise, ask the instructor
– The instructor will determine the stop time
Roadmap

1. Node Manager
2. Managed Servers Independence
– Configure Managed Server Independence
– Administration Server Backup
– Discovery Mode
3. Network Channels
4. Startup and Shutdown Classes
What If an Admin Server Is Down?

• An administration server:
– Can go down without affecting the operation of
managed servers.
– Can be restarted while managed servers are
running
• When an administration server goes down:
– Domain log entries are lost while it is down
– Managed servers can start in independent mode
– The Administration Console and management
tools are unavailable
Managed Server Independence …

• By default managed servers can function

independently of the administration server
• You configure Managed Server Independence Mode
from the Console

• <Pantallas de la página 573>

… Managed Server Independence

• If the administration server is unavailable at boot

time, managed servers search for these files:
– msi-config.xml
– SerializedSystemIni.dat
– Boot.properties (optional)
• If managed servers do not share the root directory
with the Admin Server, copy the configuration files
to the managed server’s directory, and rename
config.xml to msi-config.xml
• Specify file locations with:
– Dweblogic.RootDirectory=path
Replicating Domain Configuration Files

• Administration servers can automatically copy

configuration files onto managhed servers every
five minutes

• <Pantallas del la página 575>

Administration Server Backup

• WLS 8.1 lets you create a backup of the server, as

follows:
– Install (if necessary) WLS on backup machine
– Copy application files to backup machine
– Copy configuration files to backup machine
– Restart the Administration Server on new
machine, with Discovery enabled
• The new Administration server contacts managed
servers and informs them that it is running on a
new IP
Discovery Mode

• Discovery Mode has these properties:

– It allows re-connecting to managed servers after the
administration server goes down
– It is on by default, but can be turned off by using a special
flag when starting the administration server
– It tells the administration server to detect all managed
servers that might be running on the network
– -Dwblogic.discover.enabled=false
– weblogic.Admin … DISCOVERMANAGEDSERVEER can be
used to attach managed servers, dynamically, to the
running administration server (if is already started without
discovery mode)
Section Review

In this section, we learned how to:

– Configure managed server independence
– Backup domain configuration files
– Turn Discovery Mode on
Exercise

Configure Managed Server Independence

– For details on the exercise, refer to the Lab Guide.
– If questions arise, ask the instructor
– The instructor will determine the stop time
Roadmap

1. Node Manager
2. Managed Servers Independence
3. Network Channels
– Overview
– Configure Network Channels
4. Startup and Shutdown Classes
Network Addressing Features …

• Network addressing adds flexibility to networking

configurations, in these ways:
– Multiple NICs for a single WLS server
– Specific NICs, or multiple port numbers on a NIC,
for specific WLS servers
– Using multiple IP addresses with each server
– Using one IP address can be used with multiple
ports
– Configuring the cluster multicast port number
independently of port numbers used by cluster
members
… Network Addressing Features

• Network addressing adds flexibility to networking

configurations, in these ways:
– Administration-traffic only port
– Interoperability with earlier WLS versions
– Default configuration as per 6.X

• <Gráfico de la página 582>

Network Channels

• Network channels can do the following:

– Define a set of basic attributes of a network
connection to WLS
– Assign multiple channels to one server (segment
network traffic)
– Prioritize internal (non-url) connections
– Separate incoming client traffic from internal
server-to-server traffic in a domain
– Automatically generate a “default” channel
when a server is created
Using Channels

• Multiple NICs per sever:

– Each server has two NICs
– Two channels are configures
• Both channels are assigned to each server:
– StandardChannel
• Enables HTTP
• Disables other protocols
– SecureChannel
• Enables HTTPS
• Disables other protocols
• <Diagramas de la página 584>
Using Channels

• Channels separate internal and external traffic:

– The application channel is common among servers:
• It is used for internal communications
• The OutgoingEnabled attribute is enabled
– The client channel is used for external access:
• Clients can connect only using the secured
channel
• The OutgoingEnabled attribute is disabled

• <Diagramas de la página 585>

Configuring Network Channels …

• <Pantalla de la página 586>

… Configuring Network Channels …

• <Pantalla de la página 587>

… Configuring Network Channels

• <Pantalla de la página 588>

Administration Port …

• WLS allows configuration of dedicated administration

port for each domain, with these options:
– It generates an administration channel
– The channel settings are the same as for secured
default channel, except a separate SSLListenPort
value is defined
– Only secure t3s and https admin traffic is allowed
(no IIOP), and only from the console,
weblogic.Admin and managed servers
– All traffic requires two-way authentication
– Enables the server to start in standby mode
… Administration Port

• <Pantalla de la página 591>

Overriding Administration Port

• The Administration port can be overridden for

individual managed servers in the domain

• <Pantalla de la página 592>

Section Review

In this section, we learned how to:

– Identify scenarios in which network channels are
necessary
– Configure network channels
Exercise

Configure Network Channels

– For details on the exercise, refer to the Lab Guide.
– If questions arise, ask the instructor
– The instructor will determine the stop time
Roadmap

1. Node Manager
2. Managed Servers Independence
3. Network Channels
4. Startup and Shutdown Classes
– Overview
– Deploy a Startup or Shutdown Class
Definition: Startup Class

• The startup class is loaded and executed when

WebLogic Server boots.
• You can use startup class to do these tasks:
– Initialize objects in memory
– Reconstruct a JNDI tree
– Load critical values from the database
– Recover the system its state before shutdown
Definition: Shutdown Class

• The shutdown class is executed when WebLogic

Server is shutting down.
• A shutdown class is typically used to free resources
obtained by a startup class
Define a Startup or Shutdown Class

• <Pantalla de la página 598>

Deploy a Startup or Shutdown Class

• <Pantalla de la página 599>

When is a Startup Class loaded?

• By default, startup classes are loaded after the J2EE

deployment units
• J2EE deployment units load in this order: JDBC, JMS,
Connectors, EJBs, Web applications.
• If “Run before application deployments” is selected,
startup class are loaded just bebore JDBC Connections
Pools are deployed.

• <Esquema de la página 600>

Section Review

In this section, we learned how to:

– Deploy startup and shutdown classes using the
Administration Console
Exercise

Install Startup and Shutdown Classes

– For details on the exercise, refer to the Lab Guide.
– If questions arise, ask the instructor
– The instructor will determine the stop time
Module Review

In this module, we learned how to:

– Configure Node Manager to stop and start servers
remotely
– Set up managed server independence
– Create network channels
– Deploy and manage startup and shutdown classes