Create a Node Manager Domain

Within each domain, you can configure the Node Manager. However, the most elegant approach is to create a custom domain and let the Node Manager manage all other domains. This page will guide you through the process.

Run the Configuration Wizard again.

---

Create Domain

Create a new domain and name it "NodeManager".

---

Templates

Do not select anything except for the default Basic WebLogic Server Domain.

---

Administrator Account

Select a username and password.

---

Domain Mode and JDK

Select Development mode.

---

Advance Configuration

Do not select anything.

---

Configuration Summary

Click Create to continue...

---

Configuration Progress

Click Next to continue...

---

End of Configuration

Click Finish to complete the configuration.

---

Domains

Edit this file to add our "replicated" domain to Node Manager:

$MW_HOME/user_projects/domains/nodemanager/nodemanager/nodemanager.domains

---

Properties File

Node Managed can be configured through a properties file located at:

Change the Listen Address

Change the listen address from 'localhost' to a reachable IP address. Why not listen on all addresses?

ListenAddress=0.0.0.0

Disable Start Script

In WebLogic 12.1.1 (and higher), the nodemanager has been modified to use the "startWebLogic.sh" script to launch WebLogic. I prefer the old technique because it allows creating custom startup parameters for each server.

weblogic.StartScriptEnabled=false

Disable the Secure Listener

Temporarily disable the secure listener for testing. We will re-enable it later when securing WebLogic.

Enable Crash Recovery

Should WebLogic crash, we want Node Manager to restart it.

Starting Node Manager

You can start Node Manager by hand using this command...

Admin Console

Now we need to make some configuration changes to the domain. The best way to do this is from the Admin Console.

Modify Servers

By default, the Replicated Domain Template creates a cluster with one admin server (AdminServer) and two engine-tier servers (engine1 and engine2).

Let's modify these servers and add a new one.

The quickest way to do this is to delete engine2 and recreate it by cloning engine1.

Let's also create an engine0 server by cloning engine1 as well. We will run engine0 on the same server as the AdminServer for testing purposes.

Now that we have 3 identical servers, change the Listen Address to the IP address that each server will use.

In the configuration settings for the engine servers, add these values:

Sever Start

Class Path

How did we arrive at this value? If you start the managed server by hand, the system out screen will reveal it.

User Name

Password

Create Machines

In the WebLogic Admin Console, create 'machines' to logically represent each physical server (VM or bare-metal). Assign the "Node Manager Listen Address". This will be the IP Address that the Admin Console will use to contact the node manager.

Navigate to the machine / Configuration / Node Manager.

Set the Type to Plain. (We will add security later.)

Set the Listen Address to the IP Address of the server it is running on. (It can't be "0.0.0.0".)

Do that for all the machines.

---

Copy Files

If you're not using a shared filesystem (typical), this is the time to copy our installation of OCCAS to the managed nodes.

Zip up the 'occas' directory, and copy it to each managed node and unzip it in the exact same location.

This will allow us to start OCCAS on each server.

We still have more configuration changes to make, but OCCAS will pull down a new configuration on restart.

---

Congratulations! You are now ready to move on to Startup Scripts.