- Utility/process running on a physical server that enables you to start, stop, suspend, and restart WebLogic server instances remotely.
- Server instances in a WebLogic Server and production environment are often distributed across multiple domains, machines and geographical locations. So if you want to control them remotely we need to use node manager.
- Although Node Manager is optional, it is recommended that if your WebLogic Server environment hosts applications with high-availability requirements.
- Must run on each physical server that hosts WebLogic server instances that you want to control with the Node Manager
- Not associated with a domain. Can start any server instance that resides on the same physical server.
- Optional, but required to start/stop servers using the Administration console
- Required for Whole server Migration and for some configurations of Automatic service Migration.
Node Manager can be used to:
- Start, Shut down and Restart an Administration Server.
- Start, Shut down, Suspend and Restart and Managed Servers.
- Automatically Restart Administration and Managed Servers on failure.
- Monitor Servers and collects log data.
There are four types of Node Managers:
- SSL
- PLAIN
- SSH
- RSH
Java Based Node Manager
|
Script Based Node Manager
|
It is used in Windows, UNIX and Linux Operating Systems.
|
It is used only in UNIX/Linux Operating Systems and not supported in Windows OS
|
It is more secured.
|
It is less secured when compare to Java Based Node Manager.
|
Examples:
PLAIN
SSL
|
Examples:
SSH
RSH
|
How to start a Node Manager:
Navigate to the Following location:
WEBLOGIC_HOME\server\bin
0 comments:
Post a Comment