5 Patching Oracle WebCenter

5.2.1.1 Extending the Domain Using the Pagelet Producer Upgrade Template

A new version of Pagelet Producer is available in WebCenter Portal 11.1.1.6.0. If your upgraded WebCenter instance already has Pagelet Producer installed, you can choose to apply the new Pagelet Producer upgrade template to your domain to take advantage of the new features.

To apply the Pagelet Producer upgrade template:

1. Stop the Admin server and all managed servers.

2. Start the Configuration Wizard on the machine running the Admin server.

   On UNIX, run WebCenter_ORACLE_HOME/common/bin/config.sh.

   On Windows, run WebCenter_ORACLE_HOME\common\bin\config.cmd.

3. Select Extend an existing WebLogic domain and click Next.

4. Select your domain and click Next.

5. Select the Extend my domain using an existing extension template option.

6. Specify the path to the template, oracle.pagelet-producer-upgrade_template_11.1.1.jar and click Next. The template is available at the following location:

   WebCenter_ORACLE_HOME/common/templates/applications/oracle.pagelet-producer-upgrade_template_11.1.1.jar

7. Click Next on the remaining screens until you get the Configuration Summary screen, then click Extend.

   For more information on extending a domain, see "Extending a WebLogic Domain in Graphical Mode" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.

8. Start the Admin server and all managed servers.

9. Reconfigure the Pagelet Producer connections for the Spaces application and WebCenter custom applications (Framework applications) by using Fusion Middleware Control or WLST. For information, see "Registering the Pagelet Producer" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

   Note:

   In the previous release, it was mandatory to deploy Pagelet Producer to the following path:

   http://<pagelet-producer-server>:<port>/
   

   Pagelet Producer could not be accessed if it was deployed at any other location other than the root '/'. In Release 11.1.1.6.0, Pagelet Producer is deployed to the following path:

   http://<pagelet-producer-server>:<port>/pagelets/
   

   Where pagelets refers to any location of your choice where you want to deploy Pagelet Producer. Therefore, after extending the domain using the new Pagelet Producer upgrade template, you must reconfigure your Pagelet Producer connections.

   If you have OHS and SSO configured, you must configure them to use the new context root. For information, see Section 5.2.1.2, "Updating SSO and OHS Configuration."

10. Undeploy the older version of Pagelet Producer.

    1. In WLS Console, click Deployments.

    2. Select the checkbox next to pagelet-producer (11.1.1.4.0) deployment.

    3. Click Delete.

11. Target the WebCenterDS data source to WC_Portlet. This is required to enable the OpenSocial feature.

    1. In WLS Console, go to Services > Data Source.

    2. Click WebCenterDS.

    3. On the Targets tab, select WC_Portlet and click Save.

5.2.1.2 Updating SSO and OHS Configuration

If you have Oracle HTTP Server (OHS) and Single Sign-on (SSO) configured in your upgraded WebCenter environment, you may need to update the configuration for Pagelet Producer, Portlet Producer applications and Oracle SES.

This section includes the following subsections:

• Section 5.2.1.2.1, "Updating OHS Configuration for Pagelet Producer"

• Section 5.2.1.2.2, "Updating SSO Configuration for Pagelet Producer"

• Section 5.2.1.2.3, "Updating SSO Configuration for Portlet Producer Applications"

• Section 5.2.1.2.4, "Updating SSO Configuration for Oracle SES"

<Location /pageletadmin>
  SetHandler weblogic-handler
  WebLogicHost webcenter.example.com
  WebLogicPort 8889
</Location>
 
<Location /authenticateWithApplicationServer>
  SetHandler weblogic-handler
  WebLogicHost webcenter.example.com
  WebLogicPort 8889
</Location>

<Location /pagelets>
    SetHandler weblogic-handler
    WebLogicHost webcenter.example.com
    WebLogicPort 8889
</Location>

5.3.3.1 Save Your OmniPortlet and WebClipping Customizations

When you apply the latest patch set for Oracle WebCenter or Oracle Portal, both the OmniPortlet and WebClipping applications are re-deployed, and all configuration data stored within file-based preference stores is lost. You must save the OmniPortlet and WebClipping configuration and customizations to ensure that customizations are not lost when you apply the patch set.

To save and back up your customizations:

1. Locate the following directories:

   On UNIX operating systems:

   • path_to_war_directory/WEB-INF/providers/omniPortlet

   • path_to_war_directory/WEB-INF/providers/webclipping

   On Windows operating systems:

   • path_to_war_directory\WEB-INF\providers\omniPortlet

   • path_to_war_directory\WEB-INF\providers\webclipping

   Where path_to_war_directory refers to the following path:

   • On a UNIX operating system: DOMAIN_HOME/servers/WLS_PORTAL/tmp/_WL_user/portalTools_version/randomly_generated_directory/war

   • On a Windows operating system: DOMAIN_HOME\servers\WLS_PORTAL\tmp\_WL_user\portalTools_version\randomly_generated_directory\war

     Where, DOMAIN_HOME is the domain home locations for your Oracle Portal or Oracle WebCenter domain, as specified on the "Specify Domain Name and Location" screen in the Configuration Wizard.

2. Run the following command to back up the directory:

   • On UNIX operating systems:

     cp -fr path_to_war_directory/WEB-INF/providers/omniPortlet backup_location
     

   • On Windows operating systems:

     xcopy /y/e path_to_war_directory\WEB-INF\providers\omniPortlet backup_location
     

5.3.3.2 Run purgeMetadata() for WebCenter Spaces

If you are using WebCenter Spaces, you must run the purgeMetadata() WLST command to remove older versions of documents in MDS. This enables the patching process to run on a smaller set of data and thus decrease the time required to upgrade.

To purge metadata for WebCenter Spaces:

1. Start your Administration Server and Spaces Managed Server (WLS_Spaces) as the purgeMetadata() command is an online command.

