Friday, 8 November 2013

Applying Oracle Webcenter Portal 11.1.1.6.6 Bundle Patch 16269470

Applying Webcenter Portal 11.1.1.6.6 Bundle Patch 16269470

1. This patch is applicable to two ORACLE_HOMEs:

      -> [MW_HOME]/oracle_common (JRF Home)
      -> [MW_HOME]/Oracle_WC1    (Webcenter Home)


2. Run the following WLST commands and save the output (this will be needed during the post-install instructions):

   Using WLST:
   cd [MW_HOME]/Oracle_WC1/common/bin
   ./wlst.sh
   
   $> connect()

  $> listWebServicePolicies('/wcp_domain/WC_Spaces/webcenter', 'webcenter', 'web', 'SpacesWebService', 'SpacesWebServiceSoapHttpPort')

  $> listWebServicePolicies('/wcp_domain/WC_Collaboration/owc_discussions', 'owc_discussions', 'web', 'OWCDiscussionsServiceAuthenticated', 'OWCDiscussionsServiceAuthenticated')

3. Stop all servers (Admin Server and all Managed Server(s))

4. Run OPatch to apply the patch.

   Proceed as below:

   4.1. Set the ORACLE_HOME environment variable to "[MW_HOME]/oracle_common" directory.

       Run following command:
       - opatch apply

   4.2. Set the ORACLE_HOME environment variable to "[MW_HOME]/Oracle_WC1" directory.
  
       Run following command:
       - opatch apply 

You should see below at the end of opatch.
-------------------
Verifying the update...
Inventory check OK: Patch ID 16269470 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 16269470 are present in Oracle Home.

The local system has been patched and can be restarted.

--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67644:
Given patch "16269470" is a bug superset of patch "14361677" but is not a file superset.

--------------------------------------------------------------------------------
OPatch Session completed with warnings.


OPatch completed with warnings.
-----------------------

5. Start all servers (Admin Server and all Managed Server(s))

6. Prior to this patch, the WebCenter Spaces & WebCenter Discussions web service end points were seeded with a fixed policy - i.e., 
wss11_saml_token_with_message_protection_service_policy and wss10_saml_token_service_policy respectively. 

Post application of this patch, there is no security policy assigned to the WebService end points thereby resulting in a potential loss of functionality. 

To  fix this, you will need to reapply the policies that were set earlier on these services. This can be achieved either via WLST or the Enterprise Manager console. 

Using WLST:
cd [MW_HOME]/Oracle_WC1/common/bin
./wlst.sh
   
   $> connect()

   $> attachWebServicePolicy('webcenter', 'webcenter', 'web', 'SpacesWebService', 'SpacesWebServiceSoapHttpPort', 'oracle/wss11_saml_or_username_token_with_message_protection_service_policy')
   ... where oracle/wss11_saml_or_username_token_with_message_protection_service_policy is the policy you want to restore. 
  
   Note that this is the value you obtained by running listWebServicePolicies in the section '2 Pre-Installation Instructions'
   against WebCenter Spaces web service end point.

   $> attachWebServicePolicy('owc_discussions', 'owc_discussions', 'web', 'OWCDiscussionsServiceAuthenticated', 'OWCDiscussionsServiceAuthenticated', 'oracle/wss10_saml_token_service_policy')
   ... where oracle/wss10_saml_token_service_policy is the policy you want to restore. 

   $> exit()

   Failure to perform these steps will cause the connection between Spaces and the Discussions server to fail with an "Error while invoking endpoint" message.

7. Restart Spaces and Collaboration managed server(s).

8. Due to the fixes installed, the following is mandatory:

   8.1. Update the WebCenter Portal Extension Bundle for JDeveloper.
      
   8.2. Clear the browser cache.

9. Run opatch lsinventory to verify the patch applied. 

No comments:

Post a Comment