B Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)

B.3.2.1.1 General Prerequisites

The following are the general prerequisites for running Patch Assistant:

• Ensure that Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) is installed and configured.

• Ensure that you install 11.1.1.2.0 on the same operating system used by the 11.1.1.1.0 installation.

• Ensure that the system configuration meets the recommended system configuration described in your product documentation. For more information, see http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html.

• Ensure that you have Apache Ant 1.7.0 and Java JDKs (Java SE 6 1.6.0_11 and jrockit_160_05_R27.6.2-20), which are packaged with Oracle WebLogic Server.

  Note:

  If you are using Oracle Internet Directory, Oracle Virtual Directory, Oracle HTTP Server, or Oracle Web Cache as standalone Oracle Fusion Middleware installations, you must install and configure Apache Ant separately. For more information, see Installing Ant at http://ant.apache.org/manual/installlist.html and Section B.3.2.3, "Setting Up the Patch Assistant Environment".

• Make a detailed note of the topology used for the Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) installation.

• Ensure that you do not change the port configuration and instance names in your existing Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) installation.

• Ensure that the environment variables for tmp and temp directories for Microsoft Windows are set, as described in the Oracle Fusion Middleware Administrator's Guide.

• Back up your Oracle software, inventory, schema, and domain before applying this patch set, or before making any other changes to your existing Oracle software. Refer to your product administrator's guide for instructions on backing up your Oracle software and inventory. For more information, see the "Advanced Administration: Backup and Recovery" part in the Oracle Fusion Middleware Administrator's Guide.

• On Windows, it is recommended that you edit the patchMaster.properties file in a Notepad. If you are using any other text editor, such as Windows WordPad, then save the file as Text Document. Do not save the file in Rich Text Format.

• On Windows, you must delete the service name for Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) before installing Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) because both the installations use the same service name. To do so, run the following Ant task on the command line:

  ant master-opmn-delete-service
  

  Enter the required information when prompted by the Ant task.

  Note:

  If you want to abort the migration and revert to the 11.1.1.1.0 deployment, run the following Ant task on the command line:

  ant master-opmn-create-service
  

• Heterogeneous nodes in a Cluster (one in 11.1.1.2.0, other in 11.1.1.2.0) is not supported during the migration process. You must migrate all nodes to 11.1.1.2.0 before environment can be used.

B.3.2.1.2 Product-Specific Prerequisites

Depending on your Oracle Fusion Middleware component, you may have to meet additional prerequisites as follows:

• Oracle Fusion Middleware Audit Framework

• Oracle Directory Integration Platform

• Oracle Internet Directory and Oracle Virtual Directory

• Oracle WebCenter

• Oracle Portal

Oracle Fusion Middleware Audit Framework

For Oracle Fusion Middleware Audit Framework, the audit policy is configured for Java components in Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0), you must export the configuration before running Patch Assistant, as follows:

1. Log in to Oracle Enterprise Manager 11g Fusion Middleware Control.

2. Expand WebLogic Domain on the left pane, and select your domain.

   Your selected domain page is displayed.

3. From the WebLogic Domain, select Security, and then Audit Policy.

   The Audit Policy page is displayed.

4. Select the Audit Policy, and click Export.

5. Save the AuditConfiguration file to your machine.

Oracle Directory Integration Platform

For the Oracle Directory Integration Platform, do the following:

1. Ensure that your Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) Oracle Internet Directory is up and running in SSL No-Auth mode.

2. Extend the Oracle WebLogic domain created during the Oracle Internet Directory 11g Release 1 (11.1.1.2.0) installation, by running the following command:

   Windows

   config.cmd (Located at: ORACLE_HOME\bin)

   UNIX

   config.sh (Located at: ORACLE_HOME/bin)

   The Oracle Fusion Middleware Configuration Wizard appears. Enter the Oracle Internet Directory 11g Release 1 (11.1.1.2.0) connection details and credentials.

3. Stop the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) domain.

Oracle Internet Directory and Oracle Virtual Directory

Depending on your installation, complete the following prerequisites:

• If your 11.1.1.1.0 configuration has Oracle Internet Directory and Oracle Virtual Directory created with a new Oracle WebLogic domain, then choose the Create a new WebLogic domain option on the Welcome screen of the Oracle Fusion Middleware Configuration Wizard when configuring the 11.1.1.2.0 domain.

  During the configuration of 11.1.1.2.0, if you select the Create a new WebLogic domain option, then you must deselect Oracle Internet Directory and Oracle Virtual Directory, and select Oracle Directory Services Manager.

• If your Oracle Internet Directory and Oracle Virtual Directory are not registered to any Oracle WebLogic domain in your 11.1.1.1.0 configuration, then 11.1.1.2.0 configuration is not required. You must set the property patchMaster.Oracleinstancenewlist in the patchMaster.properties file to a new directory for the instance. Ensure that you retain the same instance name used in 11.1.1.1.0.

