In release 11.1.1.8.3, only new installations of Oracle WebCenter Portal can leverage the FrameworkFolders support. For existing Oracle WebCenter Portal installations that are already using Folders_g, you must continue to use the Folders_g interface and must not enable FrameworkFolders.

Note:

Oracle recommends that all products must be patched to their latest released versions. There is no particular order in which the products must be patched unless specified.

Chapter 3 provides instructions for patching your existing Oracle Fusion Middleware software to the latest version, whereas this chapter provides instructions for patching Oracle WebCenter Portal. Many of the steps listed in this chapter refer back to Chapter 3 or other chapters of this guide. If you have already completed any generic steps, like performing pre-patching generic tasks, patching Fusion Middleware products other than Oracle WebCenter Portal, or updating schemas, as per instructions in Chapter 3, you may skip those steps.

6.2 Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation

Figure 6-1 illustrates the steps required to patch an Oracle WebCenter Portal Release 11.1.1.7.0 installation to Release 11.1.1.8.0. Table 6-2 describes each of these steps in detail. Click the required steps in the table to navigate to the information for each step.

Note:

Many of the steps listed in Figure 6-1 and Table 6-2 refer back to chapter 3 or other chapters of this guide. If you have already completed any generic steps, like performing pre-patching generic tasks, patching Fusion Middleware products other than WebCenter Portal, or updating schemas, as per instructions in Chapter 3, you may skip those steps.

Export Web service deployment descriptors for portlet producers that are secured with OWSM security policies

Mandatory

If Oracle WebCenter Portal's Services Portlets producer or any custom portlet producers are deployed and secured with OWSM security policies, export the Web service deployment descriptors for those portlet producers to a Java Archive (JAR) file.

Before patching Oracle WebCenter Portal, make sure your system environment and configuration meet the minimum requirements and the backups are in place. Also, you must patch Oracle WebLogic Server to the latest supported release.

If you are patching your software in silent mode, rename the emCCR file.

6.3 Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation

Figure 6-2 illustrates the steps required to patch an Oracle WebCenter Portal installation from Release 11.1.1.6.0 to Release 11.1.1.8.0. Table 6-3 describes each of these steps in detail. Click the required steps in the table to navigate to the information for each step.

Note:

Many of the steps listed in Figure 6-2 and Table 6-3 refer back to chapter 3 or other chapters of this guide. If you have already completed any generic steps, like performing pre-patching generic tasks, patching Fusion Middleware products other than WebCenter Portal, or updating schemas, as per instructions in Chapter 3, you may skip those steps.

In Figure 6-2, WebCenter Portal-specific steps are highlighted in green.

If Oracle WebCenter Portal's Services Portlets producer or any custom portlet producers are deployed and secured with OWSM security policies, export the Web service deployment descriptors for those portlet producers to a Java Archive (JAR) file.

Before patching Oracle WebCenter Portal, make sure your system environment and configuration meet the minimum requirements and the backups are in place. Also, you must patch Oracle WebLogic Server to the latest supported release.

If you are patching your software in silent mode, you need to rename the emCCR file.

Download the installer for Oracle WebCenter Portal and other required products

Mandatory

Download the Oracle WebCenter Portal installer, which is a full installer that also functions as an update installer. At this stage, if required, you can also download installers for other Fusion Middleware products that you plan to patch, such as Oracle WebCenter Content and Oracle SOA Suite.

Note: If you have already downloaded the product installers as per instructions in Chapter 3, you may skip this step.

Before running Patch Set Assistant, check to make sure that your database is up and running and that the schema you want to upgrade is at the version supported for upgrade.

Note: For database-based OPSS policy store, upgrade the prefix_OPSS schema using Patch Set Assistant. Check whether schemas of other patched products need to be updated. You can update all the required schemas at this stage. You may skip this step if you have already upgraded schemas listed in Table 4-1, "Schemas That Require Updating for the Latest Release".

Figure 6-3 illustrates the steps required to update an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 installation to 11.1.1.8.0. Follow the instructions in Table 6-4 to navigate to the information for each step.

Note:

Many of the steps listed in Figure 6-3 and Table 6-4 refer back to chapter 3 or other chapters of this guide. If you have already completed any generic steps, like performing pre-patching generic tasks, patching Fusion Middleware products other than WebCenter Portal, or updating schemas, as per instructions in Chapter 3, you may skip those steps.

If Oracle WebCenter's Services Portlets producer or any custom portlet producers are deployed and secured with OWSM security policies, export the Web service deployment descriptors for those portlet producers to a Java Archive (JAR) file.

Before patching Oracle WebCenter Portal, make sure your system environment and configuration meet the minimum requirements and the backups are in place. Also, you must patch Oracle WebLogic Server to the latest supported release.

