Starts the Node Manager process. This operation can be used to start 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 start Node Manager on all hosts in your WebLogic domain.
...
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 |
---|---|---|---|
Oracle Weblogic Home (WL_HOME) |
| Yes | WebLogic Home Directory. (e.g. /u01/oracle/products/fmw/wlserver) |
Weblogic Admin Domain Directory |
| No | WebLogic Domain Directory for AdminServer. Used when the admin server runs from a different domain folder than managed servers |
Weblogic Domain Directory |
| Yes | WebLogic Domain Directory for managed servers. |
Weblogic Domain Name |
| Yes | WebLogic Domain Name. |
Weblogic Node Manager User |
| Yes | The user id for the WLS Node Manager. |
Weblogic Node Manager Password |
| Yes | The password for |
Oracle Middleware Home (MW_HOME) |
| Yes | The oracle middleware home (which has subfolders such as oracle_common, wlsserver_10.3, coherence*, etc.). |
Project 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.
...