OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894
Redeploying the OAAM Shared Library in Oracle WebLogic is one of the post patching steps after applying Patch 19162894. Refer to this post for more details.
If you have a native integration, redeploy the OAAM shared library by following these steps:
- Start the managed server.
Log in to the WebLogic Administration Console. Open a web browser and enter the URL:
http://hostname:port/console
or
https://hostname:port/console
On the Welcome screen, log in using the user name and password
- In the Domain Structure section of the console, click Deployments. The Summary of Deployments page is displayed.
- In the Summary of Deployments page, select oracle.oaam.libs in the Deployments table and then click Delete.
- In Change Center, click Activate Changes for the changes to take effect.
- Click the Install button.
- In the path field, specify the path to the oaam_native_lib.war file, including the file name.
- Select oaam_native_lib.war and Next.
- On the next screen, select the Install this deployment as a library option and click Next.
- In the Select Deployments targets page, select the managed server from the list of servers to deploy the shared library, oracle.oaam.libs, and click Next and Click Finish.
- In the Change Center, click Activate Changes for the changes to take effect.
OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894
Redeploying the OAAM applications is one of the post patching steps after applying Patch 19162894. Refer to this post for more details.
To redeploy the OAAM applications, follow these steps:
- Delete the content from the OAAM Admin server (oaam_admin_server1), OAAM Server server (oaam_server_server1), OAAM Offline server (oaam_offline_server1) temp directories:
MW_HOME/user_projects/domains/domain_home/servers/oaam_admin_server1/tmp
MW_HOME/user_projects/domains/domain_home/servers/oaam_server_server1/tmp
MW_HOME/user_projects/domains/domain_home/servers/oaam_offline_server1/tmp
Start all servers.
- Log in to the WebLogic Administration Console. Open a web browser and enter the URL:
http://hostname:port/console
or
https://hostname:port/console
- Redeploy the oaam_admin application by performing these steps:
1) In the Domain Structure section of the console, click Deployments. The Summary of Deployments page is displayed.
2) Select oaam_admin in the Deployments table and click Update.
3) In the Domain Structure section of the console, click Deployments.
4) In the Summary of Deployments page, select oaam_admin in the Deployments table.
5) Use the Stop drop-down list to select Force Stop Now.
Again select oaam_admin and then click Delete.
6) On the right, under Deployments, click Install.
When locating the deployment to install, provide the location of the oaam_admin.ear file in the Path field. You must include the file name, oaam_admin.ear, when specifying the path.
On the next screen, choose Install this deployment as an application as the targeting style and click Next.
On the next screen, select the OAAM Admin Server as the target for oaam_admin. For example, select the target oaam_admin_server1.
On the next screen for optional settings, make sure you select 'I will make the deployment accessible from the following location' and point to the location where the oaam_admin.ear file will be accessible:
Oracle_IDM/oaam/oaam_admin/ear/oaam_admin.ear
Click Finish to complete the deployment of oaam_admin.
7) Log in to the OAAM Admin Console.
In the Navigation tree, double-click Properties under Environment.
In the Properties page, search for the oaam.taskflow.enum.sessionaddtogroup property.
Select the oaam.taskflow.enum.sessionaddtogroup.name property and click Save.
Saving the property will change it from a file load type property to a database type property. The property is now available in the database.
If the oaam.taskflow.enum.sessionaddtogroup.name property does not exist, create it.
Click the New Property button or Create new Property icon.
In the New Property dialog, type in oaam.taskflow.enum.sessionaddtogroup.name as the property name and SessionAddToGroup as the property value.
Click Save to save the property.
8) Restart the OAAM Admin server.
9) Update and activate changes for OAAM Server.
In the Domain Structure section of the console, click Deployments.
In the Summary of Deployments page, select oaam_server in the deployment table and click Update.
In the Change Center, click Activate Changes for the changes to take effect.
10) Update and activate changes for OAAM Offline.
In the Domain Structure section of the console, click Deployments.
Select the oaam_offline application in the deployment table and click Update.
In the Change Center, click Activate Changes for the changes to take effect.
If you find that oaam_admin, oaam_server, and oaam_offline are not in the Active state, then select the appropriate server and click Start.
When you have applied the OAAM 11.1.2.1.3 patch (19162894), version information is shown when you click the About link on the right side bottom corner. The version information should appear as Version 11.1.2.1.0 (11.1.2.1.0.OAAM_11.1.2.1.0BP_GENERIC_140828.0325).
Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5
- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)
- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:
- OES 11.1.2.1.1
- OPSS 11.1.1.6.3
- OAM 11.1.2.1.4
- OAAM 11.1.2.1.3
- Copy p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.
- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)
Apply OAM 11.1.2.1.4 - Patch 19162892
- Stop the Admin server and Managed servers (where OAM console and servers have been deployed)
- Unzip the patch zip file into the PATCH_TOP.
$ unzip -d PATCH_TOP p19162892_111210_Generic.zip
- cd /PATCH_TOP/19157616/OAM/19162892
- Run OPatch to apply the patch.
$ opatch apply
- Restart all servers (Admin Server and all Managed Server(s))
Post-Installation Steps for IBM WebSphere (WAS) (Only applicable for OAM installed on the IBM WebSphere Application Server)
-----------------------------------------------
After applying this bundle patch on an instance of OAM installed on the IBM WebSphere Application Server (WAS), you must redeploy the OAM application in WAS for successful patch application. Follow
steps in Patch README.HTML to manually redeploy the OAM administration application (oam-admin-was.ear) and the OAM server application (oam-server.ear). They should be individually redeployed.
1. "Redeploying oam-admin-was.ear"
2. "Redeploying oam-server.ear"
Patch 19162892 Rollback Instructions:
Post patching, if any issues encountered and rollback is required, follow below steps:
- Stop the Admin server and Managed servers (where OAM console and servers have been deployed)
- Change to the directory where the patch was unzipped.
$ cd PATCH_TOP/19162892
- Run OPatch to deinstall the patch.
$ opatch rollback -id 19162892
- Restart all servers (Admin Server and all Managed Server(s))