If you are patching your software in silent mode, you need to rename the emCCR file.

Download the installer for Oracle WebCenter Portal and other required products

Mandatory

Download the Oracle WebCenter Portal installer, which is a full installer that also functions as an update installer. At this stage, if required, you can also download installers for other Fusion Middleware products that you plan to patch, such as Oracle WebCenter Content and Oracle SOA Suite.

Note: If you have already downloaded the product installers as per instructions in Chapter 3, you may skip this step.

Before running Patch Set Assistant, you should check to make sure that your database is up and running and that the schemas you want to upgrade are at the versions that are supported for upgrade.

Note: For database-based OPSS policy store, upgrade the prefix_OPSS schema using Patch Set Assistant. Check whether schemas of other patched products need to be upgraded. You can upgrade all the required schemas at this stage. You may skip this step if you have already patched the schemas listed in Table 4-1, "Schemas That Require Updating for the Latest Release".

After patching to Release 11.1.1.8.0, you can optionally disable the Analytics Collector TRACE log level and enable the NOTIFICATION log level for a stable server performance. On the WC_Utilities managed server, the level attribute of the com.plumtree.analytics logger is set to value TRACE:32. Change this value to NOTIFICATION:16. For more information, see the "Setting the Level of Information Written to Log Files" section in Oracle Fusion Middleware Administrator's Guide.

6.5.1 Managed Server Changes

From Release 11.1.1.4.0 onward, managed servers have been renamed from WLS_name to WC_name, where name refers to the name of the managed server. For more information, see the "Oracle WebCenter Portal Managed Servers" section in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.

From Release 11.1.1.4.0 onward, a new managed server, WC_Utilities, is supported that hosts the following Oracle WebCenter Portal components: Analytics Collector, Activity Graph Engines, and Personalization.

6.5.2 Migration Roadmap for Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0

Figure 6-4 illustrates the steps required to patch an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 installation to 11.1.1.8.0. Follow the instructions in Table 6-5 to navigate to the information for each step.

Note:

Many of the steps listed in Figure 6-4 and Table 6-5 refer back to chapter 3 or other chapters of this guide. If you have already completed any generic steps, like performing pre-patching generic tasks, patching Fusion Middleware products other than WebCenter Portal, or updating schemas, as per instructions in Chapter 3, you may skip those steps.

Download the installer for Oracle WebCenter Portal and other required products

Mandatory

Download the WebCenter Portal installer, which is a full installer that can also function as an update installer. At this stage, you can also download the installers for any other FMW products that you plan to patch, such as Oracle WebCenter Content and Oracle SOA Suite.

Note: If you have already downloaded product installers as per instructions in Chapter 3, you may skip this step.

Note: For WebCenter Portal (previously called WebCenter Spaces) schemas that were originally installed using the Release 11.1.1.1.0 Repository Creation Utility and have subsequently been upgraded to Release 11.1.1.2.0/11.1.1.3.0, it is necessary to grant an additional privilege to the WebCenter Portal schema owner prior to running the Patch Set Assistant to upgrade the schema to Release 11.1.1.8.0. Connect as a SYSDBA user to the database containing the WebCenter Portal schema using SQL*Plus, and grant create view to the WebCenter Portal schema owner.

Note: For database-based OPSS policy store, upgrade the prefix_OPSS schema using Patch Set Assistant. Check whether schemas of other patched products need to be upgraded. You can upgrade all the required schemas at this stage. You may skip this step if you have already upgraded schemas listed in Table 4-1, "Schemas That Require Updating for the Latest Release".

Compared to Release 11.1.1.2.0 and 11.1.1.3.0, Oracle WebCenter Portal 11.1.1.8.0 includes several new features. You can extend the WebCenter Portal domain to add new features and can update your WebCenter custom applications, if required.

domainDirName - Replace DOMAIN_HOME with the full path to your Domain home directory.

oracleHome - Replace WCP_ORACLE_HOME with the full path to your WebCenter Portal Oracle home directory.

upgradeCustomSpaces - Set to 1 if you used the custom.webcenter.spaces shared library to customize WebCenter Portal (previously named WebCenter Spaces) and you want to migrate your customizations to the upgraded instance. For information about how to use your extensions in WebCenter Portal, refer to:

If you upgrade your Oracle WebCenter Portal 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 Portal instance; there is no facility to migrate WebCenter Portal customizations after the upgrade process.

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 the operation was completed successfully. For more information about error messages, refer to Oracle Fusion Middleware Release Notes.

Start the Administration Server.

Start the WC_Spaces and WC_Collaboration managed servers.

Connect to the Administration Server.

connect(admin_username, admin_password, host)

In the domain running the WC_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 the operation was completed successfully. For more information about error messages, refer to Oracle Fusion Middleware Release Notes.

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.

