6 Upgrading Oracle WebCenter Portal from 11g to 12c

You can upgrade your existing Oracle WebCenter Portal 11.1.1.9.0 installations to 12c (12.2.1.4.0).

Note:

To patch previous releases of Oracle WebCenter Portal 12c to release 12c (12.2.1.4.0), follow the generic upgrade procedure described in About the Oracle WebCenter Upgrade Process. There are no WebCenter Portal-specific pre- or post-upgrade tasks for moving to 12c (12.2.1.4.0).

This chapter describes the WebCenter Portal 11g-specific upgrade steps. Ensure that you follow the sequence of steps listed in About the Oracle WebCenter Upgrade Process, and have performed the required generic steps before you perform the upgrade tasks listed in this chapter.

Note:

Oracle WebCenter Portal has deprecated the support for Jive features (announcements and discussions). If you have upgraded from a prior release to Release 12c (12.2.1.4.0), Jive features remain available in your upgraded instance but Oracle support is not provided for these features. In the next release, Jive features will not be available even in the upgraded instances

Note:

As of 12c (12.2.1.4) Oracle WebCenter Portal has also deprecated the support for Pagelets.

This chapter includes the following topics:

Performing Pre-Upgrade Tasks for Oracle WebCenter Portal

Before you upgrade your existing Oracle WebCenter Portal environment, complete the following tasks:

Reassociating to a Database-Based Policy Store

If your WebCenter Portal 11g environment uses a file-based policy store or Oracle Internet Directory (OID) as the policy store, you must reassociate the policy store to a database-based policy store before upgrading to Oracle WebCenter Portal 12c.

Exporting Metadata for Portlet Producer Applications

Oracle WebCenter Portal 11g provides various preconfigured portlet producers, which include OmniPortlet, Web Clipping, WSRP Parameter Form Portlet, sample WSRP portlet producers, and sample PDK-Java portlet producers. To migrate customizations or metadata of your 11g portlet producer applications, you must export the data from your 11g application before upgrading Oracle WebCenter Portal. In the upgraded instance, you can then import these customizations back into portlet producer applications.

You can export producer metadata to an EAR file by using the exportPortletClientMetadata WLST command. For information, see exportPortletClientMetadata in WebCenter WLST Command Reference.

Saving OmniPortlet and Web Clipping Configuration

If your 11g Oracle WebCenter Portal instance contains Web Clipping and OmniPortlets portlets, keep a copy of their HTTP proxy entries before you upgrade your WebCenter Portal instance.

  1. Navigate to the provider.xml file in the 11g domain at the following location:

    Web Clipping: 11g_DOMAIN_HOME/servers/WC_Portlet/tmp/_WL_user/portalTools_11.1.1.x.0/randomly_generated_directory/war/WEB-INF/providers/webClipping/provider.xml

    OmniPortlet: 11g_DOMAIN_HOME/servers/WC_Portlet/tmp/_WL_user/portalTools_11.1.1.x.0/randomly_generated_directory/war/WEB-INF/providers/omniPortlet/provider.xml

  2. Copy the HTTP proxy entries for Web Clipping and omniPortlet from the 11g provider.xml. For example:
    <proxyInfo class="oracle.portal.provider.v2.ProxyInformation">
            <httpProxyHost>proxy.example.com</httpProxyHost>
            <httpProxyPort>80</httpProxyPort>
            <dontProxyFor>*.example.com</dontProxyFor>
          </proxyInfo> 
    

    You will need to add these entries to the provider.xml files in your upgraded WebCenter Portal instance.

Preparing to Migrate Custom Task Flows

Your WebCenter Portal 11g application might contain custom task flows that are deployed through custom shared libraries. If you’ve extended Webcenter Portal with custom shared libraries by using the SampleWebCenterSpacesExtension application, then you must upgrade the application and deploy the shared libraries in Release 11g before upgrading to Release 12c. Also, if you've developed your own custom task flows using the DesignWebCenterSpaces application, you must upgrade it and deploy the shared libraries in Release 11g. The SampleWebCenterSpacesExtension and DesignWebCenterSpaces projects are not supported anymore. Therefore, you need to move them to a new WebCenter Portal Server Extension application.

  1. Create a WebCenter Portal Server Extension application in JDeveloper 11g using the WebCenter Portal Server Extension Template. For information, see Creating a WebCenter Portal Server Extension Workspace in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

    If you already have a WebCenter Portal Server Extension application, you can skip this step.

  2. Move the projects created under the SampleWebCenterSpacesExtension application to the newly created WebCenter Portal Server Extension application. Then, add reference of these shared libraries to the PortalSharedLibrary project, which is available in the newly created application.

    Also, if you've registered your own shared library using the WebCenterSpacesExtensionLibrary project in the DesignWebCenterSpace application, then move all the references to the PortalSharedLibrary project in the WebCenter Portal Server Extension application.

    For information, see Registering Additional Shared Libraries With WebCenter Portal in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

  3. Deploy new versions of WebCenter Portal's shared library extend.spaces.webapp with your shared libraries references by using the WebCenter Portal Server Extension application. Before deploying the new version of extend.spaces.webapp, make sure that all the shared libraries referenced by the PortalSharedLibrary project are deployed to the WC_Spaces managed server.

    For information, see Deploying Extensions to the WebCenter Portal Shared Library (extend.spaces.webapp.war) in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

