Oracle Access Manager Upgrade from 11.1.2.0 to 11.1.2.3.3 - Part 2

PRE UPGRADES STEPS

1 Increase JVM Memory:

1)Update the WebLogic Server memory parameters so that there is sufficient memory for the additional components after upgrade .The memory parameters must be increased for both AdminServer and OAM managed servers.

In case memory setting is set to low value then increase the size as below: 

Step 1) Go to the $DOMAIN_HOME/bin directory. 

Step 2) Take a backup of file setDomainEnv.sh
cp setDomainEnv.sh setDomainEnv.sh_BKP 

Step 3) Edit setDomainEnv.sh and search for the following lines:
<<
# IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
if [ "${USER_MEM_ARGS}" != "" ] ; then
MEM_ARGS="${USER_MEM_ARGS}"
export MEM_ARGS
fi
>> 

Step 4) Add the USER_MEM_ARGS setting. For example:

UNIX:
# IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values

USER_MEM_ARGS="-Xms4096m -Xmx4096m -XX:MaxPermSize=512m"
export USER_MEM_ARGS

if [ "${USER_MEM_ARGS}" != "" ] ; then
MEM_ARGS="${USER_MEM_ARGS}"
export MEM_ARGS
fi 

Step 5) Save changes to file. 

Step 6) Restart the AdminServer and OAM Server using command line.

Step 7) In case node manager is used to start server then make below changes:

7.1 ) Log in to the WebLogic Server administration console as the weblogic user:
http://adminserver_host.domain:port/console
7.2)Click Servers on the left navigation pane.
7.3)Select the server to be modifed.(AdminServer and oam_server) 
7.4)Go to the Server Start → Argruments
Set the value of JVM arguments. For example:
-Xms4096m -Xmx4096m 
7.5)Save the changes.
7.6)Restart Both the server (Admin Server and OAM Server ) for changes to reflect.

2) Always ensure that there is sufficient free memory available in server with top command.

2 Verify the pre-upgrade OAM schema:

Before you begin the upgrade, verify the pre-upgrade OAM schema and credential. It will be required during the upgrade.
The OAM schema name can be verified via Weblogic Server Console as below: 

Step 1) Log in to the WebLogic Server administration console as the weblogic user:
http://adminserver_host.domain:port/console 

Step 2) Under Services section, click the Data Sources link. 

Step 3) Click the Data Source with name "oamDS". 

Step 4) Click the Connection Pool tab. 

Step 5) In the Properties section, note the value of the user parameter. This is the OAM schema username.
Ex: DEV_OAM 

Login to sqlplus with username and password to verify credentials:
ex:
SQL> conn DEV_OAM/123456
Connected.
SQL> show user;
USER is "DEV_OAM"

3 Export the OAM policy objects

Export the pre-upgrade 11.1.2.0 policy objects to file. This pre-upgrade record may be a useful reference if there are any issues with the OAM 11.1.2.3 policy store upgrade.

1)Launch the WebLogic Scripting Tool (WLST) from the location $ORACLE_HOME/common/bin:

cd $ORACLE_HOME/common/bin./wlst.sh
 wls:/offline>> connect() --- connect to the AdminServer port with OAM Administrator credentials
wls> domainRuntime()
wls> exportPolicy('/tmp/policy_export.xml')
wls> exit()

2) Policy objects record will be stored at /tmp location with name policy_export.xml

4 Stop OAM Services 

Shutdown below services: 

1)Admin Server 

2)OAM Server

3)Node Manager 

Note: The database must be running during the upgrade.