Technical data

3 Node Manager
3-8 Administration Guide
In this example, ca.pem is the WebLogic certificate authority file and is identical in
content to the default trustedCerts file,
trusted.crt, and democert.pem is the public
key file. The file
demokey_new is the result of running wlkeytool on demokey.pem,
as described in Step 2: Converting a WebLogic-Style Private Key.
For more information about digital certificates and Secure Sockets Layer, see
Managing Security.
Setting Up the Administration Server to Use Node
Manager
To configure the Administration Server to use Node Manager to start and stop
WebLogic Managed Servers, there are several steps you need to carry out. You can
accomplish these tasks using the WebLogic Administration Console.
Step 1: Create a Configuration Entry for the Machine
You need to create an entry in the domain configuration for each machine on which
you have installed Managed Servers. To do this, do the following:
1. With the Administration Server running, invoke the Administration Console (if it
isn’t already running).
2. Select Machines in the left pane to display the machines table.
3. Select the Create a new Machine link (or Create a new UNIX Machine) at the top
of the table.
4. Fill in the information for the machine and click Apply to create the new machine
entry.
Step 2: Configure Node Manager on Each Machine
For each machine where you want to use Node Manager, modify the configuration
entry for that machine accordingly:
1. In the Administration Console, select Machines
→machine_name→Node
Manager, where machine_name is the name of the machine on which the Node
Manager is to run.