• If your 11.1.1.1.0 configuration has Oracle Internet Directory and Oracle Virtual Directory registered to an existing Oracle WebLogic domain, then 11.1.1.2.0 configuration is not required. You must set the property patchMaster.Oracleinstancenewlist in the patchMaster.properties file to a new directory and register the instance with the existing 11.1.1.2.0 WebLogic domain using Ant target. Ensure that you retain the same instance name used in 11.1.1.1.0.

Oracle WebCenter

To migrate Oracle WebCenter, you may choose either of these approaches:

• Keep two parallel instances of Oracle WebCenter, that is 11.1.1.1.0 as well as 11.1.1.2.0. To do this, you must perform a complete installation of Oracle WebCenter 11.1.1.2.0. You can then migrate your Oracle WebCenter 11.1.1.1.0 data into the new WebCenter instance by using the export and import utilities. This approach enables you to use both instances of Oracle WebCenter, if required. For example, you may run the two instances in parallel to minimize downtime or to ensure that the 11.1.1.2.0 instance is set up to the same level as the 11.1.1.1.0 instance before you switch over to the 11.1.1.2.0 instance completely.

  For information about how to install Oracle WebCenter, see the Oracle Fusion Middleware Installation Guide for Oracle WebCenter. For information about export and import utilities, see the "Managing Export, Import, Backup, and Recovery of WebCenter" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

• Migrate the Oracle WebCenter 11.1.1.1.0 repository and mid-tier completely to Oracle WebCenter 11.1.1.2.0. This approach preserves your Oracle WebCenter 11.1.1.1.0 repository data and enables you to reuse the repository.

  This guide describes the tasks required to implement this migration approach for Oracle WebCenter.

Oracle Portal

Before updating, you should backup your OmniPortlet and WebClipping customizations. For more information, see Section 3.4.2, "Save OmniPortlet and WebClipping Customizations for Oracle Portal and Oracle WebCenter".

B.4.2.4.1 Renaming the Oracle Content Server Schema

In Oracle Fusion Middleware 11.1.1.1.0, if you performed a standalone installation Oracle Content Server, then before migrating the schemas, you must rename the Oracle Content Server's schema so that it contains the standard suffix, OCSERVER. You must also rebuild indexes on Oracle Content Server.

To rename the Oracle Content Server schema:

1. Create a new schema (for example, DEV_OCSERVER) using the RCU. Ensure that you use the same password as that of your existing Oracle Content Server schema.

2. Export the existing schema (for example, IDC_IR10).

3. Import data into the new schema you created (DEV_OCSERVER).

   Note:

   Before you import data into the newly created schema, ensure that all the seeded database objects are removed from that schema.

4. Open the config/config.cfg file from the installation directory of your Oracle Content Server.

5. Change the Oracle Content Server schema name listed in the configuration file to the newly created schema. (for example, rename IDC_IR10 to DEV_OCSERVER)

6. Access the Oracle Content Server administration console and ensure that the data exists.

After renaming the Oracle Content Server schema, you must migrate the schema, as described in the beginning of this section.

After migrating the schemas, you must rebuild the indexes on Oracle Content Server.

To re-create the index:

1. Log on to Oracle Content Server as a system administrator.

2. Access Repository Manager from the Admin Console by navigating to Administration > Admin Applets > Repository Manager.

3. Click the Indexer tab.

4. In the Collection Builder Cycle section, click Start. If the collection rebuild is already in progress, do not choose to restart the operation. First stop the collection rebuild operation, and then start the operation. Note that the collection rebuild operation is a time-consuming task.

B.4.3.1.1 Update the Translation Table in Audit Schema

If the IAU_DISP_NAMES_TL audit event translation data is defined in the 11.1.1.1.0, then you can migrate them to the 11.1.1.2.0, by completing the following steps:

1. Run SQLPlus, and connect to the database as the system user. For example:

   sqlplus sys as sysdba
   

2. Run SQL commands in the following order:

   SQL> alter session set current_schema=<Name_of_Your_Audit_Schema>; 
   SQL> delete from iau_disp_names_tl; 
   SQL> @disp_names.sql;
   

   disp_names.sql is located at fmw11gR1ps1_patchassist\Audit folder.

   Note:

   To avoid scrambled characters, a Unicode-supported database is required to store the translation data. In addition, to ensure proper character set conversion between SQL*Plus and the database server, a compatible character set, such as UTF8 or AL32UTF8, needs to be set for the NLS_LANG environment variable before running disp_names.sql.

   For the complete list of legal NLS_LANG values, see the Oracle Database Documentation Library at:

   http://www.oracle.com/technology/documentation/database.html
   

B.4.3.1.2 Migrating Audit Policy Configuration for Java Components

If the audit policy is configured for Java components in 11.1.1.1.0, you must import the configuration file after running Patch Assistant, as follows:

1. Log in to the Oracle Enterprise Manager 11g Fusion Middleware Control.

2. Expand the WebLogic Domain on the left pane, and select your domain.

   Your selected domain page is displayed.

