7 Patching Oracle Enterprise Content Management 11g (11.1.1.2.0) with 11g (11.1.1.3.0)

7.3.1.1 Stopping the Input Agents in the 11g (11.1.1.2.0) Environment

To stop the Oracle I/PM Input Agents:

1. Log in to the Oracle Enterprise Manager Fusion Middleware Control for the 11g (11.1.1.2.0) domain.

2. From the navigation pane, expand the farm, then expand WebLogic Domain.

3. Expand the Oracle Enterprise Content Management Suite domain and select the Oracle I/PM managed server (called IPM_server1 by default).

4. From the WebLogic Server menu, select System MBean Browser.

5. In the MBean browser, navigate to oracle.imaging/Server:IPM_server1/config/config.

6. Delete the userid in the AgentUserproperty.

7.3.1.2 Ensuring That All Active Processes Have Completed

To ensure that all active processes have completed, you can use Oracle WebLogic Server Administration Console to monitor the processes and identify when they are all complete:

1. Log in to the Oracle WebLogic Server Administration Console for the 11g (11.1.1.2.0) domain.

2. Navigate to the JMS Servers page for the domain (Services > Messaging > JMS Servers).

3. Select the Monitoring tab.

4. Periodically refresh the display until the Messages Current and Messages Pending values have dropped to zero (0).

7.3.3.1 Task 1: Start the Administration Server and Node Manager in the New Domain

To start the Administration Server and the node manager for the new Oracle Enterprise Content Management Suite 11g (11.1.1.3.0) domain, refer to the following sections of the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite:

• Starting the Administration Server

• Starting Node Manager

7.3.3.2 Task 2: Update the Security Settings in the New Domain

The procedure for updating the security settings in your new Oracle Enterprise Content Management Suite 11g (11.1.1.3.0) domain vary, depending on whether you are using the default Oracle WebLogic Server security provider or an external LDAP provider.

If you are using an external LDAP provider, see "Reassociating the Identity Store with an External LDAP Authentication Provider" in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite for information on associating the new domain with your existing external LDAP provider.

If you are using the default Oracle WebLogic Server security provider, use the instructions see "Configure the embedded LDAP server" in the Oracle WebLogic Server Administration Console online help, and add the following accounts that are currently defined in the Oracle I/PM 11g (11.1.1.2.0) domain:

• The Oracle I/PM administrator account. This is the user that first signed in to the Oracle I/PM 11g (11.1.1.2.0) system after it was installed.

• At least one user or group corresponding to the users or groups that have the grant access document permission within each Application.

After entering all of the required users and groups in the embedded LDAP server, run the following WLST commands:

1. Change directory to the ORACLE_HOME/common/bin directory.

2. Start the Weblogic Scripting Tool (WLST):

   For example, on a UNIX operating system, enter ./wlst.sh.

3. Enter the following WLST command:

   connect('AdminUser', 'AdminUser_Password', 't3://localhost:16000')
   

4. Enter the following WLST command:

   refreshIPMSecurity()
   

7.3.3.3 Task 3: Configure the Credentials and Create a Workflow Connection for the New Domain

If you configured Oracle I/PM 11g (11.1.1.2.0) with an Oracle BPEL server, note that the workflow connection information is stored in the Oracle I/PM database. As a result, if you configured your new Oracle I/PM environment to use the same database, then these connections will work as they did in the original environment.

However, before Oracle I/PM can connect to the workflow server, you must configure your new Oracle I/PM installation with the required credentials.

For more information, see "Configuring a Workflow Connection CSF Credential" in the Oracle Fusion Middleware Administrator's Guide for Oracle Imaging and Process Management.

7.3.3.4 Task 4: Configure the Policy Stores in the New Domain

Oracle Web Services Manager policies are configured using Oracle WebLogic Server deployment plans. If the Oracle I/PM 11g (11.1.1.2.0) environment was configured to use deployment plans to apply policies to the Web services, then you must apply the same policies to the new 11g (11.1.1.3.0) environment.

The steps you take depend on how the Oracle I/PM application was deployed.

• If the Oracle I/PM application was deployed with only the default policies, then no further action is necessary, because the default policies were set up by the installation in the new environment.

• If the Oracle I/PM application was deployed using one of the deployment plans packaged with Oracle I/PM, you must perform the same tasks you performed when deploying the application in the original environment.

  For more information, see "Setting Policies on Services" in the Oracle Fusion Middleware Administrator's Guide for Oracle Imaging and Process Management.

