- 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.
The pathname to the directory in which WildFly has been installed.
|WildFly Admin Listen Address|
The url of the Manager web application within the WildFly server.
|WildFly Admin Listen Port|
The port number of the manager web application within the WildFly server.
|WildFly Admin User|
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|
The password for the WildFly Admin User.
WildFly Server name to activate application on.
|WildFly Server Group|
WildFly Server Group name to activate application on.
The name of the WildFly application.
The mode in which the server has been started. Valid values are Standalone, Domain.
This operation doesn't consume or produce any artifacts.
This operation will select all available endpoints associated to the environment instance which have a resource type of WildFly Management Server. For Standalone mode, this is the single endpoint which is mapped to the Environment/Instance. For Domain mode, this is the endpoint which hosts the Domain Controller.
This operation will execute on the endpoint selected above (the one which is identified as the WildFly Management Server).