3 Node Manager Tutorial

The Node Manager tutorial provides a basic example of using the default per domain Node Manager. It provides the steps to create and use Java-based Node Manager to start and stop Oracle WebLogic Server instances in a single-machine domain that hosts both an Administration Server and a Managed Server.

See Default Node Manager Configuration.

Create Node Manager in a New Domain

Use the Fusion Middleware Configuration Wizard to create and configure Node Manager in a new domain.

To create an instance of per domain, Java-based Node Manager in a new domain, complete the following steps:

  1. Start the Configuration Wizard:

    1. From a command window, change to the ORACLE_HOME/oracle_common/common/bin directory, where ORACLE_HOME represents the directory you specified as the Oracle Home when you installed WebLogic Server.

    2. Execute the config.cmd command for Windows or the config.sh command for UNIX.

  2. Use the Configuration Wizard to create a new, basic domain:

    1. On the Create Domain screen, select Create a new domain and select a domain directory location. This is your DOMAIN_HOME directory. Click Next.

    2. On the Templates screen, accept the default Create Domain Using Product Templates. Click Next.

    3. On the Administrator Account screen, enter the credentials of the WebLogic Server administrator. Click Next.

    4. On the Domain Mode and JDK screen, accept the default Domain Mode and JDK. Click Next.

  3. Create a Node Manager instance, a Managed Server, and a machine in your domain:

    1. On the Advanced Configuration screen, select Node Manager and Topology options. Click Next.

    2. On the Node Manager screen, accept Per Domain Default Location as the default Node Manager type and enter the credentials of the Node Manager administrator. Click Next.

    3. On the Managed Servers screen, click Add. Accept the default server name, listen address, and listen port (7003). Click Next.

    4. On the Clusters screen, click Next.

    5. On the Machines screen, click Add. Accept the default machine name, Node Manager listen address, and Node Manager listen port. Click Next.

  4. Assign the Administration Server and Managed Server to your machine:

    1. On the Assign Servers to Machines screen, select your Administration Server and Managed Server in the left column.

    2. Use the right arrow button to assign the Administration Server and Managed Server to your machine in the right column.

    3. Click Next.

  5. Complete your domain configuration:

    1. On the Configuration Summary screen, review your configuration and click Create.

    2. When the Configuration Process screen shows that your domain has been created successfully, click Next.

    3. On the Configuration Success screen, select Start Admin Server to start your domain. Click Finish.

Start Node Manager

To start Node Manager in a WebLogic domain environment, use the startNodeManager.cmd command for Windows and the startNodeManager.sh command for UNIX.

To start Node Manager in your domain, complete the following steps:

  1. From a command window, change to the DOMAIN_HOME/bin directory, where DOMAIN_HOME represents the directory in which your WebLogic Server domain is configured.
  2. To set your environment, execute the setDomainEnv.cmd command for Windows or the setDomainEnv.sh command for UNIX.
  3. Return to the DOMAIN_HOME/bin directory.
  4. To start Node Manager in your domain, execute the startNodeManager.cmd command for Windows or the startNodeManager.sh command for UNIX.

    If Node Manager starts successfully, you will see output similar to the following:

    <DATE TIME> <INFO> <12.2.1.0.0>
    <DATE TIME> <INFO> <Secure socket listener started on port 5556, host localhost/127.0.01>

    Note:

    If Node Manager is started by any means other than the startNodeManager script, the use of the nmRestart WLST command to restart Node Manager is not supported. If Node Manager is started from a custom script, or by the java weblogic.NodeManager command, using the nmRestart command may subsequently fail.

Use Node Manager to Start a Managed Server

Use the WebLogic Server Administration Console to ensure that Node Manager is running and to start a Managed Server in your domain.

To start a Managed Server in your domain using Node Manager, complete the following steps:

  1. Start the WebLogic Server Administration Console:

    1. Ensure the Administration Server is running.

      If you selected the Start Admin Server option in the Configuration Wizard, the Administration Server should be running.

      If the Administration Server is not running, change to the DOMAIN_HOME/bin directory and execute the startWebLogic.cmd command for Windows or the startWebLogic.sh command for UNIX.

    2. Launch a Web browser and enter the following URL:

      http://hostname:port/console
      

      where hostname is the DNS name or IP address of the Administration Server and port is the listen port on which the Administration Server is listening for requests (port 7001 by default).

    3. When the login page appears, enter the user name and the password you entered when creating your domain in the Configuration Wizard.

  2. Ensure Node Manager is running.

    1. In the left pane of the WebLogic Server Administration Console, select Environment > Machines.

    2. In the Machines table, select the name of your machine.

    3. Select Monitoring > Node Manager Status.

    4. If Node Manager is running, Status will be Reachable.

    Note:

    To configure Node Manager settings in the WebLogic Server Administration Console, navigate to the following page: Environment > Machines > machine_name > Configuration > Node Manager.

  3. In the left pane of the WebLogic Server Administration Console, select Environment > Servers.

  4. Select the Control page.

  5. In the Servers table, select the checkbox next to your Managed Server.

  6. Click Start.

    A message appears confirming that Node Manager will start the selected server instance. Refresh the WebLogic Server Administration Console page, and the Managed Server state changes from SHUTDOWN to RUNNING.

    Your Managed Server is now running in your domain.