This operation signals an existing application to make itself unavailable, but leave it deployed. Any request that comes in while an application is unavailable will see an HTTP 404 error.
The deactivateApplication operation can be used in both Standalone and Domain mode.
For Domain mode, this operation can be applied to a WildFly server or server group.
This operation is supported for WildFly versions 8, 9 and 10.
Target Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
WildFly Home |
| Yes | The pathname to the directory in which WildFly has been installed. |
WildFly Admin Listen Address |
| Yes | The url of the Manager web application within the WildFly server. |
WildFly Admin Listen Port |
| Yes | The port number of the manager web application within the WildFly server. |
WildFly Admin User |
| Yes | The name of the WildFly user with which to connect to the Manager web application. This user must be configured with the add-user script file. |
WildFly Admin Password |
| Yes | The password for the WildFly Admin User. |
Project Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
WildFly Server |
| No | WildFly Server name to activate application on. |
WildFly Server Group |
| No | WildFly Server Group name to activate application on. |
WildFly Application |
| Yes | The name of the WildFly application. |
Inputs
Input Name | Input Code | Required | Description |
---|---|---|---|
WildFly Mode |
| Yes | The mode in which the server has been started. Valid values are Standalone, Domain. |
Outputs
...
Output Name
...
Required
...
Description
...
Artifacts
This operation doesn't consume or produce any artifacts.
...