This tutorial shows you how to configure and use a java-based Node Manager Oracle WebLogic Server. It also shows you how to create and configure the machine, the distribution server, start the Node Manager to the machine, and how to use WebLogic Server Administration Console use it to start the managed server.
In a production environment, Oracle WebLogic Server instance typically distributed across a plurality of domains, and the machine location. Node Manager is a WebLogic Server utility that allows you to boot from a remote location, shut down and restart the management server and managed server. Although Node Manager is not required, but if your WebLogic application server environment carries a high availability requirements, it is recommended to use Node Manager.
In WebLogic Server domain, it can be defined to represent the physical machine hosting one or more computer servers WebLogic instances. WebLogic server copy machine definition help select the backup server for the session. Definition also specifies the machine required to connect to the Node Manager process to run on the machine attributes, and identifying the WebLogic Server instances reside on the machine.
This tutorial covers creating and configuring the machine, configure and start a java-based Node Manager, server and use it to control the Oracle WebLogic Server hosted.
First, create a machine
Creating a machine in the domain, the following steps:
1, if the domain management server is not already running, start it, that started startWebLogic.exe.
2, after the management server is running, access the WebLogic Server Administration Console.
3. In the left pane of the console, expand Environment in the domain structure, and then select Machines.
4, in the "Change Center", click "Lock and edit."
5, in the "machine" table, click "New" to open the "Create a New Machine" wizard.
On the Machine Identity page, enter the name machine1, select Other as a machine operating system, and then click Next.
On the Node Manager property page, select the node manager type Plain, keep the default listen address and listen port, and then click Finish.
Click Finish.
The console displays the message: machine is created successfully.
6. Repeat step 5, using the same set Node Manager creates machine2.
7, in the "Change Center", click "Activate Changes."
Second, the configuration of the machine
Machine configuration, the following steps:
1, in the "machine" page, select machine1.
2, in the "Change Center", click "Lock and edit."
3, in setting machine1 select Configuration, and then select Servers.
4, in the Servers table, click Add.
5, "add the server to the machine" page, be sure to select an existing server, and associate it with this machine.
6. Select server1 from the "Select Server" drop-down menu, then click "Finish."
7. Repeat steps 4, 5 and 6, will be assigned to server2 machine1.
8, the required steps are repeated, to assign the server3 machine2.
9, in the "Change Center", click "Activate Changes."
Third, start Node Manager
Node Manager starts, the following steps:
1, run the Node Manager startup script.
startNodeManager.cmd navigate to the bin directory under the domain directory
2, the output message is as follows:
<Aug 27, 2018 9:57:34,722 AM EDT> <INFO> <Server Implementation Class: weblogic.nodemanager.server.NMServer$ClassicServer.>
<Aug 27, 2018 9:57:34,817 AM EDT> <INFO> <Secure socket listener started on port 5556, host localhost/127.0.0.1>
Fourth, the state verification manager node
1, if necessary, log on to the management console.
2, expand the "environment" in the "Domain Structure", then select the "machine."
3, in the Machines table, select machine1.
4, at machine1 settings, select Monitoring, and then select the Node Manager Status.
5, Status field displays reachable, is currently running on the machine which means Node Manager.
Fifth, start the managed server
1, if necessary, log on to the management console.
2, expand the "environment" in the "Domain Structure", then select the "server."
3, Summary Servers page, select Control.
4, in the Servers table, select the check box next to server1, and then click Start.
5. Click Yes in the confirmation dialog box.
6. Repeat steps 4 and 5 to start server2.