Identity Manager startup fails when JBoss autodeployment is disabled

book

Article ID: 191839

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction


When setting scan-enabled="false" in the standalone-full-ha.xml, Identity Manager will fail at startup.

Versions:
Red Hat 7.6
Identity Manager 14.2 (14.2.0.0.425)
JBoss 6.4.21

I have been testing this issue in my lab environment and will attach the server.log files from a successful startup and a failed startup after the scan-enabled value was changed to false.

Environment

Release : 14.2

Component : IdentityMinder(Identity Manager)

Versions:
Red Hat 7.6
Identity Manager 14.2 (14.2.0.0.425)
JBoss 6.4.21

Resolution

Symantec Identity Manager relies on an exploded EAR deployment model that utilizes the jBoss/WildfFly Deployment Scanner in automatic deployment mode (i.e. scan-enabled = true).
This is required due to Identity Manager application’s use of a large set of 3rd party components that have a complex load-order specific initialization scheme.
This initialization requires real-time time changes to the application’s deployment configuration that is detected at the time of installation of the application.
It is for this reason that automatic deployment cannot be turned off. (i.e. scan-enabled = false).