Migrating Portal Framework Applications

Note:

This pre-upgrade task is applicable if you want to migrate your 11.1.1.9.x Portal Framework application to WebCenter Portal 12c.

Oracle WebCenter Portal 11g supports the Portal Framework technology for creating and deploying Portal Framework applications (previously referred as custom portal applications) in JDeveloper. The Portal Framework technology is not available in WebCenter Portal 12c release. Oracle provides the support for migrating Portal Framework applications to WebCenter Portal. This support is available for migrating applications from release 11.1.1.9.x. The migrated application is available as a portal in WebCenter Portal 12c.

To migrate your Portal Framework application to WebCenter Portal 12c, you must first patch your existing environment to the latest patch available for Oracle WebCenter Portal 11.1.1.9.0 and then migrate the application to release 11.1.1.9.x. For information, see Migrating a Portal Framework Application to WebCenter Portal in Administering Oracle WebCenter Portal. After patching to WebCenter Portal release 11.1.1.9.x, you can upgrade to release 12c as described in About the Oracle WebCenter Upgrade Process.

Migrating from Folders_g to FrameworkFolders

If your Oracle WebCenter Portal instance uses the Folders_g folder service, then migrate the content from the Folders_g folder service to the FrameworkFolders folder service on Oracle WebCenter Content Server.

For information, see Migrating Folders_g to FrameworkFolders in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

Upgrading Oracle WebCenter Portal 11g Installations

After upgrading the domain, use these steps to complete the upgrade of Oracle WebCenter Portal.

The following table describes the tasks required to upgrade Oracle WebCenter Portal 11g to 12c. These steps should be performed after you have upgrade the schemas and reconfigured the domain as described in Upgrading an Oracle WebCenter Domain.

Note:

In Oracle WebCenter Portal 11g, the default names of managed servers are WC_Spaces, WC_Portlet, WC_Collaboration, and WC_Utilities. In a fresh Oracle WebCenter Portal 12c installation, WC_Utilities, which hosted Analytics, is deprecated, and WC_Spaces is replaced by WC_Portal and hosts Analytics. When you upgrade from Oracle WebCenter Portal 11g to 12c, the default managed server names are not changed. Further, Analytics remains deployed on the WC_Utilities managed server.

Table 6-1 Upgrading from Oracle WebCenter Portal 11g

Step Description More Information

Run the upgradeWebCenterPortal WLST command if the node manager is set up and managed servers can been started from the Admin console

Run the upgradeWebCenterPortal WLST command to move the metadata from MDS to DB and upgrade security permissions.

Running the upgradeWebCenterPortal WLST Command

Access the upgrade metrics

Optional.

Access the upgrade metrics for Oracle WebCenter Portal to analyze the upgrade performance. This must be done before you restart the servers.

Accessing Upgrade Metrics

Enable additional components on Content Server and restart the server

On Content Server, enable additional components like DynamicConverter and Imaging. Enable PortalVCRHelper if Site studio is configured. Then, restart Content Server.

Enabling or Disabling a Component Using the Component Manager

Restart the Administration Server and all the managed servers

Start your Oracle Fusion Middleware environment. This involves starting your Oracle WebLogic Server, Node Manager, Administration Server, managed servers, OPMN, and all system components.

Performing Post-Upgrade Configuration Tasks

Run the upgrade audit tool by running the listDeprecatedFeaturesUsage WLST command

Run the listDeprecatedFeaturesUsage WLST command to run the upgrade audit tool to view the list of deprecated features in your upgraded WebCenter Portal 12c installation.

Running the Upgrade Audit Tool

Running the upgradeWebCenterPortal WLST Command

Run the upgradeWebCenterPortal WLST command to move metadata from MDS to database and upgrade security permissions in your upgraded Oracle WebCenter Portal 11g installation.

