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:
- Log in to the WebLogic server with administrative privileges.
- Modify the
installNodeMgrSvc.cmdfile so that it does not hard code the node manager hostname and port in the registry.- Browse to
<WebLogic_Server_Home>\server\bin. - Open
installNodeMgrSvc.cmdin a text editor. - Locate the following lines in the file:
set NODEMGR_HOST=localhostset NODEMGR_PORT=5556Note: If lines
set NODEMGR_HOST=localhostandset NODEMGR_PORT=5556do not exist, close the file and skip steps 2d and 2e. - Comment out the lines by adding @rem to the beginning of the lines. For example:
@rem set NODEMGR_HOST=localhost@rem set NODEMGR_PORT=5556 - Save the changes, and then close the file.
- Browse to
<WebLogic_domain_home>\bin. - Open
installNodeMgrSvc.cmdin a text editor. - Locate the following lines in the file:
set NODEMGR_HOST=localhostset NODEMGR_PORT=5556 - Comment out the lines by adding @rem to the beginning of the lines. For example:
@rem set NODEMGR_HOST=localhost@rem set NODEMGR_PORT=5556 - Save the changes, and then close the file.
- Browse to
- Open the command window, and then complete the following steps:
- Change the directory to
<WebLogic_domain_home>\bin. - Enter the following command:
installNodeMgrSvc.cmd
- Change the directory to
- Close the command window.
- Browse to Windows Services, and then start the Oracle WebLogic <domain_name> NodeManager service.