In previous releases of WebLogic, a node manager process was not associated with a specific WebLogic domain but with a host machine. You used the same node manager process to control server instances in any WebLogic domain as long as the server instances resided on the same machine, a machine-scoped, per host node manager. In this release of WebLogic Server, the node manager is now configured individually, per domain, and each domain will contain a unique node manager process.
To install the node manager as a Windows service:
installNodeMgrSvc.cmd
file so that it does not hard code the node manager hostname and port in the registry.<WebLogic_Server_Home>\server\bin
.installNodeMgrSvc.cmd
in a text editor.
set NODEMGR_HOST=localhost
set NODEMGR_PORT=5556
Note: If lines set NODEMGR_HOST=localhost
and set NODEMGR_PORT=5556
do not exist, close the file and skip steps 2d and 2e.
@rem set NODEMGR_HOST=localhost
@rem set NODEMGR_PORT=5556
<WebLogic_domain_home>\bin
.installNodeMgrSvc.cmd
in a text editor.
set NODEMGR_HOST=localhost
set NODEMGR_PORT=5556
@rem set NODEMGR_HOST=localhost
@rem set NODEMGR_PORT=5556
<WebLogic_domain_home>\bin.
installNodeMgrSvc.cmd
Using the WebLogic Scripting Tool on Windows
Starting an Administration and Managed Servers Using WLST With Node Manager
Adding the start_primavera.bat to the Windows Task Scheduler
Executing the start_primavera.bat file
Using WebLogic Scripting to Stop the WebLogic Domain for P6 EPPM
Legal Notices
Copyright © 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Monday, October 24, 2016