2. Start WLST from your WebCenter Oracle home.

   On UNIX operating systems:

   cd WebCenter_ORACLE_HOME/common/bin
   ./wlst.sh
   

   On Windows operating systems:

   cd WebCenter_ORACLE_HOME\common\bin
   wlst.cmd
   

3. Connect to the Administration Server using the WLST connect() command.

4. Run the purgeMetadata() WLST command. For example, run the following command to purge metadata older than 3060 seconds:

   purgeMetadata('webcenter', 'WLS_Spaces', 3060)
   

   See "purgeMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference for more details.

5. Re-collect the database statistics. For example, you can connect to the WebCenter MDS schema using SQLPlus:

   execute dbms_stats.gather_schema_stats(ownname=>null, options=>'GATHER AUTO');
   

6. Stop your WLS_Spaces managed server and Administration Server.

For more information, see "Metadata Services (MDS) Custom WLST Commands" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

5.3.3.3 Upgrade Oracle Universal Content Management

This section includes the following subsections:

• Section 5.3.3.3.1, "Using Oracle Content Server 10g"

• Section 5.3.3.3.2, "Using Oracle WebCenter Content Server 11g"

• Section 5.3.3.3.3, "Comparing Oracle Content Server Features Available in Release 10g and 11g"

5.3.4.1 Updating Oracle WebCenter Using Node Manager and Automated Script

The Oracle WebCenter patch includes a script called upgrade.py that you can use to upgrade to the latest release. This script shuts down all the Managed Servers and the Administration Server at the beginning of the update process, and then starts all the servers during the update process.

You can use this script to update Oracle WebCenter only if you have set up Node Manager, have Oracle WebCenter installed on a single machine, and have verified that it is configured correctly. If your Node Manager is not configured correctly, you must use the WLST commands instead of this script to patch Oracle WebCenter.

This section includes the following subsections:

• Section 5.3.4.1.1, "Configure Node Manager"

• Section 5.3.4.1.2, "Verify Your Node Manager Configuration"

• Section 5.3.4.1.3, "Update Oracle WebCenter"

• Section 5.3.4.1.4, "How to Run the Oracle WebCenter Automated Script"

upgrade.py path_to_upgrade_properties_file administrator_password node_manager_password

cd WebCenter_ORACLE_HOME/common/bin
./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py

cd WebCenter_ORACLE_HOME/common/bin
./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py ~/upgrade.properties

cd WebCenter_ORACLE_HOME/common/bin
./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py ~/upgrade.properties example_admin_password

cd WebCenter_ORACLE_HOME/common/bin
./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py ~/upgrade.properties example_admin_password example_nm_password

http://download.oracle.com/javase/6/docs/api/java/util/Properties.html#load%28java.io.Reader%29

domain.directory=C:\\Middleware\\domains\\domain_name
oracle.home=C:\\Middleware\\Oracle_WC1
admin.user=weblogic
admin.url=t3://examplehost:7001
admin.server=AdminServer
nodemanager.user=node_manager_user
nodemanager.host=localhost
nodemanager.port=5556
nodemanager.type=ssl
upgrade.custom.spaces=false

domain.directory=/home/Middleware/domains/domain_name
oracle.home=/home/Middleware/Oracle_WC1
admin.user=weblogic
admin.url=t3://examplehost:7001
admin.server=AdminServer
nodemanager.user=node_manager_user
nodemanager.host=localhost
nodemanager.port=5556
nodemanager.type=ssl
upgrade.custom.spaces=false

5.3.4.2 Updating Oracle WebCenter Using WLST Commands

If you choose not to configure the Node Manager, you can update your middle tier by using WLST commands. You must run the WLST commands from the same machine on which the Administration Server is running.

Before you upgrade Oracle WebCenter using WLST:

• Ensure that you have updated your Oracle WebCenter software by using Oracle WebCenter installer.

  For more information, see Section 3.6.2, "Downloading the Required Installer" and Section 3.6.3, "Start the Installer".

• Ensure that you have updated your database schemas.

  For more information, see Section 3.8, "Update Your Schemas with Patch Set Assistant".

To update Oracle WebCenter using WLST commands:

1. Stop the Administration Server and all Managed Servers.

2. Start WLST from the WebCenter Oracle home.

   On UNIX operating systems:

   cd WebCenter_ORACLE_HOME/common/bin
   ./wlst.sh
   

   On Windows operating systems:

   cd WebCenter_ORACLE_HOME\common\bin
   wlst.cmd
   

3. Ensure the external LDAP server is up and running, then run the upgradeOpss command in offline mode (without connecting to any server):

   On UNIX operating systems:

   upgradeOpss(jpsConfig='DOMAIN_HOME/config/fmwconfig/jps-config.xml', jaznData='MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml')
   

   On Windows operating systems:

   upgradeOpss(jpsConfig='DOMAIN_HOME\config\fmwconfig\jps-config.xml', jaznData='MW_HOME\oracle_common\modules\oracle.jps_11.1.1\domain_config\system-jazn-data.xml')
   

   Note:

   If you need to re-run the upgradeOpss() command, you must exit the current WLST session and start a new session before re-running upgradeOpss().

4. Run the upgradeWebCenterDomain command in offline mode:

   upgradeWebCenterDomain(domainDirName='DOMAIN_HOME', oracleHome='WebCenter_ORACLE_HOME', upgradeCustomSpaces=[1|0])
   

   Where:

   • 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 use your extensions in WebCenter Spaces, refer to:

     http://www.oracle.com/technetwork/middleware/webcenter/owcs-ps4-wcs-ext-samples-wp-406559.pdf

     WARNING:

     If you upgrade your WebCenter domain with upgradeCustomSpaces set to 0, none of your previous customizations and resources that you developed, like page templates and skins, will be available in the upgraded WebCenter Spaces instance; there is no facility to migrate WebCenter Spaces customizations after the upgrade process.

   For example:

   upgradeWebCenterDomain(domainDirName='/home/Oracle/Domains/wc_domain', oracleHome='/home/Oracle/Middleware/Oracle_WC1', upgradeCustomSpaces=1)
   

   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 error messages, refer to Oracle Fusion Middleware Release Notes.