3. From the WebLogic Domain, select Security, and then Audit Policy.

   The Audit Policy page is displayed.

4. Select the Audit Policy, and click Import.

5. Click Browse, and specify the path where your AuditConfiguration file is located.

6. Click Ok.

B.4.3.1.3 Creating the Audit Data Source

If the audit data source is used in Oracle Fusion Middleware 11.1.1.1.0, then you must re-create the audit data store used in 11.1.1.2.0. To do so, perform the following steps:

1. Log in to the Oracle WebLogic Server administration console:

   http://host:7001/console
   

2. Under JDBC, click the Data Sources link.

   The Summary of JDBC Data Sources page is displayed.

3. Click New to create a new data source.

   The Create a New JDBC Data Source page is displayed.

4. Enter the following details for the new data source:

   • Name: Enter a name such as Audit Data Source-0

   • JNDI Name: jdbc/AuditDB

   • Database Type: Oracle

   • Database Driver: Oracle's Driver (Thin XA) Versions: 9.0.1, 9.0.2, 10, 11

   If deploying to a managed cluster server, check AdminServer. This selection ensures that the data source is listed in the audit store when switching from file to database store.

5. Click Next.

   The Transaction Options page is displayed.

6. Click Next.

   The Connection Properties page is displayed.

7. In the Connection Properties page, enter the following information:

   • Database Name: Enter the name of the database to which you will connect. This usually maps to the SID.

   • Host Name: Enter the hostname of the database.

   • Port: Enter the database port.

   • Database User Name: This is the name of the audit schema that you created in RCU. The suffix is always IAU for the audit schema. For example, if you gave the prefix as test, then the schema name is test_iau.

   • Password: This is the password for the audit schema that you created in RCU.

   Click Next.

8. The next page lists the JDBC driver class and database details. Accept the default values, and click Test Configuration to test the connection. If you see the message "Connection established Successfully", click Next. If it displays any error, go back and check the connection details.

9. In the Select Targets page, select the servers where this data source must be configured, and click Finish.

B.4.3.2.1 Authorizing a New User to Access the Discoverer Catalog

Use the following commands to authorize one or more users so they can access the Discoverer Catalog:

java -classpath path_to_d4o_jar_file load . java -classpath path_to_d4o_jar_file authorize -h hostname -po portname 
     -sid database_SID -p d4osyspasswd -u user

For example. on Windows:

java -classpath C:\temp\d4o.jar load . java -classpath C:\temp\d4o.jar authorize -h sys42.example.com -po 1521
     -sid disco_db1 -p nPword432 -u jones

For example, on UNIX:

java -classpath /home/abc/temp/d4o.jar load . java -classpath /home/abc/temp/d4o.jar authorize -h sys42.example.com -po 1521
     -sid disco_db1 -p nPword432 -u jones

In this example, you must run the load command only once before authorizing any number of users. For example, if you want to authorize 10 users, run the load command once, and then run the authorize command once for each user.

B.4.3.2.2 Updating the Privileges of an Existing Discoverer Catalog User

To update the user's privileges to access all private and shared folders, use the following command:

java -classpath path_to_d4o_jar_file updatePrivileges -h hostname -po portname
     -sid database_SID -p d4osyspasswd -u user

For example, on Windows:

java -classpath C:\temp\d4o.jar updatePrivileges -h sys42.example.com -po 1521
     -sid disco_db1 -p nPword432 -u jones

For example, on UNIX:

java -classpath /home/abc/d4o.jar updatePrivileges -h sys42.example.com -po 1521
     -sid disco_db1 -p nPword432 -u jones

In this example, if you specify the -u option, then the privileges are upgraded only for that user. If you do not specify the -u option, then the privileges are upgraded for all users.

B.4.3.5.1 Migrating File-Based Policy and Credential Store

To migrate your existing file-based policy and credential store from 11.1.1.1.0 to 11.1.1.2.0, you must install Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0), which is configured to use the file-based policy (XML), credential (wallet) stores, and then migrate the credentials and application policies by using the WebLogic Scripting Tool (WLST) command migrateSecurityStore. For more information, see the "Migrating Credentials with the Command migrateSecurityStore" section in the Oracle Fusion Middleware Security Guide.

B.4.3.5.2 Migrating Oracle Internet Directory Policy and Credential Store and Reusing an Existing Oracle Internet Directory Server

To migrate your existing Oracle Internet Directory policy and credential store from Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0), start the servers in your Oracle Fusion Middleware domain and then complete the following steps:

1. Reconfigure the LDAP authenticator to use the same LDAP server used in the 11.1.1.1.0 installation. For information, see the Oracle Fusion Middleware Security Guide.

   Note:

   For information on reconfiguring the LDAP authenticator to use the same LDAP server used in Oracle WebCenter 11.1.1.1.0 installation, see the "Reassociating the Identity Store with an External LDAP" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

