Manage managed servers by configuring Node Manager in WebLogic 12c

Manage managed servers by configuring Node Manager in WebLogic 12c

This document is based on the Oracle WebLogic Server 12c: logging ing and Using Node Manager Official Document. After practice, you will get it. It is designed to provide guidance for configuring and using node manager in weblogic12c.

1. Prepare the environment as follows:

Server Status:

Host Name	Ip	Purpose
MS	192.168.68.130	Install the management server and a managed Server
As1	192.168.68.131	Install another managed Server

Cluster installation:

Weblogic Service	Ip	Purpose
AdminServer	192.168.68.130
Cs	192.168.68.130	Weblogic Cluster
As1	192.168.68.130	First managed Server
As2	192.168.68.131	Second managed Server

 

Weblogic Computer Configuration

 

Computer Name	Node Manager IP Address	Node Manager Port	Associated managed servers
Machine-0	192.168.68.130	5556	As1
Machine-1	192.168.68.131	5557	As2

 

2. node manager configuration process

1. Check the existing configuration

1.1 start the Management Server

1.2 log on to the console

2. Configure node manager

2.1 create a directory in host ms <MIDDLEWARE_HOME>/user_projects/nodemanager/Machine-0

Where <MIDDLEWARE_HOME> is/opt/Oracle/Middleware

2.2 copy the file <MIDDLEWARE_HOME>/wlserver_12.1/server/bin/startNodeManager. sh to the Machine-0 directory.

2.3 modify the value of NODEMGR_HOME in the <MIDDLEWARE_HOME>/user_projects/nodemanager/Machine-0/startNodeManager. sh file:

Change NODEMGR_HOME to the directory you just created.

2.4 create the file nodemanager. properties in the directory <MIDDLEWARE_HOME>/user_projects/nodemanager/Machine-0/. The file content is as follows:

 

ListenAddress=ms ListenPort=5556 SecureListener= false

 

ListenAddress indicates the host where the node manager Service is located. Use the domain name or ip address whenever possible. Do not use locahost as much as possible. The specific cause is described later.

ListenPort is the listening port of node manager.

 

2.5 create a directory <MIDDLEWARE_HOME>/user_projects/nodemanager/Machine-1 on the as1 host and copy the file startNodeManager. sh, create the file nodemanager. properties. For specific operations, refer to the instructions above. The configuration is as follows:

 

 

 

3. register the computer to the domain

 

3.1 log on to ms, go to the <MIDDLEWARE_HOME>/wlserver_12.1/server/bin directory, and execute the command

 

Source setWLSEnv. sh
 
Java weblogic. WLST

 

3.2 enter the command in the wlst command line to connect to the Management Server

 

Connect ('weblogic ', '000000', 't3: // ms: 66661 ')

 

3.3 run the registration command

 

NmEnroll ('/opt/Oracle/Middleware/user_projects/domains/base_domain/', '/opt/Oracle/Middleware/user_projects/nodemanager/Machine-0 ')

 

Description:

 

Purpose:

(1) Associate Machine-0 with the domain where the management server is located, and download the nm_password.properties and SerializedSystemIni. dat files from the management server.

Nm_password.properties: Manage Server authorization Node Manager manage user names and passwords of managed servers (encrypted)

Reference Path:/opt/Oracle/Middleware/user_projects/domains/base_domain/config/nodemanager/nm_password.properties

SerializedSystemIni. dat: Key File

Reference Path:

(2) Update the nodemanager. domains file and nodemanager. domains record the weblogic domain that the Node Manager can manage

Two parameters:

(1) param1: Path of the domain, for example:/opt/Oracle/Middleware/user_projects/domains/base_domain

(2) param2: Path of the Node Manager, for example:/opt/Oracle/Middleware/user_projects/nodemanager/Machine-0

3.4 use exit () to exit the wlst command line.

3.5 perform the same operation on as1. pay attention to the nmEnroll parameter.

4. Start two node managers

4.1 log on to ms and run the following command in the directory <MIDDLEWARE_HOME>/user_projects/nodemanager/Machine-0:

./StartNodeManager. sh

4.2 log on to as1 and run the following command in the directory <MIDDLEWARE_HOME>/user_projects/nodemanager/Machine-1:

./StartNodeManager. sh

5. start or stop the managed server on the weblogic Console

5.1 select the server to stop

5.2 start/Close the service

Select the service to be started and click Start or close.

Problem 3

After configuring the node manager on the as1 host and starting it, it fails to start the managed server as2. Check that the node manager corresponding to Machine-1 is also available. Then, check whether the port corresponding to node manager on as1 can be accessed. It is found that the telnet 192.168.68.131 5557 command is used on as1, I was puzzled. I thought of nodemanager later. in properties, the ip address of the listener server is configured. At that time, the localhost is configured. If you try to change it to an ip address, you can use the telnet command to change it to a domain name, in the end, the problem of starting the server through node manager is eliminated. I don't know why localhost doesn't work.

To sum up, you can start from two aspects when encountering nodemanager problems:

1. Check the available status of the node manager corresponding to the computing component on the console. It is possible that the node manager has not been started.

2. When node manager is started, check whether node manager can provide external services normally. Use the telnet command on other machines to test the node manager Port accessibility.