5. Start the Administration Server.

6. Connect to the Administration Server.

   connect()
   

7. In the domain running the WebCenter Spaces Managed Server, run the upgradeWebCenterPermissions command to add the required permission to the LDAP store.

   upgradeWebCenterPermissions()
   

   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 error messages, refer to the Oracle Fusion Middleware Release Notes.

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 need to pack and unpack your domain to replicate the changes to other nodes in your cluster.

   To pack and unpack your updated domain:

   1. Pack the Administration Server:

      cd WebCenter_ORACLE_HOME/common/bin
      ./pack.sh -managed=true -domain=DOMAIN_HOME -template=wcdomaintemplate.jar -template_name=wc_domain_template
      

   2. Copy wcdomaintemplate.jar to the WebCenter_ORACLE_HOME/common/bin on the other machines.

   3. Remove or move the old domain directories (DOMAIN_HOME and APPLICATION_HOME) on the other machines.

   4. Unpack the domain on each of the other machines:

      cd WebCenter_ORACLE_HOME/common/bin
      ./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.

    Note:

    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 Roles/Policies 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 running the WebCenter Spaces managed server, run the upgradeWebCenterApplication command.

    upgradeWebCenterApplication(appName='webcenter')
    

    If you have a cluster environment where there are multiple servers with WebCenter Spaces deployed, you must specify the server name. For example:

    upgradeWebCenterApplication(appName='webcenter', server="server_name")
    

12. Copy the Trust Store file from the Oracle home directory to the Oracle WebLogic Server domain directory.

    For example:

    cp MW_HOME/oracle_common/modules/oracle.jps_11.1.1/jps-wls-trustprovider.jar
            DOMAIN_HOME/lib/mbeantypes/jps-wls-trustprovider.jar
    

13. Restart the Administration Server and the Managed Servers in the domain.

5.3.5.1 Migrating Oracle Wiki Pages and Blogs

This section contains the following sections to help you migrate your existing Wiki pages and blogs for use in the newly patched Oracle WebCenter domain:

• Section 5.3.5.1.1, "How to Migrate Oracle Wiki Pages and Blogs"

• Section 5.3.5.1.2, "Troubleshooting Problems During Wiki Migration"

WebCenter_ORACLE_HOME/webcenter/archives/wiki-upgrade.jar

http://server:port/owc_wiki/page/show.jz?inline=1&scope=#{communityContext.communityName}&theme=#{adfFacesContext.skinFamily}

[INFO] PROCESSING Domain: domain_name
[INFO] migrating to temp folder - there is no webcenter page information stored on the domain: domain_name

[INFO] PROCESSING Domain: domain_name
[INFO] migrating to temp folder - invalid group space that corresponds to the guid: group_space_guid

[INFO] PROCESSING Domain: domain_name
[INFO] migrating to temp folder - no group space that corresponds to the guid: group_space_guid

[INFO] PROCESSING Domain: domain_name
[ERROR] migrating to temp folder - no UCM folder for the groupspace exists: page_name, gsname: group_space_name

[INFO] PROCESSING Domain: domain_name
[ERROR] migrating to temp folder - could not get UCM folder for the wiki domain, page: page_name, gsname: group_space_name

[INFO] PROCESSING Domain: domain_name
[ERROR] migrating to temp folder - no UCM folder exists for the user: user_name, page: page_name

[INFO] PROCESSING Domain: domain_name
[ERROR] migrating to temp folder - could not get personal UCM folder for the user: user_name, page: page_name

[INFO] PROCESSING Domain: domain_name
[INFO] migrating to temp folder - default scope, but no user specified on page: page_name

[INFO] PROCESSING Domain: domain_name
[INFO] sourceUrl: source_url
[INFO] migrating to temp folder - the page source url is not pointing to the correct domain, page: page_name, wcURL: wcURL

[INFO] PROCESSING User Blog: blog_name
[INFO] migrating to temp folder - could not get user UCM folder for the user: user_name

[INFO] PROCESSING User Blog: blog_name
[INFO] migrating to temp folder - could not get UCM folder for the user: user_name

5.3.5.2 Migrating Content Presenter Custom Templates

Content Presenter custom templates used in Release 11.1.1.3.0 applications are not automatically migrated when you upgrade to Release 11.1.1.6.0. You must register the required custom templates in Release 11.1.1.6.0 version of your applications.

To migrate Content Presenter custom templates from Release 11.1.1.3.0:

1. In JDeveloper 11.1.1.6.0, create or open a WebCenter Portal application.

2. On the filesystem, copy your Release 11.1.1.3.0 .jsff files to your Release 11.1.1.6.0 application.

   From the Release 11.1.1.3.0 version of your application, copy the required custom template from following folder:

   PROJECT_ROOT/public_html/oracle/webcenter/content/templates/custom

   Copy the custom template to the following folder of your upgraded Release 11.1.1.6.0 application:

   PROJECT_ROOT/public_html/oracle/webcenter/portalapp

3. In JDeveloper, create the Content Presenter custom template as a portal resource. The properties that you set for the custom template must match those that were previously registered in your Release 11.1.1.3.0 application.

   For information, see "Export a Content Presenter Display Template as a Portal Resource" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

4. Redeploy your application using the new custom Managed Servers, as described in Section 5.3.5.8, "Redeploying your Custom Applications to Upgraded Custom Managed Servers."

5. If the custom template is also used in WebCenter Spaces, prepare the template to be used in your upgraded environment:

   1. Using JDeveloper, export the Content Presenter display template as a portal resource.

   2. Log in to the Spaces application and navigate to Spaces Administration.

   3. Select Resources > Content Presenter and upload your template.

   For information, see "Using Content Presenter Display Templates in a Framework Application" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

5.3.5.3 Updating the Configuration for WebCenter REST APIs

