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
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.
|Oracle Weblogic Home (WL_HOME)|
WebLogic Home Directory. (e.g. /u01/oracle/products/fmw/wlserver)
|Weblogic Admin Domain Directory|
WebLogic Domain Directory for AdminServer. Used when the admin server runs from a different domain folder than managed servers
|Weblogic Domain Directory|
WebLogic Domain Directory for managed servers.
|Weblogic Domain Name|
WebLogic Domain Name.
|Weblogic Node Manager User|
The user id for the WLS Node Manager.
|Weblogic Node Manager Password|
The password for
|Oracle Middleware Home (MW_HOME)|
The oracle middleware home (which has subfolders such as oracle_common, wlsserver_10.3, coherence*, etc.).
Node Manager home folder location. If blank, the default host-based or domain-based location is derived automatically.
This operation doesn't consume or produce any artifacts.
This operation delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the environment instance. Selecting a specific resource will result in selection of endpoints associated to the environment instance which have that resource defined.
This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where previous step may have executed. Changing this value to "All" to will result in execution on all selected endpoints.