To run the upgradeWebCenterPortal WLST command:

  1. Navigate to your WebCenter Portal Oracle home directory and invoke the WLST script:

    (UNIX) ORACLE_HOME/common/bin/wlst.sh

    (Windows) ORACLE_HOME\common\bin\wlst.cmd

  2. At the WLST command prompt, enter the following command to connect to the Administration Server for Oracle WebCenter Portal:
    wls:/offline>connect('user_name','password', 'host_name:port_number')
    

    where

    • user_name is the username of the operator who is connecting to the Administration Server

    • password is the password of the operator who is connecting to the Administration Server

    • host_name is the host name of the Administration Server

    • port_number is the port number of the Administration Server

    For help with this command, type help('connect') at the WLST command prompt.

  3. Run the upgradeWebCenterPortal WLST command. For information about the command syntax, see upgradeWebCenterPortal in Oracle Fusion Middleware WebCenter WLST Command Reference. For information about the messages displayed and reports generated, see Output Generated by the upgradeWebCenterPortal WLST Command.
Output Generated by the upgradeWebCenterPortal WLST Command

The upgradeWebCenterPortal WLST command generates the following reports:

  • UpgradeSummary.txt: Lists the total number of portals or portal templates for which upgrade was attempted, succeeded, and failed.

  • UpgradeDetails.txt: Shows detailed upgrade information for each portal, listing the details such as the number of pages, resource catalogs, navigations upgraded. Also shows the details of any upgrade errors reported for a portal.

  • UpgradeDiagnostic.log: Shows the diagnostic information for the upgradeWebCenterPortal WLST command.

Each time you run the upgradeWebCenterPortal command, the reports get updated with the additional details from the last run. If there are upgrade errors reported at any step, fix the errors and run upgradeWebCenterPortal again. The upgrade process is considered complete when upgradeWebCenterPortal does not report any more failed attempts to upgrade any portals or portal templates, and its last output shows the message WebCenter Portal application upgrade is complete.

For information about troubleshooting the upgrade issues, see Troubleshooting Oracle WebCenter Portal Upgrade Issues.

Sample Command 1

Run the following command when your WebCenter Portal instance is configured to use WebCenter Content Server.

upgradeWebCenterPortal(appName='webcenter', server='WC_Spaces', migrationDirectory='/scratch/upgrade_log', contentServerName='UCM_server1', contentDbConnectionUrl='wccdbhost:wccdbport:wccdbsid',contentDbUserName='DEV_OCS')

Sample Command 2

When running the upgradeWebCenterPortal WLST command, you can specify the parameters depending on your requirements.

Run the following command when your 11g instance is not configured to use WebCenter Content Server. The following sample command moves the metadata from MDS to DB and upgrades security permissions.

upgradeWebCenterPortal(appName='webcenter', server='WC_Spaces', migrationDirectory='/scratch/upgrade_log')

The following is the sample message displayed when you run this command:

Starting WebCenter Portal application upgrade.
Already in Domain Runtime Tree
 
 
To effect connection changes, you must restart the managed server on which the WebCenter application is deployed.
If you have set adminPassword, keystorePassword, or privateKeyPassword in your content server connection, then set the values again in the underlying RIDC connection. Do this by running setContentServerConnection and specifying the values, if applicable.
 
Starting data migration from MDS to database...
 
[TRACE]: Upgrade may take some time to complete depending on the number of portals and pages in your Oracle WebCenter Portal installation. To monitor the upgrade progress, refer to the diagnostic log file WC_Portal-diagnostic.log at the location "/scratch/software/user_projects/domains/base_domain/servers/WC_Spaces/logs".
 
#######################################################
Upgrade Run: 1
#######################################################
Upgrade of 44 Portals/Portal Templates attempted.
Upgrade of 44 Portals/Portal Templates succeeded.
Upgrade of 0 Portals/Portal Templates failed.
 
Data migration from MDS to database is successfully completed.
 
Policy URI For Authenticated Access: oracle/wss10_saml_token_service_policy
 
Already in Domain Runtime Tree
 
Command FAILED, Reason: JPS-04207: Matching Grantee not found: [GranteeEntry: codeSource=file:${common.components.home}/modules/oracle.wsm.agent.common_11.1.1/wsm-agent-core.jar principals=[]].
 
Already in Domain Runtime Tree
 
