Node Manager Set Up in Weblogic

Server instances in a WebLogic Server production environment are often distributed across multiple domains, machines, and geographic locations. Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements. . A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process. Node Manager must run on each computer that hosts WebLogic Server instances -- whether Administration Server or Managed Server -- that you want to control with Node Manager.

Configuring Node Manager

1. Set up the Node Manager Hosts FileNode Manager accepts commands from Administration Servers running on the same machine and on trusted hosts. Trusted hosts are identified by IP address or DNS name in the nodemanager.hosts file, which is created the first time we start Node Manager, in the directory where we run it. We can specify the name and location of the trusted hosts file using the trustedHosts command-line argument. By default, nodemanager.hosts is empty. To add trusted hosts, edit the file with a text editor, and add one line for each trusted host on which an Administration Server runs. If you want Node Manager to accept commands from any host, put an asterisk in the hosts file. The location of nodemanager.hosts file will generally be ..\weblogic92\common\nodemanager\nodemanager.hosts. 2. Configure a Machine to Use Node ManagerIn order for Node Manager to accept commands from remote Administration Servers, we must create a machine definition for each machine that runs a Node Manager process. A machine definition associates a particular machine with the server instances it hosts, and specifies the connection attributes for the Node Manager process on that machine.

Process to Create Machines Using WLS Console2.1 Navigate to Domain Environment Machines. Lock the console. Under the Machines table, click New. Specify the following properties, in the Create a New Machine: Name: Any name (e.g.: ipsMachine) Machine OS: Other (Windows), UNIX (Linux) Click OK.

2.2 Activate your changes. 2.3 Assign machine to managed servers one by one

Eg: Assign ipsMachine to the ips0 server by clicking the machine name as in the below screenshot. Lock the Console and click the Servers tab and click Add under the Servers table. Select ips0 as the existing server and click Finish. Similarly, Add home managed server to this machine.

2.4 Click the Node Manager tab to enter the properties of the Node Manager for this machine according to the machine specifications. Enter the DNS name or IP address upon which Node Manager listens in the Listen Address box.

2.5 Save and activate your changes. 3. Ensure Administration Server Address is Defined Make sure that a Listen Address is defined for each Administration Server that will connect to the Node Manager process. If the Listen Address for a Administration Server is not defined, when Node Manager starts a Managed Server it will direct the target server to contact localhost for its configuration information. Set the Listen Address using the Server->Configuration>General tab in the Administration Console. 4. Configure the Node Manager settings for the machine configured (eg: ipsMachine)4.1 Make sure the AdminServer is running. Also make sure that the managed servers are not currently running.

4.2 Navigate to Environment Servers AdminServer (admin) Confirm that the managed servers are targeted to run on the machine configured.

4.3

Restart the Administration Server before starting Managed Servers.

4.4 Create the nodemanager.hosts file for ipsMachine in the <WEBLOGIC_HOME>\common\nodemanager directory. Add one line consisting of the Admin Servers IP address to the nodemanager.hosts file, i.e. 127.0.0.1. This configures AdminServer as a trusted host.

4.5 Open a prompt and change to the <WEBLOGIC_HOME>\server\bin\ directory. Start the Node Manager to listen on a port (eg: 5556) on the machine configured by executing the following command: Windows: startNodeManager.cmd 127.0.0.1 5556 Unix/Linux: ./startNodeManager.sh 127.0.0.1 5556

4.5 Start the servers using the Node Manager Service. Navigate to domain Environment Servers ips0 Control Start/Stop. Select the check box against ips0 in the Server Status table, and click Start and when prompted to verify if you want to start the ips0 Managed Server, click Yes. Repeat the preceding step to start the Managed Server home. Navigate to domain Environment Servers. Verify the Running state for both the Managed Servers ips0 and home. Alternatively, use the command prompt window and run netstat an to verify that servers ips0 and home are listening.