• If the Oracle I/PM application was deployed using a custom set of policies, you must move the policies to the new environment, using the following steps:

  Copy the Plan.xml file that was created in the original environment, along with its associated directories, to the same location in the new environment.

  Update the Oracle I/PM application deployment to use this deployment plan, as described in the section, "Setting Policies on Services" in the Oracle Fusion Middleware Administrator's Guide for Oracle Imaging and Process Management.

7.3.3.5 Task 5: Update the Input Agent Directories in the New Domain

When you are updating your configuration to use a new Oracle I/PM 11g (11.1.1.3.0) environment, you must ensure that the input directories used by the Input Agent are properly configured for the new environment.

During the installation of Oracle I/PM 11g (11.1.1.2.0), the default input directory used by the Input Agent is set to the following local file path:

MW_HOME/user_projects/domains/domain_name/IPM/InputAgent/Input

This location is usually used for simpler, single-computer installations; however, you can also change it to an external location to better facilitate sharing by clustered Oracle I/PM instances and to simplify input file placement from external scanning solutions.

Depending upon whether or not you changed the default location in 11g (11.1.1.2.0), note the following:

• If you configured Oracle I/PM 11g (11.1.1.2.0) to use a custom, central location for the input directories, then that location will be preserved for the new 11g (11.1.1.3.0) instance, as long as you configured Oracle I/PM 11g (11.1.1.3.0) to use the same Oracle I/PM database. This is because the input directories location is stored with the other Oracle I/PM configuration settings in the Oracle I/PM database.

  Note that if some aspect of that path has changed as part of the update to 11g (11.1.1.3.0), then you must update the InputDirectories property of the Imaging config MBean, accordingly. For more information, see "Configuring MBeans" in the Oracle Fusion Middleware Administrator's Guide for Oracle Imaging and Process Management.

• If you did not change the Oracle I/PM 11g (11.1.1.2.0) default input directory configuration, then you must move any unfinished input activity to the new 11g (11.1.1.3.0) Middleware home.

  To do this, copy the entire Input directory from the Oracle Enterprise Content Management Suite 11g (11.1.1.2.0) Middleware home to the same location in the new 11g (11.1.1.3.0) Middleware home. You can find the default directory and all of its subdirectories in the following location of the 11g (11.1.1.2.0) Middleware home:

  MW_HOME/user_projects/domains/domain_name/IPM/InputAgent/Input
  

  Note that input files often reference document images to be ingested, using a file path. These path references must remain valid after the update to 11g (11.1.1.3.0). For example, if any of the document references include host names, or other physical identities that might change, you must update those references in the input files.

7.3.3.6 Task 6: Update the Oracle I/PM Configuration Settings in the New Domain

The Oracle I/PM Mbean configuration settings are preserved within the Oracle I/PM database. As a result, as long as the new 11g (11.1.1.3.0) environment has been configured to connect to the same Oracle I/PM database, then the same configuration will be available when the new environment is started.

However, you should review your MBean configuration settings to verify that they are still correct after the upgrade. If any MBean values need to be changed, see "Configuring MBeans" in the Oracle Fusion Middleware Administrator's Guide for Oracle Imaging and Process Management.

On the new system, set the Listen address for the managed server that contains Oracle Application Extension Framework (AXF):

1. Log in to the Oracle WebLogic Server Administration Console for the new 11g (11.1.1.3.0) domain.

2. Navigate to the Oracle I/PM managed server (Environment > Servers > ipm_server1)

3. In the Listen Address field, enter the same name as you used for the original 11g (11.1.1.2.0) Oracle I/PM server. For example, enter the fully qualified domain name or the load balancer name.

4. Restart the Oracle I/PM managed server.

7.3.3.7 Task 7: Configure Oracle UCM for the New Oracle I/PM Instance

If you configured Oracle I/PM 11g (11.1.1.2.0) with an Oracle Universal Content Management 10g instance, then note that the Oracle UCM connection information is stored in the Oracle I/PM database. As a result, if you configured your new Oracle I/PM environment to use the same database, then these connections will work as they did in the original environment.

However, you must update Oracle UCM with information about the new Oracle I/PM 11g (11.1.1.3.0) instance:

1. In a Web browser, log in to the Oracle UCM 10g Web client as a system administrator.

2. Disable the Oracle I/PM 11g (11.1.1.2.0) repository component:

   1. Under Administration, select Admin Server.

   2. Click idc.

   3. Select Component Manager from the navigation panel.

   4. Select IpmRepository from the enabled components list and disable it.

3. Navigate to the Start/Stop Server page and restart the Content Server.