Command FAILED, Reason: JPS-04201: Cannot grant permission(s). Grant already exists for grantee [GranteeEntry: codeSource=null principals=[[AppRole: appID=webcenter name=s5f9c65ed_c93c_4467_96cf_06a82f3dad22#-#Spaces-User displayName=null description=null category=null uniquename=cn=s5f9c65ed_c93c_4467_96cf_06a82f3dad22\#-\#Spaces-User,cn=Roles,cn=webcenter,cn=opssSecurityStore,cn=JPSContext,cn=opssRoot guid=108CDE506D8A11E5BFE5CF1BB12B2942 members=[] classname=oracle.security.jps.service.policystore.ApplicationRole type=JPS_APPLICATION_ROLE]]].

Starting upgrade for portal roles...
Upgrade of the portal roles is complete.
 
Permissions upgrade completed with warnings
 
WebCenter Portal application upgrade is complete.

Note:

Running the upgradeWebCenterPortal WLST command displays certain error messages that permissions already exist. For example:

Already in Domain Runtime Tree
 
Command FAILED, Reason: JPS-04201: Cannot grant permission(s). Grant already exists for grantee [GranteeEntry: codeSource=null principals=[[AppRole: appID=webcenter name=s5f9c65ed_c93c_4467_96cf_06a82f3dad22#-#Spaces-User displayName=null description=null category=null uniquename=cn=s5f9c65ed_c93c_4467_96cf_06a82f3dad22\#-\#Spaces-User,cn=Roles,cn=webcenter,cn=opssSecurityStore,cn=JPSContext,cn=opssRoot guid=108CDE506D8A11E5BFE5CF1BB12B2942 members=[] classname=oracle.security.jps.service.policystore.ApplicationRole type=JPS_APPLICATION_ROLE]]].

Such error messages do not affect any functionality. You can safely ignore the error messages and proceed with upgrading your WebCenter Portal instance.

Running the Upgrade Audit Tool

In Oracle WebCenter Portal 12c, certain features such as document task flows have been deprecated. Post upgrade, you can run the upgrade audit tool to list down the usage of all deprecated features in your upgraded WebCenter Portal installation.

Run the listDeprecatedFeaturesUsage WLST command to list the usage of deprecated features in your upgraded Oracle WebCenter Portal installation:

listDeprecatedFeaturesUsage(appName='webcenter', server='WC_Spaces', reportDirectory='/scratch/audit', portal='portal1, portal2')

where:

  • appName is the WebCenter Portal application where deprecated features need to be audited.

  • server is the managed server on which WebCenter Portal is deployed.

  • reportDirectory is the path to the writable directory where audit report will be generated.

  • portal is the list of specific portals that you want to audit. You can pass comma separated list of portal names. It is an optional parameter. If you do not specify this parameter, report is generated for the entire WebCenter Portal application.

For example, the following command generates the audit report for the WebCenter Portal application deployed on the WC_Spaces managed server and stores the report in the /scratch/audit folder:

listDeprecatedFeaturesUsage(appName='webcenter', server='WC_Spaces', reportDirectory='/scratch/audit')

When you generate the upgrade audit report for the entire WebCenter Portal application, the following files are generated in the auditReport subdirectory under the directory specified for the reportDirectory parameter in the WLST command:

  • summary.txt: Lists the portals and portal templates that contain deprecated features and specifies the number of artifacts that contain deprecated features, as shown in Figure 6-1.

  • connections.txt: Lists the deprecated connections in WebCenter Portal.

    Note:

    You must remove the deprecated connections otherwise there might be some functionality issues.

  • A .txt file for each portal and portal template containing deprecated features: Lists the artifacts (such as pages, page templates, and resource catalogs) that contain deprecated features and specifies name of the deprecated feature. Figure 6-3 shows the audit report for a specific portal.

Figure 6-1 Upgrade Audit Report - summary.txt

Description of Figure 6-1 follows
Description of "Figure 6-1 Upgrade Audit Report - summary.txt "

Figure 6-2 Upgrade Audit Report - connections.txt

Description of Figure 6-2 follows
Description of "Figure 6-2 Upgrade Audit Report - connections.txt"

Figure 6-3 Upgrade Audit Report for a Portal

Description of Figure 6-3 follows
Description of "Figure 6-3 Upgrade Audit Report for a Portal"

The following example generates the audit report only for a portal named MyPortal. This will generate only the MyPortal.txt file. The connections and summary files are not generated for a portal.

listDeprecatedFeaturesUsage(appName='webcenter', server='WC_Spaces', reportDirectory='/scratch/audit', portal='MyPortal')

In your upgraded WebCenter Portal, if a portal page contains a deprecated feature, the feature appears blank in the page view mode. In the page edit mode, a message displays that the feature is deprecated and lists the action required. For example, Figure 6-4 shows deprecated document tasks flows listed in the page editor. Note that the messages specify that you remove the deprecated task flows or use their 12c equivalent.

Figure 6-4 Deprecated Task Flows in Page Editor in the Upgraded WebCenter Portal Instance

Description of Figure 6-4 follows
Description of "Figure 6-4 Deprecated Task Flows in Page Editor in the Upgraded WebCenter Portal Instance"

Accessing Upgrade Metrics

You can use Oracle Dynamic Monitoring Service (DMS) to view upgrade metrics and analyze how much time was taken for the overall upgrade process and for each portal and its WebCenter Service handlers.

To access upgrade metrics:

  1. Access DMS Spy Servlet using the following URL format:

    http://host:port/dms/Spy

    Where host:port refer to the location where Oracle WebCenter Portal is installed.

  2. Sign in as an administrator.
  3. Locate the webcenter_upgrade metric in the left pane.

    The upgrade metrics for each portal are displayed in milliseconds.

  4. View the upgrade processing time for your portal. For each portal, the following metrics are relevant: upgradeProcessingTime and cleanupProcessingTime.

    The metrics also display the total processing time taken for the entire upgrade of Portal Server

    If required, you can save this report as a PDF for future reference. The upgrade metrics are lost when you restart the servers.

  5. Locate webcenter_upgrade_portal metric in the left column.

    The upgrade metrics shows how long each WebCenter Service handler took for upgrade processing per portal. It shows the breakdown of the time taken for upgrading each portal.

Performing Post-Upgrade Tasks for Oracle WebCenter Portal

Complete the post-upgrade tasks after you have upgraded Oracle WebCenter Portal.

Upgrading 11g Portlet Producers

In an upgraded Oracle WebCenter Portal instance, 11g portlets are not accessible. To ensure that portlets are available, you must migrate the required portlet producer applications to release 12c. You must also import portlet producer customizations and redeploy your portlet producer applications.

Migrating a Portlet Producer Application

To migrate an 11g portlet producer application to release 12c:

  1. Install Oracle JDeveloper 12c.

    Oracle JDeveloper provides an integrated development environment (IDE) for developing portals and custom portal components. For information on obtaining and installing Oracle JDeveloper, see the Oracle JDeveloper page on OTN at:

    http://www.oracle.com/technetwork/developer-tools/jdev/overview/index.html

  2. Install the Oracle WebCenter Portal extension bundle. For information, see Installing the WebCenter Portal Extensions for JDeveloper in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.
  3. Start JDeveloper 12c.
  4. Open your 11g portlet producer application.

    This invokes the migration wizard, which is displayed every time an 11g application is opened in JDeveloper 12c.

  5. On the Confirmation page, the Yes option is selected by default. Click Next to confirm that you want to migrate your application.
  6. On the Java Web Projects page, click Next to specify that you want to migrate projects created using JavaServer Pages JSTL to the latest versions.
  7. Click Finish to begin upgrading your application.

    A progress dialog displays while the upgrade process executes.

  8. When the application upgrade is complete, the Migration Status dialog displays the list of projects that have been upgraded. Click OK.

    The upgraded application is opened and its projects are listed in the Application Navigator. If there are any errors during application upgrade, they are listed in the Message - Log window.

Redeploying a Portlet Producer Application

You can deploy your upgraded portlet producer application to any Oracle WebLogic Server managed server configured to support Oracle WebCenter Portal's portlet producers. For deployment, you can use Oracle Enterprise Manager Fusion Middleware Control, Oracle WebLogic Server Administration Console, or Oracle WebLogic Scripting Tool (WLST). For information, see Deploying Portlet Producer Applications in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

You can also deploy portlet producer applications to an Oracle WebLogic Server instance directly from a development environment by using JDeveloper, provided you have the required credentials to access the WebLogic server. For information, see Deploying the Preconfigured Portlet Producers in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

Migrating Customizations

After upgrading portlet producers, you must import their customizations if the customizations are not shared or accessible to the upgraded portlet producers. You import customizations from the EAR that you exported as described in Performing Pre-Upgrade Tasks for Oracle WebCenter Portal.

To import customizations, use the importPortletClientMetadata WLST command. For information, see importPortletClientMetadata in WebCenter WLST Command Reference.

Restoring OmniPortlet and Web Clipping Configuration

After you saved your OmniPortlet and Web Clipping configuration (as described in Saving OmniPortlet and Web Clipping Configuration) and successfully upgraded Oracle WebCenter Portal instance, you must restore them.

  1. Navigate to the provider.xml file in the upgraded domain at the following location:

    Web Clipping: ORACLE_HOME/servers/WC_Portlet/tmp/_WL_user/portalTools/randomly_generated_directory/war/WEB-INF/providers/webClipping/provider.xml

    OmniPortlet: ORACLE_HOME/servers/WC_Portlet/tmp/_WL_user/portalTools/randomly_generated_directory/war/WEB-INF/providers/omniPortlet/provider.xml

  2. Paste the HTTP proxy entries for Web Clipping and omniPortlet from the 11g provider.xml file. For example:
    <proxyInfo class="oracle.portal.provider.v2.ProxyInformation">
            <httpProxyHost>proxy.example.com</httpProxyHost>
            <httpProxyPort>80</httpProxyPort>
            <dontProxyFor>*.example.com</dontProxyFor>
          </proxyInfo> 
    
  3. Save the files.

Verify the Content Server Connection is Upgraded

After you have run the upgradeWebCenterPortal command successfully, verify that the Content Server connection has been upgraded by running the listContentServerConnections WLST command. For information, see listContentServerConnections in Oracle Fusion Middleware WebCenter WLST Command Reference.

If the output of the listContentServerConnections WLST command shows the following message, run upgradeWebCenterPortal again to upgrade the Content Server connection.

The underlying RIDC connection is missing.

Upgrading WebCenter Portal 11g Assets to 12c

To use WebCenter Portal 11g assets in your upgraded WebCenter Portal 12c instance, you must upgrade the assets. For example, you can upgrade your 11g skins, page templates, or page styles to use them in your upgraded 12c portals.
To upgrade an 11g WebCenter Portal asset to 12c:
  1. In Oracle JDeveloper 11g, open the application that contains the asset you want to upgrade.
  2. Copy the source code of the required asset. For example, copy the source code of a skin from its CSS file.
  3. In Oracle JDeveloper 12c, create a WebCenter Portal asset application, specifying the required asset type. For example, if you want to upgrade a skin asset, create an asset application specifying Skin as the Asset Type.

    For information, see Creating a WebCenter Portal Asset Application in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

  4. Remove the source code from the newly created asset application, and paste the 11g source code of the asset, which you copied in step 2. For example, in your skin asset application, remove the source code and paste the source code that you copied from the 11g CSS file.
  5. Save the asset application.
  6. Deploy the asset application to WebCenter Portal 12c as a shared asset or to a specific portal. For information, see Publishing WebCenter Portal Assets in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

Updating Custom Coherence Configuration

After you upgrade Oracle WebCenter Portal from release 11g to release 12c, Content Presenter throws errors if your 11g environment used custom Coherence configuration. You need to re-create Coherence configuration to add the new schemes. You can optionally customize Coherence settings as required.

To update Coherence configuration:

  1. Shut down the WC_Spaces managed server(s).
  2. Remove the custom coherence configuration files carried on from release 11g from the following locations: 
    • Middleware_Home/user_projects/applications/Domain_Name/custom.webcenter.spaces.fwk/APP-INF/classes

    • Middleware_HOME/user_projects/applications/Domain_Name/custom.webcenter.spaces.fwk/APP-INF/lib

    If you want to back up the files, do not save them in the lib or classes folders. Save them in a different location. 

  3. Optionally, if you don’t want to use the default coherence configuration and want to customize the settings, create a new content-coherence-cache-config.xml file. You need to place the file in the following location: 

    Middleware_HOME/user_projects/applications/Domain_Name/custom.webcenter.spaces.fwk/APP-INF/classes

    For information, see Modifying Cache Settings for Content Presenter in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

  4. Restart the WC_Spaces managed server(s). 

Migrating Custom Task Flows

If your WebCenter Portal 11g application used custom task flows deployed through a custom shared library, then after upgrading to WebCenter Portal 12c you need to deploy the custom shared library.

To deploy a custom shared library containing custom task flows on WebCenter Portal 12c:

  1. Install Oracle JDeveloper 12.2.1.3 with the WebCenter Portal extensions.
  2. In Oracle JDeveloper, open the application containing the custom task flows that you want to migrate. This should migrate your application to 12c.

  3. Deploy a new version of your shared library to the upgraded domain.
  4. In Oracle JDeveloper 12.2.1.3, open the WebCenter Portal Server Extension application. This should migrate your application to 12c.
  5. Deploy a new version of extend.spaces.webapp with the new version of shared library to the upgraded domain.
  6. To verify that the migrated custom task flows are available in WebCenter Portal 12c:

    1. Log on to WebCenter Portal.

    2. In the portal browser, click the Administration tile.

    3. Click on the Shared Assets tab.

    4. Click Resource Catalogs.

    5. In the Actions column, click Edit next to any custom resource catalog.

    6. Click Add, and then select the Add from Library option.

      Verify that your migrated custom tasks flows are listed.

For more information about deploying custom shared libraries, see Deploying Extensions to the WebCenter Portal Shared Library (extend.spaces.webapp.war) in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

Replacing Document Viewer Component

The Document Viewer component has been deprecated. After upgrade, if the page still shows Document Viewer, use the following steps to replace it with the new Content Viewer component.

  1. Edit the Portal and click on the page containing the Document Viewer component.
  2. Click on the Document Viewer component and then click the Actions button, select Parameters.
  3. Note the value of parameter Resource ID. The value should be similar to "connection-name#dDocName:document-identifier"
  4. Delete the Document Viewer component.
  5. From the Resource Catalog, add the Content Viewer component. Edit the component and select the Parameters option, and enter the Document ID as "document-identifier" noted in step 3 above. Save and Publish the page.
  6. The Document will now be displayed in the Content Viewer component.

Understanding the Impact of Upgrade on Deprecated Features

This topic describes the upgrade impact on 11g features that have been deprecated in release 12c.

Portal-Level Device Settings

Device settings control how portals render on different kinds of devices including desktop browsers, smart phones, and tablets. In release 12c, device settings can be configured only at the WebCenter Portal application level, and not for individual portals. When you upgrade to release 12c, any portal-level customization done for device settings are lost. Only application-level device settings are applied to the upgraded WebCenter Portal instance.

Hierarchical Portals

Release 11g supported portal hierarchy consisting of a parent portal and its subportals, where by default subportals inherited security defined in the parent portal. When you upgrade WebCenter Portal to release 12c, subportals are moved as top-level portals. During upgrade, for each such upgraded portal, the following two attributes are added:

  • 11g.upgraded.portal.parent.guid - Specifies the ID of the parent portal.

  • 11g.upgraded.portal.parent.security.id - If present, specifies the portal from which security was inherited. If the value is null, it indicates that the subportal did not inherit the security from a parent portal and the subportal managed its own security.

Deprecated Portlets

In release 12c, Web Clipping portlets, Pagelet Producer, and the rich text portlets have been deprecated. If an upgraded portal page includes a deprecated portlet, the page displays the Remote Portlet Error. You must either remove the deprecated portlets from the page or replace them with their 12c equivalent.

In release 12c, content contribution and publishing components replace the functionality of rich text portlets.

Troubleshooting Oracle WebCenter Portal Upgrade Issues

This topic describes the solutions to the issues you might encounter while upgrading WebCenter Portal to the latest release.

Extra Entries Appear for the ACTIVITIES Schema

Problem

In the upgraded WebCenter Portal 12c instance, extra entries are shown for the ACTIVITIES schema.

Solution

In release 12c, Activity Graph is deprecated. When you upgrade from an 11g release, the existing Activity Graph entries are not removed. However, these entries are not present in the ACTIVITIES schemas when you install a fresh instance of Oracle WebCenter Portal 12c.

Floating Toolbar Not Available for Custom Page Templates

In your upgraded WebCenter Portal instance, for upgraded portals that include pages supporting content contribution and use a custom page template developed in a prior release, the floating toolbar is not available. To enable the floating toolbar, add it to the custom page template. For information, see Adding a Floating Toolbar to a Page Template in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

Running the Predeployment Tool does not Update 11g Portlet Producers

WebCenter Portal provides a predeployment tool that adds the required configuration to a portlet producer application's EAR file to expose the portlets over WSRP. You cannot directly run the predeployment tool on portlet EARs from 11g versions. You need to migrate the portlet producer application in Oracle JDeveloper, regenerate the EAR, and then run the predeployment tool. For information about migrating portlet producers, see Upgrading 11g Portlet Producers. For information about running the predeployment tool, see Managing Portlet Producers in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

Handling Errors While Upgrading Oracle WebCenter Portal

While upgrading Oracle WebCenter Portal, you might encounter error messages. The following are some of the error messages displayed when you run the upgradeWebCenterPortal WLST Command.

Error Message 1

Upgrade ends with one of the following messages:

 - Migration of Content Server from Folders_g to FrameworkFolders failed, Check MigrationDiagnostic.log for further details.
 - An error occurred during migration, Check MigrationDiagnostic.log for further details.

Error Message 2

Upgrade ends with following message:

 - Export of Folders_g data failed.
 - Updating Content Server general configuration failed.
 - Migration of <folder name> folder and content from Folders_g to the FrameworkFolders data structure failed.
 - Migration of WebCenter Portal data to FrameworkFolders failed.
 - Enabling <component name> server components failed.
 - Disabling <component name> server components failed.
 - Migration to FrameworkFolders failed.

Error Message 3

Upgrade ends with following message:

- WebCenter Content Server foldering service is not supported. Supported foldering service is FrameworkFolders version 2.1 and above.

Solution

To fix the issues, you need to:

  1. Restore WebCenter Content Server.

  2. Migrate from Folders_g to FrameworkFolders manually, as described in "Migrating Folders_g to FrameworkFolders" in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

  3. Run the following command:

    upgradeWebCenterPortal(appName='webcenter', server='WC_Spaces', migrationDirectory='/tmp/upgrade',contentServerName='UCM_server1')
    

    For more information about the command, see upgradeWebCenterPortal in Oracle Fusion Middleware WebCenter WLST Command Reference.

Errors on Accessing Documents/Blogs/Wiki Pages in an Upgraded Portal

After upgrade, on accessing the Documents, Blogs, or Wiki pages of an upgraded portal, if there are any errors, check the Content Server whether the upgrade has completed properly using the following steps:

  1. Sign in to Content Server using the following URL format: host:port/cs

  2. Navigate to Enterprise Libraries, and identify the portal's folder name.

  3. Access the following URL format:

    host:port/cs/idcplg?IdcService=FLD_INFO&path=/Enterprise Libraries/portal-folder-name&IsSoap=1

  4. In the resulting output, search for fApplicationGUID. If it contains uppercase GUID, contact Oracle Support.

Portal Upgrade Fails

While upgrading Oracle WebCenter Portal if the upgrade of a portal fails, review the logs to identify the issue. In UpgradeDetails.txt, search for issue keywords like NAMESPACE or DOCUMENT_DEF to find the related exception stack for more details. This topic describes the scenarios for troubleshooting portal upgrade failure.

Error Message 1

In UpgradeDetails.txt, when you search for DOCUMENT_REF for the portal that failed to be upgraded, the following entry is displayed:

 - java.sql.SQLException: ORA-12899: value too large for column "DEV_WEBCENTER"."WC_PORTAL_ENTITY"."DOCUMENT_REF" 

Solution

One of the possible causes of portal upgrade failure can be that space.xml contains the binary or encoded content for the logo and icon attributes, and the value of these attributes exceeds the character limit. Modify the value for both the attributes by replacing the binary content with the MDS path for the logo and icon files. After you have successfully upgraded the portal, you can again change the portal logo and icon as required.

To fix the issue:

  1. Export space.xml from MDS for the target portal using the importMetadata WLST command.

    For example, the following command exports spaces.xml for a portal named MyPortal to the specified location:

    exportMetadata(application='webcenter', server='WC_Spaces', toLocation='/scratch/export', docs='/oracle/webcenter/space/metadata/spaces/MyPortal/space.xml')

    For information about the exportMetadata WLST command syntax, see exportMetadata in Oracle Fusion Middleware WLST Command Reference for Infrastructure Components.

  2. Verify the value of the Icon and Logo attributes in the exported space.xml file. If the value of these attributes begins with data:image, edit the attributes with the following values and save the file.

    • Icon: /oracle/webcenter/siteresources/scopedMD/shared/images/portalnew_icon.png

    • Logo: /oracle/webcenter/siteresources/scopedMD/shared/images/portalnew_logo.png

  3. Import the modified space.xml file using the importMetadata WLST command.

    For example, the following command exports spaces.xml for MyPortal from the specified location:

    importMetadata(application='webcenter',server='WC_Spaces',fromLocation='/scratch/export',docs='/oracle/webcenter/space/metadata/spaces/MyPortal/space.xml')

    For information about the importMetadata WLST command syntax, see importMetadata in Oracle Fusion Middleware WLST Command Reference for Infrastructure Components.

  4. Run the upgradeWebCenterPortal WLST command again.

  5. Once your portal is upgraded successfully, log on to WebCenter Portal, navigate to your portal, and modify the logo and icon of the portal as per your requirement. For information, see Administering Look and Feel Settings for a Portal in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

Error Message 2

In UpgradeDetails.txt, when you search for NAMESPACE for the portal that failed to be upgraded, the following entry is displayed:

 java.sql.SQLException: ORA-12899: value too large for column "DEV_WEBCENTER"."WC_PORTAL_ENTITY"."NAMESPACE"

Solution

One of the possible causes of this issue can be that the value of a portal resource’s title attribute exceeds the limit of 200 characters. Modify the value not to exceed the character limit.

  1. Review the UpgradeDetails.txt file to identify the portal resource that is causing the issue.

    For example, suppose the title of a page definition file named Page20PageDef.xml exceeds 200 characters.

  2. Export the portal resource using the exportMetadata WLST command.

    The following code exports shows that the Page20PageDef.xml file is exported to the specified location:

    exportMetadata(application='webcenter', server='WC_Spaces', toLocation='/scratch/export', docs='/pageDefs/oracle/webcenter/page/scopedMD/sfe492158_7b1a_421c_a242_37897a 2529e7/Page20PageDef.xml') 

    For information about the exportMetadata WLST command syntax, see exportMetadata in Oracle Fusion Middleware WLST Command Reference for Infrastructure Components.

  3. Edit the value of exported resource’s page_title and page_info attributes to be less than 200 characters.

  4. Import the portal resource using the importMetadata WLST command. For example, the following command imports the updated Page20PageDef.xml from the specified location:

    importMetadata(application='webcenter',server='WC_Spaces',fromLocation='/scrat ch/export', docs='/pageDefs/oracle/webcenter/page/scopedMD/sfe492158_7b1a_421ca242_37897a 2529e7/Page20PageDef.xml') 

    For information about the importMetadata WLST command syntax, see importMetadata in Oracle Fusion Middleware WLST Command Reference for Infrastructure Components.

  5. Run the upgradeWebCenterPortal WLST command again.