Skip Headers
Oracle® Fusion Middleware Patching Guide
11g Release 1 (11.1.1.5.0)

Part Number E16793-12
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

5 Patching Oracle WebCenter

This chapter provides instructions for Oracle WebCenter users who want to apply the 11.1.1.5.0 patch set to their existing Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 installations.

If your existing software version is 11.1.1.4.0, you do not need to follow the instructions in this chapter. To patch your existing release 11.1.1.4.0 software, follow the instructions in Section 3.8.3, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.4.0".

The following topics are covered:

For additional information about installing and patching Oracle WebCenter, refer to Oracle WebCenter Installation and Configuration Roadmap.

5.1 Preparing for Applying the Oracle WebCenter Patch Set

Before you perform the steps in this chapter, make sure you have performed the steps outlined in Section 3.4, "Perform General Pre-Patching Tasks". In addition, some WebCenter products require additional pre-patching attention:

5.1.1 Performing General Oracle Fusion Middleware Pre-Patching Steps

Before you begin patching your Oracle WebCenter environment, perform the steps outlined in Section 3.4, "Perform General Pre-Patching Tasks".

5.1.2 Saving Your OmniPortlet and WebClipping Customizations

This procedures in this section are needed only if you are using OmniPortlet and WebClipping customizations, and they are being used with a file-based preferences store. By default, in Oracle WebCenter and Portal, file-based preferences store is not used. Such stores are only used by default for 11g Release 1 (11.1.1) Portal environments that were upgraded from their 10g versions.

When you apply the latest Oracle Fusion Middleware patch set, both the Omniportlet and WebClipping applications are re-deployed and all configuration data stored within file-based preference stores are lost. Therefore, before running Patch Set Installer, you must save the OmniPortlet and WebClipping configuration and customizations to ensure that customizations are not lost after applying the patch set.

To save and backup your customizations, you must first find 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/

The path_to_war_directory refers to the following path on a UNIX operating system:

DOMAIN_HOME/servers/WLS_PORTAL/tmp/_WL_user/portalTools_version/randomly_generated_directory/war

On a Windows operating system:

DOMAIN_HOME\servers\WLS_PORTAL\tmp\_WL_user\portalTools_version\randomly_generated_directory\war

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.

After you locate the omniportlet directory, you can use the following command on UNIX operating systems to back up the directory:

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

On Windows operating systems:

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

Then, after you patch your software, follow the instructions in Section 5.5.2, "Restoring Your OmniPortlet and WebClipping Customizations".

5.1.3 Purging Old Documents in MDS for WebCenter Spaces

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

To purge metadata for WebCenter Spaces:

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

  2. Start WLST from your WebCenter Oracle home.

    On UNIX operating systems:

    cd WebCenter_ORACLE_HOME/common/bin
    ./wlst.sh
    

    On Windows operating systems:

    cd WebCenter_ORACLE_HOME\common\bin
    wlst.cmd
    
  3. Connect to the Administration Server using the WLST connect() command.

  4. Run the purgeMetadata() WLST command. For example:

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

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

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

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

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

5.2 Upgrading Oracle Universal Content Management 10g

If you have Oracle Universal Content Management 10g installed, it is recommended that you upgrade to Release 11g before you patch Oracle WebCenter to the latest version in order to take advantage of the full set of features. If you choose not to upgrade, you will only have access to a subset of features (see Table 5-1 for a comparison of available features).

Table 5-1 Oracle WebCenter Features Supported by Oracle Content Server 10.1.3.5.1 and 11g

Feature Description Support Available in OCS 10.1.3.5.1? Support Available in OCS 11g?

Spaces/Group Spaces

Support available for Space folder creation and role mapping.

No

Yes

Home Space/Personal space

Support available for automatic creation of Home Space folders.

No

Yes

IFRAME Support

Support to show Oracle Content Server UI directly in WebCenter applications. Support also available for creating content profiles and editing advanced properties of items.

No

Yes, if OHS installed and webContextRoot set in your connection, and IFRAME is enabled.

Wiki Document

Support for creating a wiki document. The New Wiki Document option is available for creating a new wiki document.

No

Yes

Advanced metadata edit

Support for editing advanced metadata details, such as the user access list and web site object. If the properties are editable, an Edit button is displayed in the Properties pane.

No

Yes, if IFRAME is enabled.

Thumbnails

When viewing a document, in the Properties pane, a thumbnail is rendered at the top. If there are multiple versions of the document, a thumbnail is rendered for each version.

No

Yes

Upload profiles

When uploading a document, you can choose the profile to use.

No

Yes, if IFRAME feature is available.

Document Previewer - Web rendition

When viewing a document, if there is a web rendition, it is displayed.

The web rendition is the native file of the web viewable (html, image or PDF), or in the case of OCS, the IBR has created one (PDF rendition only in this case).

