Oracle Access Manager Upgrade from 11.1.2.0 to 11.1.2.3.3 - Part 5

1 Upgrade OPSS:

Upgrading Oracle Platform Security Services is required to upgrade the configuration and policy stores of Oracle Access Manager to 11.1.2.3.0.
It upgrades the jps-config.xml file and policy stores. 

Execute below command: 

$ cd $MW_HOME/oracle_common/common/bin/wlst.sh 
$ cd /u10/oracle/middlewaroam/oracle_common/common/bin
$ ./wlst.sh
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands

wls:/offline> upgradeOpss(jpsConfig="/u10/oracle/middlewareoam/user_projects/domains/oam_domain/config/fmwconfig/jps-config.xml",
...jaznData="/u10/oracle/middlewareoam/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml",
...auditStore="/u10/oracle/middlewareoam/oracle_common/modules/oracle.jps_11.1.1/domain_config/audit-store.xml",
...jdbcDriver="oracle.jdbc.OracleDriver",
...url="jdbc:oracle:thin:@DBHostname:DBPort:DB_SID",
...user="XXX_OPSS",
...password="welcome1",
...upgradeJseStoreType="false") 

Starting upgrade of opss configuration and security stores.
….
….
Upgrade of opss configuration and security stores is done.
wls:/offline> exit()
$ exit
Script done, file is /u10/oracle/middlewareoam/upgradeOpss.log

2 Copy Modified System mbean Configurations:

If you are upgrading Oracle Access Management 11.1.2.0.0 to Oracle Access Management 11.1.2.3.0, you must copy the modified system or domain mbean configurations from the OAM_ORACLE_HOME to the DOMAIN_HOME, after you update the Access Manager binaries to 11.1.2.3.0. 

$ cd $ORACLE_HOME/common/bin
$ pwd
/u10/oracle/middlewareoam/Oracle_IAM1/common/bin
$ ./wlst.sh
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell

wls:/offline> copyMbeanXmlFiles('/u10/oracle/middlewareoam/user_projects/domains/oam_domain','/u10/oracle/middlewareoam/Oracle_IAM1') 
_____________________________________
STATUS: SUCCESS
The mbean xml files have been upgraded to new version.
The original mbean xml is saved in "<domain_directory>/output/upgrade".
Please restart the admin and oam servers.
____________________________________

1) Start WebLogic Administration Server
2) Start Oracle Access Manager Managed Server
Note : During startup of OAM Manage server below error will be observed:

<<
<Error> <Deployer> <BEA-149205> <Failed to initialize the application 'coherence [LibSpecVersion=3.7.1.1,LibImplVersion=3.7.1.1]' due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: coherence, Specification-Version: 3.7.1.13, Implementation-Version: 3.7.1.13, because of conflicting library Manifest values, and library information registered with the server: [Specification-Version: 3.7.1.13 vs. 3.7.1.1, Implementation-Version: 3.7.1.13 vs. 3.7.1.1]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigured library.
>> 
To resolve above error please proceed with below steps:

3 Undeploy Coherence 3.7.1.1 Library:

To undeploy the coherence#3.7.1.1 library using the WebLogic Administration Console:

Step 1) Log in to the WebLogic Administration Console using the following URL: 
http://host:port/console 
Step 2) Click Lock & Edit.
Step 3) Click Deployments under Domain Structure on the left navigation pane. 
Step 4) Select coherence(3.7.1.1,3.7.1.1) library, and click Delete. 

Step 5) Click Activate Changes. 

Step 6) Restart the AdminServer and OAM managed server and check whether above error is observed in logs or not.

4 Upgrade System Configuration : 

 

For the Oracle Access Management 11.1.2.3.0 features to work, you must run the upgradeConfig() utility on the machine that hosts Administration Server. This utility upgrades the system configuration of Access Manager to 11.1.2.3.0.   

This step will upgrade the OAM 11.1.2.0 configuration and policy store to OAM 11.1.2.3. The upgradeConfig utility must complete successfully or Single Sign On (SSO) to OAM-protected resources after upgrade will fail.

1) Shutdown AdminServer + OAM  Manage Server

2) The upgradeConfig command needs to be run using the IPv4 stack. The WL_HOME/common/bin/wlst.sh file should be edited to add the java.net.preferIPv4Stack=true property. 
3) $ cd $ORACLE_HOME/common/bin/wlst.sh
Initializing WebLogic Scripting Tool (WLST) 
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands

wls:/offline> upgradeConfig("/u10/oracle/middlewareoam/user_projects/domains/oam_domain", "sys", "welcome1", "XXX_OAM", "jdbc:oracle:thin:@DBHostname:DBPort/DB_SID")
....
....
INFO: System configurations have been successfully upgraded to version: 11.1.2.3.0

4 Start the servers:

1) Start WebLogic Administration Server
2) Start Oracle Access Manager Managed Server

Verify that all servers reach RUNNING state.  

3) Post upgrade, the OAM 11.1.2.3 Administration Console should be accessible. Use the following URL to verify access:
http://<oam_admin_server_host>:<oam_admin_server_port>/oamconsole