Oracle® Fusion Middleware Patching Guide 11g Release 1 (11.1.1.7.0) Part Number E16793-20 |
|
|
PDF · Mobi · ePub |
This chapter provides instructions for Oracle WebCenter Portal users who want to apply the 11.1.1.7.0 patch set to their existing WebCenter Portal installations.
The chapter includes the following sections:
Section 6.1, "New Product Names for Oracle WebCenter and Oracle Enterprise Content Management Suite"
Section 6.2, "Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation"
Section 6.3, "Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation"
Section 6.4, "Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation"
Section 6.5, "Patching an Oracle WebCenter 11.1.1.1.0 Installation"
For additional information about the various starting points available for installing and patching Oracle WebCenter Portal, refer to Oracle WebCenter Portal Installation and Configuration Roadmap.
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 in the procedures documented in this chapter.
Oracle WebCenter and Oracle Enterprise Content Management Suite have been rebranded (renamed) from Release 11.1.1.6.0 onward. Table 6-1 provides a mapping of the old product names and terminology with the new ones.
Note:
This chapter uses the old terminology unless a product name is accompanied by the release number (11.1.1.6.0, 11.1.1.7.0 or 11g) or a Release 11.1.1.6.0 or 11.1.1.7.0-specific feature is discussed.
Table 6-1 Mapping Old Terminology with the Terminology Used From Release 11.1.1.6.0 Onward
Old Name | New Name from Release 11.1.1.6.0 Onward |
---|---|
Product Name Changes |
|
Oracle WebCenter |
Oracle WebCenter Portal |
Oracle WebCenter Spaces |
Oracle WebCenter Portal: Spaces |
Oracle Enterprise Content Management Suite |
Oracle WebCenter Content |
Oracle Universal Content Management (Oracle UCM) |
Oracle WebCenter Content (short name WebCenter Content) |
Oracle Content Server |
Oracle WebCenter Content Server (short name Content Server) |
Feature Name Changes in Documentation |
|
WebCenter application |
WebCenter Portal application (Umbrella term for: Framework applications, Portlet Producer applications, and the Spaces application) |
WebCenter Portal application/WebCenter custom application |
WebCenter Portal: Framework application/Framework application |
Group Space workflows/WebCenter Spaces workflows |
Spaces workflows |
Personal Space |
Home space |
Group Space/Space |
Space |
WebCenter domain |
WebCenter Portal domain |
WebCenter Spaces |
Spaces/Spaces application |
Figure 6-1 illustrates the steps required to update an Oracle WebCenter Portal installation from Release 11.1.1.6.0 to Release 11.1.1.7.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. Many of these steps refer back to chapter 3 or other chapters of this guide.
Table 6-2 Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.6.0
Task | Mandatory or Optional? | Description | Links |
---|---|---|---|
Determine OWSM policy URIs for the Web service end points of Spaces and Discussions, and if required portlet producers |
Mandatory |
Before you begin, note down the OWSM policy URIs so that you can restore the polices in your patched instance If WebCenter Services Portlets producer or any custom portlet producers are deployed and OWSM security policies are configured for their Web service end points, determine the security policy URIs. |
|
Perform the general pre-patching tasks:
|
Mandatory |
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 either version 10.3.6 or 10.3.5. If you are patching your software in silent mode, you need to rename the |
|
Download the installer for WebCenter Portal and other required products |
Mandatory |
Download the 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 FMW 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. |
|
Run Patch Set Installer to patch the following Fusion Middleware products to 11.1.1.7.0:
|
Mandatory only if these products are installed in your environment |
Patch these products before you patch WebCenter Portal. This Oracle Fusion Middleware patch set provides Oracle Portal 11.1.1.6.0, which is the latest version of Oracle Portal. If Oracle Portal 11.1.1.6.0 is already installed, you do not need to patch it. Note: If you have already patched these Fusion Middleware products as per instructions in Chapter 3, you may skip this step. Note: Oracle recommends that Oracle Portal, Forms, Reports and Discoverer should be installed in a separate Middleware home directory that is not shared with other Oracle Fusion Middleware products. |
|
Run the WebCenter Portal installer to patch to Release 11.1.1.7.0 |
Mandatory |
Run the WebCenter Portal 11.1.1.7.0 installer. While applying the patch set, specify your existing Oracle Middleware home and WebCenter Portal Oracle home locations. |
|
Patch the other required Fusion Middleware products |
Mandatory only for the products installed in the Middleware home |
At this stage, you can patch other Fusion Middleware products, such as Oracle WebCenter Content and Oracle SOA Suite, by running their product installers. Note: If you have already patched the other Fusion Middleware products and updated the schemas as per instructions in Chapter 3, you may skip this step. |
|
Update the |
Mandatory |
Use the Patch Set Assistant to update the Before running Patch Set Assistant, you should 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: 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 patched schemas listed in Table 4-1, "Schemas That Require Updating for the Latest Release". |
|
Perform the following post-patching tasks for WebCenter Portal:
|
Mandatory |
You must restore your previous OWSM security policy configuration. If WebCenter Services Portlets producer or any custom portlet producers are deployed, attach the security policies to their Web services end points. If Spaces workflows are configured, upgrade the related configuration. It is optional, but recommended, to upgrade Process Spaces. |
|
Perform post-patching tasks for the other patched Fusion Middleware products. |
Mandatory |
For all the Fusion Middleware products that you patched to Release 11.1.1.7.0, perform the required post-patching tasks. |
|
Start the servers and processes |
Mandatory |
Start your Oracle Fusion Middleware environment. This involves starting your Oracle WebLogic Server Administration Server, managed servers, node manager, OPMN and all system components. |
|
Verify Oracle WebCenter Portal 11.1.1.7.0 installation |
Mandatory |
Verify your patched WebCenter Portal instance by trying to access various URLs like for Administration Server and Oracle WebCenter Portal: Spaces. |
"Verifying the Installation" section in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal |
Figure 6-2 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.7.0. Follow the instructions in Table 6-2 to navigate to the information for each step. Many of these steps refer back to chapter 3 or other chapters of this guide.
Table 6-3 Applying the Latest Patch to Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0
Task | Mandatory or Optional? | Description | Links |
---|---|---|---|
Determine the OWSM policy URIs for Spaces and Discussions Web service end points, and if required, for portlet producers |
Mandatory |
Before you begin, note down the policy names so that you can restore the polices in your patched instance. If any custom portlet producers are deployed and OWSM security policies are configured for their Web service end points, determine the security policy URIs. |
|
Perform the general pre-patching tasks:
|
Mandatory |
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 either version 10.3.6 or 10.3.5. If you are patching your software in silent mode, you need to rename the emCCR file. |
|
Download the installer for WebCenter Portal and other required products |
Mandatory |
Download the 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 FMW 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. |
|
Run Patch Set Installer to patch the following Fusion Middleware products to the latest release:
|
Mandatory only if these products are installed in your environment |
Patch these products before you patch Oracle WebCenter This Oracle Fusion Middleware patch set provides Oracle Portal 11.1.1.6.0, which is the latest version of Oracle Portal. When you run the patch set, Oracle Portal is patched to release 11.1.1.6.0. Note: Oracle recommends that Oracle Portal, Forms, Reports and Discoverer be installed in its own Middleware home directory that it does not share with any other Oracle Fusion Middleware products. Note: If you have already patched these Fusion Middleware products as per instructions in Chapter 3, you may skip this step. |
|
Run the WebCenter Portal installer to patch to Release 11.1.1.7.0 |
Mandatory |
Run the WebCenter Portal 11.1.1.7.0 installer. While applying the patch set, specify your existing Oracle Middleware home and WebCenter Portal Oracle home locations. |
|
Patch the other required Fusion Middleware products |
Mandatory only for the products installed in the Middleware home |
At this stage, you can patch other FMW products, such as Oracle WebCenter Content and Oracle SOA Suite, by running their product installers. Note: If you have already patched the other Fusion Middleware products as per instructions in Chapter 3, you may skip this step. |
|
Update the |
Mandatory |
Use the Patch Set Assistant to update your schemas. 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: 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 patched schemas listed in Table 4-1, "Schemas That Require Updating for the Latest Release". |
|
Perform the following post-patching tasks for WebCenter Portal:
|
Mandatory/Optional |
You must restore your previous security policy configuration. If any custom portlet producers are deployed, attach the security policies to their Web service end points. If group space workflows, SSO, and OHS are configured, it is mandatory to reconfigure them after patching your instance. It is optional, but recommended, to upgrade Pagelet Producer and Process Spaces. |
|
Perform post-patching tasks for the required Fusion Middleware products. |
Mandatory |
For all the Fusion Middleware products that you patched to Release 11.1.1.7.0, perform the required post-patching tasks. |
|
Start the servers and processes |
Mandatory |
Start your Oracle Fusion Middleware environment. This involves starting your Oracle WebLogic Server Administration Server, managed servers, node manager, OPMN and all system components. |
|
Verify Oracle WebCenter Portal 11.1.1.7.0 installation |
Mandatory |
Verify your patched WebCenter Portal instance by trying to access various URLs like for Administration Server and Oracle WebCenter Portal: Spaces. |
"Verifying the Installation" section in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal |
Note:
Beginning with Release 11.1.1.6.0, a new WebCenter Services Portlets producer is available for exposing task flows from WebCenter services as portlets. You can consume portlets from WebCenter Services Portlets in Oracle Portal, Oracle WebLogic Portal, and Oracle WebCenter Interaction applications. For information, see Section 6.8.7.1, "Installing Activity Graph, Analytics, Pagelet Producer, Personalization Server, and WebCenter Services Portlets."
Note:
After patching to Release 11.1.1.7.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 "Setting the Level of Information Written to Log Files" in Oracle Fusion Middleware Administrator's Guide.
This section describes the procedures involved in migrating Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 installation to 11.1.1.7.0. It contains the following subsections:
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 "WebCenter Portal Managed Servers" section in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.
In Release 11.1.1.2.0 and 11.1.1.3.0, the WLS_Services
managed server hosts Oracle WebCenter Discussions and Oracle WebCenter Wiki and Blog Server. From Release 11.1.1.4.0 onward, WLS_Services
is no longer supported. Oracle WebCenter Discussions is deployed to WC_Collaboration
, and wikis and blogs reside on Content Server.
From Release 11.1.1.4.0 onward, a new managed server, WC_Utilities
, is supported that hosts the following WebCenter components: Oracle WebCenter Analytics Collector, Oracle WebCenter Activity Graph Engines, and Oracle WebCenter Personalization.
Figure 6-3 illustrates the steps required to update an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 installation to 11.1.1.7.0. Follow the instructions in Table 6-4 to navigate to the information for each step. Many of these steps refer back to chapter 3 or other chapters of this guide.
Table 6-4 Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Task | Mandatory or Optional? | Description | Link |
---|---|---|---|
Perform the general pre-patching tasks:
|
Mandatory |
Before you begin patching Oracle WebCenter, make sure your system environment and configuration meet the minimum requirements, and the backups are in place. |
Refer to the following sections: |
Perform pre-patching tasks for WebCenter:
|
Mandatory |
If any custom portlet producers are deployed and OWSM security policies are configured for their Web service end points, determine the security policy URIs. |
|
Patch WebLogic Server to the latest version |
Mandatory |
||
Rename the emCCR File if using the silent mode for patching |
Mandatory for silent mode |
Section 3.4.8, "Renaming the emCCR File for Silent Patching" |
|
Download the installer for 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. |
|
Run Patch Set Installer to patch the following Fusion Middleware products to the latest release:
|
Mandatory only if these products are installed in your environment |
Patch these products before you patch Oracle WebCenter This Oracle Fusion Middleware patch set provides Oracle Portal 11.1.1.6.0, which is the latest version of Oracle Portal. When you run the patch set, Oracle Portal is patched to release 11.1.1.6.0. Note: Oracle recommends that Oracle Portal, Forms, Reports and Discoverer be installed in its own Middleware home directory that it does not share with any other Oracle Fusion Middleware products. Note: If you have already patched these Fusion Middleware products as per instructions in Chapter 3, you may skip this step. |
|
Run the WebCenter Portal installer to patch to Release 11.1.1.7.0 |
Mandatory |
Run the WebCenter Portal 11.1.1.7.0 installer. While applying the patch set, specify your existing Oracle Middleware home and WebCenter Portal Oracle home locations. |
|
Run other product installers to patch the other required Fusion Middleware products |
Mandatory only for the products installed in the Middleware home |
At this stage, you can patch other FMW products, such as Oracle WebCenter Content and Oracle SOA Suite. Note: If you have already patched the other Fusion Middleware products as per instructions in Chapter 3, you may skip this step. |
|
Update the required schemas: |
Mandatory |
Update the WebCenter-specific schemas. Note: For 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 Spaces schema owner prior to running the Patch Set Assistant to upgrade the schema to Release 11.1.1.7.0. Connect as a Note: 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 patched schemas listed in Table 4-1, "Schemas That Require Updating for the Latest Release". |
|
Update the Spaces application using either of the following:
|
Mandatory |
If Oracle WebCenter is installed on multiple machines, you can update your software only by using WLST commands, and not through the automated script. |
|
Perform post-patch tasks for the required Fusion Middleware products. |
Mandatory |
For all the Fusion Middleware products that you patched to Release 11.1.1.7.0, perform the required post-patching tasks. |
|
Perform post-patching tasks for WebCenter Portal:
|
Mandatory |
Perform post-patching tasks for WebCenter Portal. |
|
Perform post-patch tasks for WebCenter Spaces:
|
Mandatory |
Perform post-patch tasks for WebCenter Spaces. |
Section 6.8.5, "Performing Post-Patching Tasks for Oracle WebCenter Spaces" |
Perform post-patch tasks for WebCenter security:
|
Mandatory |
You must configure the security policy for Spaces and Discussions Web service end points. It is mandatory to configure security policies for portlet producers only if policies were configured in your pre-patched instance. If an external authentication provider or identity asserter was configured in your pre-patched instance, you must configure it again after patching the instance. Note: If you want to set additional WS-Security for WebCenter Portal, refer to the chapter "Configuring WS-Security" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal. |
|
Add new Oracle WebCenter Portal features:
|
Optional |
Compared to Release 11.1.1.2.0 or 11.1.1.3.0, Oracle WebCenter Portal 11.1.1.7.0 includes several new features. You can extend the WebCenter Portal domain to add new features and can update your applications, if required. |
|
Start the servers and processes |
Mandatory |
Start your Oracle Fusion Middleware environment. This involves starting your Oracle WebLogic Server Administration Server, managed servers, node manager, OPMN and all system components. |
|
Verify Oracle WebCenter Portal 11.1.1.7.0 installation |
Mandatory |
Verify your patched WebCenter Portal instance by trying to access various URLs like for Administration Server and Oracle WebCenter Portal: Spaces. |
"Verifying the Installation" section in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal |
You can update Oracle WebCenter 11.1.1.7.0 using either Node Manager and automated script, or WebLogic Scripting Tool (WLST).
This section includes the following subsections:
Section 6.4.3.1, "Updating Oracle WebCenter Using Node Manager and Automated Script"
Section 6.4.3.2, "Updating Oracle WebCenter Using WLST Commands"
Note:
If Oracle WebCenter is installed on multiple machines, you can update your software only by using WLST commands, and not through the automated script. Make sure that the product installer is run on each WebCenter Oracle home directory on each machine, and all the domains are updated using pack/unpack.
The Oracle WebCenter patch includes a script called upgrade.py
that you can use to upgrade to the latest release. This script shuts down all the Managed Servers and the Administration Server at the beginning of the update process, and then starts all the servers during the update process.
You can use this script to update Oracle WebCenter only if you have set up Node Manager, have Oracle WebCenter installed on a single machine, and have verified that it is configured correctly. If your Node Manager is not configured correctly, you must use the WLST commands instead of this script to patch Oracle WebCenter.
This section includes the following subsections:
To use the upgrade.py
script, you must configure Node Manager as follows:
Make sure that all the servers in the domain (including the Administration Server) are associated with a machine that is configured to use your Node Manager. See "Configure a Machine to Use Node Manager" in Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.
If you are using demo certificates (the certificates that ship with Oracle WebLogic Server), disable host name verification for all the servers. For more information, see "Disable host name verification" at the following URL:
http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/security/DisableHostNameVerification.html
Ensure the following properties are set to true
in the nodemanager.properties
file:
StartScriptEnabled
for the Node Manager, so that Managed Servers can receive proper classpath and command arguments.
DomainRegistrationEnabled
, so that domain can be registered.
Refer to Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server for more information.
Make sure the nmConnect
command can be used to connect to the Node Manager in WLST. If you are in a production environment, follow the instructions in "Using nmConnect in a Production Environment" in Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.
Make sure the nmStart
command can be used to start the Administration Server in WLST. If you are in a production environment, a user name and password may be required to start the Administration Server, so ensure that Node Manager has the required credentials.
For more information, refer to "nmstart" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference, and also "How Node Manager Starts an Administration Server" in Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.
To verify that Node Manager has been configured correctly:
Stop all the servers in your domain.
Start WLST and connect to the Node Manager using nmConnect
. For example, on a UNIX operating system:
cd WebCenter_ORACLE_HOME/common/bin ./wlst.sh nmConnect(username = 'weblogic', password = 'examplepassword', host = 'localhost', port = '5556', domainDir = 'DOMAIN_HOME', nmType = 'ssl')
Start the Administration Server using nmStart
. For example:
nmStart('AdminServer')
Connect to the Administration Server in WLST and start a Managed Server. For example:
connect() start('WLS_Spaces')
Check that the Managed Server you started is running. For example, try to access the following URL and log in:
http://localhost:8888/webcenter
Note:
If you are not able to verify your Note Manager configuration, then you must use WLST commands instead of the automated script to update Oracle WebCenter.
To update Oracle WebCenter using the Node Manager and the automated script:
Ensure that you have run the Oracle WebCenter installer to update your software. For information, see Section 3.5.2, "Downloading the Required Installer" and Section 3.6.1, "Starting the Installer."
Ensure that you have updated your database schemas using the Patch Set Assistant. For information, see Section 3.7, "Updating Your Schemas with Patch Set Assistant".
Run the upgrade.py
script as described in Section 6.4.3.1.4, "How to Run the Oracle WebCenter Automated Script".
Copy the Trust Store file from the Oracle home directory to the Oracle WebLogic Server domain directory.
For example:
cp MW_HOME/oracle_common/modules/oracle.jps_11.1.1/jps-wls-trustprovider.jar DOMAIN_HOME/lib/mbeantypes/jps-wls-trustprovider.jar
Restart the Node Manager, Administration Server, and the Managed Servers in the domain.
The upgrade.py
script must be run on the same machine as the Administration Server. The script is located in the WebCenter_ORACLE_HOME
/webcenter/scripts/upgrade_11.1.1.4
(on UNIX operating systems) or WebCenter_ORACLE_HOME
\webcenter\scripts\upgrade_11.1.1.4
(on Windows operating systems) directory.
The following is the command line syntax for running the upgrade.py
script:
upgrade.py path_to_upgrade_properties_file administrator_password node_manager_password
The upgrade.py
script takes optional command line parameters, where:
path_to_upgrade_properties_file
is the path to the upgrade properties file
See Section 6.4.3.1.9, "Properties That can be Set in the Upgrade Properties File" and Section 6.4.3.1.10, "Formatting Your Properties File" for more information about the properties file.
administrator_password
is the password for the Administration Server.
node_manager_password
is the password for the Node Manager.
Refer to the following sections for examples of how to run the upgrade.py
script.
If no optional parameters are specified, the script uses the default values for all the properties with the exception of the domain.directory
and the passwords; you are prompted for these values. Here is an example:
cd WebCenter_ORACLE_HOME/common/bin ./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py
If you specify a properties file that sets the value of the user.config.file
property, then the script overrides the default values of the properties with the values specified in the properties file and connects to the Administration Server and Node Manager with the credentials stored in the user configuration file. Here is an example:
cd WebCenter_ORACLE_HOME/common/bin ./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py ~/upgrade.properties
If you specify a properties file and that properties file does not set the value of the user.config.file
property and you do not pass the Administration Server and Node Manager passwords as a command line argument, then the script overrides the default values of the properties with the values specified in the properties file and prompt for passwords.
If you specify a properties file and administrator_password, then the script overrides the default values of the properties with the values specified in the properties file and uses the specified password to connect to the Administration Server. You will be prompted for the Node Manager password even if the Node Manager user name is same as the Administrator user name. Here is an example:
cd WebCenter_ORACLE_HOME/common/bin ./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py ~/upgrade.properties example_admin_password
If you specify a properties file, administrator_password and node_manager_password, then it overrides the default values of the properties with the values specified in the properties file and uses the passwords specified to connect to the Administration Server and Node Manager. Here is an example:
cd WebCenter_ORACLE_HOME/common/bin ./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py ~/upgrade.properties example_admin_password example_nm_password
Table 6-5 lists the properties that can be set in the upgrade properties file.
Tip:
A sample upgrade properties (upgrade.properties
) file is available in the WebCenter_ORACLE_HOME
/webcenter/scripts/upgrade_11.1.1.4
directory.
Table 6-5 Upgrade Properties File
Property | Description |
---|---|
|
Path to the domain directory (Domain Home). |
|
Path to the WebCenter Oracle home directory. |
|
Name of a user that is part of the LDAP wired to WebCenter Spaces and has Administrator privileges in the WLS embedded LDAP. To give a user Administrator privileged in WLS embedded LDAP:
|
|
URL used to connect to the Administration Server. |
|
Name of the Administration Server. |
|
User name for the Node Manager. |
|
Host name for the Node Manager server. |
|
Port number for the Node Manager server. |
|
Connection type for the Node Manager server. |
|
Indicates whether previous WebCenter Spaces customizations using the Set this property to Warning: If you upgrade your WebCenter domain with |
|
Name and location of a user configuration file which contains an encrypted username and password. When you create a user configuration file, the NOTE: If you set this property, you do not need to pass a password and it does not use the See |
|
Name and location of the key file that is associated with the specified user configuration file and is used to decrypt it. NOTE: You need to set this property only if you set the See |
You must make sure you escape values correctly in your properties file. This is particularly important when entering Windows paths because all backslashes must be escaped with backslashes (in other words, a single backslash is represented by two backslashes in a Java properties file).
Refer to the following URL for details:
http://download.oracle.com/javase/6/docs/api/java/util/Properties.html#load%28java.io.Reader%29
The following is a sample properties file on a Windows operating system:
domain.directory=C:\\Middleware\\domains\\domain_name oracle.home=C:\\Middleware\\Oracle_WC1 admin.user=weblogic admin.url=t3://examplehost:7001 admin.server=AdminServer nodemanager.user=node_manager_user nodemanager.host=localhost nodemanager.port=5556 nodemanager.type=ssl upgrade.custom.spaces=false
The following is a sample properties file on a UNIX operating system:
domain.directory=/home/Middleware/domains/domain_name oracle.home=/home/Middleware/Oracle_WC1 admin.user=weblogic admin.url=t3://examplehost:7001 admin.server=AdminServer nodemanager.user=node_manager_user nodemanager.host=localhost nodemanager.port=5556 nodemanager.type=ssl upgrade.custom.spaces=false
If you choose not to configure the Node Manager, you can update your middle tier by using WLST commands. You must run the WLST commands from the same machine on which the Administration Server is running.
Before you upgrade Oracle WebCenter using WLST:
Ensure that you have updated your Oracle WebCenter software by using Oracle WebCenter installer.
For more information, see Section 3.5.2, "Downloading the Required Installer" and Section 3.6.1, "Starting the Installer".
Ensure that you have updated your database schemas.
For more information, see Section 3.7, "Updating Your Schemas with Patch Set Assistant".
To update Oracle WebCenter using WLST commands:
Stop the Administration Server and all Managed Servers.
Start WLST from the WebCenter Oracle home.
On UNIX operating systems:
cd WebCenter_ORACLE_HOME/common/bin
./wlst.sh
On Windows operating systems:
cd WebCenter_ORACLE_HOME\common\bin
wlst.cmd
Ensure the external LDAP server is up and running, then run the upgradeOpss
command in offline mode (without connecting to any server):
On UNIX operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME/config/fmwconfig/jps-config.xml', jaznData='MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml')
On Windows operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME\\config\\fmwconfig\\jps-config.xml', jaznData='MW_HOME\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_config\\system-jazn-data.xml')
Note:
If you need to re-run the upgradeOpss()
command, you must exit the current WLST session and start a new session before re-running upgradeOpss()
.
Run the upgradeWebCenterDomain
command in offline mode:
upgradeWebCenterDomain(domainDirName='DOMAIN_HOME', oracleHome='WebCenter_ORACLE_HOME', upgradeCustomSpaces=[1|0])
Where:
domainDirName
- Replace DOMAIN_HOME
with the full path to your Domain home directory.
oracleHome
- Replace WebCenter_ORACLE_HOME
with the full path to your WebCenter Oracle home directory.
upgradeCustomSpaces
- Set to 1
if you used the custom.webcenter.spaces
shared library to customize WebCenter Spaces and you want to migrate your customizations to the upgraded instance. For information about how to use your extensions in WebCenter Spaces, refer to:
http://www.oracle.com/technetwork/middleware/webcenter/owcs-ps4-wcs-ext-samples-wp-406559.pdf
WARNING:
If you upgrade your WebCenter domain with upgradeCustomSpaces
set to 0
, none of your previous customizations and resources that you developed, like page templates and skins, will be available in the upgraded WebCenter Spaces instance; there is no facility to migrate WebCenter Spaces customizations after the upgrade process.
For example:
upgradeWebCenterDomain(domainDirName='/home/Oracle/Domains/wc_domain', oracleHome='/home/Oracle/Middleware/Oracle_WC1', upgradeCustomSpaces=1)
Note:
You may see error messages when you run the upgradeWebCenterDomain
command. These errors can be safely ignored so long as there is some text indicating that your operation was completed successfully. For more information about error messages, refer to Oracle Fusion Middleware Release Notes.
Start the Administration Server.
Connect to the Administration Server.
connect()
In the domain running the WebCenter Spaces Managed Server, run the upgradeWebCenterPermissions
command to add the required permission to the LDAP store.
upgradeWebCenterPermissions()
Note:
You may see error messages when you run the upgradeWebCenterPermissions
command. These errors can be safely ignored so long as there is some text indicating that your operation was completed successfully. For more information about error messages, refer to the Oracle Fusion Middleware Release Notes.
All of the instructions to this point have been for a single node. If your domain has servers running on more than one machine, you need to pack and unpack your domain to replicate the changes to other nodes in your cluster.
To pack and unpack your updated domain:
Pack the Administration Server:
cd WebCenter_ORACLE_HOME/common/bin ./pack.sh -managed=true -domain=DOMAIN_HOME -template=wcdomaintemplate.jar -template_name=wc_domain_template
Copy wcdomaintemplate.jar
to the WebCenter_ORACLE_HOME
/common/bin
on the other machines.
Remove or move the old domain directories (DOMAIN_HOME
and APPLICATION_HOME
) on the other machines.
Unpack the domain on each of the other machines:
cd WebCenter_ORACLE_HOME/common/bin ./unpack.sh -domain=DOMAIN_HOME -template=wcdomaintemplate.jar
Start the WebCenter Managed Servers:
WC_Spaces
(WebCenter Spaces)
WC_Portlet
(Oracle Portlet Producers)
WC_Collaboration
(Oracle WebCenter Discussion Server)
Make sure the WC_Spaces
server is up and running before moving on to the next step.
Disconnect from the Administration Server, and connect to the WC_Spaces
server as an Oracle WebCenter administrator that is defined in the external LDAP server and is defined as an administration user in the embedded Oracle WebLogic Server.
Note:
It is important to note that the administration user must be defined both as a user in the external LDAP directory and as a user with administration privileges in the embedded Oracle WebLogic Server LDAP directory.
If necessary, you can add a user to the Administration Group of the embedded Oracle WebLogic Server LDAP server as follows:
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.
Click Add Condition, then select User from the "Predicate List" field, then click Next.
Enter the user name in the "User Argument Name" field, then click Add.
Click Finish. The user you just entered should now be listed along with the administrators.
Save your changes and exit.
In the domain running the WebCenter Spaces managed server, run the upgradeWebCenterApplication
command.
upgradeWebCenterApplication(appName='webcenter')
If you have a cluster environment where there are multiple servers with WebCenter Spaces deployed, you must specify the server name. For example:
upgradeWebCenterApplication(appName='webcenter', server="server_name")
Copy the Trust Store file from the Oracle home directory to the Oracle WebLogic Server domain directory.
For example:
cp MW_HOME/oracle_common/modules/oracle.jps_11.1.1/jps-wls-trustprovider.jar DOMAIN_HOME/lib/mbeantypes/jps-wls-trustprovider.jar
Restart the Administration Server and the Managed Servers in the domain.
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.7.0 patch.
Figure 6-4 illustrates the steps required to update an Oracle WebCenter 11.1.1.1.0 installation to Release 11.1.1.7.0. Table 6-6 describes these steps in detail. Click the required steps in the table to navigate to the information about each step. Alternatively, follow the instructions in Appendix C, "Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)".
Table 6-6 Applying the Latest Patch to Oracle WebCenter 11.1.1.1.0
Task and Link to More Information | Mandatory or Optional? | Links |
---|---|---|
Mandatory |
||
Patch Oracle WebCenter and other Fusion Middleware products to 11.1.1.2.0 |
Mandatory |
|
Perform post-patching configuration for WebCenter: |
Mandatory |
Appendix C, "Post-Migration Configuration for Oracle WebCenter" |
Perform post-patching configuration for other Fusion Middleware products |
Mandatory |
Appendix C, "Post-Migration Configuration for Oracle Fusion Middleware Components" |
Mandatory |
||
Mandatory |
Section 6.4, "Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation" |
This section provides information to help you troubleshoot problems you may encounter while patching or after patching Oracle WebCenter.
This section provides information to help you troubleshoot problems you may encounter while patching Oracle WebCenter.
Problem
While running the upgrade.py
script, you may encounter the following error:
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager.
Solution
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 instance.
This section provides information to help you troubleshoot issues you may encounter after patching to WebCenter Portal 11.1.1.7.0. It contains the following subsections:
Section 6.6.2.2, "Content Getting Clipped and Inner Scrollbars Appearing"
Section 6.6.2.3, "Pretty URLs Not Working for Page Navigation"
Section 6.6.2.4, "Content Queries Not Rendered in Navigation Model"
Section 6.6.2.6, "Comments and Likes Not Displayed in Activity Stream"
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.
Problem
In the 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 Spaces 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. When you upgrade your Spaces instance, Top Navigation is set as the default template, and therefore space 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 spaces, 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.
Problem
In your patched Spaces 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 space have changed.
To go to a specific page in the Home Space, use:
http://host:port/webcenter/spaces/profile/userName/page/escapedPageDisplayName
The variable userName
is your user name or the name of the user who owns the page in the Home Space. 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
Problem
After patching to Release 11.1.1.7.0, content queries do not get rendered in a navigation model.
Solution
After patching 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 "Rebuilding the Collection" in Oracle WebCenter Content System Administrator's Guide for Content Server.
Problem
After you patched your Oracle WebCenter 11.1.1.2.0 instance, blog posts are not getting displayed in spaces.
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 space, 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 space 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 space. This will create a new page that exposes the wiki or blog. You can then delete the old broken page.
Problem
In your patched 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 WebCenter Portal 11.1.1.7.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.
Preparing to patch your 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 WebCenter Portal. This section describes all the WebCenter Portal-specific pre-patching tasks that you may need to perform before patching WebCenter Portal to release 11.1.1.7.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 WebCenter Portal 11.1.1.6.0, refer to the diagram and the table given in Section 6.2, "Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation."
This section contains the following subsections:
Section 6.7.2, "Saving Your OmniPortlet and WebClipping Customizations"
Section 6.7.3, "Running purgeMetadata() for WebCenter Spaces"
Section 6.7.4, "Considerations for Upgrading Oracle WebCenter Content or Oracle ECM"
In an out-of-the-box installation, the Web service end points for Spaces and Discussions are seeded with Oracle Web Services Manager (OWSM) security policies. In certain configurations, WSRP portlet producer endpoints (WSRP_v2_Markup_Service
) could also be configured with OWSM security policies. When you patch your WebCenter Portal instance, the assigned security policy configuration is changed to no security policy, causing functional loss. To be able to restore OWSM security policies in your patched instance, you must note down the policy URIs before you patch the instance.
This section contains the following sections:
Chapter 6, "Determining OWSM Policy URI for the Spaces Web Service End Point"
Chapter 6, "Determining OWSM Policy URI for the Discussions Web Service End Point"
Chapter 6, "Determining OWSM Policy URIs for Portlet Producer Web Service End Points"
To list the OWSM security policy URI for the Spaces Web service end point:
Ensure the WC_Spaces
managed server is up and running.
Invoke the WLST script from your WebCenter Portal Oracle home directory, and connect to the Administration Server for WebCenter Portal.
For information, see the section "Running Oracle WebLogic Scripting Tool (WLST) Commands" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
Run the following command:
listWebServicePolicies('/wc_domain/WC_Spaces/webcenter#11.1.1.4.0', 'webcenter', 'web', 'SpacesWebService', 'SpacesWebServiceSoapHttpPort')
Where, wc_domain refers to the WebCenter Portal domain, and WC_Spaces is the name of the managed server on which the Spaces application is deployed. The other parameters are all fixed. To get details about parameters, you can use the WLST command help('listWebServicePolicies')
.
If you are using the out-of-the-box OWSM security policy, the command result is displayed in the following format:
SpacesWebServiceSoapHttpPort :security : oracle/wss11_saml_or_username_token_with_message_protection_service_policy, enabled=true
Attached policy or policies are valid; endpoint is secure.
Note down the security policy name displayed in bold. You will need to specify this security policy URI to restore the security configuration post patching.
To list the OWSM policy URI for the Discussions Web service end point:
Ensure the WC_Collaboration
managed server is up and running.
Invoke the WLST script from your WebCenter Portal Oracle home directory and connect to the Administration Server for WebCenter Portal. For information, see the section "Running Oracle WebLogic Scripting Tool (WLST) Commands" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
Run the following command:
listWebServicePolicies('/wc_domain/WC_Collaboration/owc_discussions', 'owc_discussions', 'web', 'OWCDiscussionsServiceAuthenticated', 'OWCDiscussionsServiceAuthenticated')
Where, wc_domain refers to the WebCenter Portal domain, and WC_Collaboration is the name of the managed server on which Discussion Server is deployed. The other parameters are all fixed.
If you are using the out-of-the-box OWSM security policy, the command's result is of the following format:
OWCDiscussionsServiceAuthenticated :security : oracle/wss10_saml_token_service_policy, enabled=true
Attached policy or policies are valid; endpoint is secure.
Note down the security policy URI highlighted in bold. You will need to specify the security policy name while restoring the security settings post patching.
All out-of-the-box portlet producers get redeployed during the patching process. If you have OWSM security policies attached to portlet producers' Web service end points, you must note down the policy URIs.
For this, invoke the WLST script from your WebCenter Portal Oracle home directory and connect to the Administration Server for WebCenter Portal. For information, see the section "Running Oracle WebLogic Scripting Tool (WLST) Commands" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal. Also, ensure the WC_Portlet
managed server and any custom managed servers on which custom portlet producers are deployed are up and running. Then, run WLST commands to determine OWSM policy URIs for your portlet producers.
WebCenter Services Portlets producer
This producer is available out-of-the-box from WebCenter Portal release 11.1.1.6.0 onward. If this producer is deployed in your instance, run the following command to list the security policy attached to the Web service end point, services-producer:
listWebServicePolicies('/wc_domain/WC_Portlet/services-producer#11.1.1.6.0','services-producer','web','WSRP_v2_Service','WSRP_v2_Markup_Service')
Custom portlet producers
You may have various custom portlet producers deployed in your WebCenter Portal instance, and have OWSM security policies attached to custom portlet producers' Web service end points (WSRP_v2_Markup_Service
). After patching your WebCenter Portal instance, if you intend to redeploy the custom portlet producers, you must note down the OWSM policy URI for each custom portlet producer before your patch your instance.
For example, if your custom portlet producer is named TestJSR286
and deployed to WC_PORTLET
managed server with version 1.0, run the following command to determine the security policy URI:
listWebServicePolicies('/wc_domain/WC_Portlet/TestJSR286#1.0','TestJSR286','web','WSRP_v2_Service','WSRP_v2_Markup_Service')
The following is a sample output for the command:
WSRP_v2_Markup_Service :
security : oracle/wss10_saml_token_service_policy, enabled=true
Attached policy or policies are valid; endpoint is secure.
Note down the security policy URI highlighted in bold. You will need to specify the security policy URI while restoring the security settings in your patched instance.
Note:
Perform the procedure listed in this section only if you are using OmniPortlet and WebClipping customizations, and they are stored in a file-based preferences store. By default, in Oracle WebCenter 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 or Oracle Portal, both the OmniPortlet and WebClipping applications are re-deployed, and all configuration data stored within file-based preference stores is lost. You must save the OmniPortlet and WebClipping configuration and customizations to ensure that customizations are not lost when you apply the patch set.
To save and back up your customizations:
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 domain, as specified on the "Specify Domain Name and Location" screen in the Configuration Wizard.
Run the following command to back up the directory:
On UNIX operating systems:
cp -fr path_to_war_directory/WEB-INF/providers/omniPortlet backup_location
cp -fr path_to_war_directory/WEB-INF/providers/webclipping backup_location
On Windows operating systems:
xcopy /y/e path_to_war_directory\WEB-INF\providers\omniPortlet backup_location
xcopy /y/e path_to_war_directory\WEB-INF\providers\webclipping backup_location
If you are using WebCenter Spaces, you must run the purgeMetadata()
WLST command to remove older versions of documents in MDS. This enables the patching process to run on a smaller set of data and thus decrease the time required to upgrade.
To purge metadata for WebCenter Spaces:
Start your Administration Server and Spaces Managed Server (WLS_Spaces
) as the purgeMetadata()
command is an online command.
Start WLST from your WebCenter Oracle home.
On UNIX operating systems:
cd WebCenter_ORACLE_HOME/common/bin
./wlst.sh
On Windows operating systems:
cd WebCenter_ORACLE_HOME\common\bin
wlst.cmd
Connect to the Administration Server using the WLST connect()
command.
Run the purgeMetadata()
WLST command. For example, run the following command to purge metadata older than 3060 seconds:
purgeMetadata('webcenter', 'WLS_Spaces', 3060)
See "purgeMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference for more details.
Re-collect the database statistics. For example, you can connect to the WebCenter MDS
schema using SQLPlus:
execute dbms_stats.gather_schema_stats(ownname=>null, options=>'GATHER AUTO');
Stop your WLS_Spaces
managed server and Administration Server.
For more information, see "Metadata Services (MDS) Custom WLST Commands" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
Note:
Beginning with Release 11.1.1.6.0, Oracle Enterprise Content Management Suite (Oracle ECM) and Oracle Universal Content Management (Oracle UCM) have been rebranded (renamed) as Oracle WebCenter Content, and Oracle Content Server has been renamed as Oracle WebCenter Content Server (short name Content Server).
Oracle WebCenter Content includes Content Server. If your WebCenter Portal instance uses Content Server as a content repository, consider the following:
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 11g or WebCenter Portal 11g.
If your existing environment uses Oracle Content Server 10g as the content repository, you must upgrade to Oracle WebCenter Content 11.1.1.7.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 WebCenter Portal and Oracle WebCenter Content must be of the same patch set level. For example, if you are patching to WebCenter Portal 11.1.1.7.0, you must also patch to Oracle WebCenter Content 11.1.1.7.0.
WebCenter Portal and Oracle WebCenter Content can be within the same domain or in separate domains.
For information about upgrading to Oracle WebCenter Content 11g, see Oracle Fusion Middleware Upgrade Guide for Oracle WebCenter Content.
Note:
For Content Server 11g, Oracle recommends Folders (the FrameworkFolders
component) as the folder interface instead of Contribution Folders (the Folders_g
component). However, WebCenter Portal uses the Folders_g
foldering capability. Therefore, to use Content Server 11g as a content repository for WebCenter Portal, you MUST have Folders_g
enabled and FrameworkFolders
disabled. You cannot have both enabled on an Oracle WebCenter Content instance.
This section describes all the tasks that you may need to perform to complete patching WebCenter Portal to release 11.1.1.7.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 WebCenter Portal 11.1.1.6.0, refer to the diagram and table given in Section 6.2, "Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation."
This section contains the following subsections:
Section 6.8.2, "Extending the Domain Using the Pagelet Producer Upgrade Template"
Section 6.8.5, "Performing Post-Patching Tasks for Oracle WebCenter Spaces"
When you patch your WebCenter Portal instance, the assigned Oracle Web Services Manager (OWSM) security policies are removed, and no other security policy is applied. You must restore your previous security policy configuration using the policy names you noted down in Section 6.7.1, "Determining OWSM Policy URIs for Spaces, Discussions, and Portlet Web Service End Points."
To restore or attach OWSM security policies to Web service end points:
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.
Connect to the Administration Server for WebCenter Portal, for running WLST commands. For information, see the section "Running Oracle WebLogic Scripting Tool (WLST) Commands" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
Run the following WLST command to attach the OWSM security policy to the Web service endpoint (SpacesWebService
) for Spaces:
attachWebServicePolicy('webcenter', 'webcenter', 'web', 'SpacesWebService', 'SpacesWebServiceSoapHttpPort', 'oracle/wss11_saml_or_username_token_with_message_protection_service_policy')
Where oracle/wss11_saml_or_username_token_with_message_protection_service_policy
is the policy you want to restore. Note that this is the same value you obtained by running the listWebServicePolicies
WLST command against the Spaces Web service end point in Section 6.7.1.1, "Determining OWSM Policy URI for the Spaces Web Service End Point."
Run the following WLST command to attach the OWSM security policy to the Web service endpoint (OWCDiscussionsServiceAuthenticated
) for Discussions:
attachWebServicePolicy('owc_discussions', 'owc_discussions', 'web', 'OWCDiscussionsServiceAuthenticated', 'OWCDiscussionsServiceAuthenticated', 'oracle/wss10_saml_token_service_policy')
Where oracle/wss10_saml_token_service_policy
is the policy you want to restore. Note that this is the same value that you obtained by running listWebServicePolicies
against the Discussions Web service end point in Section 6.7.1.2, "Determining OWSM Policy URI for the Discussions Web Service End Point."
Run the WLST command to attach the OWSM security policy to the Web service endpoint (WSRP_v2_Markup_Service
) 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:
attachWebServicePolicy('/wc_domain/WC_Portlet/TestJSR286#1.0','TestJSR286','web','WSRP_v2_Service','WSRP_v2_Markup_Service', 'oracle/wss10_saml_token_service_policy')
Where oracle/wss10_saml_token_service_policy
is the policy you want to restore. Note that this is the same value that you obtained by running listWebServicePolicies
against the portlet producer's Web service end point in Section 6.7.1.3, "Determining OWSM Policy URIs for Portlet Producer Web Service End Points."
Note:
This step is required only if any custom portlet producers are deployed in your 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 WebCenter Services Portlets producer:
attachWebServicePolicy('services-producer#11.1.1.6.0','services-producer','web','WSRP_v2_Service','WSRP_v2_Markup_Service', 'oracle/wss10_saml_token_service_policy')
Where oracle/wss10_saml_token_service_policy
is the policy you want to restore.
Note:
This step is required only if you are patching from release 11.1.1.6.0, and WebCenter Services Portlets producer is deployed.
WebCenter Services Portlets producer is available from release 11.1.1.6.0 onward. If you are patching from a previous release and want to deploy the WebCenter Services Portlets producer, you must first extend your domain as described in Section 6.8.7.1, "Installing Activity Graph, Analytics, Pagelet Producer, Personalization Server, and WebCenter Services Portlets." Then, attach the OWSM security policy for the Web services end point for WebCenter Services Portlets producer.
Restart the WC_Spaces
, WC_Collaboration
, and WC_Portlet
managed servers. Also restart custom managed servers if custom portlet producers are deployed to those managed servers.
A new version of Pagelet Producer was released with WebCenter Portal 11.1.1.6.0. If your upgraded WebCenter instance already has Pagelet Producer installed, you can choose to apply the new Pagelet Producer upgrade template to your domain to take advantage of the new features.
To apply the Pagelet Producer upgrade template:
Stop the Admin server and all managed servers.
Start the Configuration Wizard on the machine running the Admin server.
On UNIX, run WebCenter_ORACLE_HOME
/common/bin/config.sh
.
On Windows, run WebCenter_ORACLE_HOME
\common\bin\config.cmd
.
Select Extend an existing WebLogic domain and click Next.
Select your domain and click Next.
Select the Extend my domain using an existing extension template option.
Specify the path to the template, oracle.pagelet-producer-upgrade_template_11.1.1.jar
and click Next. The template is available at the following location:
WebCenter_ORACLE_HOME
/common/templates/applications/oracle.pagelet-producer-upgrade_template_11.1.1.jar
Click Next on the remaining screens until you get the Configuration Summary screen, then click Extend.
For more information on extending a domain, see "Extending a WebLogic Domain in Graphical Mode" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.
Start the Admin server and all managed servers.
Reconfigure the Pagelet Producer connections for the Spaces application and WebCenter custom applications (Framework applications) by using Fusion Middleware Control or WLST. For information, see "Registering the Pagelet Producer" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
Note:
In the previous release, it was mandatory to deploy Pagelet Producer to the following path:
http://<pagelet-producer-server>:<port>/
Pagelet Producer could not be accessed if it was deployed at any other location other than the root '/
'. 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.
If you have OHS and SSO configured, you must configure them to use the new context root. For information, see Section 6.8.3, "Updating SSO and OHS Configuration."
Undeploy the older version of Pagelet Producer.
Stop WC_Portlet
, the managed server on which Pagelet Producer is running.
In WLS Console, click Deployments.
Select the checkbox 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.
If you have Oracle HTTP Server (OHS) and Single Sign-on (SSO) configured in your upgraded WebCenter Portal environment, you may need to update the configuration for Pagelet Producer, Portlet Producer applications and Oracle SES.
This section includes the following subsections:
Section 6.8.3.1, "Updating OHS Configuration for Pagelet Producer"
Section 6.8.3.2, "Updating SSO Configuration for Pagelet Producer"
Section 6.8.3.3, "Updating SSO Configuration for Portlet Producer Applications"
Section 6.8.3.4, "Updating SSO Configuration for Oracle SES"
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:
WT_ORACLE_HOME
/instances/
your_instance
/config/OHS/
ohs1
Where, WT_ORACLE_HOME
refers to the Web Tier Oracle Home.
Replace the following entries, if present:
<Location /pageletadmin>
SetHandler weblogic-handler
WebLogicHost webcenter.example.com
WebLogicPort 8889
</Location>
<Location /authenticateWithApplicationServer>
SetHandler weblogic-handler
WebLogicHost webcenter.example.com
WebLogicPort 8889
</Location>
With the following entry:
<Location /pagelets> SetHandler weblogic-handler WebLogicHost webcenter.example.com WebLogicPort 8889 </Location>
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 WebCenter 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.
Updating OAM 11g policies for Pagelet Producer
Updating OAM 11g policies for Pagelet Producer involves creating the following resources:
/pagelets
* and /pagelets/.../
*
/pagelets/authenticateWithApplicationServer
* and /pagelets/authenticateWithApplicationServer/.../
*
/pagelets/admin
* and /pagelets/admin/.../
*
To update OAM 11g policies for Pagelet Producer:
Log in to the OAM Console using the following URL format:
http://
host:port
/oamconsole
Go to Policy Configuration > Application Domains. The Policy Manager pane displays.
Locate the application domain created while registering the WebGate agent.
Open the Resources tab, and click New Resource.
Add the resources for Pagelet Producer applications.
To add the /pagelets
* resource:
In Resource Type, select HTTP.
In the Host Identifier field, select the host created while registering the WebGate agent.
In the Resource URL field, enter the following:
/pagelets*
In the Description field, enter a description for the resource.
Set Protection Level to Unprotected.
Set Authentication Policy to Public Resource Policy.
Set Authorization Policy to Protected Resource Policy.
Click Apply.
Repeat step 5 to add /pagelets/.../
* as a resource.
Add /pagelets/authenticateWithApplicationServer
* as a resource:
In the Resource Type field, select HTTP.
In the Host Identifier field, select the host created while registering the WebGate agent.
In the Resource URL field, enter the following:
/pagelets/authenticateWithApplicationServer*
In the Description field, enter a description for the resource.
Set Protection Level to Protected.
Set Authentication Policy to Protected Resource Policy.
Set Authorization Policy to Protected Resource Policy.
Click Apply.
Repeat step 7 to add /pagelets/authenticateWithApplicationServer/.../
* as a protected resource.
Repeat step 7 to add /pagelets/admin
* as a protected resource.
Repeat step 7 to add /pagelets/admin/.../
* as a protected resource.
On the Resources tab, search for /pageletadmin
* and /authenticateWithApplicationServer
* and remove these old resources.
Restart Web Tier and verify your changes.
Updating OAM 10g Policies for Pagelet Producer
Updating OAM 10g
policies for Pagelet Producer involves creating the following resources:
/pagelets
/pagelets/authenticateWithApplicationServer
/pagelets/admin
To update OAM 10g policies for Pagelet Producer:
Log in to the OAM Console using the following URL format:
http://
host:port
/access/oblix
Select Policy Manager.
Locate the policy domain that you created to protect your WebCenter resources.
Open the Resources tab and click Add.
Add the /pagelets
resource. For the resource:
Select HTTP as the resource type.
Select the Host Identifier for the WebCenter Web Tier.
Enter /pagelets
as the URL Prefix.
Enter a description for the resource.
Ensure that Update Cache is selected, and then click Save.
Repeat step 5 to add /pagelets/authenticateWithApplicationServer
as a resource.
Repeat step 5 to add /pagelets/admin
as a resource.
Go to the Policies tab and locate the public policy.
Open the public policy and select the resource created in step 5 (that is, /pagelets
) to apply public policy to this resource.
Do not select the other two resources (/pagelets/authenticateWithApplicationServer and /pagelets/admin
) created as we want them to be protected by default.
Save your changes.
On the Resources tab, delete the old resource entries, /pageletadmin
and /authenticateWithApplicationServer
.
Restart Web Tier and verify your changes.
Updating OSSO Configuration for Pagelet Producer
If you have an OSSO setup, to update the policy for Pagelet Producer:
In the mod_osso.conf
file, replace the following entry:
<Location /pageletadmin> OssoSendCacheHeaders off require valid-user AuthType Osso </Location>
With:
<Location /pagelets/admin> OssoSendCacheHeaders off require valid-user AuthType Osso </Location>
Replace the following entry:
<Location /authenticateWithApplicationServer*> OssoSendCacheHeaders off require valid-user AuthType Osso </Location>
With:
<Location /pagelets/authenticateWithApplicationServer*> OssoSendCacheHeaders off require valid-user AuthType Osso </Location>
Restart Web Tier and verify your changes.
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 Administrator's Guide for Oracle WebCenter Portal:
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 Administrator's Guide for Oracle WebCenter Portal:
For OAM 11g: Registering the WebGate Agent
For OAM 10g: Configuring the WebCenter Portal Policy Domain
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 domain.
Ensure AttributeService
is configured.
The default jps
context must have the following entry for configuring the attribute service:
<serviceInstanceRef ref="attribute"/>
The serviceProviders
list must contain the following entry:
<serviceProvider class="oracle.security.jps.internal.attribute.impl.AttributeServiceProviderImpl" name="attribute.provider" type="ATTRIBUTE"> <description>Attribute Service Provider</description> </serviceProvider>
The serviceInstances list must contain the following entry:
<serviceInstance provider="attribute.provider" name="attribute"> <description>Attribute Service Instance</description> <property value="86400" name="attribute.expire.time.seconds"/> </serviceInstance>
Ensure that the SSOFilter
JAR has the AttributeAccessPermission
grant. To verify this, log in to WLST as described in "Running Oracle WebLogic Scripting Tool (WLST) Commands" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal. Then, run the following WLST command to list permissions:
listCodeSourcePermissions(codeBaseURL="file:${common.components.home}/modules/oracle.ssofilter_11.1.1/ssofilter.jar")
If you get an output containing the following it means you already have the required grant.
[Permission Clz Name : oracle.security.jps.service.attribute.AttributeAccessPermission, Target : *, Actions : get,set,remove ]
If you do not have the required grant, add it using the following WLST command:
grantPermission(codeBaseURL='file:$common.components.home/modules/oracle.ssofilter_11.1.1/ssofilter.jar',
permClass='oracle.security.jps.service.attribute.AttributeAccessPermission',
permTarget='*', permActions='get,set,remove')
Restart all servers in your WebLogic domain.
This section describes the tasks that you may need to perform, depending on your system environment, after patching to Oracle WebCenter Portal 11.1.1.7.0.
The section contains the following subsections:
Section 6.8.4.2, "Migrating Content Presenter Custom Templates"
Section 6.8.4.3, "Updating the Configuration for WebCenter REST APIs"
Section 6.8.4.5, "Restoring Your OmniPortlet and WebClipping Customizations"
Section 6.8.4.6, "Extending a Domain to Install Oracle WSM Policy Manager"
Section 6.8.4.7, "Remove openusage
Properties in setDomainEnv
"
Section 6.8.4.8, "Redeploying your Custom Applications to Upgraded Custom Managed Servers"
Section 6.8.4.9, "Remove the LD_LIBRARY_PATH Entry from the setDomainEnv Script"
This section contains the following sections to help you migrate your existing Wiki pages and blogs for use in the newly patched Oracle WebCenter domain:
Section 6.8.4.1.1, "How to Migrate Oracle Wiki Pages and Blogs"
Section 6.8.4.1.2, "Troubleshooting Problems During Wiki Migration"
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 Oracle home:
WebCenter_ORACLE_HOME/webcenter/archives/wiki-upgrade.jar
This Wiki Migrator utility migrates your wiki pages and blogs into Space-specific folders in Content Server. Existing WebCenter Spaces pages for wikis and blogs are migrated, accordingly. The utility also migrates attachments and provide 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 Spaces root that is provided in the migration parameters. The utility does not migrate comments, discussion threads, templates, nor it alters wiki or blog content.
If you encounter any errors during the migration process, check the output log, which is located in the same directory as the wiki-upgrade.jar
file. For more information, see Section 6.8.4.1.2, "Troubleshooting Problems During Wiki Migration.".
Before performing wiki migration, do the following:
Make sure you have upgraded to Oracle WebCenter Content 11.1.1.7.0 (see Section 6.7.4, "Considerations for Upgrading Oracle WebCenter Content or Oracle ECM."
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 Spaces managed server is started. Therefore, it is recommended that you start the Spaces managed server prior to performing wiki migration.
Update the folder limit in Oracle WebCenter Content as follows:
Log in 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 the orphan data (for example, the data that does not have a corresponding Group Space). This does NOT have to be a root folder; it can be created as the Administrator user under the PersonalSpaces or Group Space root folder. If a root folder is preferred, the service using the URL IdcService=COLLECTION_ADD
will need to be used. For example:
http://host:port/idc/idcplg?IdcService=COLLECTION_ADD&dParentCollectionID=-1&hasParentCollectionID=true&force=true%20&xForceFolderSecurity=FALSE&ignoreMaxFolderLimit=true&hasMark=true&dCollectionName=PS3WikiMigration_Orphans&mark=PS3WikiMigration_Orphans&dDocAccount=PUBLIC&idcToken=1290338486670:A17C2CCCCE0C2FD2544E0A1B2F03DB67
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 Oracle home:
Do not pass any arguments from the command line, as follows:
> cd WebCenter_ORACLE_HOME/webcenter/archives > MW_HOME/jdk160_21/bin/java -jar wiki-upgrade.jar
You will be prompted for each of the required arguments listed in Table 6-7.
Pass a properties file (WikiMigrator.properties
) as an argument:
MW_HOME/jdk160_21/bin/java -jar WebCenter_ORACLE_HOME/webcenter/archives/wiki-upgrade.jar WikiMigrator.properties
The WikiMigrator.properties
must reside in the same directory as wiki-upgrade.jar
. The following is a sample properties file:
MDSConn = jdbc:oracle:thin:@exampleDB:1521:exampleSID
MDSUser = dbuser_example_mds
UCMConn = idc://examplehost:9444
UCMUser = sysadmin
UCMConnName = example_connection_name
UCMTempFolderPath = /RootFolder/.../TempFolder
wikiConn = jdbc:oracle:thin:@exampleDB:1521:exampleSID
wikiUser = example_wiki
SpacesRootURL = http://examplehost:port/webcenter
You will be prompted for the MDS, UCM, and Wiki passwords from the command line.
Pass all arguments from the command line:
MW_HOME/jdk160_21/bin/java -jar wiki-upgrade.jar MDSConn MDSUser MDSPswd UCMConn UCMTempFolderPath UCMUser UCMPswd UCMConnName wikiConn wikiUser wikiPswd SpacesRootURL
For example:
java -jar WikiMigrator.jar
jdbc:oracle:thin:@exampleDB:1521:exampleSID
dbuser_example_mds
example_mds_password
idc://examplehost:9444
sysadmin
example_ucm_password
example_ucm_connection_name
example_path_to_ucm_temporary_folder
jdbc:oracle:thin:@example:1521:exampleSID
example_wiki
example_wiki_password
http://examplehost:port/webcenter
Table 6-7 Descriptions and Examples of the Wiki Migration Utility Arguments
Argument | Description |
---|---|
|
Name of the connection used to connect to the MDS data source. For example: |
|
Name of the database user used to connect to the MDS data source. |
|
Password to the database user that is used to connect to the MDS data source. |
|
UCM connection URL over the For example: |
|
Use |
|
Password for the UCM user account. |
|
Name used in Enterprise Manager or WLST to create the connection to UCM. |
|
Temporary folder on UCM to store orphaned data For example: |
|
Name of the connection used to connect to the Wiki data source. For example: |
|
Name of the database user that is used to connect to the Wiki data source. |
|
Password for the database user connecting to the Wiki data source. |
|
Spaces root URL. For example: |
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.
http://server:port/owc_wiki/page/show.jz?inline=1&scope=#{communityContext.communityName}&theme=#{adfFacesContext.skinFamily}
Special Note for 10g and Release 1 (11.1.1.1.0) Users
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 group space 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 group space folders. You may need to rename the wiki and blog folders to match the corresponding group space names in WebCenter Spaces.
Log in to the Spaces application, navigate to the required group space 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.
During wiki migration, you may see some error messages in the output log. Descriptions and available workarounds are described below.
Error Message 1
[INFO] PROCESSING Domain: domain_name [INFO] migrating to temp folder - there is no webcenter page information stored on the domain: domain_name
This message indicates that there is no data specified in the domain to connect it with a group space page (the wcURL on the domain is missing).
Note:
The last part of the migration program will find any remaining unmigrated group space 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 group space folder.
Error Message 2
[INFO] PROCESSING Domain: domain_name [INFO] migrating to temp folder - invalid group space that corresponds to the guid: group_space_guid
This message indicates that there is either no group space information specified in the domain, or the group space guid specified is not valid (the group space 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: group_space_guid
This message indicates that the domain's group space information points to a group space that no longer exists. Doing a lookup with the group space guid does not find a corresponding group space name. Most likely the group space has been deleted.
Error Message 4
[INFO] PROCESSING Domain: domain_name [ERROR] migrating to temp folder - no UCM folder for the groupspace exists: page_name, gsname: group_space_name
This message indicates that the spaces page has been migrated already, but the Content Server folder for that group space does not exist.
To correct this, create the group space folder (by provisioning the Document service in the group space), and then move the folder (with the same name as the domain) from migration temp to the group space folder. Then rename the domain folder to have the same name as the page.
Error Message 5
[INFO] PROCESSING Domain: domain_name [ERROR] migrating to temp folder - could not get UCM folder for the wiki domain, page: page_name, gsname: group_space_name
This message indicates that the spaces page has been migrated already, but the Content Server folder for domain could not be created in the group space folder.
To correct this, move the folder (with the same name as the domain) from migration temp to the group space folder. Then rename the domain folder to have the same name as the page.
Error Message 6
[INFO] PROCESSING Domain: domain_name [ERROR] migrating to temp folder - no UCM folder exists for the user: user_name, page: page_name
This message indicates that the spaces 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 space), 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.
Error Message 7
[INFO] PROCESSING Domain: domain_name [ERROR] migrating to temp folder - could not get personal UCM folder for the user: user_name, page: page_name
This message indicates that the spaces page has been migrated already, but the Content Server folder for the domain could not be created in the user's personal folder.
To correct this, move the folder (with the same name as the domain) from migration temp to the user's personal folder. Then rename the domain folder to have the same name as the page.
Error Message 8
[INFO] PROCESSING Domain: domain_name [INFO] migrating to temp folder - default scope, but no user specified on page: page_name
This message indicates that this is a personal wiki or blog, but the information stored on the domain (the wcURL passed in from the spaces page) does not indicate a user.
Error Message 9
[INFO] PROCESSING Domain: domain_name [INFO] sourceUrl: source_url [INFO] migrating to temp folder - the page source url is not pointing to the correct domain, page: page_name, wcURL: wcURL
This message indicates that there is more than one domain pointing to the same group space and page information, and the current domain being processed does not match the domain indicated in the source URL.
Error Message 11
[INFO] PROCESSING User Blog: blog_name [INFO] migrating to temp folder - could not get user 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 Content Server folder for the user does not exist, so the content could not be migrated there.
Error Message 12
[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.
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.7.0. You must register the required custom templates in Release 11.1.1.7.0 version of your applications.
To migrate Content Presenter custom templates from Release 11.1.1.3.0:
In JDeveloper 11.1.1.7.0, create or open a WebCenter Portal application.
On the filesystem, copy your Release 11.1.1.3.0 .jsff
files to your Release 11.1.1.7.0 application.
From the Release 11.1.1.3.0 version of your application, copy the required custom template from following folder:
PROJECT_ROOT
/public_html/oracle/webcenter/content/templates/custom
Copy the custom template to the following folder of your upgraded Release 11.1.1.7.0 application:
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.
For information, see "Export a Content Presenter Display Template as a Portal Resource" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter Portal.
Redeploy your application using the new custom Managed Servers, as described in Section 6.8.4.8, "Redeploying your Custom Applications to Upgraded Custom Managed Servers."
If the custom template is also used in WebCenter Spaces, prepare the template to be used in your upgraded environment:
Using JDeveloper, export the Content Presenter display template as a portal resource.
Log in to the Spaces application and navigate to Spaces Administration.
Select Resources > Content Presenter and upload your template.
For information, see "Using Content Presenter Display Templates in a Framework Application" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter Portal.
Before you can use the WebCenter Representational State Transfer (REST) APIs, you must perform the server-side configurations. You must configure an identity asserter. You must also seed the required entries in the credential store, which enables the REST security tokens to function properly.
This section includes the following subsections:
Note:
This configuration is not required for the navigation REST APIs or for the CMIS REST APIs.
For more information about security tokens, see "Security Considerations for CMIS REST APIs" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter Portal.
You must configure an identity asserter before using the REST APIs. For detailed instructions, see "Configuring the REST Service" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
You must seed entries in the credential store that enable the REST security tokens to function properly. Run the following WLST commands to configure the credential store:
createCred(map="o.webcenter.jf.csf.map", key="keygen.algorithm", user="keygen.algorithm", password="AES") createCred(map="o.webcenter.jf.csf.map", key="cipher.transformation", user="cipher.transformation", password="AES/CBC/PKCS5Padding")
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 "createCred" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
In Release 11.1.1.2.0 and 11.1.1.3.0, the Calendar Overlay Style FULL
could be used to enable multiple calendars for some events task flow and add multiple Space calendars in one events task flow. In the upgraded Release 11.1.1.7.0, the Events task flow no longer displays multiple calendars; only the current Space calendar is displayed.
To work around this issue, you must enable the calendar overlaying feature for the Events task flow. Go to the page editor, find the Calendar Overlay Style
parameter and select Full
from the list of available options. For more information, see "Enabling Calendar Overlaying" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.
After you have saved your OmniPortlet and WebClipping customizations ( as described in Section 6.7.2, "Saving Your OmniPortlet and WebClipping Customizations") and successfully patched your software, you must restore them.
Note:
The Web Clipping portlet is deprecated in Release 11g (11.1.1.7.0). Consider using a clipper pagelet using Oracle WebCenter Portal's Pagelet Producer. For more information, see the "Oracle WebCenter Portal's Pagelet Producer" chapter in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
To restore OmniPortlet and WebClipping 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 domain, as specified on the "Specify Domain Name and Location" screen in the Configuration Wizard.
Note:
Since the Patch Set Installer re-deployed the OmniPortlet and WebClipping applications, the new path may be different than the path from where you backed up customizations.
Replace these directories with their backed up copies.
For example, to restore the omniportlet
directory, you can use the following commands:
On a UNIX operating system:
cp -fr backup_location path_to_war_directory/WEB-INF/providers/omniPortlet
On a Windows operating system:
xcopy /y/e backup_location path_to_war_directory\WEB-INF\providers\omniPortlet
Restart the Managed Server WC_Portlet
.
If discussions server is the only WebCenter Portal application installed in the domain, you must extend the domain to install Oracle WSM Policy Manager, if not already installed.
To extend a WebCenter domain to install Oracle WSM Policy Manager:
Stop the Admin server and all managed servers.
Start the Configuration Wizard on the machine running the Admin server.
On UNIX, run WebCenter_ORACLE_HOME
/common/bin/config.sh
.
On Windows, run WebCenter_ORACLE_HOME
\common\bin\config.cmd
.
Select Extend an existing WebLogic domain and click Next.
Select your domain and click Next.
Select the checkbox for Oracle WSM Policy Manager and click Next.
Enter the connection details for OWSM MDS Schema and click Next.
Click Next on the remaining screens until you get the Configuration Summary screen, then click Extend.
For more information on extending a domain, see "Extending a WebLogic Domain in Graphical Mode" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.
Note:
If your domain is running on multiple machines, you must pack the domain on the machine running the Administration Server and unpack on the other machines. For information, see Section 6.4.3.2, "Updating Oracle WebCenter Using WLST Commands."
openusage
Properties in setDomainEnv
If you want to extend your WebCenter domain to install Oracle WebCenter Portal's Analytics Collector, you must remove the openusage
properties:
Back up the DOMAIN_HOME
\bin\setDomainEnv.cmd
(on Windows operating systems) or DOMAIN_HOME
/bin/setDomainEnv.sh
(on UNIX operating systems).
Remove the openusage
properties from EXTRA_JAVA_PROPERTIES
in setDomainEnv.sh
or setDomainEnv.cmd
.
Specifically, the entries that need to be removed are:
EXTRA_JAVA_PROPERTIES="-Doracle.wc.openusage.clustername=localhost
-Doracle.wc.openusage.collectorport=port_number
-Doracle.wc.openusage.timeout=30
-Doracle.wc.openusage.unicast=true
-Doracle.wc.openusage.enabled=false
${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES
Note:
These entries may appear multiple times in setDomainEnv.sh
or setDomainEnv.cmd
. So ensure that all the entries are removed.
If you extend your domain to add new products, you may need to repeat the task of removing the openusage
properties from setDomainEnv
.
Restart all the servers in the WebCenter domain.
If there are custom Managed Servers in your domain, they may not have the correct libraries targeted. Therefore you must upgrade them after patching WebCenter, and redeploy your custom applications.
To upgrade custom managed servers:
Remove the old custom Managed Servers.
Use Repository Creation Utility (RCU) to install the ACTIVITIES
schema for the custom managed server. For information, see "Obtaining and Running Repository Creation Utility" in Oracle Fusion Middleware Repository Creation Utility User's Guide.
Run the Configuration Wizard to extend your existing WebCenter domain and apply custom templates.
On the "Select Extension Source" screen, select Extend my domain using an existing extension template.
Navigate to the WebCenter_ORACLE_HOME
/common/templates/applications
(on UNIX operating systems) or WebCenter_ORACLE_HOME
\common\templates\applications
(on Windows operating systems) directory and locate the following templates:
oracle.wc_custom_portal_template_11.1.1.jar
(for WebCenter custom applications/Framework applications)
oracle.wc_custom_services_producer_template_11.1.1.jar
(for WebCenter Custom Producer/Portlet Producer applications)
Select the desired template and complete the domain extension process.
Re-deploy your custom applications using the new custom Managed Servers.
Note:
Oracle recommends that you open your projects in Oracle JDeveloper and migrate your applications to the latest version before deploying to the new custom Managed Servers.
After patching Oracle WebCenter, you must remove the following entry from the setDomainEnv
script:
LD_LIBRARY_PATH="${WL_HOME}/server/native/linux/i686${CLASSPATHSEP}${LD_LIBRARY_PATH}" export LD_LIBRARY_PATH
The setDomainEnv script is available at the following path:
DOMAIN_HOME
/bin/setDomainEnv.sh
(on UNIX operating systems)
DOMAIN_HOME
\bin\setDomainEnv.cmd
(on Windows operating systems)
Note:
If you extend your domain to add new products, you may need to repeat this task.
By default, all custom JSR286 portlets (created using Portlet Creation Wizard) use a file-based preference store. Post upgrade, you must move WSRP portlet preferences from:
$MW_HOME/Oracle_WC1/portal/portletdata
To:
$MW_HOME/oracle_common/portal/portletdata
Where, MW_HOME
refers to Middleware Home, and Oracle_WC1
refers to WebCenter Portal Oracle Home.
You can move WSRP portlet preferences manually or by using a migration utility. For more information, see "Migrating a WSRP Producer Persistence Store" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter Portal.
This section contains the following topics:
Section 6.8.5.1, "Setting the Web Server Context Root on the Content Server Connection"
Section 6.8.5.3, "Updating the Timezone Attribute in WebCenter Spaces"
Section 6.8.5.5, "Choosing a Default Start (or Landing) Page"
Section 6.8.5.6, "Migrating WebCenter Spaces Custom Library"
If Oracle WebCenter Content and WebCenter 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 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 "Setting Connection Properties for the Spaces Content Repository" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
If your WebCenter instance had Group Space Workflows configured, after upgrading to the latest release, you must redeploy sca_CommunityWorkflows.jar
and WebCenterWorklistDetailApp.ear
.
To configure Group Space Workflows:
Log in to Fusion Middleware Control.
Deploy sca_CommunityWorkflows.jar
to the SOA managed server. This file is located at the following path in your Oracle SOA Suite installation:
SOA_ORACLE_HOME/webcenter/modules/oracle.webcenter.sca_11.1.1/sca_CommunityWorkflows.jar
Where, SOA_ORACLE_HOME
refers to the Oracle SOA Suite installation directory.
Note that version 11.1.1.7.0 is active in the console, and other older versions like 11.1.1.5.0 are inactive.
For information about deploying the JAR using Fusion Middleware Control, see "Deploying SOA Composite Applications" in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.
For information about deploying the JAR using WLST, see the section "Deployment Commands" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
Undeploy WebcenterWorklistDetailApp.ear
, and then redeploy it to the SOA managed server. You can find the application at the following location in your Oracle SOA Suite installation:
SOA_ORACLE_HOME/webcenter/applications/WebCenterWorklistDetailApp.ear
For information about deploying the EAR using WLST, see the chapter "Deploying Applications" in Oracle Fusion Middleware Administrator's Guide. For information about deploying the EAR using Fusion Middleware Control, see "Deploying the Application to a WebLogic Managed Server" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
In Release 11.1.1.2.0, the Timezone attribute in WebCenter Spaces is a free-form text field. From Release 11.1.1.4.0 onward, this attribute was changed to a drop-down list.
If you are upgrading WebCenter Spaces from Release 11.1.1.2.0, the Timezone attribute is not carried over, and you must manually select the appropriate timezone from the drop-down list.
If you are upgrading WebCenter Group Spaces from Release 11.1.1.2.0 or 11.1.1.3.0, you must update the metadata of your Group Spaces to ensure that they display correctly.
To update a Group Space to display correctly:
Export the group space. For information, see the "Exporting Spaces" section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
At a command prompt, go to the directory where you saved the export archive.
Extract the metadata from the export archive.
For example, the following code extracts the export archive named export.ear
, which contains transport.mar
. The code further extracts transport.mar
in a directory named mar
.
jar xvf export.ear transport.mar
mkdir mar
cd mar
jar xvf ../transport.mar
The transport.mar
file contains space.xml
that you must edit to update the group space's display mode.
Open the space.xml
file from the following path:
oracle/webcenter/space/metadata/spaces/
spaceName
/space.xml
Where, spaceName
refers to the name of the group space whose display mode you are updating.
Delete the entire <shell-chrome-type>
entry from space.xml
.
Update the export archive.
For example, the following code updates the space.xml
file in transport.mar
, and then updates transport.mar
in export.ear
.
jar uvfM ../transport.mar
oracle/webcenter/space/metadata/spaces/
spaceName
/space.xml
cd ..
jar uvfM export.ear transport.mar
Import the group space. For information, see the "Importing Spaces" section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
By default, when you log in to the Spaces application, the last accessed page is displayed. This behavior can be overridden by setting the oracle.webcenter.spaces.disableLastAccessPageBehavior
system property to false
in the setDomainEnv
domain startup script. This script is available at DOMAIN_HOME
/bin/setDomainEnv.sh
(on UNIX operating systems) or DOMAIN_HOME
\bin\setDomainEnv.cmd
(on Windows operating systems).
If you had overridden the default behavior, you must re-apply this change after patching Oracle WebCenter. For information, see section "Choosing a Default Start (or Landing) Page" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.
WebCenter Spaces can be customized, for example to deploy additional shared libraries that include custom code or some additional resources like task flows, page styles, and skins. If you deployed any custom page styles by extending Spaces through the custom library custom.webcenter.spaces.war
, then after patching you must modify the entry for each page style in the custom library and redeploy custom.webcenter.spaces.war
.
If you migrated your WebCenter Spaces customizations:
In JDeveloper, open ExtendWebCenterSpaces.jws
(11.1.1.2.0 or 11.1.1.3.0).
For each and every deployed page style, find the following:
<af:pageTemplate
And replace it with the following:
<af:pageTemplate value="#{bindings.shellTemplateBinding.templateModel}" id="T"
For each and every pageDef, find the following:
<page>
And replace it with the following:
<page viewId="#{WCAppContext.application.siteTemplateManager.currentSiteTemplateViewId}" id="shellTemplateBinding" Refresh="ifNeeded" />
Redeploy the custom.webcenter.spaces.war
shared library to your Spaces 11.1.1.7.0 managed server.
Note:
Always use Oracle JDeveloper 11.1.1.2 or 11.1.1.3 to build and deploy extensions developed for this release. For detailed steps, see the links for white papers "Extending WebCenter Spaces (11.1.1.2.0)" or "Extending WebCenter Spaces (11.1.1.3.0)" on Oracle Technology Network: http://www.oracle.com/technetwork/middleware/webcenter/portal/overview/index.html
Oracle Business Process Management (Oracle BPM) Process Spaces is a workspace built on top of Oracle WebCenter Spaces, and provides Spaces that are designed specifically for modeling and executing business processes. If you have Process Spaces installed, then after patching to WebCenter Portal 11.1.1.7.0, you must upgrade it by running the install.xml
script. The installation script can be used for a single-server configuration as well as a cluster configuration.
For more information about the Process Spaces functionality, refer to "Understanding Oracle Business Process Management Process Spaces" in Oracle Fusion Middleware User's Guide for Oracle Business Process Management.
Note:
The procedure described in this section applies only if you already have Process Spaces enabled on Webcenter Spaces and are upgrading your existing WebCenter installation to the latest release.
For information about enabling Process Spaces in a new WebCenter installation (or new domain), see "Extending a Domain to Enable Oracle BPM Process Spaces" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.
To upgrade Process Spaces installed in your upgraded WebCenter instance:
Take the Process Workspace and Modeling Space offline.
Log in to WebCenter Spaces.
Click the Administration link to open WebCenter administration pages.
Under the Spaces tab, select the Modeling Space row.
From the Edit menu, select Offline for Maintenance.
In the Bring Space Offline dialog, click OK.
Repeat this procedure to take Process Workspace offline.
Copy the process_spaces
folder from the SOA Oracle home directory to any location on the system where WebCenter is installed. Copy the folder from the following location:
On UNIX: SOA_ORACLE_HOME
/bpm/process_spaces
On Windows: SOA_ORACLE_HOME
\bpm\process_spaces
Open the process-portal-install.properties
file from the newly copied process_spaces
folder on your WebCenter Portal system.
Specify the required Oracle BPM and WebCenter properties as listed in Table 6-8.
Note:
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 |
---|---|
|
The flag to decide whether to extend the existing BPM domain or create a new one. Specify the value as |
|
The flag to decide whether to prompt for passwords or read them from the |
Oracle BPM Schema Details |
|
|
User name to connect to the database configured for Oracle BPM |
|
Password to connect to Oracle BPM's database |
|
Database type configured for Oracle BPM |
|
Driver used to connect to Oracle BPM's database |
|
URL of Oracle BPM's database, like |
Oracle BPM MDS Details |
|
|
User name for the MDS schema used for Oracle BPM |
|
Password for Oracle BPM's MDS schema |
Oracle BPM Runtime Details |
|
|
Oracle BPM server URL. For a single BPM server: 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:
For example, |
|
Name of the user that has Administrator privileges on the Oracle BPM server |
|
Password for the Oracle BPM Admin user |
WebCenter Spaces Installation Details |
|
|
Path to the WebCenter Oracle home directory |
|
Name of the domain where WebCenter is installed. If |
|
Flag to control whether to set the domain realm password; set the value to either Note: This property is for setting up Global Trust. It is recommended that you set Global Trust manually; so set this property to |
|
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. |
|
Port on which |
WebCenter's WebLogic Installation Details |
|
|
Host name on which WebCenter's Administration server is running |
|
Port number on which WebCenter's Administration server is running |
|
Admin user for the WebCenter Administration server |
|
Password of the WebCenter Administration server |
|
In a single-server environment, specify the name of the managed server where Spaces is deployed. In a clustered environment, specify the name of any one of the Spaces managed servers that is part of the cluster. |
|
Flag to configure the Content Server and Discussions Server to work with Oracle WebCenter. The Content Server and Discussion Server details listed later in this table must be specified only if Note: It is strongly recommended that instead of using the |
|
Flag to specify whether WebCenter Portal installation is configured for a cluster. Set to |
|
Name of the Spaces application's cluster. Set this property only if |
Content Server Details |
Set these properties if |
|
Name of the Content Server configured for Oracle WebCenter |
|
Port on which Content Server is running. |
|
Name of the Spaces root folder on Content Server |
|
Name of the Admin user for Content Server |
Discussions Server Details |
Set these properties if |
|
Name of the Discussions Server configured for WebCenter |
|
Name of the Admin user for Discussions 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 ant script install.xml
:
SOA_ORACLE_HOME/modules/org.apache.ant_1.7.0/bin/ant -f install.xml -DpromptForPasswords=true
Use the -DpromptForPasswords=true
argument only if you did not specify passwords in the process-portal-install.properties
file.
If wcConfigServices
is set to true
in process-portal-install.properties
, do the following:
Restart WC_Spaces
. Running the install.xml
script shuts down the WC_Spaces
managed server.
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 have been configured in different domains, configure Trusted Domain Credentials in both the Oracle BPM and WebCenter domains, and restart the Oracle BPM Admin Server and the WebCenter Portal Admin Server.
For more information, see "Enabling Trust Between WebLogic Server Domains" in Oracle Fusion Middleware Securing Oracle WebLogic Server.
Start Oracle BPM. For information, see "Configuring Oracle SOA Suite and Oracle Business Process Management Suite" in Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite.
Note:
If Oracle BPM is not up and running, you may face problems logging into WebCenter Spaces.
If required, bring the Process Workspace and Modeling Space online by selecting Bring the Space(s) Online from the Edit menu, as described in step 1.
In WebCenter Spaces, delete the old process spaces, templates, and resources, if required.
When you run the install.xml
ant script, Release 11.1.1.4.0 or 11.1.1.5.0 process spaces and related templates and resources are imported with '11.1.1.7.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.7.0' and 'Process Workspace'. If you do not want the old items, you can delete them manually. For information, see the following sections in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces: Deleting a Space, Deleting a Space Template, and Deleting a Resource Catalog.
In the upgraded WebCenter environment, Oracle Single Sign-on (OSSO) Identity Asserter does not appear in the list of authentication providers. If you continue to use OSSO 10g even after upgrading to WebCenter Portal 11.1.1.7.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:
ALT_TYPES_DIR="${ORACLE_HOME}/modules/oracle.ossoiap_11.1.1,${ORACLE_HOME}/modules/oracle.oamprovider_11.1.1
Replace the entry with:
ALT_TYPES_DIR="${COMMON_COMPONENTS_HOME}/modules/oracle.ossoiap_11.1.1,${COMMON_COMPONENTS_HOME}/modules/oracle.oamprovider_11.1.1
Restart the Administration Server.
This section includes the following subsections:
Compared to Release 11.1.1.2.0 or 11.1.1.3.0, Oracle WebCenter Portal 11.1.1.7.0 includes several new features, including:
Activity Graph, which provides suggestions of people that a user may be interested in connecting with, based on existing connections and shared interaction with objects within an application
Analytics, which allows you to track and analyze Spaces usage
Note:
If you want to extend your WebCenter domain to install Oracle WebCenter Portal's Analytics Collector, you must remove the openusage
properties. For information, see Section 6.8.4.7, "Remove openusage
Properties in setDomainEnv
."
Pagelet Producer, which provides a collection of useful tools and features that facilitate dynamic pagelet development
Personalization Server, which can deliver targeted content
WebCenter Services Portlets, which enables you to expose WebCenter Portal service task flows in other applications as WSRP portlets or pagelets. You can consume WebCenter Services Portlets in the following applications: Oracle Portal, Oracle WebLogic Portal, and Oracle WebCenter Interaction.
For more information about these features as well as other WebCenter components, see "Getting Started with WebCenter Portal Components" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal and see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
To take advantage of these new features, you must extend your domain by installing the required WebCenter components. For information about extending a domain in a:
Simple topology, see "Extending an Existing Domain" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.
Cluster or distributed environment, refer to:
Chapter "Extending the Domain for WebCenter Components" in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Portal.
Chapter "Configuring High Availability for Oracle ADF and WebCenter Applications" in Oracle Fusion Middleware High Availability Guide.
Before you extend your domain, you must do the following:
Decide on the products and topology for your environment.
To verify that your system meets the necessary minimum requirements, refer to the following documents:
Oracle Fusion Middleware System Requirements and Specifications:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html
This document contains information related to hardware and software requirements, minimum disk space and memory requirements, database schema requirements, and required system libraries, packages, or patches.
Oracle Fusion Middleware Supported System Configurations:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
This page contains various certification documents for current and previous product releases. The System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document contains certification information related to supported 32-bit and 64-bit operating systems, databases, web servers, LDAP servers, adapters, IPv6, JDKs, and third-party products.
Oracle Fusion Middleware Interoperability and Compatibility Guide
This document covers the compatibility and interoperability issues that may arise when installing or upgrading Oracle Fusion Middleware 11g products.
Use Repository Creation Utility (RCU) to install any necessary schemas.
Analytics and Activity Graph require the ACTIVITES
schema. WebCenter Services Portlets requires three additional schemas: MDS
, WEBCENTER
, and PORTLET
. These schemas must be mapped to the data sources mds-ServicesProducerDS
, WC-ServicesProducerDS
, and Portlet-ServicesProducerDS
, respectively. No additional schemas are required for Pagelet Producer or Personalization Server.
See "Oracle WebCenter Schemas" for information about required WebCenter schemas, and "Obtaining and Running Repository Creation Utility" for instructions on how to install the schemas with RCU. Both these topics are in Oracle Fusion Middleware Repository Creation Utility User's Guide.
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.7.0 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 Framework application. For information about adding features to your Framework application, see Oracle Fusion Middleware Developer's Guide for Oracle WebCenter Portal.