Install, Configure, and Run - Oracle WebLogic Server 12c Advanced Administration - page 9

How it works...
The unpack command will create the necessary files to host the WebLogic domain
PROD_DOMAIN on the prod02 machine based on the template created with the pack
command on prod01 .
An entry to the PROD_DOMAIN domain will automatically be added to the nodemanager.
properties file.
There's more...
We can also distribute the WebLogic domain files manually. In this section, we will see how
this can be achieved.
Distributing WebLogic domain files manually
You can simply copy the domain files manually too; just don't forget to edit the
nodemanager.domains file and add the domain entry.
As in the prior chapter and the rest of the topic, the $DOMAIN_HOME environment variable
points to the /oracle/Middleware/user_projects/domains/PROD_DOMAIN directory.
1. Log in as a wls user on the machine prod02 and copy the domain from prod01 :
[wls@prod02]$ mkdir -p $DOMAIN_HOME
[wls@prod02]$ scp -rp wls@prod01:$DOMAIN_HOME $DOMAIN_HOME/..
2. Edit the nodemanager.domains file:
[wls@prod01]$ vi $WL_HOME/common/nodemanager/nodemanager.domains
3. Add the following entry if it doesn't exist:
PROD_DOMAIN=/oracle/Middleware/user_projects/domains/PROD_DOMAIN/
See also
F Starting the Node Manager
Starting the Node Manager
The Node Manager is the WebLogic Server utility to control the lifecycle—start, stop, restart—of
the WebLogic Managed Server instances and the Administration Server.
In production environments, the Node Manager is needed to meet the high
availability requirements.
In this recipe, the system administrator will learn how to start and stop the Node Manager.