Stops the Node Manager process. This operation can be used to stop Node Manager on all hosts in your WebLogic domain.You can control which plugin operation execution by selecting endpoint specification on Workflow, which should allow you to stop Node Manager on all hosts in your WebLogic domain.
If node manager is not installed in default location, then you need to specify FDWLS_INP_NODEMANAGER_HOME. Node Manager home (location of NodeManager.properties file) is different for 11g and 12c environments, plugin will derive default location based on WebLogic version and whether it is Node or Domain based node manager setup.
If your entire domain is on shared folder, then you will have defined custom Node Manager home folder, in which case you must specify FDWLS_INP_NODEMANAGER_HOME input.
| Note |
|---|
If you are using Enterprise Deployment for 12c installation, you will need node manager for aserver folder structure as well, which is different than mserver folder even if AdminServer and some of the Managed Servers are running on same host. |
Blog Posts
Environment/Instance Properties
...
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| NodeManager Home |
| No | Node Manager home folder location. If blank, the default host-based or domain-based location is derived automatically. |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation doesn't consume or produce any artifacts.
...