|Applies To||RSA Product Set: RSA Identity Governance and Lifecycle|
RSA Version/Condition: 7.0
|Issue||Previous versions of RSA Identify Management and Governance, that is versions 6.9.1 and earlier, included instructions for adding library files to the deployed instance of the acm application in order to integrate custom plugins and Customized Web Service command handlers. Older custom applications delivered by RSA Professional Services also may include documentation that makes references to this procedure. |
Command handlers are written using the RSA IMG plug-in architecture where the classes are packaged as a jar along with an aveksa-plug-ins.xml file. The package must be placed in a directory under aveksa.ear/aveksa.war/WEB-INF/plugins. A generic plugin manager parses any aveksa-plug-ins.xml found under this directory and the associated plugin class is created and started.
RSA Via Lifecycle and Governance 7.0 uses the WildFly application server instead of Tomcat and the location of the deployed aveksa.ear and aveksa.war files has changed in this version. The files are no longer located in the directory /home/oracle/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/plug-ins/.
|Resolution||Modifying the deployed aveksa.war file directly is no longer supported in RSA Via Lifecycle and Governance 7.0 . The deployed aveksa.ear and aveksa.war file are typically located in dynamic directory similar but not identical to the following path.|
If changes are made to the file structure in this deployed directory these changes may be lost during subsequent server restarts or when applying patches.
The recommended procedure for updating the aveksa.war file is to use the documented tool customizeACM.sh. The documentation for using this tool is located in the RSA Via Lifecycle and Governance
Installation Guide V7.0, starting on page 147 in the section "Customize RSA Via L&G."