2. Update the Java Platform Security (JPS) LDAP schema in the LDAP store by using the WLST reassociateSecurityStore command. The reassociation creates a temporary node under a pre-existing jps root node. The temporary data is the domain, you specified during reassociation. The domain needs to be a new temporary name and the jpsroot should have the same name that contains the domain you are migrating from 11.1.1.1.0. For information, see the "reassociateSecurityStore" section in the Oracle Fusion Middleware Security Guide. This command creates a temporary domain that will be deleted later. For example:

   reassociateSecurityStore(domain="ps1_tmp_domain",admin="cn=orcladmin", password="welcome1", ldapurl="ldap://example.com:3060", servertype="OID", jpsroot="cn=jpsroot_r1_name")
   

   Note:

   Set a temporary name for the domain, and ensure that the jpsroot has the same name as in 11.1.1.1.0.

3. Ensure that the Oracle WebLogic Administration Server is stopped to change the server configuration. To stop the server, run the following command:

   Windows:

   MW_HOME\user_projects\domains\<domain_name>\bin\stopWebLogic.cmd
          username password admin_url
   

   UNIX:

   $ MW_HOME/user_projects/domains/<domain_name>/bin/stopWeblogic.sh 
          username password admin_url
   

4. Rebuild the Oracle Internet Directory catalog by running the following catalog commands from the Oracle Internet Directory machine:

   Note:

   Before you start using the Oracle Identity Management command-line tools, you must configure your environment. This involves setting the appropriate environment variables as follows:

   • ORACLE_HOME - The location of non-writable files in your LDAP-based identity store installation.

   • ORACLE_INSTANCE - The location of writable files in your LDAP-based identity store installation.

   • TNS_ADMIN - The location of tnsnames.ora file in your Oracle home.

     Ensure that the tnsnames.ora file (Located at ORACLE_HOME/network/admin) contains the conn_str that will be used in the catalog command.

   • PATH - Add the following directory locations to your PATH:

     ORACLE_HOME/bin
     ORACLE_HOME/ldap/bin
     ORACLE_HOME/ldap/admin
     

   Drop the catalog first before re-creating it as follows:

   catalog connect="conn_str" delete=true attribute= createtimestamp
   catalog connect="conn_str" delete=true attribute= modifytimestamp
   catalog connect="conn_str" delete=true attribute= orclJpsResourceName 
   catalog connect="conn_str" delete=true attribute= orclJPSObjGUID 
   catalog connect="conn_str" delete=true attribute= orclJpsResourceTypeActionNames
   

   Then add the following:

   catalog connect="conn_str" add=true attribute= createtimestamp 
   catalog connect="conn_str" add=true attribute= modifytimestamp
   catalog connect="conn_str" add=true attribute= orclJpsResourceName
   catalog connect="conn_str" add=true attribute= orclJPSObjGUID
   catalog connect="conn_str" add=true attribute= orclJpsResourceTypeActionNames
   

   For more information, see "Performing Bulk Operations" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

5. Delete the temporary domain, created in step 1, by performing the following:

   1. Disable the Server Entry Cache. For more information, see "Tuning Recommendations for Server Entry Cache" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

   2. Stop Oracle Internet Directory by running the following command:

      Windows

      ORACLE_INSTANCE\bin\opmnctl stopall
      

      UNIX

      ORACLE_INSTANCE/bin/opmnctl stopall
      

   3. Run the following command:

      bulkdelete connect=”connect string” basedn=”cn=ps1_tmp_domain,cn=JPSContext,cn=jpsroot_r1_name”
      

      Note:

      Do not use JXplorer or any other LDAP browser to delete the JPS root node.

      For more information, see "Deleting Entries or Attributes of Entries by Using bulkdelete" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

   4. Start Oracle Internet Directory by running the following command:

      Windows

      ORACLE_INSTANCE\bin\opmnctl startall
      

      UNIX

      ORACLE_INSTANCE/bin/opmnctl startall
      

   5. Enable the Server Entry Cache. For more information, see the "Tuning Recommendations for Server Entry Cache" section and the "Attributes of the Instance-Specific Configuration Entry" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

   6. Stop and start Oracle Internet Directory by running the following commands:

      Windows

      ORACLE_INSTANCE\bin\opmnctl stopall ORACLE_INSTANCE\bin\opmnctl startall
      

      UNIX

      ORACLE_INSTANCE/bin/opmnctl stopall ORACLE_INSTANCE/bin/opmnctl startall
      

6. Open the jps-config.xml file (located in your MW_HOME\user_projects\domains\<DomainName>\config\fmwconfig directory) in a text editor and replace the 11.1.1.2.0 domain name with 11.1.1.1.0 domain name. For example, replace cn=ps1_tmp_domain with cn=R1_domain_name.

