Article Content
Article Number | 000038362 |
Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x |
Issue | Running customizeACM.sh -d on a standalone server in RSA Identity Governance & Lifecycle fails with:
If you encounter this error installing an RSA Identity Governance & Lifecycle patch, please see related RSA Knowledge Base Article 000038350 -- Patch/upgrade fails with 'Error deploying the ear file' error in RSA Identity Governance & Lifecycle for resolution. |
Cause | The key error here is: {"Operation step-1" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"aveksa.ear\")]' not found"}} The aveksa.ear file cannot be found. The reason for this error is that the deployed aveksa ear file has a filename other than aveksa.ear. By default, the RSA Identity Governance & Lifecycle installation, patch/upgrade and customizeACM.sh processes automatically deploy the ear file with the name aveksa.ear and expect the name of the ear file to be aveksa.ear when they go to undeploy the ear. In cases where the ear file has been deployed manually, it is possible to deploy the ear file with a name other than aveksa.ear. In this case future patching, upgrading and customization of the ear file will fail. |
Resolution | Redeploy the current ear file as aveksa.ear and re-run customizeACM.sh.
You will see output similar to the following:
This is the reason for the failure. The name should be aveksa.ear.
Now the current ear file is deployed with the name aveksa.ear so customizeACM.sh will be able to find and undeploy the current ear file.
To avoid the problem in the future:If you are deploying the ear file manually and not through patching, upgrading or customizeACM.sh, ensure that the ear file is deployed as aveksa.ear by following the instructions in RSA Knowledge Base Article 000038351 -- How to manually deploy an aveksa ear file in RSA Identity Governance & Lifecycle. |
Notes |