Place
the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: Because this action loads all screenshots simultaneously, response
time may be slow depending on your Internet connection.)
Note: Alternatively, you can place the cursor
over each individual icon in the following steps to load and view only the screenshot
associated with that step.
The screenshots will not reflect the specific environment that
you are using. They are provided to give you an idea of where to locate specific
functionality in Oracle WebLogic Server.
Overview
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.
The Dizzyworld system architects have decided that it is beneficial to
have the option of remotely starting Managed Servers. They decide to configure
the Node Manager for the dizzyMachine2 that will allow them to start dizzy2
and dizzy3 running on dizzyMachine2.
With the WLST tool, you can monitor servers from the command
line. Also, from the command line, you can shut down the server, change server
attributes, and configure a domain. To configure using the WLST tool, perform
the following steps:
1.
In a new terminal window, add the path to the JRockit
to the environment variable PATH.
2.
Browse to /u01/app/oracle/product/Middleware/wlserver_10.3/server/bin
and run the setWLSEnv.sh script.
3.
Start the WLST by entering the command java
weblogic.WLST.
Note: WLST is case-sensitive
4.
Notice that the WLST prompt appears. Next, connect to the server by entering
the command connect ('admin','welcome1','t3://localhost:7001')
5.
Notice that the connection is successfully established to the AdminServer.
After you are connected, enter the following command with the syntax nmEnroll
([domainDir], [nmHome]).
6.
In a new terminal window, browse to /u01/app/oracle/product/Middleware/wlserver_10.3/server/bin
and run ./setWLSEnv.sh
to set the environment values. You can copy the CLASSPATH from the output.
7.
From Change Center, click Lock & Edit.
8.
In the Environment section, click Servers. Next, click dizzy1
and click the Configuration tab and then the Server Start
tab. In the Class Path section, enter or paste from clipboard the CLASSPATH
that you copied earlier.
9.
Click Save. Notice the message: Settings updated successfully.
10.
Browse to the /u01/app/oracle/product/Middleware/user_projects/domains/dizzyworld/bin
location and you can start dizzy1 by using the following command: ./startManagedWebLogic.sh dizzy1
http://localhost:7001
11.
After the Managed Server starts, you can check the status of dizzy1 from
the Admin Console. Repeat steps 8 through 10 for the Managed Servers dizzy2 and
dizzy3. From Change Center, click Activate Changes.
12.
Notice the message: All changes have been activated. No restarts are
necessary.
13.
In the "Summary of Servers" section, click dizzy2.
14.
In the "Settings for dizzy2" section, click the Control
tab and then the Start/Stop tab.
15.
Select the dizzy2 check box and then select Shutdown > Force Shutdown
Now.
16.
In the "Server Life Cycle Assistant" section, click Yes.
17.
Notice the message: A request has been sent to immediately shut down
the selected servers.
Note: Repeat steps 13 through 17 for dizzy1 and dizzy3.
To start the Node Managers, perform the following steps:
1.
Browse to /u01/app/oracle/product/Middleware/wlserver_10.3/common/nodemanager
and browse the contents for the nodemanager.domains
file.
Note: In this setup, the keystore is by default
set to Demo Identity and Demo Trust.
2.
Browse to /u01/app/oracle/product/Middleware/wlserver_10.3/server/bin and enter ./startNodeManager.sh
127.0.0.1 5555. Notice that the Node Manager starts for dizzyMachine1.
3.
Browse to /u01/app/oracle/product/Middleware/wlserver_10.3/server/bin and enter ./startNodeManager.sh
127.0.0.1 5556. Notice that the Node Manager starts for dizzyMachine2.
Starting Managed Servers by Using the Node
Manager
To start the Managed Servers, perform the following steps:
1.
In Oracle WebLogic Server Console, in the "Domain Structure"
section, click Servers.
2.
Click dizzy1.
3.
In the "Settings for dizzy1" section, click the Control
tab and then the Server Start tab.
4.
Select the dizzy1 server check box and click Start.
5.
In the "Server Life Cycle Assistant" section, click Yes.
8.
Notice the message: A request has been sent to the Node Manager to
start the selected servers. Next, perform step 1 through 5 for dizzy2
and dizzy3. Next, in the "Summary of Servers" section, you can view
the state of all the Managed Servers.
Bookmark
Place
the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: Because this action loads all screenshots simultaneously, response
time may be slow depending on your Internet connection.)