7. Migrate the default system policies from the XML store to the LDAP store by using the WLST Command migrateSecurityStore. For more information, see the "Migrating Credentials with the Command migrateSecurityStore" section in the Oracle Fusion Middleware Security Guide. In the jps-config.xml file, add the entries to specify the source and the destination source JPS context. The source JPS context must be the one that uses the XML store as the policy store, and the destination JPS context must be the one that uses the LDAP store. For example, add the following entries in the jps-config.xml file:

   <jpsContext name="filestore"> 
      <serviceInstanceRef ref="policystore.xml"/>
   </jpsContext>
   <jpsContext name="ldapstore"> 
      <serviceInstanceRef ref="policystore.ldap"/>
   </jpsContext>
   

   Ensure that the policystore.xml service instance in jps-config.xml file refers to the shipped system-jazn-data.xml file (out-of-the-box), as in the following example:

   <serviceInstance location="./system-jazn-data.xml" provider="policystore.xml.provider" name="policystore.xml">
               <description>File Based Policy Store Service Instance</description>
           </serviceInstance>
   

   Migrate the system policies by using the WLST migrateSecurityStore command, as shown in the following example:

   migrateSecurityStore(type="globalPolicies", configFile="<domain level jpsconfig.xml file loc>", src="filestore" ,dst="ldapstore")
   

   For more information about the migrating system policies, see the "Migrating Policies to the Domain Policy Store" section in the Oracle Fusion Middleware Security Guide.

8. Ensure that the LDAP server contains the Role Categories entry under your application policy node.

   1. Run the ldapsearch command to search for this Role Categories entry from the Oracle Internet Directory machine:

      LDAP_OH/bin/ldapsearch -h <host> -p <port> -D "<Admin DN>" -w password -b "cn=Role Categories,cn=<app name>,cn=<domain name>,cn=JpsContext,cn=<jpsroot name>" -s base "(objectclass=*)"
      

      Where LDAP_OH/bin is the OID/IdM IDM_ORACLE_HOME/bin directory.

      Example:

      LDAP_OH/bin/ldapsearch -h oid.example.com -p 3060 -D "cn=orcladmin" -w password -b "cn=Role Categories,cn=appname,cn=domainname,cn=JpsContext,cn=jpsroot" -s base "(objectclass=*)"
      

      For detailed syntax, see the "ldapsearch" topic in the Oracle Fusion Middleware User Reference for Oracle Identity Management.

      Note:

      If the Role Categories entry is not available, the following message is displayed:

      ldap_search: No such object
      

   2. If the Role Categories entry is not present, create an LDIF file named rolecat.ldif with the following content:

      dn: cn=Role Categories,cn=<app name>,cn=<domain name>,cn=JPSContext,cn=<jpsroot name>
      objectclass: top
      objectclass: orclContainer
      cn: Role Categories
      

      Example:

      dn: cn=Role Categories,cn=webcenter,cn= R1_domain_name,cn=JPSContext,cn=jpsroot_r1_name 
      objectclass: top
      objectclass: orclContainer
      cn: Role Categories
      

   3. Run the ldapadd command to add this node to the application policy store as follows:

      LDAP_OH/bin/ldapadd -p <port> -h <host> -D "<Admin DN>" -w <password> -vf rolecat.ldif 
      

      Where LDAP_OH/bin is the OID/IdM IDM_ORACLE_HOME/bin directory.

      Example:

      LDAP_OH/bin/ldapadd -p 3060 -h oid.example.com -D "cn=orcladmin" -w password -vf rolecat.ldif
      

      For detailed syntax, see the "ldapadd" topic in the Oracle Fusion Middleware User Reference for Oracle Identity Management.

      Note:

      If the node exists, the output of the ldapadd command indicates that the object already exists.

   Note:

   The ldapadd command for Role Categories must be run for every application that uses LDAP as policy store.

9. Start the Oracle WebLogic Administration Server, as shown in the following example:

   MW_HOME/user_projects/domains/domain_name/bin/startWebLogic.sh
            -Dweblogic.management.username=weblogic
            -Dweblogic.management.password=password
   

   For more information, see "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

10. Redeploy any user applications that were deployed in 11.1.1.1.0.

B.4.3.8.1 Migrating Configuration for Additional Custom-Deployed Drivers

If your Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) domain has configuration files for additional User Messaging Service driver deployments beyond those provisioned at install time, then you must migrate them to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0). Run the following Ant command on the command-line:

ant -f UMS/build.xml patch-ums-driver-config -Ddriver.name=<driver_name>

Where <driver_name> is the deployment name of the custom driver. The build.xml file is located in your patchMaster directory.

B.4.3.8.2 Migrating Configuration for User Messaging Service Worklist Driver

If your Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) domain has the User Messaging Service Worklist Driver installed and configured, then the configuration of the Worklist Driver is automatically migrated by the Patch Assistant. Patch Assistant does not install this additional driver. You must re-install the driver in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) domain. For more information, see "Install the Worklist Driver" section in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.

B.4.3.9.1 Overview of Tasks for Configuring Oracle WebCenter Post Mid-Tier Migration

Table B-2 describes the tasks involved in configuring Oracle WebCenter 11.1.1.2.0 after the Patch Assistant script has been executed. The table also specifies whether these tasks are optional or mandatory.