4. Uninstall the Oracle I/PM 11g (11.1.1.2.0) repository component:

   1. Navigate back to the Component Manager page.

   2. Select the IpmRepository component and select Uninstall.

   3. Click OK and return to Component Manager page.

5. Install and enable the new Oracle I/PM 11g (11.1.1.3.0) repository component:

   1. Click Browse and navigate to the following directory in the new Oracle Enterprise Content Management Suite 11g (11.1.1.3.0) Middleware home:

      ECM_ORACLE_HOME/ipm/lib
      

   2. Select the IpmRepository.zip file, and then click Install.

   3. Click Continue.

   4. Select the option to enable the component.

6. Navigate to the Start/Stop Server page and restart the Content Server.

7. Verify that Oracle I/PM 11g (11.1.1.3.0) is connected successfully to the Oracle UCM 10g instance.

7.3.3.8 Task 8: Upgrade Oracle UCM 10g to Oracle UCM 11g

After you have verified that Oracle I/PM 11g (11.1.1.3.0) is connected successfully to your existing Oracle UCM 10g installation, you can then upgrade Oracle UCM 10g to Oracle UCM 11g (11.1.1.3.0).

For complete information about upgrading to Oracle UCM 11g (11.1.1.3.0), see the Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Content Management Suite.

7.3.3.9 Task 9: Verify Any Oracle I/PM Integrations

Oracle I/PM 11g (11.1.1.3.0) introduces minor changes to the Oracle I/PM application programming interface (API). As a result, you should verify that your Oracle I/PM applications work successfully with the new API.

For more information, see Oracle Fusion Middleware Oracle Imaging and Process Management Java API Reference.

7.3.4.1 Task 1: Move the Oracle IRM Configuration File to the New Domain

To move your Oracle IRM configuration settings from the 11g (11.1.1.2.0) domain to the new 11g (11.1.1.3.0) domain:

1. Locate the XML file that contains the Oracle IRM configuration settings in the 11g (11.1.1.2.0) domain.

   The file is called irm-config.xml and it is located in the following directory inside the domain home:

   DOMAIN_HOME/config/fmwconfig/irm-config.xml
   

2. Copy the Oracle IRM 11g (11.1.1.2.0) irm-config.xml file to the same location in the new 11g (11.1.1.3.0) domain home:

   DOMAIN_HOME/config/fmwconfig/irm-config.xml
   

7.3.4.2 Task 2: Copy Oracle IRM Key Store to the New Domain

To copy the Oracle IRM 11g (11.1.1.2.0) key store to the new 11g (11.1.1.3.0) domain:

1. Locate the Oracle IRM 11g (11.1.1.2.0) key store file.

   The Oracle IRM 11g (11.1.1.2.0) installation instructions suggest that you store the key store in the following location in the domain home; however, it can actually be stored in any location on the Oracle IRM host:

   DOMAIN_HOME/config/fmwconfig/
   

   The name of the file is usually irm.jks or irm.jceks, but there are no restrictions on the naming of the file.

   You can find the exact location and file name of the key store in one of two ways:

   • In Oracle Enterprise Manager Fusion Middleware Control, navigate to the IRM home page and select Administration > General Settings from the IRM menu.

   • Use the getIRMKeyStore() WebLogic Scripting Tool (WLST) command. For more information, see "getIRMKeyStore" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

2. Copy the key store file to the equivalent location in the Oracle IRM 11g (11.1.1.3.0) domain.

7.3.4.3 Task 3: Copy the Oracle IRM Key Store Credentials to the New Domain

To copy the Oracle IRM key store credentials to the Oracle IRM 11g (11.1.1.3.0) domain:

1. Verify that the Administration server in the Oracle IRM 11g (11.1.1.3.0) domain is up and running.

2. Change directory to the following location in the Oracle IRM 11g (11.1.1.3.0) domain:

   MW_HOME/Oracle_ECM1/common/bin
   

3. Start the WLST shell, connect to the Administration server, and use the createCred command to configure the credentials in the new Oracle IRM 11g (11.1.1.3.0) domain.

   For example:

   connect("weblogic", "welcome1", "adminserver.example.com:7001")
   createCred("IRM", "keystore:irm.jceks", "user", "password")
   createCred("IRM", "key:irm.jceks:oracle.irm.wrap", "user", "password")
   

   In the previous example:

   • Replace irm.jceks with the actual name of the Oracle IRM key store.

   • Replace user and password with the key store username and password.

   For more information, see:

   • "createCred" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference

   • "Adding Key Store Passwords to the Credential Store" in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.