Choosing Your Oracle WebCenter Update Method

Patching Oracle WebCenter 5-7 ■ domainDirName - Replace DOMAIN_HOME with the full path to your Domain home directory. ■ oracleHome - Replace WebCenter_ORACLE_HOME with the full path to your WebCenter Oracle home directory. ■ upgradeCustomSpaces - Set to 1 if you used the custom.webcenter.spaces shared library to customize WebCenter Spaces and you want to migrate your customizations to the upgraded instance. For information about how to user your extensions in WebCenter Spaces 11.1.1.5.0, refer to: http:www.oracle.comtechnetworkmiddlewarewebcenterowc s-ps4-wcs-ext-samples-wp-406559.pdf For example: upgradeWebCenterDomaindomainDirName=homeOracleDomainswc_domain, oracleHome=homeOracleMiddlewareOracle_WC1, upgradeCustomSpaces=1 5. Start the Administration Server. 6. Connect to the Administration Server. connect 7. In the domain that is running the WebCenter Spaces Managed Server, run the upgradeWebCenterPermissions command. upgradeWebCenterPermissions 8. All of the instructions to this point have been for a single node. If your domain has servers running on more than one machine, you will need to pack and unpack your domain to replicate the changes to other nodes in your cluster. To pack and unpack your updated domain: WARNING: If you upgrade your WebCenter domain with upgradeCustomSpaces set to 0, none of your previous customizations will be available in the upgraded WebCenter Spaces instance and there is no facility to migrate WebCenter Spaces customizations after the upgrade process. Note: You may see error messages when you run the upgradeWebCenterDomain command. These errors can be safely ignored so long as there is some text indicating that your operation was completed successfully. For more information about the error messages, refer to Oracle Fusion Middleware Release Notes. Note: You may see error messages when you run the upgradeWebCenterPermissions command. These errors can be safely ignored so long as there is some text indicating that your operation was completed successfully. For more information about the error messages, refer to the Oracle Fusion Middleware Release Notes. 5-8 Oracle Fusion Middleware Patching Guide a. Pack the Administration Server: cd WebCenter_ORACLE_HOME commonbin .pack.sh -managed=true -domain= DOMAIN_HOME -template=wcdomaintemplate.jar -template_name=wc_domain_template b. Copy wcdomaintemplate.jar to the WebCenter_ORACLE_ HOME commonbin on the other machines. c. Remove or move the old domain directories DOMAIN_HOME and APPLICATION_HOME on the other machines. d. Unpack the domain on each of the other machines: cd WebCenter_ORACLE_HOME commonbin .unpack.sh -domain= DOMAIN_HOME -template=wcdomaintemplate.jar 9. Start the WebCenter Managed Servers: ■ WC_Spaces WebCenter Spaces ■ WC_Portlet Oracle Portlet Producers ■ WC_Collaboration Oracle WebCenter Discussion Server Make sure the WC_Spaces server is up and running before moving on to the next step. 10. Disconnect from the Administration Server and connect to the WC_Spaces server as an Oracle WebCenter administrator that is defined in the external LDAP server and is defined as an administration user in the embedded Oracle WebLogic Server. It is important to note that the administration user must be defined both as a user in the external LDAP directory and as a user with administration privileges in the embedded Oracle WebLogic Server LDAP directory. If necessary, you can add a user to the Administration Group of the embedded Oracle WebLogic Server LDAP server, as follows: 1. Log in to the WebLogic Server console. 2. Click Security Realms and select the myrealm link. 3. Click the RolesPolicies tab. 4. Expand Global Roles, then expand Roles, then click View Role Conditions for the Admin role. 5. Click Add Condition, then select User from the Predicate List field, then click Next. 6. Enter the user name in the User Argument Name field, then click Add. 7. Click Finish. The user you just entered should now be listed along with the administrators. 8. Save your changes and exit. 11. In the domain that is running the WebCenter Spaces managed server, run the upgradeWebCenterApplication command. upgradeWebCenterApplicationappName=’webcenter’ If you have a cluster environment where there are multiple servers with WebCenter Spaces deployed, you must specify the server name. For example: upgradeWebCenterApplicationappName=’webcenter’, server= server_name