Before you can use the WebCenter Representational State Transfer (REST) APIs, you must perform the server-side configurations. You must configure an identity asserter. You must also seed the required entries in the credential store, which enables the REST security tokens to function properly.

This section includes the following subsections:

• Section 5.3.5.3.1, "Configure an Identity Asserter"

• Section 5.3.5.3.2, "Configure the Credential Store"

For more information about security tokens, see "Security Considerations for CMIS REST APIs" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

createCred(map="o.webcenter.jf.csf.map", key="keygen.algorithm",
    user="keygen.algorithm", password="AES")
createCred(map="o.webcenter.jf.csf.map", key="cipher.transformation",
    user="cipher.transformation", password="AES/CBC/PKCS5Padding") 

5.3.5.4 Updating Multi-Calendar Layouts

In Release 11.1.1.2.0 and 11.1.1.3.0, the Calendar Overlay Style FULL could be used to enable multiple calendars for some events task flow and add multiple Space calendars in one events task flow. In the upgraded Release 11.1.1.6.0, the Events task flow no longer displays multiple calendars; only the current Space calendar is displayed.

To work around this issue, you must enable the calendar overlaying feature for the Events task flow. Go to the page editor, find the Calendar Overlay Style parameter and select Full from the list of available options. For more information, see "Enabling Calendar Overlaying" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

5.3.5.5 Restoring Your OmniPortlet and WebClipping Customizations

After you have saved your customizations (Section 5.3.3.1, "Save Your OmniPortlet and WebClipping Customizations") and successfully patched your software, you must restore OmniPortlet and WebClipping configuration and customizations as follows:

1. Navigate to the following directories:

   On UNIX operating systems:

   • path_to_war_directory/WEB-INF/providers/omniPortlet

   • path_to_war_directory/WEB-INF/providers/webclipping/

   Where path_to_war_directory refers to DOMAIN_HOME/servers/WLS_PORTAL/tmp/_WL_user/portalTools_version/randomly_generated_directory/war

   On Windows operating systems:

   • path_to_war_directory\WEB-INF\providers\omniPortlet

   • path_to_war_directory\WEB-INF\providers\webclipping/

   Where path_to_war_directory refers to DOMAIN_HOME\servers\WLS_PORTAL\tmp\_WL_user\portalTools_version\randomly_generated_directory\war

   DOMAIN_HOME is the domain home locations for your Oracle Portal or Oracle WebCenter domain, as specified on the "Specify Domain Name and Location" screen in the Configuration Wizard.

   Note:

   Since the Patch Set Installer re-deployed the OmniPortlet and WebClipping applications, the new path may be different than the path from where you backed up customizations.

2. Replace these directories with their backed up copies.

   For example, to restore the omniportlet directory, you can use the following commands:

   On a UNIX operating system:

   cp -fr backup_location path_to_war_directory/WEB-INF/providers/omniPortlet
   

   On a Windows operating system:

   xcopy /y/e backup_location path_to_war_directory\WEB-INF\providers\omniPortlet
   

3. If applicable, in the Oracle Portal domain, restart the Managed Server WLS_PORTAL.

4. In the WebCenter domain, restart the Managed Server WC_Portlet.

5.3.5.6 Extending a Domain to Install Oracle WSM Policy Manager

When you upgrade Oracle WebCenter, existing WSM-PM applications and associated datasource are re-targeted to the WC_Collaboration managed server. If your upgraded WebCenter domain has discussions server installed, you must extend the domain to install Oracle WSM Policy Manager if not already installed.

To extend a WebCenter domain to install Oracle WSM Policy Manager:

1. Stop the Admin server and all managed servers.

2. Start the Configuration Wizard on the machine running the Admin server.

   On UNIX, run WebCenter_ORACLE_HOME/common/bin/config.sh.

   On Windows, run WebCenter_ORACLE_HOME\common\bin\config.cmd.

3. Select Extend an existing WebLogic domain and click Next.

4. Select your domain and click Next.

5. Select the checkbox for Oracle WSM Policy Manager and click Next.

6. Enter the connection details for OWSM MDS Schema and click Next.

7. Click Next on the remaining screens until you get the Configuration Summary screen, then click Extend.

   For more information on extending a domain, see "Extending a WebLogic Domain in Graphical Mode" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.

   Note:

   If your domain is running on multiple machines, you must pack the domain on the machine running the Administration Server and unpack on the other machines. For information, see Section 5.3.4.2, "Updating Oracle WebCenter Using WLST Commands."

5.3.5.7 Remove openusage Properties in setDomainEnv

If you want to extend your WebCenter domain to install Oracle WebCenter Portal's Analytics Collector, you must remove the openusage properties:

1. Remove the openusage properties from EXTRA_JAVA_PROPERTIES in DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems) or DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows operating systems).

   Specifically, the entries that need to be removed are:

   EXTRA_JAVA_PROPERTIES="-Doracle.wc.openusage.clustername=localhost
   -Doracle.wc.openusage.collectorport=port_number
   -Doracle.wc.openusage.timeout=30
   -Doracle.wc.openusage.unicast=true
   -Doracle.wc.openusage.enabled=false
   ${EXTRA_JAVA_PROPERTIES}"
   export EXTRA_JAVA_PROPERTIES
   

   Note:

   These entries may appear multiple times in setDomainEnv.sh or setDomainEnv.cmd. So ensure that all the entries are removed.

   If you extend your domain to add new products, you may need to repeat the task of removing the openusage properties from setDomainEnv.

2. Restart all the servers in the WebCenter domain.

5.3.5.8 Redeploying your Custom Applications to Upgraded Custom Managed Servers

If there are custom Managed Servers in your domain, they may not have the correct libraries targeted. Therefore you must upgrade them after patching WebCenter, and redeploy your custom applications.

To upgrade custom managed servers:

1. Remove the old custom Managed Servers.