No

When clicking on a document, if it is not a file type which can be rendered without slide previewer/renditions (image, .html, .txt) properties are shown instead.

Yes

When OCS setup is not set up to have web renditions, it shows file properties.

Document Previewer - Slide Previewer

When viewing a document, a slide preview of the document is rendered.

No

Yes, if IFRAME and DynamicConverter are enabled, and Dynamic Converter templates have been created.

Item Level Security

An item gets security from its own settings; it does not inherit the security from the Space in which it resides.

No

Yes, if:

  • UseEntitySecurity=true

  • Document or folder security group included in SpecialAuthGroups

  • RoleEntityACL component is enabled

AutoVue

Support for document review and collaboration feature available in Oracle AutoVue

No

Yes

Wiki and blogs page styles

Wiki and Blog page styles available for creating a page

No

Yes, in a Space or Home Space in which the Documents service is enabled.

Site Studio content creation and editing

Ability to create and edit Site Studio content from within the Content Presenter wizard, and from the content contribution mode of Content Presenter.

No

Yes, if Site Studio components have been installed on Oracle Content Server.

Site Studio region templates

Ability to use Site Studio region templates to render Site Studio content.

No

Yes, if Site Studio components have been installed on Oracle Content Server, and region templates have been created for the selected content.

Content edit

Ability to edit non-Site Studio content from within the Content Presenter wizard.

No

Yes


