Oracle by Example brandingConfigure and Use Node Manager

section 0Before You Begin

This tutorial shows you how to configure and use the Oracle WebLogic Server Java-based Node Manager. It also shows you how to create and configure machines, assign servers to machines, start Node Manager, and use it to start Managed Servers using the WebLogic Server Administration Console.

Background

This tutorial is part of the Oracle WebLogic Server 12c series, and assumes that you have completed these tutorials, in this order:

In production environments, Oracle WebLogic Server instances 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 the Administration Server and Managed Servers from a remote location. Although Node Manager is not required, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.

In a WebLogic Server domain, machines can be defined to represent physical computers that host one or more WebLogic Server instances. Machine definitions help WebLogic Server choose backup servers for session replication. Machine definitions also specify attributes required to connect to the Node Manager process running on the machine, as well as identify which WebLogic Server instances reside on the machine.

This tutorial covers creating and configuring machines, configuring and starting the Java-based Node Manager, and using it to control Oracle WebLogic Server Managed Servers.

What Do You Need?

  • An installation of Oracle WebLogic Server 12c. See http://www.oracle.com/technetwork/middleware/weblogic/downloads/index.html.
  • This tutorial uses an instance of WebLogic Server installed in /u01/app/fmw.
  • A properly configured WebLogic Server domain containing an Administration Server and three Managed Servers. This tutorial uses the domain, /u01/domains/ExampleDomain, with servers, server1, server2, and server3.

section 1Create Machines

To create machines in the domain:

  1. If the Administration Server of the domain is not already running, start it.
    • Open a terminal window and navigate to the domain directory:
      • $ cd /u01/domains/ExampleDomain
    • In the domain directory, enter:
      • $ ./startWebLogic.sh
    • At the prompt, enter the credentials of the domain administrator.
    • Examine the terminal output and wait for the Administration Server to reach the RUNNING state.
      • <Aug 27, 2018 9:57:34,722 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
      <Aug 27, 2018 9:57:34,817 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>
  2. After the Administration Server is running, access the WebLogic Server Administration Console.
    • Open a web browser and enter the URL:
      • http://localhost:7001/console
    • On the Welcome screen, enter the user name and password that you specified when you created the domain, and then click Login.
      • The home page of the Administration Console is displayed.
  3. In the left pane of the Console, under Domain Structure, expand Environment, and then select Machines.
    • On the Summary of Machines page, you can view all the machines defined in the domain.
    • To create machines, you must first lock the domain configuration (to prevent other accounts from making changes during your edit session) and enable an edit session.
  4. In the Change Center, click Lock & Edit.
  5. In the Machines table, click New to open the Create a New Machine wizard.
    • On the Machine Identity page, enter machine1 for the Name, select Other for the Machine OS, and then click Next.
      • In this tutorial, WebLogic Server is running on Linux. Although Linux is a UNIX-based operating system, you don’t need the UNIX-specific machine settings for this tutorial.
    • On the Node Manager Properties page, select Plain for the Node Manager Type, keep the default Listen Address and Listen Port, and then click Finish.
      • In this tutorial, localhost is the Listen Address, and 5556 is the Listen Port.
    • Click Finish.
    • The Console displays the message: Machine created successfully.
  6. Repeat step 5 to create machine2 with the same Node Manager settings.
  7. In the Change Center, click Activate Changes.
    • The Console displays the message: All changes have been activated. No restarts are necessary.
    • The Administration Console updates the domain configuration with the machine configuration data.

section 2Configure Machines

To configure machines:

  1. On the Summary of Machines page, select machine1.
    • The settings for machine1 are displayed.
    • To modify the settings for machine1, you must again lock the domain configuration and enable an edit session.
  2. In the Change Center, click Lock & Edit.
  3. Under Settings for machine1, select Configuration, and then Servers.
  4. In the Servers table, click Add.
  5. On the Add a Server to Machine page, ensure that Select an existing server, and associate it with this machine is selected.
  6. From the Select a server drop-down menu, select server1, and then click Finish.
    • The Console displays the following message: Server created successfully.
  7. Repeat steps 3, 4, 5, and 6, to assign server2 to machine1.
  8. Repeat the required steps to assign server3 to machine2.
  9. In the Change Center, click Activate Changes.
    • The Console displays the message: All changes have been activated. No restarts are necessary.
    • The Administration Console updates the domain configuration with the new machine configuration data.

section 3Start Node Manager

To start Node Manager:

  1. Run the Node Manager start script.
    • Open a terminal window and navigate to the bin directory under your domain directory. In this tutorial, the domain directory is: /u01/domains/ExampleDomain
    • Enter: startNodeManager.sh
      • $ cd /u01/domains/ExampleDomain/bin
$ ./startNodeManager.sh
  2. Wait for the following terminal output messages:
    3. <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>

section 4Verify the Node Manager Status

To verify the status of Node Manager:

  1. If necessary, log in to the Administration Console.
  2. Under Domain Structure, expand Environment, and then select Machines.
  3. In the Machines table, select machine1.
  4. Under Settings for machine1, select Monitoring, and then Node Manager Status.
    5. The Status field shows Reachable, which means that the Node Manager is currently running on the machine.

section 5Start Managed Servers

To start Managed Servers from the Console:

  1. If necessary, log in to the Administration Console.
  2. Under Domain Structure, expand Environment, and then select Servers.
  3. On the Summary of Servers page, select Control.
  4. In the Servers table, select the check box next to server1 and click Start.
  5. Click Yes in the confirmation dialog.
    • The Console displays the message: A request has been sent to the Node Manager to start the selected servers.
    • Click the refresh icon to periodically refresh the data in the Servers table.
    • After a few minutes, verify that the server State is RUNNING and the Status of Last Action is TASK COMPLETED.
  6. Repeat steps 4 and 5 to start server2.

more informationNext Steps

The WebLogic Server 12c collection contains a number of additional tutorials, covering a variety of topics. See the WebLogic Server 12c collection here for additional topics and content.