File Downloads
- Download the hotfix files from RSA Link. See 000033845 - How to download patch files for RSA Identity Governance and Lifecycle from RSA Link for more information.
- Download the following files:
- Aveksa_<VersionNumber>_P<PatchNumber>_HF<>HotfixNumber.tar.gz (e. g., Aveksa_7.0.1_P02_HF02.tar.gz)
- JDK update for security updates (optional).
NOTE: A hotfix release also includes updated connector packages. If you are running AFX, you must download and import the packages. Please see the Notes section below for more details.
- For a software appliance (IMG Software Bundle), the 7.0.1 P02_HF02 files are shown below:
Upgrading the JDK (optional)
If you choose to upgrade JDK, please perform the following steps:
- Change to the Oracle directory:
cd /home/oracle
- Uncompress and untar the file:
tar vxf upgradeJDK.tar
- Log in as root and run the following commands:
cd /home/oracle/upgradeJDK chmod 777 * cd deploy/ chmod 777 * cd .. sh upgradeJDK.sh
Shutdown all AFX instances
- If you have AFX installed, login with the AFX user account.
- Shut down all of the AFX instances before installing the patch upgrade:
cd <path-to-AFX_installation-directory>/AFX/ afx stop
- Check the afx status and make sure all three processes are stopped.
oracle@acm-701:~/AFX> afx status AFX Server Status: Setting MULE_HOME to /home/oracle/AFX/esb... INFO: Using default configuration (you can configure options in one of these file: /etc/default/activemq /home/oracle/.activemqrc) INFO: Invoke the following command to create a configuration file /home/oracle/AFX/activemq/bin/activemq setup [ /etc/default/activemq | /home/oracle/.activemqrc ] INFO: Using java '/etc/alternatives/java_sdk_1.7.0/bin/java' AcvtiveMQ not running. ---- MULE_HOME is set to /home/oracle/AFX/esb Mule Enterprise Edition is not running. ---- MMC Console is not running. done oracle@acm-701:~/AFX>
Uncompress and untar the hotfix
- Create a directory named /tmp/aveksa/packages/7.0.1-P02-HF02.
- Using a secure copy client, copy the hotfix file (i. e., Aveksa_7.0.1_P02_HF02.tar.gz) to /tmp/aveksa/packages/7.0.1-P02-HF02.
- Login as the oracle user.
- Navigate to /home/oracle.
- Extract the contents of the hotfix file. This will also create a directory named /home/oracle/Aveksa_7.0.1_P02_HF02.
- Exit the shell.
mkdir /tmp/aveksa/packages/7.0.1-P02-HF02 cd /home/oracle tar -zxvf /tmp/aveksa/packages/7.0.1-P02-HF02/Aveksa_7.0.1_P02_HF02.tar.gz exit
Install the hotfix
- Login as the root user.
- Navigate to /home/oracle/Aveksa_7.0.1_P02_HF02.
- Running Il or ls -l will show the files in the directory, as listed below:
acm-701:/home/oracle # whoami root acm-701:/home/oracle # cd Aveksa_7.0.1_P02_HF02 acm-701:/home/oracle # ll total 48 -rw-r--r-- 1 oracle oinstall 12323 Mar 2 05:17 PatchInfo.txt drwxr-xr-x 5 oracle oinstall 4096 Mar 10 09:08 aveksa.ear drwxr-xr-x 2 oracle oinstall 4096 Mar 10 09:08 aveksaWFArchitect.ear drwxrwxrwx 2 oracle oinstall 4096 Mar 10 09:08 deploy -rw-r--r-- 1 oracle oinstall 4096 Mar 2 05:17 patch.sh acm-701:/home/oracle/Aveksa_7.0.1_P02_HF02 #
- Run the following command:
acm-701:/home/oracle/Aveksa_7.0.1_P02_HF02 # sh ./patch.sh =========================================================================== Begin ACM patch 7.0.1 P02_HF_2 on acm-701 at Fri Mar 10 09:11:59 EST 2017 =========================================================================== Detailed output from this installation can be found in: /home/oracle/Aveksa_7.0.1_P02_HF02/logs/7.0.1_P02_HF-2_2017-03-10-0911.log You can view the detailed installation log information while the install is running by entering the following command in another console: tail -f /home/oracle/Aveksa_7.0.1_P02_HF02/logs/7.0.1_P02_HF-2_2017-03-10-0911.log Patch will be overlaid on an archived ear that has/had been deployed already. The archived ears are in the /home/oracle archive directory ------------------------------------------------ Checking environment. . . -- Verifying existence of /home/oracle/Aveksa_system.cfg -- Checking for need to update groovy files from deployment fixes --- No updates needed for file CustomizeACM.groovy Preparing to the ear file for deployment at Fri Mar 10 09:11:59 EST 2017 -- Expanding the CURRENTLY deployed ear to filesystem for further checks to apply patch. Deploying aveksaWFArchitect.ear ----------------------------------------------------- ----------------------------------------------------- Restarting Application server with newly loaded ear... Stopping RSA Identity Governance and Lifecycle: The server has shut down. Updating System Values... Verifying database Timezone value ... Detected change in database Timezone. Restarting Oracle instance ... Starting RSA Identity Governance and Lifecycle: Verifying Oracle and System time match ... Database : 03-10-2017 09:25:57 -0500 ~ Web : 03-10-2017 09:25:54 -0500 Waiting for RSA Identity Governance and Lifecycle to start....... RSA Identity Governance and Lifecycle is running Starting ACM Watchdog: done ----------------------------------------------------- AFX service found, starting AFX service... Successful connection detected to RSA Identity Governance and Lifecycle Starting AFX Server: Setting MULE_HOME to /home/oracle/AFX/esb... Checking Aveksa OEM ESB License for AFX... INFO: Using default configuration INFO: Using default configuration (you can configure options in one of these file: /etc/default/activemq /home/oracle/.activemqrc) INFO: Invoke the following command to create a configuration file /home/oracle/AFX/activemq/bin/activemq setup [ /etc/default/activemq | /home/oracle/.activemqrc ] INFO: Using java '/etc/alternatives/java_sdk_1.7.0/bin/java' INFO: Starting - inspect logfiles specified in logging.properties for log4j.properties to get details INFO: pidfile created : 'home/oracle/AFX/activemq/data/activemq.pid' (pid '17688') --- MULE_HOME is set to /home/oracle/AFX/esb Starting Mule Enterprise Edition... Waiting for AFX application to start... AFX applications started. done =========================================================================== End ACM patch 7.0.1 P02_HF02 on acm-701 at Fri Mar 10 09:28:40 EST 2017 ===========================================================================
Confirm the hotfix install
- Login to the RSA Identity Governance and Lifecycle Admin Console as the AveksaAdmin user.
- Checking Product Information shows the hotfix has just been installed.
|