B.4.3.9.2 Reconfiguring Oracle WebCenter Identity Store and Migrating the Application Policy to the WebCenter Policy Store

You must migrate your existing identity store and credential store. Before doing so, be sure to start all the servers in your WebCenter domain.

If you are using the embedded LDAP based policy and credential store, for information about the tasks that you need to perform, see the "Exporting and Importing a File-based Policy Store" and "Exporting and Importing a File-based Credential Store" sections in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

When Oracle WebCenter 11.1.1.1.0 is configured to use an external LDAP-based identity store, then post mid-tier migration you must migrate your identity store and credential store to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0). For information about how to migrate Oracle Internet Directory policy and credential store, see Section B.4.3.5.2, "Migrating Oracle Internet Directory Policy and Credential Store and Reusing an Existing Oracle Internet Directory Server."

After migrating the identity and credential store, you must run the updateSpacesPolicy.py script to update the WebCenter Spaces application policy to include appropriate security permissions. If you do not run this script, WebCenter Spaces users will not be able to access their profile information or the service tabs in group spaces.

To execute updateSpacesPolicy.py:

1. Launch WLST with this command:

   WC_ORACLE_HOME/common/bin/wlst.sh
   

   Where WC_ORACLE_HOME refers to the Oracle WebCenter installation directory.

2. At the WLST command prompt, enter the following command to connect to the Administration Server:

   wls:/offline> connect('user_name,'password, 'host_name:port_number')
   

   For example, use the following command:

   connect('weblogic','weblogic', 'myhost.example.com:7001')
   

3. Use the following command to run the updateSpacesPolicy.py script:

   wls:/weblogic/serverConfig> execfile('WC_ORACLE_HOME/webcenter/scripts/updateSpacesPolicy.py')
   

4. Ensure that there are no errors logged on the console. If there are errors, use the error message as a guide and inspect the updateSpacesPolicy.py script to determine the grant command that failed. You must fix errors, if any, and run the grant command manually.

5. Restart the Administration Server and the WLS_Spaces Managed Server.

B.4.3.9.3 Configuring Oracle WebCenter for Secure Sockets Layer (SSL)

Secure Sockets Layer (SSL) provides additional security for connections between WebCenter applications or components by providing an additional authentication layer, and by encrypting the data exchanged. During mid-tier migration, the SSL configuration does not get migrated. After running the Patch Assistant script, you must reconfigure SSL for Oracle WebCenter and, if required, for various WebCenter Services integrated into your WebCenter applications. For information about how to configure SSL for WebCenter applications and WebCenter Services, see the "Configuring WebCenter Applications and Components to Use SSL" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For example, in Oracle WebCenter 11.1.1.1.0, if secured portlets were used in WebCenter Spaces, then your keystore must have been set to the Custom Identity and Java Standard Trust keystore and you would have imported the required portlet certificates in the Java standard trust keystore (typically cacerts). Now, post mid-tier migration, you must configure the WLS_Spaces server, in your Oracle WebCenter 11.1.1.2.0 instance, to use the Custom Identity and Java Standard Trust keystore and other SSL-specific settings that were configured for Oracle WebCenter 11.1.1.1.0. Also, you must reimport all your portlet certificates into the trust keystore to access secured portlets in Oracle WebCenter 11.1.1.2.0.

B.4.3.9.4 Configuring Oracle WebCenter for Single Sign-On (SSO)

For single sign-on (SSO) authentication, your Oracle WebCenter 11.1.1.1.0 may be configured to use Oracle Access Manager (OAM), Oracle Single Sign-on (OSSO), or a SAML-based single sign-on solution for WebCenter applications only. After mid-tier upgrade, you may need to perform the following configuration, depending on the SSO solution used:

• Configuring OAM: Configure the authenticator and the OAM asserter to use the same configuration as used in Oracle WebCenter 11.1.1.1.0. For information, see the "Configuring Oracle Access Manager (OAM)" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

• Configuring OSSO: Configure the authenticator and the OSSO asserter to use the same configuration as used in Oracle WebCenter 11.1.1.1.0. For information, see the "Configuring Oracle Single Sign-On (OSSO)" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

• Configuring SAML-based SSO: You must set up your entire SAML-based SSO solution. For information, see the "Configuring SAML-based Single Sign-on" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Note:

If WebCenter is running with SSO, the OmniPortlet producer receives an authorization exception when it tries to store connection information in the Credential Store Framework (CSF) wallet. For information about how to resolve this issue, see the "OmniPortlet Producer Authorization Exception in SSO Environment" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

B.4.3.9.5 Refreshing Group Space Data in WebCenter Spaces

After mid-tier migration, you must refresh the group space data. Also, refresh the member data for each group space individually.

To refresh the group space data:

1. Log on to WebCenter Spaces as an administrator.

2. Click the Administration link, and go to the Group Spaces tab.

3. Click the Refresh icon.

To refresh the member data for a group space:

1. Log on to WebCenter Spaces as an administrator.