Make sure the WC_Spaces server is up and running before moving to the next step.

Disconnect from the Administration Server, and connect to the WC_Spaces server as an Oracle WebCenter Portal 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:

Log in to the WebLogic Server console.

Click Security Realms and select the "myrealm" link.

Click the Roles/Policies tab.

Expand Global Roles, then expand Roles, then click "View Role Conditions" for the Admin role.

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

6.6 Patching an Oracle WebCenter 11.1.1.1.0 Installation

If you are running Oracle WebCenter 11g (11.1.1.1.0), you must first update your Oracle Fusion Middleware environment to 11g Release 11.1.1.2.0, and then apply the Oracle WebCenter Portal 11.1.1.8.0 patch.

If you encounter this error, check that the Node Manager is running and that the user and server details provided to the script are correct. Then, re-run the upgrade.py script to complete patching your Oracle WebCenter Portal instance.

6.7.2 Troubleshooting Post-Patching Issues

This section provides information to help you troubleshoot issues you may encounter after patching to Oracle WebCenter Portal 11.1.1.8.0. It contains the following subsections:

6.7.2.1 Related Items Tab Not in Focus

Problem

In Oracle WebCenter 11.1.1.4.0, your WebCenter Portal application contained a Document Viewer task flow, and the Initial Sidebar property was set to relatedItems. However in the patched instance, the Related Items tab is not in focus when you navigate to the task flow though the related items are visible.

Solution

Beginning with Release 11.1.1.6.0, Related Items no longer exists as a tab. You can change the value of the Initial Sidebar property to target one of the new tabs: tags, links or recommendations.

6.7.2.2 Content Getting Clipped and Inner Scrollbars Appearing

Problem

In the portals (previously called spaces) upgraded from Release 11.1.1.2.0 and 11.1.1.3.0, content is getting clipped and inner scrollbars appear on the components.

Solution

Beginning with Release 11.1.1.6.0, the default page template for WebCenter Portal is Top Navigation, which implements a flowing layout. All the page templates that implement a flowing layout have a fixed width. Most of the pages created before Release 11.1.1.4.0 were based on page templates that implemented a stretching layout that allows components to be stretched to maximize the usage of the viewable area. In your upgraded WebCenter Portal instance, Top Navigation is set as the default template, and therefore portal pages might not be rendered properly if they are based on a stretching layout page template.

After patching from Release 11.1.1.2.0 or 11.1.1.3.0, configure your portals, if required, to use a page template that allows the content to be stretched. Beginning with Release 11.1.1.6.0, the following out-of-the-box page templates support a stretching layout: Top Navigation (Stretch), Side Navigation (Stretch), Fusion Top Navigation, and Fusion Side Navigation.

6.7.2.3 Pretty URLs Not Working for Page Navigation

Problem

In your patched WebCenter Portal application, you are unable to navigate to a specific page using the pretty URL.

Solution

Beginning with Release 11.1.1.6.0, the pretty URLs to navigate to a specific page in a portal have changed.

The variable userName is your user name or the name of the user who owns the page in the Home portal. The variable escapedPageDisplayName indicates the use of an escaped version of the page display name. For example, when you create a page with the name My Page, the URL to this page ends with My+Page. For example:

http://host:port/webcenter/spaces/profile/weblogic/page/My+Page

Use the following syntax for UI URLs that target business role pages and system pages:

http://host:port/webcenter/spaces/system/page/pageName

For example:

http://host:port/webcenter/spaces/system/page/Documents

6.7.2.4 Content Queries Not Rendered in Navigation Model

Problem

After patching to Release 11.1.1.8.0, content queries do not get rendered in a navigation model.

Solution

After patching Oracle WebCenter Portal, if previous content queries are no longer listed in your navigation model, you must re-build the index collection on Content Server. For information, see the "Rebuilding the Collection" section in Oracle WebCenter Content System Administrator's Guide for Content Server.

6.7.2.5 Blog Posts Not Displayed in Portals

Problem

After you patched your Oracle WebCenter 11.1.1.2.0 instance, blog posts are not getting displayed in portals.

Solution

The Wiki Migrator utility wiki-upgrade.jar migrates only the wiki pages and blogs that are created using the Wiki and Blog page styles. In a portal, you can configure a page to point to a different wiki or blog by using the wcURL parameter. However, this type of customization is not supported in wiki migration. Therefore, in Release 11.1.1.2.0, if your page was custom wired to point to a different wiki or blog, the page will not display the wiki or blog in the patched instance.

The wiki-upgrade.jar utility migrates your Release 11.1.1.2.0 wiki and blog data to a temporary folder with the same name as the domain. You must move this folder to the required portal folder. Then, you can either:

Rename the domain folder to have the same name as the wiki page or blog.