2. Run the Configuration Wizard to extend your existing WebCenter domain and apply custom templates.

   1. On the "Select Extension Source" screen, select Extend my domain using an existing extension template.

   2. Navigate to the WebCenter_ORACLE_HOME/common/templates/applications (on UNIX operating systems) or WebCenter_ORACLE_HOME\common\templates\applications (on Windows operating systems) directory and locate the following templates:

      oracle.wc_custom_portal_template_11.1.1.jar (for WebCenter custom applications/Framework applications)

      oracle.wc_custom_services_producer_template_11.1.1.jar (for WebCenter Custom Producer/Portlet Producer applications)

   3. Select the desired template and complete the domain extension process.

3. Re-deploy your custom applications using the new custom Managed Servers.

   Note:

   Oracle recommends that you open your projects in Oracle JDeveloper and migrate your applications to the latest version before deploying to the new custom Managed Servers.

5.3.5.9 Remove the LD_LIBRARY_PATH Entry from the setDomainEnv Script

Before patching Oracle WebCenter, you must remove the following entry from the setDomainEnv script:

LD_LIBRARY_PATH="${WL_HOME}/server/native/linux/i686${CLASSPATHSEP}${LD_LIBRARY_PATH}"
export LD_LIBRARY_PATH 

The setDomainEnv script is available at the following path:

• DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems)

• DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows operating systems)

5.3.5.10 Migrating WSRP Portlet Preferences

By default, all custom JSR286 portlets (created using Portlet Creation Wizard) use a file-based preference store. Post upgrade, you must move WSRP portlet preferences from:

$MW_HOME/Oracle_WC1/portal/portletdata
 

To:

$MW_HOME/oracle_common/portal/portletdata

Where, MW_HOME refers to Middleware Home, and Oracle_WC1 refers to WebCenter Portal Oracle Home.

You can move WSRP portlet preferences manually or by using a migration utility. For more information, see "Portlet Preference Store Migration Utilities" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

5.3.6.1 Setting the Web Context Root on the UCM Connection

If Universal Content Management (UCM) and WebCenter instances are configured for access through a common Oracle HTTP server, the Web Server Context Root property (WebContextRoot) on the existing UCM connection can be set to make UCM features available in the WebCenter application via an iFrame. The UCM connection can be set either through Fusion Middleware Control or WLST using the setJCRContentServerConnection command. For information, see "Setting Connection Properties for the Spaces Content Repository" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

5.3.6.2 Configuring Group Space Workflows

If your WebCenter instance had Group Space Workflows configured, after upgrading to the latest release, you must redeploy sca_CommunityWorkflows.jar and WebCenterWorklistDetailApp.ear.

To configure Group Space Workflows:

1. Log in to Fusion Middleware Control.

2. Deploy sca_CommunityWorkflows.jar to the SOA managed server. This file is located at the following path in your Oracle SOA installation:

   SOA_ORACLE_HOME/webcenter/modules/oracle.webcenter.sca_11.1.1/sca_CommunityWorkflows.jar
   

   Where, SOA_ORACLE_HOME refers to the Oracle SOA installation directory.

   Note that version 11.1.1.6.0 is active in the console, and other older versions like 11.1.1.5.0 are inactive.

3. Undeploy WebcenterWorklistDetailApp.ear, and then redeploy it to the SOA managed server. You can find the application at the following location in your Oracle SOA installation:

   SOA_ORACLE_HOME/webcenter/applications/WebCenterWorklistDetailApp.ear
   

Refer to "Deploying the Application to a WebLogic Managed Server" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter for instructions on how to deploy WebCenter applications.

5.3.6.3 Reconfiguring a Default Template Set for Group Spaces

In Release 11.1.1.2.0 and 11.1.1.3.0, the WebCenter Spaces administrator had the ability to set default page template for both personal spaces and group spaces. From Release 11.1.1.4.0 onward, the option of setting a default page for group spaces is no longer available.

To reconfigure a default page template for your upgraded group spaces:

1. As an administrator, export webcenter-config.xml.xml:

   1. Start the WebLogic Scripting Tool (WLST).

      On UNIX operating systems:

      cd WebCenter_ORACLE_HOME/common/bin
      ./wlst.sh
      

      On Windows operating systems:

      cd WebCenter_ORACLE_HOME\common\bin
      ./wlst.cmd
      

      For more information, see "Running Oracle WebLogic Scripting Tool (WLST) Commands" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

   2. Connect to the Administration Server for WebCenter Portal. For example:

      connect(username='weblogic', password='mypassword', url='myhost.example.com:7001')
      

   3. Run the exportMetadata WLST command to export application metadata:

      exportMetadata(application, server, toLocation, docs, [restrictCustTo], [excludeAllCust], [excludeBaseDocs], [excludeExtendedMetadata], [fromLabel], [toLabel], [applicationVersion])
      

      For example:

      exportMetadata(application='webcenter', server='WC_Spaces', toLocation='/tmp/myrepos', docs='/oracle/webcenter/webcenterapp/metadata/mdssys/cust/site/webcenter/webcenter-config.xml.xml')
      

      For more information see "exportMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

2. Navigate to the exported directory (for example, /tmp/repos on a UNIX operating system or C:\TEMP\repos on a Windows operating system). From webcenter-config.xml, remove the <defaultGSSiteTemplateId> parameter, and save the file.

   If the defaultGSSiteTemplateId parameter was changed in your previous WebCenter installation, the parameter is available in webcenter-config.xml.xml here: oracle/webcenter/webcenterapp/metadata/mdssys/cust/site/webcenter/webcenter-config.xml.xml

   If the defaultGSSiteTemplateId parameter was not changed, it will be commented out. You must uncomment the parameter in the file available here:

   /oracle/webcenter/webcenterapp/metadata/webcenter-config.xml

3. As an administrator, import the document.

   1. Start WLST.

   2. Connect to the Administration Server for WebCenter Portal.

   3. Run the importMetadata WLST command:

      importMetadata(application, server, fromLocation, docs, [restrictCustTo], [excludeAllCust], [excludeBaseDocs], [excludeExtendedMetadata], [cancelOnException], [applicationVersion])
      

      For example:

      importMetadata(application='webcenter', server='WC_Spaces', fromLocation='/tmp/myrepos', docs='/**')
      

      For more information see "importMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

