Oracle WebLogic Server 12c:node Manager configuration and use

In a production environment, WebLogic server instances are often deployed separately across multiple administrative domains (domains), physical hosts (machines), or geographies (geographic locations). Node Manager is a tool for remotely starting, stopping, or restarting Management servers and managed servers. Although it is not required, it is recommended if your application in your WebLogic server has a high availability requirement.

The Node manager process is not associated with a specific WebLogic management domain and is associated with only a specific physical host. The same node manager process can be used to control server instances on multiple WebLogic management domains as long as they are on the same physical host as the node manager process.

This guidance includes configuring and starting Java-based node Manager and using it to control Oracle WebLogic Server (12.1.1) managed servers.

At the beginning of this guide preschool, you should have completed:

Oracle WebLogic Server 12c:installing WebLogic server and Creating a Domain,

Oracle WebLogic Server 12c:configuring Managed Servers,

Oracle WebLogic Server 12c:creating and configuring machines.

View the configuration of the current physical host

Check the configuration of the physical host by following these steps:

1.	If the Management server in the admin domain does not start, you must first start it. Enter the admin domain directory through the terminal window and type the following command: $ ./startweblogic.sh When you are prompted for a user name and password, enter the administrator credentials for the admin domain.
2.	After the Management Server starts, go to the WebLogic Server Management console. Open your browser and enter the following address: HTTP/hostname:Port/console The address in this study is: http://host01.example.com:8001/console Note: Use the host name of your host. Also, if you are using a different Management Server port, use this port. On the Welcome screen, log in with the user name and password of the Management server.
3.	If there are managed servers (dizzy1, Dizzy2, Dizzy3) running, close them.
4.	Check the configuration of the physical host that was created in the guided Oracle WebLogic Server 12c:creating and configuring machines . In domain structure, expand Environment (by clicking the + next to it). Click Machines
5.	In machines , click dizzyMachine1.
6.	In Configure DizzyMachine1, click the Configuration tab and the Node Manager Sub-tab.
	You can now see the configuration of the node manager for this physical host. Type is set to plain (indicates that Java-based node Manager is not using SSL), Listen Address is set to host01.example.com , Listen Port is set to Span class= "Obe_code_element" >5556 .
8.	Check the dizzyMachine2 corresponding Node Manager's configuration. Under Domain structure environment click Machines. In the Machines table, click dizzyMachine2. In Configure DizzyMachine2, click the Configuration tab and the Node Manager Sub-tab. At this point, you can see the configuration of the node manager corresponding to this physical host. It has the same configuration as Node Manager for DizzyMachine2 , except that the Listen Address is set to Host02.example.com ,Listen Port is set to 5557.

Configure node Manager
In order to create a new Node Manager directory on the physical host and configure it, perform the following steps:

1.	Open a new terminal on the host01 and go to the installation directory <MIDDLEWARE_HOME>. In this study, /u01/app/oracle/middlewareis the guide.
2.	Create a new catalog <middleware_home>/user_projects/nodemanager/dizzymachine1.
3.	Copy the following files to the dizzyMachine1 directory:<middleware_home>/wlserver_12.1/server/bin/startnodemanager.sh
4.	Edit the file <middleware_home>/user_projects/nodemanager/dizzymachine1/startnodemanager.sh.
5.	Set the nodemgr_home variable to the current path. In this study, <middleware_home>/user_projects/nodemanager/dizzymachine1is the guide. and then save.
6.	Create a new file <middleware_home>/user_projects/nodemanager/dizzymachine1/nodemanager.properties and edit it.
7.	Add the following three lines to the new file: Listenaddress=host01.example.com listenport=5556 Securelistener=false and then save.
8.	Access a second physical host host02. Set the node Manageron DizzyMachine2: Create a new directory <middleware_home>/user_projects/nodemanager/dizzymachine2, and startnodemanager.sh Copied to this directory. Set nodemgr_home to the current path in this script. In this study, <middleware_home>/user_projects/nodemanager/dizzymachine2 is the guide . Save the file. Create again nodemanager.properties file, enter the following listen address and port number for DizzyMachine2 : Listenaddress=host02.example.com listenport=5557 Securelistener=false Save the file.