Create a new page with the same name as the newly moved folder, in the required portal. This will create a new page that exposes the wiki or blog. You can then delete the old broken page.

6.7.2.6 Comments and Likes Not Displayed in Activity Stream

Problem

In your patched Oracle WebCenter Portal instance, Activity Stream lists the various messages that were posted and documents that were added in your pre-patched instance. However, it does not show the comments and likes associated with these messages and documents.

Explanation

In Oracle WebCenter Portal 11.1.1.8.0, comments and likes are associated with an activity, and not with the object (a message or a document), whereas in previous releases, comments and likes were associated with the object itself.

For example, suppose you upload version 1 of a document, and later update the document to version 2. Activity Stream will display any comments or likes associated with the activity of uploading version 1 or updating the document to version 2. Any comments or likes associated with the document itself are not displayed.

6.8 Pre-Patching Tasks for Oracle WebCenter Portal

Preparing to patch your Oracle WebCenter Portal environment involves performing generic tasks such as stopping the servers, backing up your environment, and upgrading to the latest version of WebLogic Server. It also involves preparing your Oracle WebCenter Portal instance. This section describes all Oracle WebCenter Portal-specific pre-patching tasks that you may need to perform before patching WebCenter Portal to release 11.1.1.8.0.

Note:

The pre-patching tasks described in this section are not required for all upgrade paths. To determine whether a task is applicable, refer to the diagram and the table given in this chapter for your existing environment. For example, if you are patching Oracle WebCenter Portal 11.1.1.6.0, refer to the diagram and the table given in Section 6.3, "Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation."

In your Oracle WebCenter Portal instance, if Services Portlets producer or any custom portlet producers are deployed and secured with OWSM security policies, you will need to re-configure the security policies after patching your instance. To prepare for this, you must export the Web service deployment descriptors for those portlet producers to a Java Archive (JAR) file.

To export the Web service deployment descriptors for portlet producers to a JAR file:

Ensure the WC_Portlet managed server and any custom managed servers on which custom portlet producers are deployed are up and running.

You may have various custom portlet producers deployed in your Oracle WebCenter Portal instance, and have OWSM security policies attached to custom portlet producers' Web service end points (WSRP_v2_Markup_Service). You must export the Web service deployment descriptors to a JAR file for each custom portlet producer before your patch your instance.

For example, if your custom portlet producer is named TestJSR286 and is deployed to WC_PORTLET managed server with version 1.0, run the following command to export the deployment descriptor to a JAR file named exportPDD.jar:

6.8.2 Saving Your OmniPortlet and Web Clipping Customizations

Note:

Perform the procedure listed in this section only if you are using OmniPortlet and Web Clipping customizations, and they are stored in a file-based preferences store. By default, in Oracle WebCenter Portal and Oracle Portal, a file-based preferences store is not used. Such stores are used by default only for 11g Release 1 (11.1.1) Portal environments that are upgraded from their 10g versions.

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

To save and back up your customizations:

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_Portlet/tmp/_WL_user/portalTools_version/randomly_generated_directory/war

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

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

6.8.3 Running 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.

If your existing environment uses Oracle Content Server 10g as the content repository, you must upgrade to Oracle WebCenter Content 11.1.1.8.0. This is important to take advantage of the full set of features that the 11g release provides.

If you are using Content Server, both Oracle WebCenter Portal and Oracle WebCenter Content must be of the same patch set level. For example, if you are patching to Oracle WebCenter Portal 11.1.1.8.0, you must also patch to Oracle WebCenter Content 11.1.1.8.0.

Oracle WebCenter Portal and Oracle WebCenter Content can be within the same domain or in separate domains.

For Content Server 11g, Oracle recommends Folders (the FrameworkFolders component) as the folder interface instead of Contribution Folders (the Folders_g component). However, Oracle WebCenter Portal uses the Folders_g foldering capability. Therefore, to use Content Server 11g as a content repository for Oracle WebCenter Portal, you MUST have Folders_g enabled and FrameworkFolders disabled. You cannot have both enabled on an Oracle WebCenter Content instance.

6.8.4.1 Upgrading Oracle ECM

If you are running a version of Oracle ECM older than 10g Release 3 (10.1.3.5.1), you must upgrade to the 10g Release 3 (10.1.3.5.1) version before attempting to upgrade to Oracle WebCenter Content 11.1.1.8.0.

6.9 Post Patching Tasks for Oracle WebCenter Portal

This section describes all the tasks that you may need to perform to complete patching to Oracle WebCenter Portal release 11.1.1.8.0.

Note:

The tasks described in this section are not required for all patching paths. To determine whether a task is applicable, refer to the diagram and the table given in this chapter for your existing environment. For example, if you are patching Oracle WebCenter Portal 11.1.1.6.0, refer to the diagram and table given in Section 6.3, "Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation."

