000033885 - How to add content to the RSA Identity Governance & Lifecycle 7.x application

Document created by RSA Customer Support Employee on Sep 19, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000033885
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0
IssueThe method for adding content to the RSA Identity Governance & Lifecycle application in 7.x changed to accommodate redeployment of the application when the server starts.  The following guide will illustrate how to add content in 7.x.
TasksSince the aveksa.ear file is redeployed each time the server starts, the ear file must be modified for changes to persist. A script is provided to facilitate this process, customizeACM.sh. We will be performing the following tasks:
  1. Inspect archive for latest ear file.
  2. Explode latest ear file.
  3. Make modifications in exploded ear file hierarchy.
  4. Repackage exploded ear file hierarchy, save backups and deploy.
Resolution
  1. First, inspect /home/oracle/archive, note the latest backup. This will reflect the latest changes that were made. This location contains an archive of each time the ear file is modified and repackaged. You could also choose to revert to a previous modification by using one of the earlier files as well.  Each is saved with a date.
  2. Using /home/oracle/deploy/customizeACM.sh, explode the ear file noted in step 1 using the following command format:
    cd /home/oracle/deploy/
    ./customizeACM.sh -c ../archive/<FILENAME TO MODIFY>

    This will explode the ear file to the /tmp/customizeACM directory.
  3. Modify the contents of /tmp/customizeACM to add your content (images, drivers, etc.).
  4. Using /home/oracle/deploy/customizeACM.sh, repackage the ear file using the following command format:
    cd /home/oracle/deploy/
    ./customizeACM.sh -d

    This will repackage the ear file, archive the change by date in the /home/oracle/archive/ directory, and deploy the new ear file.
The following sample illustrates the process:
acm-700:/ # cd /home/oracle/archive
acm-700:/home/oracle/archive # ll
total 739396
-rw-rw---- 1 oracle oinstall 756391543 Aug 20  2015 aveksa_7.0.0_93958-2015-Aug-20-17.54.ear
-rw-rw---- 1 oracle oinstall       125 Aug 20  2015 wildfly_deployment.properties
acm-700:/home/oracle/archive # cd ../deploy/
acm-700:/home/oracle/deploy # ./customizeACM.sh -c aveksa_7.0.0_93958-2015-Aug-20-17.54.ear
unzipping ear...
    [unzip] Expanding: /home/oracle/archive/aveksa_7.0.0_93958-2015-Aug-20-17.54.ear into /tmp/customizeACM
Ready for customization. Please go to /tmp/customizeACM to continue modifications.
acm-700:/home/oracle/deploy # cd /tmp/customizeACM
acm-700:/tmp/customizeACM # ll
total 10084
drwxr-xr-x   3 root root    4096 Feb 21  2014 APP-INF
drwxr-xr-x   2 root root    4096 Aug 26 15:30 META-INF
drwxr-xr-x 107 root root    4096 Aug 26 15:30 aveksa.war
-rw-r--r--   1 root root 6983341 Aug 11  2015 server.jar
-rw-r--r--   1 root root   16753 Feb 21  2014 wpClientServletLite.war
-rw-r--r--   1 root root 1969704 Feb 21  2014 wpConsole.war
-rw-r--r--   1 root root  138332 Feb 21  2014 wpQMonitor.war
-rw-r--r--   1 root root 1173982 Feb 21  2014 wpServer.jar
acm-700:/tmp/customizeACM # cd -
/home/oracle/deploy
acm-700:/home/oracle/deploy # ./customizeACM.sh -d
repackaging the ear...
      [zip] Building zip: /tmp/customizeACM/aveksa.ear
undeploy...
deploy...    this may take a while...
aveksa.ear redeployed
aveksa_7.0.0_93958-2016-Aug-26-15.31.ear archived
acm-700:/home/oracle/deploy # cd ../archive/
acm-700:/home/oracle/archive # ll
total 1477244
-rw-rw---- 1 oracle oinstall 756391543 Aug 20  2015 aveksa_7.0.0_93958-2015-Aug-20-17.54.ear
-rw-rw---- 1 oracle oinstall 754814339 Aug 26 15:32 aveksa_7.0.0_93958-2016-Aug-26-15.31.ear
-rw-rw---- 1 oracle oinstall       125 Aug 26 15:36 wildfly_deployment.properties
acm-700:/home/oracle/archive #
NotesThe customizeACM.sh must be run from /home/oracle/deploy/ or you will receive the following error:
Error: Could not find or load main class groovy.lang.GroovyShell

Attachments

    Outcomes