stopServer (WebSphere)
- Ben Hoffman
- Dan Reynebeau
Stops one or multiple IBM WebSphere Servers.
Due to limitations in the WSAdmin tool, server names must be node-qualified to start. This means that server names must be formatted as "Node-Name/Server-Name".
This operation is executed in a different manner depending upon the WebSphere installation.
- In a Network Deploy environment, the plugin will use the WSAdmin tool to start the servers.
- In a WAS Base environment, the plugin uses the startServer script located in the same directory as the WSAdmin script (WebSphere Install Root/bin).
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
WebSphere 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.
Endpoint Execution
This operation will execute on any endpoint selected.
- style