4. Verify that 'system default' now appears for the Page Template setting in Space Administration.

5.3.6.4 Updating the Timezone Attribute in WebCenter Spaces

In Release 11.1.1.2.0, the Timezone attribute in WebCenter Spaces is a free-form text field. From Release 11.1.1.4.0 onward, this attribute was changed to a drop-down list.

If you are upgrading WebCenter Spaces from Release 11.1.1.2.0, the Timezone attribute is not carried over, and you must manually select the appropriate timezone from the drop-down list.

5.3.6.5 Updating the Group Spaces Display Mode

If you are upgrading WebCenter Group Spaces from Release 11.1.1.2.0 or 11.1.1.3.0, you must update the metadata of your Group Spaces to ensure that they display correctly.

To update a Group Space to display correctly:

1. Export the group space. For information, see the "Exporting Spaces" section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

2. At a command prompt, go to the directory where you saved the export archive.

3. Extract the metadata from the export archive.

   For example, the following code extracts the export archive named export.ear, which contains transport.mar. The code further extracts transport.mar in a directory named mar.

   1. jar xvf export.ear transport.mar

   2. mkdir mar

   3. cd mar

   4. jar xvf ../transport.mar

   The transport.mar file contains space.xml that you must edit to update the group space's display mode.

4. Open the space.xml file from the following path:

   oracle/webcenter/space/metadata/spaces/spaceName/space.xml

   Where, spaceName refers to the name of the group space whose display mode you are updating.

5. Delete the entire <shell-chrome-type> entry from space.xml.

6. Update the export archive.

   For example, the following code updates the space.xml file in transport.mar, and then updates transport.mar in export.ear.

   1. jar uvfM ../transport.mar oracle/webcenter/space/metadata/spaces/spaceName/space.xml

   2. cd ..

   3. jar uvfM export.ear transport.mar

7. Import the group space. For information, see the "Importing Spaces" section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

5.3.6.6 Choosing a Default Start (or Landing) Page

By default, when you log in to the Spaces application, the last accessed page is displayed. This behavior can be overridden by setting the oracle.webcenter.spaces.disableLastAccessPageBehavior system property to false in the setDomainEnv domain startup script. This script is available at DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems) or DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows operating systems).

If you had overridden the default behavior, you must re-apply this change after patching Oracle WebCenter.

5.3.6.7 Migrating WebCenter Spaces Custom Library

WebCenter Spaces can be customized, for example to deploy additional shared libraries that include custom code or some additional resources like task flows, page styles, and skins. If you deployed any custom page styles by extending Spaces through the custom library custom.webcenter.spaces.war, then after patching you must modify the entry for each page style in the custom library and redeploy custom.webcenter.spaces.war.

If you migrated your WebCenter Spaces customizations:

1. In JDeveloper, open ExtendWebCenterSpaces.jws (11.1.1.2.0 or 11.1.1.3.0).

2. For each and every deployed page style, find the following:

   <af:pageTemplate
   

   And replace it with the following:

   <af:pageTemplate
   value="#{bindings.shellTemplateBinding.templateModel}" id="T"
   

3. For each and every pageDef, find the following:

   <page>
   

   And replace it with the following:

   <page viewId="#{WCAppContext.application.siteTemplateManager.currentSiteTemplateViewId}" id="shellTemplateBinding" Refresh="ifNeeded" />
   

4. Redeploy the custom.webcenter.spaces.war shared library to your Spaces 11.1.1.6.0 managed server.

   Note:

   Always use Oracle JDeveloper 11.1.1.2 or 11.1.1.3 to build and deploy extensions developed for this release. For detailed steps, see the links for white papers "Extending WebCenter Spaces (11.1.1.2.0)" or "Extending WebCenter Spaces (11.1.1.3.0)" on Oracle Technology Network: http://www.oracle.com/technetwork/middleware/webcenter/portal/overview/index.html

5.3.6.8 Upgrading Process Spaces

Oracle Business Process Management (Oracle BPM) Process Spaces is a workspace built on top of Oracle WebCenter Spaces, and provides Spaces that are designed specifically for modeling and executing business processes. If you have Process Spaces installed, then after patching to WebCenter Portal 11.1.1.6.0, you must upgrade it by running the install.xml script. The installation script can be used for a single-server configuration as well as a cluster configuration.

For more information about the Process Spaces functionality, refer to "Understanding Oracle Business Process Management Process Spaces" in Oracle BPEL Process Manager User's Guide.

To upgrade Process Spaces installed in your upgraded WebCenter instance:

1. Take the Process Workspace and Modeling Space offline.

   1. Log in to WebCenter Spaces.

   2. Click the Administration link to open WebCenter administration pages.

   3. Under the Spaces tab, select the Modeling Space row.

   4. From the Edit menu, select Offline for Maintenance.

   5. In the Bring Space Offline dialog, click OK.

   6. Repeat this procedure to take Process Workspace offline.

2. Copy the SOA_ORACLE_HOME/bpm/process_spaces (on UNIX) or SOA_ORACLE_HOME\bpm\process_spaces (on Windows) folder from the SOA Oracle home directory to any location from where it can connect to the WebCenter installation.

