Friday, 8 January 2016

OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894

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).





No comments:

Post a Comment