Prerequisites - JBoss EAP 7.x (ExpertCTStudio)

Few functions that you should be aware before doing this deployment procedure are as follows:

 example.war.dodeploy - This file is placed by the user to indicate that the given content (example.war) should be deployed into the runtime or it can also be used to redeploy if the content is already deployed in the runtime.

 example.war.skipdeploy - This file is placed by the user to disable auto-deploy of the content for as long as the file is present. Most useful for allowing updates to exploded content without having the scanner initiate redeploy in the middle of the update. It can be used with zipped content as well, although the scanner will detect in-progress changes to zipped content and wait until changes are complete.

 example.war.isdeploying - Placed by the deployment scanner service to indicate that it has noticed a .dodeploy file or new or updated auto-deploy mode content and is in the process of deploying the content. This marker file will be deleted when the deployment process completes.

 example.war.deployed - Placed by the deployment scanner service to indicate that the given content has been deployed into the runtime. If an end user deletes this file, the content will be undeployed.

 example.war.failed - Placed by the deployment scanner service to indicate that the given content failed to deploy into the runtime. The content of the file will include some information about the cause of the failure. Note that with auto-deploy mode, removing this file will make the deployment eligible for deployment again.

 example.war.isundeploying - Placed by the deployment scanner service to indicate that it has noticed a .deployed file has been deleted and the content is being undeployed. This marker file will be deleted when the undeployment process completes.

 example.war.undeployed - Placed by the deployment scanner service to indicate that the given content has been undeployed from the runtime. If an end user deletes this file, it has no impact.

 example.war.pending - Placed by the deployment scanner service to indicate that it has noticed the need to deploy content but has not yet instructed the server to deploy it. This file is created if the scanner detects that some auto-deploy content is still in the process of being copied or if there is some problem that prevents auto-deployment. The scanner will not instruct the server to deploy or undeploy any content (not just the directly affected content) as long as this condition holds.

The following table gives the prerequisite information that has to be complied before deploying the Canvas technology.

Refer the following page: