10.7. Control the order of Deployed Applications on JBoss EAP 6

Procedure 10.16. Control the order of deployment in EAP 6.0

1. Create CLI scripts that will deploy and undeploy the applications in sequential order when the server is started/stopped.
2. CLI also supports the concept of batch mode which allows you to group commands and operations and execute them together as an atomic unit. If at least one of the commands or operations fails, all the other successfully executed commands and operations in the batch are rolled back.

Procedure 10.17. Control the order of deployment in EAP 6.1 and later

1. Create (if it doesn't exist) a jboss-all.xml file in the app.ear/META-INF folder, where app.ear is the application archive that depends on another application archive to be deployed before it is.
2. Make a jboss-deployment-dependencies entry in this file as shown below. Note that in the listing below, framework.ear is the dependency application archive that should be deployed before app.ear application archive is.

   <jboss umlns="urn:jboss:1.0">
     <jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0">
       <dependency name="framework.ear" />
     </jboss-deployment-dependencies>
   </jboss>

   Copy to Clipboard Toggle word wrap

   Note

   You can use the deployment's runtime name as the dependency name in the jboss-all.xml file.

   Important

   Although the jboss-all.xml file allows you to declare dependencies that the server does not otherwise detect, it is not a strict ordering feature. JBoss EAP assumes that all dependencies specified in the jboss-all.xml file have already been deployed or are available. If there are missing dependencies, JBoss EAP does not automatically deploy them, and the deployment fails.