To enroll computers in an administrative domain

After registering the computer with the Admin domain, Node Manager on this computer can accept requests from the admin domain and perform the following steps:

1.	Access host01. Open the Terminal window to enter <middleware_home>/wlserver_12.1/server/bin. Run the script setwlsenv.sh Set the environment required for WLST: $ Source setwlsenv.sh
2.	Open Wlst in interactive mode by entering the following command in the terminal window: (Translator Note: You can also perform wlst.sh entry) Java WebLogic. WLST
3.	In the Wlst prompt box, enter the following command to connect to the running Management Server: wls:/offline> Connect (' <USERNAME> ', ' <PASSWORD> ', ' t3://<admin_host>:<admin_port> ') Replace the sample variable with a parameter that matches your environment, as follows: wls:/offline> Connect (' WebLogic ', ' Welcome1 ', ' t3://host01.example.com:8001 ')
4.	Run the nmenroll () command. This command enlists the computer that is running WLST to the administrative domain where the Management server to which the Wlst is connected is located. The so-called "registration" is the download of two files from the Management Server to this computer:nm_password.properties and SerializedSystemIni.dat. Node Manager's "Encrypted files"nm_password.properties contains encrypted user names and passwords that the Management Server uses to authenticate itself to the node manager process. This file is in the admin domain directory /config/nodemanager/. The files that are used to encrypt and decrypt SerializedSystemIni.dat are placed in the Admin domain directory/security/ . In addition, thenmenroll () command creates or updates the nodemanager.domains file in the Node Manager home directory. It adds the current admin domain to the list of admin domains that Node Manager allows to manage. The nmenroll () command consists of two parameters: The admin domain home directory on this computer The Node Manager home directory on this computer The command in this guide should be: Nmenroll ('/u01/app/oracle/middleware/user_projects/domains/dizzyworld ', '/u01/app/oracle/middleware/user_projects/nodemanager/dizzymachine1 ') Note : The admin domain path and the Node Manager path are set correctly.
5.	Enter the following command in the prompt window to exit Wlst: exit ()
6.	To access host02, run nmenroll () in the dizzyMachine2 corresponding Node Manager home directory to repeat the above steps: Nmenroll ('/u01/app/oracle/middleware/user_projects/domains/dizzyworld ', '/u01/app/oracle/middleware/user_projects/nodemanager/dizzymachine2 ')

Start Node Manager

Perform the following steps to start node Manager:

1.	Enter <middleware_home>/user_projects/nodemanager/dizzymachine1 in the host01 and enter: ./startnodemanager.sh Note that the corresponding node manager for DizzyMachine1 has started.
2.	Enter <middleware_home>/user_projects/nodemanager/dizzymachine2 in the host02 and enter: ./startnodemanager.sh

To start a managed server by using Node Manager and the management console
Perform the following steps to start a managed server from the management console:

1. /th>	To access the WebLogic Server Management console again. In domain structure, expand Environment and click Servers :
.	Click the Control tab.
		5.	Click the Refresh icon to periodically refresh the server table.

Summary

In this tutorial, what do learned to:

• Configure Node Manager Communication settings in a domain
• Configure and start a Node Manager
• Enroll a domain with a Node Manager
• Start servers with Node Manager

Resources

• For documentation on Oracle WebLogic Server,visit the documentation Library.
• For more information in configuring machines, see the Create and configure machines sections of the administration Console Online Help.
• For more information on configuring and using Node Manager, see the Node Manager Administrator's Guide.
• To learn more on Oracle WebLogic Server, refer to additional OBEs in the OLL website.

Credits

• Author: TJ Palazzolo
• Contributor: Bill Bell

Translator Note:

about how to configure WebLogic's node manager,oracle WebLogic The library is not very detailed and has never found a very complete document on the Web. Today accidentally found an article about 12c, feel good, translated a bit for everyone to reference the study.

Original address

Http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/12c/10-NodeMgr--4472/nodemgr.htm

Oracle WebLogic Server 12c:node Manager configuration and use