If you choose to stay with Oracle Content Management 10g, you must install the latest UpdateBundle and Folders_g components. You can obtain these from My Oracle Support (formerly OracleMetaLink: https://support.oracle.com).

Oracle Universal Content Management 11g is included as part of Oracle Enterprise Content Management. See Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite for installation instructions.

For instructions on upgrading to Oracle Universal Content Management 11g, see Oracle Fusion Middleware Upgrade Guide for Enterprise Content Management.

If Oracle WebCenter and Oracle Content Server are installed in the same domain, no additional configuration is required for using an external LDAP authentication provider. Authentication provider configuration is applicable to an entire domain.

5.3 Removing the LD_LIBRARY_PATH Entry from the setDomainEnv Script

Before patching Oracle WebCenter, you must remove 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:

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

5.4 Updating Oracle WebCenter to 11.1.1.5.0

There are two main methods for updating Oracle WebCenter to 11.1.1.5.0. Use the information in the following sections to determine which method to use and to perform the update:

5.4.1 Choosing Your Oracle WebCenter Update Method

Patching your Oracle WebCenter middle tier involves additional steps not required by other Fusion Middleware products.

You must choose one of the following update options:

If you have Oracle WebCenter installed on multiple machines, you can only update your software by using WLST commands (Section 5.4.2, "Updating Oracle WebCenter Using WLST Commands"). Make sure that the WebCenter Oracle home directory on each machine is updated.

5.4.2 Updating Oracle WebCenter Using WLST Commands

If you choose not to configure the Node Manager, you can update your middle tier by using WebLogic Scripting Tool (WLST) commands. Before you do so, first do the following:

  1. Run the Oracle WebCenter installer to update your Oracle WebCenter software.

    For more information, see Section 3.5.2, "Download the Installer" and Section 3.5.3, "Start the Installer".

  2. Update your database schemas.

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

After you have patched your Oracle WebCenter software and database schemas, you must run the WLST commands in this section to complete the middle tier update. You must run these commands from the same machine on which the Administration Server is running.

Follow the instructions below to complete the upgrade of your Oracle WebCenter domain:

  1. Stop all Managed Servers, including the Administration Server.

  2. Start WLST from the WebCenter Oracle home.

    On UNIX operating systems:

    cd WebCenter_ORACLE_HOME/common/bin
    ./wlst.sh
    

    On Windows operating systems:

    cd WebCenter_ORACLE_HOME\common\bin
    wlst.cmd
    
  3. Make sure the external LDAP server is up and running, then run the upgradeOpss command in offline mode (without connecting to any server):

    On UNIX operating systems:

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

    On Windows operating systems:

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

    Note:

    If you need to re-run the upgradeOpss() command, you must exit the current WLST session and start a new session before re-running upgradeOpss().
  4. Run the upgradeWebCenterDomain command in offline mode:

    upgradeWebCenterDomain(domainDirName='DOMAIN_HOME', oracleHome='WebCenter_ORACLE_HOME', upgradeCustomSpaces=[1|0])
    
    • domainDirName - Replace DOMAIN_HOME with the full path to your Domain home directory.

    • oracleHome - Replace WebCenter_ORACLE_HOME with the full path to your WebCenter Oracle home directory.

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

      http://www.oracle.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 will be available in the upgraded WebCenter Spaces instance and 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 the error messages, refer to Oracle Fusion Middleware Release Notes.
  5. Start the Administration Server.

  6. Connect to the Administration Server.

    connect()
    
  7. In the domain that is running the WebCenter Spaces Managed Server, run the upgradeWebCenterPermissions command.

    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 the error messages, refer to the Oracle Fusion Middleware Release Notes.
  8. All of the instructions to this point have been for a single node. If your domain has servers running on more than one machine, you will need to pack and unpack your domain to replicate the changes to other nodes in your cluster.

    To pack and unpack your updated domain:

    1. Pack the Administration Server:

      cd WebCenter_ORACLE_HOME/common/bin
      ./pack.sh -managed=true -domain=DOMAIN_HOME -template=wcdomaintemplate.jar -template_name=wc_domain_template
      
    2. Copy wcdomaintemplate.jar to the WebCenter_ORACLE_HOME/common/bin on the other machines.

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

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

      cd WebCenter_ORACLE_HOME/common/bin
      ./unpack.sh -domain=DOMAIN_HOME -template=wcdomaintemplate.jar
      
  9. Start the WebCenter Managed Servers:

    • WC_Spaces (WebCenter Spaces)

    • WC_Portlet (Oracle Portlet Producers)

    • WC_Collaboration (Oracle WebCenter Discussion Server)

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

  10. Disconnect from the Administration Server and connect to the WC_Spaces server as an Oracle WebCenter administrator that is defined in the external LDAP server and is defined as an administration user in the embedded Oracle WebLogic Server.

    It is important to note that the administration user must be defined both as a user in the external LDAP directory and as a user with administration privileges in the embedded Oracle WebLogic Server LDAP directory.

    If necessary, you can add a user to the Administration Group of the embedded Oracle WebLogic Server LDAP server, as follows:

    1. Log in to the WebLogic Server console.

    2. Click Security Realms and select the "myrealm" link.

    3. Click the Roles/Policies tab.

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

    5. Click Add Condition, then select User from the "Predicate List" field, then click Next.

    6. Enter the user name in the "User Argument Name" field, then click Add.

    7. Click Finish. The user you just entered should now be listed along with the administrators.

    8. Save your changes and exit.

  11. In the domain that is running the WebCenter Spaces managed server, run the upgradeWebCenterApplication command.

    upgradeWebCenterApplication(appName='webcenter')
    

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

    upgradeWebCenterApplication(appName='webcenter', server="server_name")
    
  12. Copy the Trust Store file from the Oracle home directory to the Oracle WebLogic Server domain directory.

    For example:

    cp MW_HOME/oracle_common/modules/oracle.jps_11.1.1/jps-wls-trustprovider.jar
            DOMAIN_HOME/lib/mbeantypes/jps-wls-trustprovider.jar
    
  13. Update your OWSM policies, as described in Section 3.8.8, "Adding New OWSM Pre-Defined Policies". This step is required if your upgraded domain has Oracle Web Services Manager (OWSM) installed.

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

5.4.3 Updating Oracle WebCenter Using Node Manager and Automated Script

The Oracle WebCenter patch includes a script called upgrade.py. This script will shut down all the Managed Servers and the Administration Server at the beginning of the update process, and then start all the servers during the update process.

You can only use this script if you have set up Node Manager correctly (see Section 5.4.3.1, "Configuring Node Manager") and verified that is been configured correctly (see Section 5.4.3.2, "Verifying Your Node Manager Configuration"). If you have not configured Node Manager correctly, you must use the WLST commands instead of this script (Section 5.4.2, "Updating Oracle WebCenter Using WLST Commands").

To use the script, you must perform all of the tasks below:

5.4.3.1 Configuring Node Manager

In order to use the upgrade.py script, you must configure Node Manager as follows:

  1. Make sure that all the servers in the domain (including the Administration Server) are associated with a machine which 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.

  2. If you are using demo certificates (the certificates that ship with Oracle WebLogic Server) then 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
    
  3. Make sure the StartScriptEnabled property for the Node Manager is set to true in the nodemanager.properties file so that Managed Servers can receive proper classpath and command arguments.

    Refer to Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server for more information.

  4. Make sure the nmConnect command can be used to connect to the Node Manager in WLST. If you are in a production environment, you will need to follow the instructions in "Using nmConnect in a Production Environment" in Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.

  5. 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 you will need to ensure that Node Manager has the 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.

5.4.3.2 Verifying Your Node Manager Configuration

To verify that Node Manager has been configured correctly, do the following:

  1. Stop all the servers in your domain.

  2. 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')
    
  3. Start the Administration Server using nmStart. For example:

    nmStart('AdminServer')
    
  4. Connect to the Administration Server in WLST and start a Managed Server. For example:

    connect()
    start('WLS_Spaces')
    
  5. Check that the Managed Server is running and the applications are running. For example, try to access the following URL and log in:

    http://localhost:8888/webcenter
    

5.4.3.3 Updating Your Oracle WebCenter Software and Database Schemas

After you have verified your Node Manager configuration, update your Oracle WebCenter software and database schemas:

  1. Run the Oracle WebCenter installer to update your software. See Section 3.5.2, "Download the Installer" and Section 3.5.3, "Start the Installer".

  2. Run the Patch Set Assistant to update your database schemas. See Section 3.7, "Update Your Schemas with Patch Set Assistant".

5.4.3.4 Running the Oracle WebCenter Automated Script

The upgrade.py script must be run on the same machine as the Administration Server, and 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 script takes the following optional command line parameters:

Below is the command line syntax:

upgrade.py path_to_upgrade_properties_file administrator_password node_manager_password

Refer to the following sections for examples of how to run the Oracle WebCenter script:

5.4.3.4.1 Example 1: No Optional Parameters Specified

If no optional parameters are specified, the script will use the default values for all the properties with the exception of the domain.directory and the passwords; you will be prompted for these values. Below is an example:

cd WebCenter_ORACLE_HOME/common/bin
./wlst.sh WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4/upgrade.py
5.4.3.4.2 Example 2: Specifying a Properties File and Setting the Value of user.config.file

If you specify a properties file and that properties file sets the value of the user.config.file property, then the script will override the default values of the properties with the values specified in the properties file and connect to the Administration Server and Node Manager with the credentials stored in the user configuration file. Below 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 either password as a command line argument, then it will override the default values of the properties with the values specified in the properties file and prompt for the passwords.

5.4.3.4.3 Example 3: Specifying a Properties File and Administrator Password

If you specify a properties file and administrator_password, then it will override the default values of the properties with the values specified in the properties file and will use the password specified to connect to the Administration Server. You will be prompted for the Node Manager password even if the Node Manager user name is the same as the Administrator user name. Below 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
5.4.3.4.4 Example 4: Specifying a Properties File, Administrator Password, and Node Manager Password

If you specify a properties file, administrator_password and node_manager_password, then it will override the default values of the properties with the values specified in the properties file and will use the passwords specified to connect to the Administration Server and Node Manager. Below 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
5.4.3.4.5 Properties That can be Set in the Upgrade Properties File

Table 5-2 lists the properties that can be set in the upgrade properties file.

Table 5-2 Upgrade Properties File

Property Description

domain.directory

The path to the domain directory (Domain Home).

oracle.home

The path to the WebCenter Oracle home directory.

admin.user

The 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:

  1. Log in to the WebLogic Server console.

  2. Click Security Realms and select the security realm.

  3. Click the Roles/Policies tab.

  4. Expand Global Roles and Roles, then click "ViewRole Conditions" for the Admin role.

  5. Select the User role from the drop-down list, enter the user ID, then click Add.

  6. Save your changes and exit.

admin.url

The URL used to connect to the Administration Server.

admin.server

The name of the Administration Server.

nodemanager.user

The user name for the Node Manager.

nodemanager.host

The host name for the Node Manager server.

nodemanager.port

The port number for the Node Manager server.

nodemanager.type

The connection type for the Node Manager server.

upgrade.custom.spaces

Indicates whether previous WebCenter Spaces customizations using the custom.webcenter.spaces shared library (if any) are migrated to the upgraded instance.

Set this property to true to migrate your customizations.

Warning: If you upgrade your WebCenter domain with upgrade.custom.spaces set to FALSE, none of your previous customizations will be available in the upgraded WebCenter Spaces instance, and there is no facility to migrate WebCenter Spaces customizations after the upgrade process. For information about how to user your extensions in WebCenter Spaces (11.1.1.5.0), refer to:

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

user.config.file

Name and location of a user configuration file which contains an encrypted username and password. When you create a user configuration file, the storeUserConfig command uses a key file to encrypt the username and password. Only the key file that encrypts a user configuration file can decrypt the username and password.

NOTE: if you set this property then you will not need to pass a password and it will not use the admin.user and admin.url properties.

See help('storeUserConfig') in WLST for details on how to create a user configuration file.

user.key.file

Name and location of the key file that is associated with the specified user configuration file and is used to decrypt it.

NOTE: you only need to set this property if you set the user.config.file property.

See help('storeUserConfig') in WLST for details on how to create a user configuration file.


A sample upgrade properties (upgrade.properties) file is available in the WebCenter_ORACLE_HOME/webcenter/scripts/upgrade_11.1.1.4 directory.

5.4.3.4.6 Formatting Your Properties File

You must make sure you escape values correctly in your properties file. This is particularly import to 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://java.sun.com/javase/6/docs/api/java/util/Properties.html#load%28java.io.Reader%29

Below 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

Below 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

5.4.3.5 Completing Your Update

After you have run the automated script, do the following to complete your Oracle WebCenter update:

  1. 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
    
  2. Start the node manager, Administration Server, and the Managed Servers in the domain.

  3. Update your OWSM policies, as described in Section 3.8.8, "Adding New OWSM Pre-Defined Policies".

5.5 Performing Oracle WebCenter Post-Patching Tasks

Depending on your system environment, patching Oracle WebCenter may require one or more of the following:

5.5.1 Migrating Your Oracle Wiki Pages and Blogs

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

5.5.1.1 Procedure for Migrating Oracle Wiki Pages and Blogs

If you have installed Oracle Wiki, you must run the Wiki Migrator utility, which is available in the following directory in the Oracle WebCenter Oracle home:

WEBCENTER_ORACLE_HOME/webcenter/archives/wiki-upgrade.jar

This utility migrates your wiki pages and blogs into group space-specific folders in UCM. Existing WebCenter Spaces pages for wikis and blogs will be migrated, accordingly.

This process also migrates attachments and provide links to them in your wiki pages as appropriate. Links to other wiki pages within your wiki page content will be 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 migration process will not migrate comments, discussion threads, templates, nor will it alter any other wiki or blog content.

Any errors during this process can be found in the output log, which is located in the same directory as the wiki-upgrade.jar file. For more information, see Section 5.5.1.2, "Troubleshooting Problems During Wiki Migration".

Before performing wiki migration, make sure you do the following:

  1. Make sure Oracle Universal Content Management (UCM) is upgraded to Release 11g (see Section 5.2, "Upgrading Oracle Universal Content Management 10g").

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

  3. Update the folder limit in UCM as follows:

    1. Log in to the UCM user interface, go to Administration > Folder Configuration and change the "Maximum Folders Per Virtual Folder" and "Maximum Content Per Virtual Folder" to 1000.

    2. 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 UCM. Alternatively, the attribute DisableAuthorizationTokenCheck can be disabled by selecting Administration > Content Server > General Configuration > Additional Configuration Variables -> DisableAuthorizationTokenCheck=true and then restarting the server.

After these tasks are finished, choose one of the following ways to run the wiki-upgrade.jar file:

  • 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 5-3.

  • 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. Below are the contents of a sample 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 following from the command line:

    • Enter MDS Password:

    • Enter UCM Password:

    • Enter Wiki Password:

  • 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 5-3 Descriptions and Examples of the Wiki Migration Utility Arguments

Argument Description or Example

MDS Spaces Data Source Connection

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

MDS Spaces Data Source User

This is the name of the database user that is used to connect to the MDS data source.

MDS Spaces Data Source Password

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

UCM Connection

For example: idc://host:port

UCM User

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

UCM Password

The password for the UCM user account.

UCM Connection Name

This is the name used in Enterprise Manager or WLST to create the connection to UCM.

UCM Temporary Folder

For example: /RootFolder/.../TempFolder

Wiki Data Source Connection

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

Wiki Data Source User

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

Wiki Data Source Password

The password for the database user that is used to connect to the Wiki data source.

Spaces Root URL

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


Special Note for 10g Users

If you are migrating from a 10g release or Release 1 (11.1.1.1.0) version of Wiki, you must also perform the following after migration:

  1. Log in to UCM and go to the MigrationTemp folder under sysadmin (or the UCM user running the migration program). Move the Wiki and Blog folders to the correct group space folder.

  2. Log in to the 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.

5.5.1.2 Troubleshooting Problems During Wiki Migration

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

[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.
[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).

[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.

[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 UCM 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.

[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 UCM 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.

[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 UCM 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.

[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 UCM 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.

[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.

[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.

[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 UCM folder for the user does not exist, so the content could not be migrated there.

[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" UCM folder for the user does not exist and could not be created, so the content could not be migrated there.

5.5.2 Restoring Your OmniPortlet and WebClipping Customizations

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

  1. Find out the path to 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/

    The path_to_war_directory refers to the following path on a UNIX operating system:

    DOMAIN_HOME/servers/WLS_PORTAL/tmp/_WL_user/portalTools_version/randomly_generated_directory/war
    

    On a Windows operating system:

    DOMAIN_HOME\servers\WLS_PORTAL\tmp\_WL_user\portalTools_version\randomly_generated_directory\war
    

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

    Note:

    Since the Patch Set Installer re-deployed the OmniPortlet and WebClipping applications, the new path may be different than the path from where you backed up customizations.
  2. Replace these directories with their backed up copies.

    For example, to restore the omniportlet directory, you can use the following command on a UNIX operating system:

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

    On a Windows operating system:

    xcopy /y/e backup_location path_to_war_directory\WEB-INF\providers\omniPortlet
    
  3. In the Oracle Portal domain, restart the Managed Server WLS_PORTAL.

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

5.5.3 Upgrading Oracle WebCenter Custom Portal Managed Servers

If you have custom Managed Servers in your domain, then it may not have the correct libraries targeted to it after updating your software.

Follow the procedure below to resolve this issue:

  1. Remove the old custom Managed Server.

    Managed Servers can be removed on the "Configure Managed Servers" screen when running the Oracle Fusion Middleware Configuration Wizard. See Oracle Fusion Middleware Creating Domains Using the Configuration Wizard for more information.

  2. Run the Configuration Wizard to extend your existing 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 find the following templates:

    • oracle.wc_custom_portal_template_11.1.1.jar (for WebCenter Custom Applications)

    • oracle.wc_custom_services_producer_template_11.1.1.jar (for WebCenter Custom Producer)

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

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

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

5.5.4 Migrating Content Presenter Custom Templates

If you have developed custom templates in your Release 11.1.1.3.0 applications, you must follow the steps below to register those templates in your Release 11.1.1.4.0 applications:

  1. Open a Release 11.1.1.4.0 JDeveloper project.

  2. Copy the Release 11.1.1.3.0 .jsff files to the Web Content oracle/webcenter/portalapp folder.

  3. Right-click to create the site resource and specify the properties for the template that match how the template was previously registered in your Release 11.1.1.3.0 application:

    1. If this template was used in WebCenter Spaces, right-click again after creating the site resource and export the file.

    2. Log in to WebCenter Spaces and navigate to the Administration section.

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

5.5.5 Updating Oracle WebCenter Portal Schemas

In Release 11.1.1.2.0 and 11.1.1.3.0, the MW_HOME/jdeveloper/jdev/extensions/oracle.webcenter.install/sql/oracle/wc_schema.sql (on UNIX Operating systems) or MW_HOME\jdeveloper\jdev\extensions\oracle.webcenter.install\sql\oracle\wc_schema.sql (on Windows Operating systems) could be used to created schemas used by custom WebCenter applications deployed to the custom Managed Servers. Since these schemas would not be registered in the schema version registry, Patch Set Assistant cannot be used to update them.

To update these schemas, use the MW_HOME/jdeveloper/jdev/extensions/oracle.webcenter.install/sql/oracle/11.1.1.4.0RR/wc_objects.sql (on UNIX operating systems) or MW_HOME\jdeveloper\jdev\extensions\oracle.webcenter.install\sql\oracle\11.1.1.4.0RR\wc_objects.sql (on Windows operating systems) script. For example:

sqlplus "exampleuser/examplepassword/@examplehost as sysdba" MW_HOME/jdeveloper/jdev/extensions/oracle.webcenter.install/sql/oracle/11.1.1.4.0RR/wc_objects.sql schemaname

5.5.6 Updating Your Configuration for WebCenter REST APIs

Before you can use the WebCenter Representational State Transfer (REST) APIs, you must perform the server-side configurations described in this section. You must perform two separate configurations:

You must configure an identity asserter and you must seed required entries in the credential store, which enables the REST security tokens to function properly.

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.

5.5.6.1 Configuring an Identity Asserter

You must configure an identity asserter before using the REST APIs. For detailed instructions, see "Configuring the REST Service" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

5.5.6.2 Configuring the Credential Store

Run the following WLST commands to configure the credential store. Execute these commands while the server is running. You do not have to restart the server after executing these commands.

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

5.5.7 Updating Multi Calendar Layouts

In Release 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. After upgrading to Release 11.1.1.4.0, the events task flow no longer displays multiple calendars (only the current space calendar is displayed).

To work around this issue, go to the page editor, find the Calendar Overlay Style parameter and select "Full" from the list of available options.

5.5.8 Extending a Domain to Install Oracle WSM Policy Manager

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

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

  1. Stop the Admin server and all managed servers.

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

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

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

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

  4. Select your domain and click Next.

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

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

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

    Note:

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

5.5.9 Setting the Web Context Root on the UCM Connection

Assuming that the Universal Content Management (UCM) and WebCenter instances are configured for access through a common Oracle HTTP server, the Web Server Context Root property (WebContextRoot) on the existing UCM connection can be set either through Fusion Middleware Control or WLST using the setJCRContentServerConnection command to make UCM features available in the WebCenter application via an iFrame:

5.5.10 Performing Post-Patching Tasks for WebCenter Spaces

This section contains the following topics:

5.5.10.1 Configuring Group Space Workflows

After updating your Oracle WebCenter environment to Release 11.1.1.4.0, if you have Group Space Workflows previously configured, you will need to do the following in order for Group Space Workflows to work properly:

  1. Log in as administrator.

  2. Deploy the Release 11.1.1.4.0 version of WebcenterWorklistDetailApp.ear.

  3. Deploy the Release 11.1.1.4.0 version of sca_CommunityWorkflows.jar.

Refer to "Deploying WebCenter Applications" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter for instructions on how to deploy WebCenter applications.

5.5.10.2 Allowing Group Spaces to Have a Default Template Set

Prior to Release 11.1.1.4.0, the WebCenter Spaces administrator had the ability to set default page template for personal spaces as well as group spaces. In Release 11.1.1.4.0, the latter option of setting a default page for group spaces is no longer available.

To set a default page for group spaces in Release 11.1.1.4.0:

  1. As administrator, export the document:

    1. Start the WebLogic Scripting Tool (WLST).

      On UNIX operating systems:

      cd WebCenter_ORACLE_HOME/common/bin
      ./wlst.sh
      

      On Windows operating systems:

      cd WebCenter_ORACLE_HOME\common\bin
      ./wlst.cmd
      

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

    2. Run the exportMetadata WLST command:

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

      For example:

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

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

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

  3. As administrator, import the document.

    1. Start the WebLogic Scripting Tool (WLST).

      On UNIX operating systems:

      cd WebCenter_ORACLE_HOME/common/bin
      ./wlst.sh
      

      On Windows operating systems:

      cd WebCenter_ORACLE_HOME\common\bin
      ./wlst.cmd
      

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

    2. Run the importMetadata WLST command:

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

      For example:

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

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

  4. Verify that 'System Default' is now honouring the page template at the administration level for group spaces.

Note:

WebCenter Spaces 11.1.1.4.0 supports the built-in skins, Fusion FX and WebCenter Spaces FX. Prior to Release 11.1.1.4.0, WebCenter Spaces supported various other built-in skins such as Mist, DeepSea, and MistFX. You can still use the old skins with your upgraded personal spaces and group spaces by using the format #{'old family name'} in EL expressions. However, you cannot use the old skins with any new Space or Home Space created in WebCenter Spaces 11.1.1.4.0.

5.5.10.3 Updating the Timezone Attribute in WebCenter Spaces

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

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

5.5.10.4 Updating the Group Spaces Display Mode

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

To update a group space to display correctly:

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

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

  3. Extract the metadata from the export archive.

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

    1. jar xvf export.ear transport.mar

    2. mkdir mar

    3. cd mar

    4. jar xvf ../transport.mar

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

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

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

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

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

  6. Update the export archive.

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

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

    2. cd ..

    3. jar uvfM export.ear transport.mar

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

5.5.10.5 Migrating WebCenter Spaces Custom Library

If you have migrated WebCenter Spaces, check the following to see if any of the scenarios apply to your environment:

  • By default, when you log in to WebCenter Spaces, the page you see when you log in is the page that was last accessed. This behavior can be overridden by setting the oracle.webcenter.spaces.disableLastAccessPageBehavior system property to false in the setDomainEnv domain startup script.

    If you have overridden the default behavior, you must re-apply this change when you migrate WebCenter Spaces.

  • For page styles that are deployed through extending spaces (custom.webcenter.spaces.war):

    For each and every pageStyle, 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" />
    

5.5.10.6 Starting Oracle BPM to Login to WebCenter Spaces

If your WebCenter domain has been extended using the Oracle BPM Spaces template, and Process Spaces has been installed, any attempt to log in to WebCenter Spaces throws exceptions if the Oracle BPM server is down.

5.5.11 Performing Post-Patching Tasks for Security Features

This section contains the following topics:

5.5.11.1 Configuring Web Services Security for Discussions

In Release 11.1.1.4.0, Oracle Discussions is shipped with no message protection for Web Service interaction between Discussions and Spaces; this allows you to use Discussions without further configuration. If you have a previous version of Oracle Discussions and the WebService call was protected with WS-Security, you will need to reapply this configuration after upgrading to Release 11.1.1.4.0.

In order to do so:

  1. Configure the domain keystore.

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

  2. Setup WS-Security on the Discussions Server:

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

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

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

    4. Restart the WC_Collaboration Managed Server.

  3. Secure the Spaces ForumConnection:

    Using WLST:

    1. Connect to the domain server.

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

      setDiscussionForumConnection('webcenter', name='forum-con-name',
      policyURIForAuthAccess='oracle/wss11_saml_token_with_message_protection_client_policy',
      policyURIForPublicAccess='oracle/ wss11_message_protection_client_policy',
      recipientKeyAlias='orakey')
      
    3. Restart the WC_Spaces Managed Server.

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

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

After upgrade, 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 Oracle WebCenter 11.1.1.4.0, then you must replace 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

Note:

After making this change, you must restart the Administration Server.

5.6 Adding New Features to Oracle WebCenter

This section includes the following subsections:

5.6.1 Enabling Process Spaces in a Patched Domain

This manual step should be followed if you would like to add Process Spaces BPM functionality – which is an integration between WebCenter and a BPM enabled SOA domain - to a WebCenter domain. This procedure must be performed regardless of whether the domain was an existing Release 11.1.1.2.0 domain which was updated to Release 11.1.1.4.0 or whether it is a brand new domain created with a brand new Release 11.1.1.4.0 installation.

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

  1. If you have not already enabled Process Spaces in your existing WebCenter domain, perform the following steps to extend your domain using the Oracle BPM Spaces template.

    1. Go to the common/bin (on UNIX operating systems) or common\bin (on Windows operating systems) directory in your WebCenter Oracle home and start the Configuration Wizard (config.sh on UNIX operating systems or config.cmd on Windows operating systems).

    2. Follow the instructions in "Extending a WebLogic Domain in Graphical Mode" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard to extend your domain.

      On the "Select Extension Source" screen, select Base this domain on an existing template. Click Browse and select the following template from the list:

      On UNIX operating systems:

      WebCenter_ORACLE_HOME/common/templates/applications/oracle.bpm.spaces_template_11.1.1.jar
      

      On Windows operating systems:

      WebCenter_ORACLE_HOME\common\templates\applications\oracle.bpm.spaces_template_11.1.1.jar
      
    3. Close the Configuration Wizard when the domain extension is complete.

  2. Copy the SOA_ORACLE_HOME/bpm/process_spaces (on UNIX operating systems) or SOA_ORACLE_HOME\bpm\process_spaces (on UNIX operating systems) folder from the SOA Oracle home directory to any location from where it would be able to connect to the Webcenter installation.

  3. Edit the process-portal-install.properties file located in the process_spaces folder you just copied to specify the required BPM and WebCenter properties.

    For security purposes, you can leave the passwords empty and provide them later when prompted.

    Note:

    The config services flag in the properties file can be used to configure WebCenter services if WebCenter Services has not already been configured as part of the Webcenter installation.
  4. Make sure you have ant installed with the PATH and CLASSPATH configured.

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

    ant -f install.xml -DpromptForPasswords=true
    
  6. If config services was set to true in process-portal-install.properties:

    1. Restart the WebCenter server.

    2. Run the following ant command:

      ant -f install.xml post-install -DpiArgs -importGSOnly
      
  7. If Oracle BPM and WebCenter have been configured in different domains, configure Trusted Domain Credentials in both the Oracle BPM and WebCenter domains.

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

5.6.2 Extending a WebCenter Domain to Add Oracle WebCenter Analytics Collector

If you want to extend an existing Oracle WebCenter domain to add Oracle WebCenter Analytics Collector, you need to do the following:

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

    Specifically, the lines 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
    
  2. Restart all the servers in the domain.

5.6.3 Adding Activity Graph, Analytics, Pagelet Producer, and Personalization Server to the Patched Domain

Oracle WebCenter 11.1.1.4.0 introduces several new features for Oracle WebCenter Spaces, including:

  • Activity Graph, which provides suggestions of people that a user may be interested in

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

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

  • Personalization Server, which can deliver targeted content

For more information about these features, as well as the other components of Oracle WebCenter, see "Getting Started with WebCenter Components" in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

To take advantage of these new features, you must apply the Oracle WebCenter 11.1.1.4.0 patch set, and then extend your Oracle WebLogic Server domain, as follows:

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

    To verify that your system meets the minimum necessary requirements, you should consult the following documents:

    1. Oracle Fusion Middleware System Requirements and Specifications:

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

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

    2. Oracle Fusion Middleware Supported System Configurations:

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

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

    3. Oracle Fusion Middleware Interoperability and Compatibility Guide

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

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

    Oracle WebCenter Analytics and Oracle WebCenter Activity Graph require the ACTIVITES schema. No additional schemas are required for Oracle WebCenter Pagelet Producer or Oracle WebCenter Personalization Server.

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

  3. Run the Configuration Wizard.

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

  4. Extend the domain by selecting the products Oracle WebCenter Analytics, Oracle WebCenter Activity Graph, Oracle WebCenter Pagelet Producer, Oracle WebCenter Personalization Server from the Configuration Wizard.

    Note:

    It is recommended that you deploy Oracle WebCenter Analytics, Oracle WebCenter Activity Graph, and Oracle WebCenter Personalization Server to the WC_Utilities managed server, and Oracle WebCenter Pagelet Producer to the WC_Portlet managed server.Oracle WebCenter Pagelet Producer must not be deployed to the WC_Spaces managed server.

    See "Extending an Existing Domain" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter for instructions.

If you have cluster or distributed environment, refer to:

5.6.4 Upgrading a WebCenter Custom Application to Add Portal Framework Features

WebCenter Portal Framework supports various new features such as page navigations and page hierarchies. You can manually add WebCenter Portal Frame file structures, components, and configurations to an existing custom WebCenter 11.1.1.3.0 application that has been migrated to 11.1.1.4.0 by using the automatic migration feature in Oracle JDeveloper.

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