2. Go to the desired group space, open the Settings tab, and then the Members tab.

3. Click the Refresh icon in the Manage Group Space Members section.

   You must perform this procedure for each group space individually.

B.4.3.9.6 Reapplying Configuration Changes

If you want the same configuration as defined in your Oracle WebCenter 11.1.1.1.0, then you must reapply the configuration changes in Oracle WebCenter 11.1.1.2.0. Configuration changes may relate to the any of the following:

• WebCenter Portlet Producers: Any changes made to the provider.xml file of a portlet producer, like changing a proxy server, require that post mid-tier migration you reconfigure those changes, redeploy the portlet producer EAR application, and restart WLS_Portlet Managed Server. For information about redeploying portlet producers, see the "Managing Portlet Producers" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

• WebCenter Services: While installing Oracle Fusion Middleware 11.1.1.2.0, if you changed the host and port number of the back-end servers on which your WebCenter Services rely, you must reconfigure the required service connections to use the new server configuration. For information about specific services, see the "Managing Services, Portlet Producers, and External Applications" part in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

• WebCenter Wikis and Blogs: Any configuration changes made to your Oracle WebCenter Wiki and Blog Server 11.1.1.1.0, such as changing the theme or setting the attachment size, require that you reapply those changes in Oracle WebCenter Wiki and Blog Server 11.1.1.2.0. To reconfigure settings, use Administration mode of your Oracle WebCenter Wiki and Blog Server. For information, see the "Oracle WebCenter Wiki and Blog Server - Configuration" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

• WebCenter Spaces and Workflows: The WebCenter Spaces workflows functionality requires sca_CommunityWorkflows.jar and WebCenterWorklistDetailApp.ear to be deployed to a SOA server. If WebCenter Spaces workflows were enabled in Oracle WebCenter 11.1.1.1.0, you must redeploy these applications to the SOA server post mid-tier migration. For information, see the "Back-End Requirements for WebCenter Spaces Workflows" section in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

• WebCenter Spaces profile settings: In WebCenter Spaces, profile settings set on the WebCenter Administration > Services > Profile screen are not retained when you upgrade from Oracle WebCenter 11.1.1.1.0 to Oracle WebCenter 11.1.1.2.0. After the upgrade, you must reapply the required profile settings on the WebCenter Administration > Services > People Connections > Profiles screen.

B.4.3.9.7 Importing Wiki Templates and Attachments

In Oracle WebCenter Wiki and Blog Server 11.1.1.1.0, regardless of the repository type configured for the server, templates and attachments are stored in a file-based repository. Oracle WebCenter Wiki and Blog Server 11.1.1.2.0 supports only a database repository; templates and attachments are also stored in the database repository.

If your Oracle WebCenter Wiki and Blog Server 11.1.1.1.0 used a database repository, then during migration templates and attachments are migrated to the database repository configured for Oracle WebCenter Wiki and Blog Server 11.1.1.2.0. If your Oracle WebCenter Wiki and Blog Server 11.1.1.1.0 used a file-based repository, then during migration wiki templates and attachments are migrated to a file-based repository. To make these templates and attachments available in Oracle WebCenter Wiki and Blog Server 11.1.1.2.0, you must manually migrate them to the database repository.

To import attachments for a wiki page, the user who owns that wiki page or you as an administrator must reupload the attachments on the wiki page. When you reupload an attachment, the attachment gets stored in the database repository. Note that attachments must be reuploaded for each wiki page individually.

To migrate templates:

1. Log on to Oracle WebCenter Wiki and Blog Server 11.1.1.2.0 as an administrator.

2. Click the Administration link to open Administration mode.

3. Click Templates.

4. Click import.

5. On the Import Templates page, in the Folder field, enter the path to templates. For example:

   $APPLICATIONS_DIRECTORY/owc_wiki/templates.

   Where, $APPLICATIONS_DIRECTORY is the directory where you installed Oracle WebCenter Wiki and Blog Server 11.1.1.2.0. That is, $APPLICATIONS_DIRECTORY = MW_HOME/user_projects/applications/DOMAIN_NAME.

6. Click Import Templates. The existing file-based templates are individually re-created in the wiki database repository.

B.4.3.9.8 Migrating Oracle Content Server

Oracle WebCenter 11.1.1.2.0 is compatible with Oracle Content Server 10.1.3.5.1. To migrate your existing Oracle Content Server and prepare it to work with Oracle WebCenter 11.1.1.2.0, you must perform the following tasks:

• Run the WebCenter configuration script, wc_contentserverconfig. This script is available on the Universal Content Management (UCM) media shipped with Oracle WebCenter. For information about how to run the script, see the "Oracle Content Server - Installation" section in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

• Reconfigure the identity store for Oracle Content Server. To connect to an LDAP-based identity store, Oracle Content Server 10.1.3.5.1 requires a JPS user provider, instead of an LDAP user provider. Therefore, you must configure a JPS user provider and ensure that the existing LDAP user provider for Oracle Content Server is disabled. For information, see the "Configuring the Identity Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

