000033000 - Error when running RSA Via Lifecycle & Governance 7.0 customizeACM.sh:  Could not find Aveksa ear

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000033000
Applies ToRSA Product Set: RSA Lifecycle & Governance
RSA Version/Condition: 7.0.0, 7.0.0 P01
 
IssueRunning customizeACM.sh -c returns the following error if no archive ear file is specified and it is left to default to "The current ear file deployed to Wildlfy."  An example of the error is:
acm-700:/home/oracle/deploy # ./customizeACM.sh -c
You have not specified an archive ear file to customize.
The current ear file deployed to Wildlfy is stored at:
/home/oracle/archive/aveksa_7.0.0_93958-2015-Aug-20-17.54.ear
Do you want to customize that archived ear file [yes/no]?yes
Could not find aveksa_7.0.0_93958-2015-Aug-20-17.54.ear.  Please check /home/oracle/archive/ if using a relative path.
CauseIf you do not specify the path location of the ear file when customizeACM.sh is run, the script should use the currently deployed ear file.  However, due to a defect in the affected RSA Lifecycle & Governance versions, the configured .ear file is not present under the /home/oracle/archive folder.
 
WorkaroundAs a precaution, before continuing, make a backup copy of /home/oracle/archive to another location, e. g., mkdir /tmp/archive.
  1. Navigate to cd /home/oracle/deploy.
  2. Run the following command:
./customizeACM.sh -i /tmp/aveksa/staging,/tmp/repackaged_ear_dir

This will create a new .ear in the /home/oracle/archive directory with today's date in the filename, and update the wildfly_deployment.properties file with its name (CURRENTLY_DEPLOYED_ARCHIVE and INITIAL_ARCHIVE).   Example output is as follows:

acm-700:/home/oracle/deploy # ./customizeACM.sh -i /tmp/aveksa/staging,/tmp/repackaged_ear_dir
inflated: aveksa.war
inflated: WEB-INF/classes/aveksa-version.properties
source : /tmp/repackaged_ear_dir/aveksa.ear
target : /home/oracle/archive/aveksa_7.0.0_93958-2016-Apr-26-0.31.ear

  1. After completing the above steps,  run ./customizeACM.sh -c and it should find the new .ear file. If this is successful, delete the /tmp/archive backup directory and its contents. An example of a successful run of ./customizeACM.sh -c is:
acm-700:/home/oracle/deploy # ./customizeACM.sh -c
You have not specified an archive ear file to customize.
The current ear file deployed to Wildlfy is stored at:
/home/oracle/archive/aveksa_7.0.0_93958-2015-Aug-20-17.54.ear
Do you want to customize that archived ear file [yes/no]?yes
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.
NotesThe aveksa ear file name is configured in the /home/oracle/archive/wildfly_deployment.properties file and has a value of CURRENTLY_DEPLOYED_ARCHIVE.

This issue occurs when the CURRENTLY_DEPLOYED_ARCHIVE file is not present under the /home/oracle/archive folder.

Attachments

    Outcomes