Ensure the WC_Spaces, WC_Collaboration, and WC_Portlet managed servers are running. If custom portlet producers are deployed to any custom managed servers, ensure those servers are also up and running.

Run the WLST command to import Web service deployment descriptor for a custom portlet producer. For example, if your portlet producer's name is TestJSR286, and it is deployed to the WC_Portlet managed server with version 1.0, run the following command to import the Web service deployment descriptor from a file named exportPDD.jar.

This step is required only if any custom portlet producers are deployed in your Oracle WebCenter Portal environment. To attach the OWSM security policy, you must run the WLST command for each custom portlet producer separately.

Run the following WLST command to attach the OWSM security policy to the Web service endpoint (services-producer) for the Oracle WebCenter Portal's Services Portlets producer:

6.9.3 Extending the Domain Using the Pagelet Producer Upgrade Template

A new version of Pagelet Producer was released with WebCenter Portal 11.1.1.6.0. If your upgraded Oracle WebCenter Portal 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:

Stop the Admin server and all managed servers.

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

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

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

Where WCP_ORACLE_HOME refers to the WebCenter Portal Oracle home directory.

Reconfigure the Pagelet Producer connections for the WebCenter Portal application and WebCenter custom applications (Portal Framework applications) by using Fusion Middleware Control or WLST. For information, see the "Registering the Pagelet Producer" section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

Note:

In previous releases, 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 '/'. From Release 11.1.1.6.0 onward, 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.

Stop WC_Portlet, the managed server on which Pagelet Producer is running.

In WLS Console, click Deployments.

Select the check box next to pagelet-producer (11.1.1.4.0) deployment.

Click Delete.

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

In WLS Console, go to Services > Data Source.

Click WebCenterDS.

On the Targets tab, select WC_Portlet and click Save.

6.9.4 Updating SSO and OHS Configuration

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

6.9.4.1 Updating OHS Configuration for Pagelet Producer

Beginning with Release 11.1.1.6.0, Pagelet Producer's web context root has changed from "/" to "/pagelets", where pagelets refers to any location of your choice where Pagelet Producer is deployed. Before Release 11.1.1.6.0, since Pagelet Producer used "/" as a web context root, virtual host configuration was recommended, but it is no longer required.

If you have OHS configured, you must update the OHS entry in mod_wl_ohs.conf. This file is available at the following path:

6.9.4.2 Updating SSO Configuration for Pagelet Producer

Beginning with Release 11.1.1.6.0, Pagelet Producer's web context root has changed from "/" to "/pagelets". If SSO is configured for your Oracle WebCenter Portal environment, you must update your SSO configuration or policy to use the new context root for protected and public URIs.

This section describes how you can update the policy for OAM 11g, OAM 10g, and OSSO.

6.9.4.3 Updating SSO Configuration for Portlet Producer Applications

Beginning with Release 11.1.1.6.0, you must explicitly exclude the portlets URI in an OAM setup. You must update all custom and out-of-the-box Portlet Producer applications configured with SSO. For information, see the following sections in Oracle Fusion Middleware Administering Oracle WebCenter Portal:

6.9.4.4 Updating SSO Configuration for Oracle SES

In Release 11.1.1.4.0 and 11.1.1.5.0, the recommendation was to use virtual host configuration to configure SES crawl and authorization end points. However, this is no longer required from Release 11.1.1.6.0 onward. You can consider marking the SES endpoints as excluded resources in OAM configuration. For information, see the following sections in Oracle Fusion Middleware Administering Oracle WebCenter Portal:

6.9.4.5 Verifying SSOFilter Grant

If your environment is configured with Oracle Access Manager SSO, check the OAM Asserter configured in your WebLogic domain. Ensure the active types chosen are OAM_REMOTE_USER and ObSSOCookie. If OAM_IDENTITY_ASSERTION is also one of the chosen active types, you need to ensure the following:

Open the jps-config.xml file. The file is located at the following path:

DOMAIN_HOME/config/fmwconfig/jps-config.xml

Where, DOMAIN_HOME is the domain home location for your Oracle WebCenter Portal domain.

Ensure AttributeService is configured.

The default jps context must have the following entry for configuring the attribute service:

Ensure that the SSOFilter JAR has the AttributeAccessPermission grant. To verify this, log on to WLST as described in "Running Oracle WebLogic Scripting Tool (WLST) Commands" in Oracle Fusion Middleware Administering Oracle WebCenter Portal. Then, run the following WLST command to list permissions:

6.9.5.1.1 How to Migrate Oracle Wiki Pages and Blogs

If you had Oracle Wiki installed, you must run the Wiki Migrator utility wiki-upgrade.jar to migrate the wiki pages and blogs. The utility is available in the following directory in the WebCenter Portal Oracle home:

WebCenter_ORACLE_HOME/webcenter/archives/wiki-upgrade.jar

This Wiki Migrator utility migrates your wiki pages and blogs into portal-specific folders in Content Server, and the upgraded pages for wikis and blogs are migrated accordingly. The utility also migrates attachments and provides links to them in your wiki pages as appropriate. Links to other wiki pages within your wiki page content are updated to point to the new locations, provided that the URL in each link has the same WebCenter Portal root that is provided in the migration parameters. The utility does not migrate comments, discussion threads, templates, nor it alters wiki or blog content.

Verify that the root folder PersonalSpaces exists in Oracle WebCenter Content; this is the folder in which all personal folders get created. Wiki migration may fail if the PersonalSpaces folder does not exist in Oracle WebCenter Content. The PersonalSpaces folder gets created when the WC_Spaces managed server is started. Therefore, it is recommended that you start WC_Spaces prior to performing wiki migration.

Update the folder limit in Oracle WebCenter Content as follows:

Log on to the Oracle WebCenter Content user interface, go to Administration > Folder Configuration and change the "Maximum Folders Per Virtual Folder" and "Maximum Content Per Virtual Folder" to 1000.

Create a temporary folder that the Wiki migration utility will use to store orphan data (for example, the data that does not have a corresponding portal). This does NOT have to be a root folder; it can be created as the Administrator user under the PersonalSpaces folder or the Spaces root folder. If a root folder is preferred, the service using the URL IdcService=COLLECTION_ADD will need to be used. For example:

Note the idcToken can be retrieved via the browser's Page Source from a logged in session to Oracle WebCenter Content. Alternatively, the attribute DisableAuthorizationTokenCheck can be disabled by selecting Administration > Content Server > General Configuration > Additional Configuration Variables -> DisableAuthorizationTokenCheck=true and then restarting the server.

Choose one of the following ways to run the wiki-upgrade.jar file from WebCenter Portal Oracle home:

Password to the database user that is used to connect to the MDS data source.

UCMConn

Content Server connection URL over the idc protocol.

For example: idc://host:port

UCMUser

Use sysadmin as the Content Server user; the user weblogic does not get administrator privileges with socket connections.

UCMPswd

Password for the Content Server user account.

UCMConnName

Name used in Enterprise Manager or WLST to create the connection to Content Server.

UCMTempFolderPath

Temporary folder on Content Server to store orphaned data

For example: /RootFolder/.../TempFolder

wikiConn

Name of the connection used to connect to the Wiki data source.

For example: jdbc:oracle:thin:@host:port:SID

wikiUser

Name of the database user that is used to connect to the Wiki data source.

wikiPswd

Password for the database user connecting to the Wiki data source.

SpacesRootURL

WebCenter Portal root URL.

For example: http://host:port/context_root

Note:

If you have wiki or blog pages that use Query String parameters, then after upgrade these parameters do not take effect. Any links that pointed to other wiki pages through a URL such as the following are converted to a Resource Action Handler URL that points to the corresponding wiki document in the content repository, assuming the server:port value entered for SpacesRootURL matches the server:port value in the URL.

If you are upgrading from a 10g release or Release 1 (11.1.1.1.0) version of Wiki, then after you run the Migrator utility wiki-upgrade.jar, there may be some wiki and blog folders that end up in the MigrationTemp folder. You must manually move these folders to the correct portal folders on Content Server.

Perform the following steps after migrating Oracle Wiki pages and blogs:

Log on to Content Server and go to the MigrationTemp folder under sysadmin (or the Content Server user running the migration program). Move the wiki and blog folders to the correct portal folders. You may need to rename the wiki and blog folders to match the corresponding portal names in WebCenter Portal.

Log on to the WebCenter Portal application, navigate to the required portal and create a new page with Wiki or Blog page style. The name of the page must match the name of the wiki/blog folder in order for the page to properly display the wiki/blog content.

6.9.5.1.2 Troubleshooting Problems During Wiki Migration

During wiki migration, you may see some error messages in the output log. Descriptions and available workarounds are described below.

This message indicates that there is no data specified in the domain to connect it with a portal (previously called group space) page (the wcURL on the domain is missing).

Note:

The last part of the migration program will find any remaining unmigrated portal pages that still point to owc_wiki and will try to gather domain information from the page's source URL to be matched against a jzwiki domain. If the proper information is found, it will move the folder and content out of migration temp and into the proper portal folder.

This message indicates that there is either no portal information specified in the domain, or the portal GUID specified is not valid (the portal GUID specified in the wcURL is not valid).

Error Message 3

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

This message indicates that the domain's portal information points to a portal that no longer exists. Doing a lookup with the portal GUID does not find a corresponding portal name. Most likely the portal has been deleted.