3. Open the process-portal-install.properties file located in the process_spaces folder and specify the required Oracle BPM and WebCenter properties as listed in Table 5-6.

   Note:

   For security purposes, you can skip specifying the passwords, and provide them later when prompted.

   Table 5-6 Properties Specified in process-portal-install.properties

   Property	Description
   extendSoa	Specify the value as true if WebCenter and SOA are in the same domain, else false.
   promptForPasswords	The flag to decide whether to prompt for passwords or read them from the process-portal-install.properties file while running the installer.
   Oracle BPM Schema Details
   bpmDBUser	User name to connect to the database configured for Oracle BPM
   bpmDBPassword	Password to connect to Oracle BPM's database
   bpmDBType	Database type configured for Oracle BPM
   bpmDBDriver	Driver used to connect to Oracle BPM's database
   bpmDBUrl	URL of Oracle BPM's database, like jdbc:oracle:thin:@adc2170307:1521
   Oracle BPM MDS Details
   bpmMDSUser	User name for the MDS schema used for Oracle BPM
   bpmMDSPassword	Password for Oracle BPM's MDS schema
   Oracle BPM Runtime Details
   bpmServerURL	Oracle BPM server URL. For a single BPM server: t3://<bpmHost>:<bpmRuntimePort> For example: t3://myHost:8001 For BPM cluster, specify separated list of BPM server URLs for all servers in the cluster in the following format: t3://host1:port1,host2:port2,... For example, t3://myHost1:8001,myHost2:8002,myHost3:8003
   bpmAdminUser	Name of the user that has Administrator privileges on the Oracle BPM server
   bpmAdminPassword	Password for the Oracle BPM Admin user
   WebCenter Spaces Installation Details
   wcOracleHome	Path to the WebCenter Oracle home directory
   wcDomainName	Name of the domain where WebCenter is installed. If extendSoa flag is set to true, point to the BPM domain.
   wcSetDomainRealmPassword	Flag to control whether to set the domain realm password; set the value to either true or false. Note: This property is for setting up Global Trust. It is recommended that you set Global Trust manually; so set this property to false.
   wcDomainRealmPassword	Password to set up trusted domains. Same password must be set on Oracle BPM domain as well. Note: This property is for setting up Global Trust. It is recommended that you set Global Trust manually, and not by using this property.
   wc.server.port	Port on which WC_Spaces managed server is hosted
   WebCenter's WebLogic Installation Details
   wcHost	Host name on which WebCenter's Administration server is running
   wcAdminPort	Port number on which WebCenter's Administration server is running
   wcAdminUser	Admin user for the WebCenter Administration server
   wcAdminPwd	Password of the WebCenter Administration server
   wcManagedServerName	In a single-server environment, specify the name of the managed server where Spaces is deployed. In a clustered environment, specify the name of any one of the Spaces managed servers that is part of the cluster.
   wcConfigServices	Flag to configure the Oracle Content Server and Discussions Server to work with Oracle WebCenter. The Content Server and Discussion Server details listed later in this table must be specified only if wcConfigServices is set to true. Note: It is strongly recommended that instead of using the install.xml script, you manually configure Oracle Content Server and Discussions Server to work with Oracle WebCenter. For information, see the "Managing Content Repositories" and "Managing the Announcements and Discussions Services" chapters in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
   isWebcenterClusterConfig	Flag to specify whether WebCenter Portal installation is configured for a cluster. Set to true if it is a cluster configuration.
   wcSpacesClusterName	Name of the Spaces application's cluster. Set this property only if isWebcenterClusterConfig is set to true.
   Content Server Details	Set these properties if wcConfigServices is set to true.
   wcContentServerName	Name of the Oracle Content Server configured for Oracle WebCenter
   wcContentServerPort	Port on which Oracle Content Server is running.
   wcContentSpacesRoot	Name of the Spaces root folder on Oracle Content Server
   wcContentAdminUser	Name of the Admin user for Oracle Content Server
   Discussions Server Details	Set these properties if wcConfigServices is set to true.
   wcDiscussionServerUrl	Name of the Discussions Server configured for WebCenter
   wcDiscussionAdminUser	Name of the Admin user for Discussions Server

   
   

4. Make sure you have ant and Java JDK installed.

   Ant is shipped with Oracle BPM. You can find the installer under the path SOA_ORACLE_HOME/modules/org.apache.ant_1.7.0.

5. Ensure that the PATH and CLASSPATH environment variables are set for both ant and Java JDK.

6. Run the ant script install.xml located in the process_spaces folder:

   ant -f install.xml -DpromptForPasswords=true
   

7. If wcConfigServices has been set to true in process-portal-install.properties:

   1. Restart WC_Spaces.

   2. Run the following ant command:

      ant -f install.xml post-install -DpiArgs -importGSOnly
      

8. If Oracle BPM and Oracle WebCenter have been configured in different domains, configure Trusted Domain Credentials in both the Oracle BPM and WebCenter domains.

   For more information, see "Enabling Trust Between WebLogic Server Domains" in Oracle Fusion Middleware Securing Oracle WebLogic Server.

9. Start Oracle BPM. For information, see "Configuring Oracle SOA Suite and Oracle Business Process Management Suite" in Oracle Fusion Middleware Installation Guide for Oracle SOA Suite.

   Note:

   If you do not start Oracle BPM, you may face problems logging into WebCenter Spaces.

   If required, bring the Process Workspace and Modeling Space online by selecting Bring the Space(s) Online from the Edit menu, as described in step 1.

10. In WebCenter Spaces, delete the old process spaces, templates, and resources, if required.

    When you run the install.xml ant script, release 11.1.1.4.0 or 11.1.1.5.0 process spaces and related templates and resources are imported with '11.1.1.6.0' appended to their names. So, after the upgrade, there are two sets of process spaces and related templates and resources, for example 'Process Workspace 11.1.1.6.0' and 'Process Workspace'. If you do not want the old items, you can delete them manually. For information, see the following sections in Oracle Fusion Middleware User's Guide for Oracle WebCenter: Deleting a Space, Deleting a Space Template, and Deleting a Resource Catalog.

5.3.7.1 Configuring Web Services Security for Discussions

In Release 11.1.1.6.0, discussions server is shipped with no message protection for Web Service interaction between discussions server and Spaces; this allows you to use discussions server without any further configuration. In your pre-patched Oracle WebCenter environment, if Oracle WebCenter Discussions was installed and the WebService call was protected with WS-Security, you must reapply this configuration after upgrading to the latest release.

To configure Web Services security for discussions server:

1. Configure the domain keystore.

   For more information, see "Configuring WS-Security" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

