000038351 - How to manually deploy an aveksa ear file in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jan 17, 2020Last modified by RSA Customer Support Employee on Jan 20, 2020
Version 5Show Document
  • View in full screen mode

Article Content

Article Number000038351
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x
 
IssueDuring installation, patch/upgrade, and customizeACM.sh, the aveksa ear file is automatically deployed as aveksa.ear regardless of its actual name in $AVEKSA_HOME/archive However, there may be times when one of these files needs to be manually deployed. In this case it is very important to deploy the aveksa ear file as aveksa.ear. This article explains how to manually deploy the aveksa ear file as aveksa.ear.
ResolutionThe aveksa ear files are stored in $AVEKSA_HOME/archive unless you remove them. See RSA Knowledge Base Article 000038190 -- Can archived aveksa.ear files stored in $AVEKSA_HOME/archive be deleted in RSA Identity Governance & Lifecycle? for more information on what aveksa ear files may be removed from this directory.

Any of these ear files may be manually deployed using the jboss-cli.sh utility in $AVEKSA_HOME/wildfly/bin. The process is to undeploy the existing ear file, deploy the new ear file as aveksa.ear and update the $AVEKSA_HOME/archive/wildfly_deployment.properties file to point to the deployed ear file.
  1. Login as the oracle user.
  2. Determine the name of the existing deployed ear file.


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deployment-info"


  1. You should see the following output:


NAME                   RUNTIME-NAME          PERSISTENT ENABLED STATUS
aveksaWFArchitect.ear aveksaWFArchitect.ear  true       true    OK
aveksa.ear            aveksa.ear             true       true    OK


 However, you may see output similar to the following if you have previously deployed the ear file manually and did not deploy the ear file as aveksa.ear.



NAME                              RUNTIME-NAME                      PERSISTENT ENABLED STATUS
aveksaWFArchitect.ear             aveksaWFArchitect.ear             true       true    OK
<name other than aveksa.ear>      <name other than aveksa.ear>      true       true    OK


  1. Undeploy the ear file (Standalone)


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="undeploy <name of deployed aveksa ear file>"


  1. Undeploy the ear file  (Clustered)


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="undeploy <name of deployed aveksa ear file> --server-groups=img-server-group"


  1. Deploy the new ear file as aveksa.ear. (Standalone)


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deploy $AVEKSA_HOME/archive/<name of aveksa ear file to be deployed>
--name=aveksa.ear --runtime-name=aveksa.ear"


  1. Deploy the new ear file as aveksa.ear. (Clustered)


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deploy $AVEKSA_HOME/archive/<name of aveksa ear file to be deployed>
--name=aveksa.ear --runtime-name=aveksa.ear --server-groups=img-server-group"


  1. Check that the aveksa.ear file deployed correctly.


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deployment-info"


You should see the following output:



NAME                   RUNTIME-NAME          PERSISTENT ENABLED STATUS
aveksaWFArchitect.ear aveksaWFArchitect.ear  true       true    OK
aveksa.ear            aveksa.ear             true       true    OK


  1. Check that the variable name CURRENTLY_DEPLOYED_ARCHIVE in $AVEKSA_HOME/archive/wildfly_deployment.properties is defined as the currently deployed ear file. This variable is used when patching, upgrading and/or customizing RSA Identity Governance & Lifecycle so it is important that the variable points to the correct ear file. For example, given the below deployment command:


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deploy $AVEKSA_HOME/archive/aveksa_7.1.1_161195_P04-2020-Jan-20-9.00_custom.ear
--name=aveksa.ear --runtime-name=aveksa.ear"


the wildfly_deployment.properties file should look like the below where CURRENTLY_DEPLOYED_ARCHIVE is the name of the ear file you just deployed, and INITIAL_ARCHIVE is the name of the GA ear file.



CURRENTLY_DEPLOYED_ARCHIVE=aveksa_7.1.1_161195_P04-2020-Jan-20-9.00_custom.ear
INITIAL_ARCHIVE=aveksa_7.1.1_161195-<date of installation>.ear


 
Notes

 

Attachments

    Outcomes