How to force Identity Manager ear files deployment with JBoss 6.x / Wildfly 8.x

Document ID : KB000045834
Last Modified Date : 14/02/2018
Show Technical Document Details




Attempting to start JBoss/Wildfly after it was stopped - however Identity Manager is unavailable.
We do not see any errors in server.log however neither management console or actual environment(s) are accessible.




-Identity Manager using JBoss 6.x EAP or Wildfly 8.2.x as its Application Server




-Previous partial / failed deployment stopping the application server from attempting to deploy




To trigger / force Identity Manager deployment, we need to:
1. Stop JBoss - verify via task manager (Windows) or ps -ef|grep java (linux) that JBoss has properly shut down
2. Navigate to <JBOSS_HOME>/standalone/deployments
3. create an empty file called iam_im.ear.dodeploy
4. create an empty file called castylesr5.1.1.ear.dodeploy
5. Start JBoss
We should expect Application Server to start now, with Identity Manager properly deployed.


Additional Information:  


Review <JBOSS_HOME>/standalone/deployments/Readme.txt for further information about file names in the deployment folder