2. Setup WS-Security on the discussions server:

   1. Using the Enterprise Manager console, access the owc_discussions application and navigate to the WebServices section.

   2. Select the OWCDiscussionsServiceAuthenticated end point and attach the oracle/wss11_saml_token_with_message_protection_service_policy policy.

   3. Select the OWCDiscussionsServicePublic end point and attach the oracle/wss11_message_protection_service_policy policy.

   4. Restart the WC_Collaboration Managed Server.

3. Secure the Spaces ForumConnection:

   Using WLST:

   1. Connect to the domain server.

   2. Set the policy and recipient key alias. For example:

      setDiscussionForumConnection('webcenter', name='forum-con-name',
      policyURIForAuthAccess='oracle/wss11_saml_token_with_message_protection_client_policy',
      policyURIForPublicAccess='oracle/ wss11_message_protection_client_policy',
      recipientKeyAlias='orakey')
      

   3. Restart the WC_Spaces Managed Server.

   If you want to do this using Enterprise Manager, locate the forum connection and specify the policy and recipient key aliases as defined above.

5.3.7.2 Adding Oracle Single Sign-On Authentication Provider to the List of Authentication Providers

In the upgraded WebCenter environment, Oracle Single Sign-on (OSSO) Identity Asserter does not appear in the list of authentication providers. If you continue to use OSSO 10g even after upgrading to WebCenter Portal 11.1.1.6.0, you must update the setDomainEnv script to add the authentication provider.

To add the OSSO authentication provider:

1. Search for the following entry in the DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems) or DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows operating systems) file:

   ALT_TYPES_DIR="${ORACLE_HOME}/modules/oracle.ossoiap_11.1.1,${ORACLE_HOME}/modules/oracle.oamprovider_11.1.1
   

   Replace the entry with:

   ALT_TYPES_DIR="${COMMON_COMPONENTS_HOME}/modules/oracle.ossoiap_11.1.1,${COMMON_COMPONENTS_HOME}/modules/oracle.oamprovider_11.1.1
   

2. Restart the Administration Server.

5.3.8.1 Installing Activity Graph, Analytics, Pagelet Producer, Personalization Server, and WebCenter Services Portlets

Compared to release 11.1.1.2.0 or 11.1.1.3.0, Oracle WebCenter Portal 11.1.1.6.0 includes several new features, including:

• Activity Graph, which provides suggestions of people that a user may be interested in connecting with, based on existing connections and shared interaction with objects within an application

• Analytics, which allows you to track and analyze Spaces usage

  Note:

  If you want to extend your WebCenter domain to install Oracle WebCenter Portal's Analytics Collector, you must remove the openusage properties. For information, see Section 5.3.5.7, "Remove openusage Properties in setDomainEnv."

• Pagelet Producer, which provides a collection of useful tools and features that facilitate dynamic pagelet development

• Personalization Server, which can deliver targeted content

• WebCenter Services Portlets, which enables you to expose WebCenter Portal service task flows in other applications as WSRP portlets or pagelets. You can consume WebCenter Services Portlets in the following applications: Oracle Portal, Oracle WebLogic Portal, and Oracle WebCenter Interaction.

For more information about these features as well as other WebCenter components, see "Getting Started with WebCenter Portal Components" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter and see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

To take advantage of these new features, you must extend your domain by installing the required WebCenter components.

To extend your domain to install these WebCenter components:

1. Decide on the products and topology for your environment.

   To verify that your system meets the necessary minimum requirements, refer to the following documents:

   1. Oracle Fusion Middleware System Requirements and Specifications:

      http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html
      

      This document contains information related to hardware and software requirements, minimum disk space and memory requirements, database schema requirements, and required system libraries, packages, or patches.

   2. Oracle Fusion Middleware Supported System Configurations:

      http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
      

      This page contains various certification documents for current and previous product releases. The System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document contains certification information related to supported 32-bit and 64-bit operating systems, databases, web servers, LDAP servers, adapters, IPv6, JDKs, and third-party products.

   3. Oracle Fusion Middleware Interoperability and Compatibility Guide

      This document covers the compatibility and interoperability issues that may arise when installing or upgrading Oracle Fusion Middleware 11g products.

2. Use Repository Creation Utility (RCU) to install any necessary schemas.

   Analytics and Activity Graph require the ACTIVITES schema. WebCenter Services Portlets requires three additional schemas: MDS, WEBCENTER, and PORTLET. These schemas must be mapped to the data sources mds-ServicesProducerDS, WC-ServicesProducerDS, and Portlet-ServicesProducerDS, respectively. No additional schemas are required for Pagelet Producer or Personalization Server.

   See "Oracle WebCenter Schemas" for information about required WebCenter schemas, and "Obtaining and Running Repository Creation Utility" for instructions on how to install the schemas with RCU. Both these topics are in Oracle Fusion Middleware Repository Creation Utility User's Guide.

3. Run the Configuration Wizard.

   See "Starting the Oracle Fusion Middleware Configuration Wizard" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter for instructions.

4. Extend the domain by selecting the following products from the products Configuration Wizard: Oracle WebCenter Analytics Collector, Oracle WebCenter ActivityGraph Engines, Oracle WebCenter Pagelet Producer, Oracle WebCenter Personalization, and Oracle WebCenter Services Portlets.

   For a simple topology, see "Extending an Existing Domain" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter for instructions.

If you have cluster or distributed environment, refer to:

• Chapter "Extending the Domain for WebCenter Components" in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

• Chapter "Configuring High Availability for Oracle ADF and WebCenter Applications" in Oracle Fusion Middleware High Availability Guide

5.3.8.2 Upgrading WebCenter Custom Applications to Add Portal Framework Features

Oracle WebCenter Portal: Framework supports various new features such as page navigations and page hierarchies. You can manually add WebCenter Portal Frame file structures, components, and configurations to your custom WebCenter applications that have been migrated to 11.1.1.6.0.

For information, see the "Manually Migrating a Framework Application" appendix in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.