B.4.3.9.9 Configuring Oracle WebCenter Discussions for WebCenter Spaces

When you migrate from Oracle Fusion Middleware 11.1.1.1.0 to Oracle Fusion Middleware 11.1.1.2.0, the patch assistant script migrates the database schema of your Oracle WebCenter Discussions server. Out-of-the-box, Oracle WebCenter Discussions 11.1.1.2.0 is configured to use the embedded LDAP identity store of Oracle WebLogic Server.

You must configure Web Services Security (WS-Security) if you want to use Oracle WebCenter Discussions with WebCenter Spaces.

To configure Oracle WebCenter Discussions:

1. Log on to the Oracle WebCenter Discussions 11.1.1.2.0 server as an administrator by using the following URL format:

   http://host:port/owc_discussions/admin
   

   Where host:port refer to the host name and port number of the system where Oracle WebCenter is installed.

2. To verify that Oracle WebCenter Discussions has been migrated successfully, in Jive Forums Admin Console, ensure that "Jive Forums Silver 5.5.20.2-oracle" is displayed in the top-right corner.

3. Configure WS-Security trusted authentication if you want to use Oracle WebCenter Discussions with WebCenter Spaces. For information about how to configure WS-Security, see the "Configuring WS-Security" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4. Reconfigure SSO for Oracle WebCenter Discussions, if required. For information, see the "Configuring a WebCenter Application to Use Single Sign-On" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

B.4.3.9.10 Migrating Custom WebCenter Applications

To make your custom WebCenter applications available in Oracle WebCenter 11.1.1.2.0, you must migrate them from your Oracle WebCenter 11.1.1.1.0 instance. You do not need to migrate the metadata of these applications because Oracle WebCenter 11.1.1.2.0 schemas are an in-place patch of your Oracle WebCenter 11.1.1.1.0 schemas for MDS, PORTLET, and WEBCENTER.

To migrate a custom WebCenter application:

1. Open the application in Oracle JDeveloper 11.1.1.2.0.

   This invokes the migration wizard that automatically migrates your application to Oracle WebCenter 11.1.1.2.0.

2. Save the application.

3. Create a WebLogic Managed Server instance and provision it with a required set of shared libraries. For information, see the "Creating and Provisioning a WebLogic Managed Server Instance" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4. Create and register the Metadata Service (MDS) repository for your application on the WebLogic Domain's Administration Server instance. For information, see the "Creating and Registering the Metadata Service Repository" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

5. Deploy the application to a Managed Server. For information, see the "Deploying the Application to a WebLogic Managed Server Instance" section and the "Deploying Portlet Producer Applications" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Your custom WebCenter applications may have WebCenter Services integrated that rely on back-end servers. For example, Discussions and Search services rely on Oracle WebCenter Discussions and Oracle SES, respectively. While installing Oracle Fusion Middleware 11.1.1.2.0, if you changed the host or port number of your back-end servers, you must reconfigure the required WebCenter Services to use the new server configuration. For information about specific services, see the "Managing Services, Portlet Producers, and External Applications" part in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

B.4.3.10.1 Purging the Policy Usage Analysis Information from the Metadata Services Repository

In this release, the same Oracle Metadata Services (MDS) repository can be used to manage policies across multiple domains. In previous releases, an MDS repository could only be used by a single domain.

If you have analyzed policy usage using the Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) installation, you will need to purge the policy usage analysis information from the MDS repository to ensure that accurate usage results are reflected for the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) version.

To purge the policy usage analysis information from the MDS repository, use the deleteMetadata MDS command as follows:

deleteMetadata(application='wsm-pm',server='server_name',
                docs='/policyAttachments/**')

server_name specifies the name of the server on which the Oracle WSM policy manager is running.

After purging the policy usage analysis information, you must restart the server.

For more information about managing MDS repositories, see "Maintaining the MDS Repository" section in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

B.4.3.10.2 Migrating the Oracle WSM Policies in the MDS Repository

In Oracle WSM 11g Release 1 (11.1.1), predefined and custom Oracle WSM policies are stored in the Oracle MDS repository. In this patch set, there are two new predefined policies available:

• oracle/wss_saml_or_username_token_over_ssl_service_policy

• oracle/wss11_saml_or_username_token_with_message_protection_service_policy

You can use Oracle WebLogic Scripting Tool (WLST) commands to upgrade the repository with the new predefined policies. You can also refresh the repository by deleting all Oracle WSM policies from the repository, including custom policies, and then repopulating it using the predefined policies provided in your installation. All of the policies in the repository are also revalidated when you upgrade the repository.

For more information, see "Upgrading the Oracle WSM Policies in the MDS Repository" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

B.4.3.10.3 Migrating Custom Policy Accessor Properties

If you have customized the policy accessor properties, you must re-apply the policy manager connection information once you have migrated your installation. For more information, see "Configuring Platform Policy Properties" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.