This message indicates that the portal page has been migrated already, but the Content Server folder for that portal does not exist.

To correct this, create the portal folder (by provisioning the Document feature in the portal), and then move the folder (with the same name as the domain) from migration temp to the portal folder. Then rename the domain folder to have the same name as the page.

This message indicates that the portal page has been migrated already, but the Content Server folder for the user does not exist.

To correct this, create the user's personal folder (this folder is created when the user accesses Documents from the Home portal), and then move the folder (with the same name as the domain) from migration temp to the personal folder. Then rename the domain folder to have the same name as the page.

This message indicates that there is more than one domain pointing to the same portal and page information, and the current domain being processed does not match the domain indicated in the source URL.

This is a jzwiki user blog that is not connected with a domain. The message indicates that the Content Server folder for the user does not exist, so the content could not be migrated there.

Error Message 11

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

This is a jzwiki user blog that is not connected with a domain. The message indicates that the "Blogs" Content Server folder for the user does not exist and could not be created, so the content could not be migrated there.

6.9.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.8.0. You must register the required custom templates in Release 11.1.1.8.0 version of your applications.

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 application upgraded to Release 11.1.1.8.0:

PROJECT_ROOT/public_html/oracle/webcenter/portalapp

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.

6.9.5.3 Updating the Configuration for WebCenter REST APIs

Before you can use the WebCenter Representational State Transfer (REST) APIs, you must perform 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.

Run these commands while the Administration server is running. You do not have to restart the server after executing these commands. For more information, see the "createCred" command in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

6.9.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 portal calendars in one events task flow. In the upgraded Release 11.1.1.8.0, the Events task flow no longer displays multiple calendars; only the current portal 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 the "Displaying Additional Calendars" section in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

The Web Clipping portlet has been deprecated in Release 11g (11.1.1.8.0). Consider using a clipper pagelet using Oracle WebCenter Portal's Pagelet Producer. For more information, see the "Managing the Pagelet Producer" chapter in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

To restore OmniPortlet and Web Clipping configuration and customizations:

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/WC_Portlet/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\WC_Portlet\tmp\_WL_user\portalTools_version\randomly_generated_directory\war

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

Note:

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

Replace these directories with their backed up copies.

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

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

Where, MW_HOME refers to Middleware Home, and WCP_ORACLE_HOME refers to the WebCenter Portal Oracle Home directory.

You can move WSRP portlet preferences manually or by using a migration utility. For more information, see the "Migrating a WSRP Producer Persistence Store" chapter in Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal and Oracle JDeveloper.

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

6.9.6.2 Configuring WebCenter Portal Workflows

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

To configure WebCenter Portal workflows:

Log on to Fusion Middleware Control.

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

6.9.6.5 Choosing a Default Start (or Landing) Page

By default, when you log on to the WebCenter Portal 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 setting after patching Oracle WebCenter Portal. For information, see the "Choosing a Default Start (or Landing) Page" section in Oracle Fusion Middleware Using Oracle WebCenter Portal.

6.9.6.6 Migrating WebCenter Portal Customizations

WebCenter Portal can be customized, for example to deploy additional shared libraries that include custom code or some additional assets (previously called resources) like task flows, page styles, and skins. If you deployed any custom page styles by extending WebCenter Spaces 11.1.1.2.0 or 11.1.1.3.0 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.

To migrate WebCenter Portal customizations:

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

6.9.6.7 Upgrading Process Spaces

Oracle Business Process Management (Oracle BPM) Process Spaces is a workspace built on top of WebCenter Portal, and provides portals 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.8.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.

Note:

To extend your Oracle WebCenter Portal 11.1.1.8.0 domain with Oracle BPM 11.1.1.7.0 Process Spaces, you may also need to apply a patch. For information, refer to the latest Oracle Fusion Middleware Release Notes on OTN here:

The procedure described in this section applies only if you have upgraded your existing Oracle WebCenter Portal installation to the latest release, and Process Spaces is already enabled on Webcenter Portal.

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

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

Property

Description

extendSoa

The flag to decide whether to extend the existing BPM domain or create a new one. Specify the value as true if WebCenter Portal 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 Portal Installation Details

wcOracleHome

Path to the WebCenter Portal Oracle home directory

wcDomainName

Name of the domain where Oracle WebCenter Portal 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

Oracle WebCenter Portal's WebLogic Installation Details

wcHost

Host name on which Oracle WebCenter Portal's Administration server is running

wcAdminPort

Port number on which Oracle WebCenter Portal's Administration server is running

wcAdminUser

Admin user for the Administration server

wcAdminPwd

Password of the Administration server

wcManagedServerName

In a single-server environment, specify the name of the managed server where WebCenter Portal is deployed.

In a clustered environment, specify the name of any one of the WebCenter Portal managed servers that is part of the cluster.

