Node Manager Management Summary

Node Manager Introduction

After you have created a machine, you must configure Node Manager to start and manage managed servers that are configured under machine.

Node Manager is a Java program provided by WebLogic server that allows you to start, shut down, restart, and supervise managed servers in the local domain console. Node Manager allows you to control the managed server from a remote machine. To use the NodeManager feature, you must start node Manager on the managed server machine. Environment Introduction

Need two computers to test connection, this time two computer information is as follows

Terminal	IP	WebLogic Path	Environmental Information	Notes
Machine A	10.10.39.178	D:\bea103	Win7 X86 Bea 10.3.0.0	As a Management Server machine
Machine B	10.10.36.72	D:\bea	Winserver 2003 X86 Bea 10.3.0.0	As a managed server machine

on-Machine Real operation New Domain

1. Create a new domain in machine A as the admin domain

Switch to Bea_home/wlserver_10.3/common/bin path, execute config.cmd

By default the next step, until the last part when the domain name is modified to DomainA, the WebLogic domain (DomainA) is created.

2. Similarly, in machine B, create a new domain test _domaina.

Configure the server

Start the DomainA service on machine A, log in to the console, and create a new ServerB

The configuration information is as follows:

Click Save.

Open the AdminServer information, select the SSL tab,

Expand the advanced information to save the hostname verification value to none. Similarly set ServerB, restart the service.

Configuring Startup parameters for ServerB

Open the Configuration page for ServerB, select the Server Start tab, and save as follows.

Configuring Machine

New Machineb

Click Machineb, go to the configuration page, configure the relevant information.

=

Click on the Node Manager tab, as configured above. Because the SSL authentication is not used, GU type that chooses plain. Listen address is configured as the IP of Machine B.

Click the Machineb Servers tab to add the ServerB. As shown in the following illustration:

Click on the Monitoring tab and the error is as follows because the NodeManager service has not been started in Machine B.

configuration, start node Manager

1. Modify the Bea_home/wlserver_10.3/common/nodemanager path on machine b

The Nodemanager.properties file resets the value of Securelistener to False, which is true by default.

2. Set WLST (WebLogic Scripting tool,weblogic script tool) to run the machine information.

Switch to Machine B's Bea_home/wlserver_10.3/common/bin path to execute the WLST command.

Enter the following command, carriage return

L Connect (' WebLogic ', ' WebLogic ', ' t3://10.10.39.178:7001 ') the first two parameters for the admin domain DomainA username and password, the third parameter is DomainA IP: port

Execution success is as follows: (think there is no SSL authentication, GU will have warning message)

Execute after successful execution

L nmenroll (' D:/bea103/wlserver_10.3/common/nodemanager ') parameter is the NodeManager path of the WebLogic domain end of the machine a end. (When executing a command, note the command case, and the path delimiter with "/")

The results of the successful execution are as follows:

3. Once the above operation is successful, you can start Node Manager.

Connection Node Manager

Wls:/myserver/serverconfig> nmconnect (' WebLogic ', ' weblogic ', ' localhost ', ' 5555 ', ' oamdomain ', ' c:/bea/user_ ' Projects/domains/oamdomain ', ' plain ')

Switch to the Bea_home/wlserver_10.3/server/bin path to execute the startnodemanager command to start node Manager. The startup success information is as follows:

4. Switch to the machine's domain console and observe Machineb's Monitoring tab, which is already accessible.

start ServerB via node Manger

Before starting the Machine B,d:\bea\user_projects\domains\test_domaina\servers folder is empty:

Machine B, Machine b,d:\bea\user_projects\domains\test_domaina\config Config.lok modified on 2011-9-25 16:35, Config + + modified for 2011-9-25 16:32

Through the DomainA console, start the ServerB,

Startup success:

Start again and observe the two directories under machine B,test_domaina

After starting the machine B,d:\bea\user_projects\domains\test_domaina\servers folder for more than two folders, ServerB under the general server startup related information:

Machine B,d:\bea\user_projects\domains\test_domaina\config Config.lok modified on 2011-9-25 16:35

Because my ServerB has been started in this, gu config: change time has not changed, if it is the first time to start ServerB, Node Manager will first the machine a broken config.

Doubts

L NodeManager to the WebLogic version of the managed end and the management side, the JDK version has no requirement limit.

This should not affect the test success in the following cases

Terminal	IP	WebLogic Path	Environmental Information	Notes
Machine A	10.10.39.178	D:\bea103	Win7 X86 Bea 10.3.0.0 JDK 1.6.0_05	As a Management Server machine
Machine B	10.10.36.25	/home/lcam_mm/oracle/middleware/	Open SuSE X86 Bea 10.3.3.0 JDK 1.6.0_18	As a managed server machine

Just after the console startup, a long time is the starting state, and then view the 36.25-side log, the server has started up, the console information is not updated, the reason is unknown%>_<%

After about 5 minutes, the console display started successfully.

The environment configuration information is as follows:

L How to use SSL authentication.

Appendix

TableA-10 Node Manager Commands for WLST Configuration

This command.	enables to	Use with WLST
Nm	Determine whether WLST is connected to Node Manager.	Online
Nmconnect	Connect WLST to Node Manager to establish a session.	Online or Offline
Nmdisconnect	Disconnect WLST from a Node Manager session.	Online
Nmenroll	Enroll the which WLST is currently running.	Online
Nmgenbootstartupprops	Generates the Node Manager property files, Boot.properties and startup.properties, for the specified server.	Online
Nmkill	Kill The specified server instance that is started with Node Manager.	Online
Nmlog	Return the Node Manager log.	Online
Nmserverlog	Return the server output log of the server is started with Node Manager.	Online
Nmserverstatus	Return the status of the server is started with Node Manager.	Online
Nmstart	Start a server in the current domain using Node Manager.	Online
Nmversion	Return the Node Manager server version.	Online
Startnodemanager	Start Node Manager at default port (5556).	Online or Offline