Stops an IBM WebSphere Server.
This operation accepts server names both with and without a node name. If no node name is entered with the serer name, the server name must be unique within the cell, so the plugin can determine which node it's running on. NOTE: In a WAS Base environment, node name is not necessary, as there is only one node.
This operation performs slightly differently, depending on if you're using a Network Deploy environment, or a WAS Base environment.
- In a Network Deploy environment, the plugin will use the wsadmin tool to stop the servers.
- In a WAS Base environment, the plugin uses the stopServer script located in the same directory as the wsadmin script.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
WAS Install Root | FDWAS_WAS_INSTALL_ROOT | Y | The base installation directory for the WebSphere Application Server. For example: |
| WSAdmin User | FDWAS_WSADMIN_USER | N | The user to connect to wsadmin as |
| WSAdmin Password | FDWAS_WSADMIN_PASSWORD | N | The password for WSAdmin User |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Server Names |
| Y | A comma separated list of node-qualified server names to perform the operation on. (e.g. node01/server1, node02/server2) |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation doesn’t consume or produce any artifacts.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.