wcConfigServices

Flag to configure the Content Server and Discussions Server to work with Oracle WebCenter Portal. 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 to configure Content Server and Discussion Server by setting wcConfigServices to true, you should set wcConfigServices to false, and manually configure Content Server and Discussion Server to work with Oracle WebCenter Portal. For information, see the "Managing Content Repositories" and "Managing Announcements and Discussions" chapters in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

isWebcenterClusterConfig

Flag to specify whether Oracle WebCenter Portal installation is configured for a cluster. Set to true if it is a cluster configuration.

wcSpacesClusterName

Name of the WebCenter Portal 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 host Content Server configured for Oracle WebCenter Portal

wcContentServerPort

Port on which Content Server is running.

wcContentSpacesRoot

Name of the WebCenter Portal root folder on Content Server

wcContentAdminUser

Name of the Admin user for Content Server

Discussion Server Details

Set these properties if wcConfigServices is set to true.

wcDiscussionServerUrl

Name of the Discussion Server configured for WebCenter Portal

wcDiscussionAdminUser

Name of the Admin user for Discussion Server

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.

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

Run the install script again to complete the post upgrade steps. Use the following command:

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

Note:

If wcConfigServices is set to false, you do not need to run the install script again.

If Oracle BPM and Oracle WebCenter Portal have been configured in different domains, configure Trusted Domain Credentials in both the Oracle BPM and Oracle WebCenter Portal domains, and restart the Oracle BPM Admin Server and the Oracle WebCenter Portal Admin Server.

If Oracle BPM is not up and running, you may face problems logging into WebCenter Portal.

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

In WebCenter Portal, 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.8.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.8.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 Using Oracle WebCenter Portal: "Deleting a Portal", "Deleting a Portal Template", and "Deleting an Asset".

6.9.6.8 Granting Permissions to Manage Assets

In the portals upgraded from release 11.1.1.2.0 or 11.1.1.3.0, you must enable authorized users to be able to manage portal assets. For this, grant the Create, Edit and Delete Assets permission to the required roles. For information, see the "Managing Roles and Permissions for a Portal" chapter in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

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

In the upgraded Oracle WebCenter Portal 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.8.0, you must update the setDomainEnv script to add the authentication provider.

To add the OSSO authentication provider:

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:

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

Personalization Server, which enables you to deliver application content to targeted users based on selected criteria.

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

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

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

Analytics and Activity Graph require the ACTIVITES schema. 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.

Oracle WebCenter Portal Framework supports various new features such as page navigations and page hierarchies. If you want to use new features, the recommended best practice for migration of a release 11.1.1.2.0 or 11.1.1.3.0 custom application that contains portal components (like portlets) is to create a new release 11.1.1.8.0 Portal Framework application using the WebCenter Portal Framework Application template and then manually migrate the content, configurations, and logic from your old application (release 11.1.1.2.0 or 11.1.1.3.0) to the new Portal Framework application. For information about adding features to your Portal Framework application, see Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal and Oracle JDeveloper.

6.9.9 Running the upgradeWebCenterPermissions WLST Command

Run the upgradeWebCenterPermissions() WLST command to upgrade permissions for WebCenter Portal. This command creates additional application roles, and grants some additional permissions required for Oracle WebCenter Portal. It also determines and restores the OWSM security policy to the Web service endpoints for WebCenter Portal and Discussions.

To run the upgradeWebCenterPermissions() WLST command:

Ensure the Administration Server and all the Oracle WebCenter Portal managed servers are up and running.

Invoke the WLST script from your WebCenter Portal Oracle home directory, and connect to the Administration Server for Oracle WebCenter Portal. You must run all WebCenter Portal WLST commands from your WebCenter Portal Oracle home directory (WCP_ORACLE_HOME).

When you run this command, various warnings or error messages like 'COMMAND FAILED due to an unknown reason, Check the stack trace for details' are displayed. You can ignore these as long as there is a message that the command completed successfully.

Restart the WC_Spaces and WC_Collaboration managed servers.

6.9.10 Resetting Search Customizations

When you upgrade your existing Oracle SES instance to release 11.2.2.2, all the crawlers sources, crawler schedules, and source groups get migrated to the upgraded instance. But because of different Authorization Manager on the old and upgraded Oracle SES instances, search query will not render any results. After upgrading to Oracle SES 11.2.2.2, you must perform the following tasks:

Re-create spaces crawler (delete the existing spaces crawler and create it again), and assign it to your upgraded portals.

Configure a connection between WebCenter Portal and Oracle SES 11.2.2.2. Note that the default port numbers on the old and the upgraded Oracle SES instances are different.

This task must also include running the setSESVersion WLST command to enable the Tools and Services - Search administration page, and to gain access to the capabilities of Oracle SES 11.2.2.2.