3 Applying the Latest Oracle Fusion Middleware Patch Set

3.5.1.1 Product Installers

The product installers for Oracle SOA Suite, Oracle WebCenter, Oracle Application Developer, Oracle Enterprise Content Management Suite, Oracle Business Intelligence and Oracle Data Integrator can be used by existing customers to patch an existing Oracle Fusion Middleware installation, or they can be used to install a fresh Oracle Fusion Middleware environment. For these products, you download the same software and run the same installer to perform both functions.

If you are patching an existing environment, use the instructions in this guide.

If you are a new Oracle Fusion Middleware user, refer to the product installation guides for information about installing and configuring a new Oracle Fusion Middleware environment:

• Oracle Fusion Middleware Installation Guide for Oracle SOA Suite

• Oracle Fusion Middleware Installation Guide for Oracle WebCenter

• Oracle Fusion Middleware Installation Guide for Application Developer

• Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite

• Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence

• Oracle Fusion Middleware Installation Guide for Oracle Data Integrator

3.5.1.2 Patch Set Installers

If you are patching an existing Oracle Identity Management, Oracle Web Tier, or Oracle Portal, Forms, Reports and Discoverer environment, a separate Patch Set Installer must be downloaded and used to patch your environment.

The instructions for doing so are provided in this chapter in Section 3.5.2, "Download the Installer" and Section 3.6, "Patch Set Installer Instructions".

3.8.4.1 Upgrading System Components

This step is required for any system component that is associated with a WebLogic domain. In some cases (for example, Oracle WebTier and Oracle Internet Directory), you can choose to create system components that are not associated with any domain; in these cases, you do not have to perform this procedure.

After you have patched your system component software that is associated with a WebLogic domain, you must run the ORACLE_HOME/opmn/bin/upgradenonj2eeapp.sh (on UNIX operating systems) or ORACLE_HOME\opmn\bin\upgradenonj2eeapp.bat (on Windows operating systems) script to update your system components.

Before running this script, make sure:

1. The Administration Server is up and running.

2. The ORACLE_HOME environment variable has been set to your product's Oracle home directory.

3. The OPMN instance in the bin directory in the Instance home is up and running.

To run the script on UNIX operating systems:

cd ORACLE_HOME/opmn/bin
./upgradenonj2eeapp.sh
   -oracleInstance Instance_Home_Location
   -adminHost WebLogic_Server_Host_Name
   -adminPort administration_server_port_number
   -adminUsername administration_server_user

On Windows operating systems:

cd ORACLE_HOME\opmn\bin
upgradenonj2eeapp.bat
   -oracleInstance Instance_Home_Location
   -adminHost WebLogic_Server_Host_Name
   -adminPort administration_server_port_number
   -adminUsername administration_server_user

3.8.4.2 Updating Configuration Properties in Oracle Identity Federation

The 11g Release 1 (11.1.1.4.0) of Oracle Identity Federation contains several new configuration properties (for example, enabling XML schema validation for federation protocol messages) that were not available in 11g Release 1 (11.1.1.2.0). If you want to take advantage of the functionality provided by these new properties, you must run the oif-upgrade-11.1.1.2.0-11.1.1.4.0.py WLST script as follows:

1. On Linux operating systems, enter the bash command:

   bash
   

2. Set the DOMAIN_HOME variable to your Oracle Identity Federation Domain home location.

3. Set the ORACLE_HOME variable to your Oracle Identity Federation Oracle home location.

4. Run the setOIFEnv script.

   On UNIX operating systems:

   bash
   export DOMAIN_HOME=full_path_to_domain_home_directory
   source ORACLE_HOME/fed/scripts/setOIFEnv.sh
   

   On Microsoft Windows operating systems:

   cd ORACLE_HOME\fed\scripts
   setOIFEnv.cmd
   

5. Run the oif-upgrade-11.1.1.2.0-11.1.1.4.0.py script.

   On UNIX operating systems:

   cd ORACLE_HOME/fed/scripts
   java weblogic.WLST oif-upgrade-11.1.1.2.0-11.1.1.4.0.py
   

   On Microsoft Windows operating systems:

   cd ORACLE_HOME\fed\scripts
   java weblogic.WLST oif-upgrade-11.1.1.2.0-11.1.1.4.0.py
   

   You will be prompted for the WebLogic Server Administrator credentials (user name and password) and the location of the Managed Server where Oracle Identity Federation is running. You only need to do this for one Managed Server even if you have multiple Managed Servers in your domain.

3.8.4.3 Updating Oracle Configuration Manager (Windows Only)

If you are patching Oracle Identity Manager or Oracle Portal, Forms, Reports and Discoverer on a Microsoft Windows operating system, you must run some emCCR commands after applying the latest patch set in order for the correct version to appear. emCCR is used by Oracle Configuration Manager, which is used to collect client configuration information and upload it to the Oracle repository:

If you are patching Oracle Identity Manager on a Microsoft Windows operating system, you must run some emCCR commands after applying the latest patch set in order for the correct version to appear. emCCR is used by Oracle Configuration Manager, which is used to collect client configuration information and upload it to the Oracle repository:

1. Go to the ORACLE_HOME\ccr\bin directory.

2. Set the ORACLE_CONFIG_HOME environment variable to the Instance home that contains Oracle Configuration Manager. For example:

   set ORACLE_CONFIG_HOME=C:\Oracle\Middleware\Instances\asinst_ocmoc
   

3. Run the following emCCR commands:

   emccr stop
   emccr start
   emccr status
   

3.8.4.4 Resolving JDBC Errors in Oracle Reports and Oracle Portal

If you have Oracle Reports or Oracle Portal configured in a domain and you apply the latest patch set, you will see the following error if you try to change the invalidation password:

Error.  Check logs for details.  [OK]. 

The following errors are seen in the portal_wls.log and wls_portal.out log files:

<Date and time> <Warning> <RMI> <BEA-080003>
<RuntimeException thrown by rmi server:
javax.management.remote.rmi.RMIConnectionImpl.invoke
(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
javax.management.RuntimeErrorException:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I.javax.management.RuntimeErrorException:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I
at
oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:991)
at
oracle.adf.mbean.share.AdfMBeanInterceptor.internalInvoke(AdfMBeanInterceptor.java:104)
at
oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
....
 
Caused By: java.lang.UnsatisfiedLinkError:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I
at oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber(Native
        Method)
at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:3537)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.jdbc.driver.T2CConnection.loadNativeLibrary
        (T2CConnection.java:3532)
.... 

You must perform the following in order to avoid these JDBC error messages:

1. Go to the bin directory inside your DOMAIN_HOME.

2. Edit the setDomainEnv.sh (on UNIX operating systems) or setDomainEnv.cmd (on Windows operating systems) file and search for EXT_PRE_CLASSPATH.

3. Change the definition to match the following:

   On UNIX operating systems:

   EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar
   export EXT_PRE_CLASSPATH
   

   On Windows operating systems:

   EXT_PRE_CLASSPATH=%ORACLE_HOME%\jdbc\lib\ojdbc6.jar
   

4. Restart the Portal Managed Server.

3.8.4.5 Updating the Configuration in SSL-Enabled Oracle Portal Instances

Due to security changes in WebLogic Server, if you were running an SSL-enabled 11g version of Oracle Portal and patched it to Release 11.1.1.5.0, you will need to perform the steps mentioned in the "Enable the WebLogic Plug-In, and WLProxySSL and WLProxySSLPassThrough Parameters" section of the Oracle Fusion Middleware Administrator's Guide for Oracle Portal before your Oracle Portal instance will be functional again.

3.8.5.1 Updating Fusion Middleware Shared Libraries

For each WebLogic Server domain, you must run the updateJRF() WLST command to update the shared libraries in your domain:

1. Stop all running instances, Managed Servers, Administration Server, and Node Manager in the domain. See "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide for more information.

2. Start WLST.

   On UNIX operating systems:

   cd oracle_common/common/bin
   ./wlst.sh
   

   On Windows operating systems:

   cd oracle_common\common\bin
   wlst.cmd
   

3. Run the upgradeJRF() command on the node or system where the Administration Server is located for each domain you want to update. Your domain location is passed as a parameter:

   wlst> upgradeJRF('/DOMAIN_HOME')
   

3.8.5.2 Updating Configurations and Stores

For each WebLogic Server domain, you must run the upgradeOpss() WLST command to update your configurations and stores from previous releases to Release 11.1.1.5.0 configurations and stores using a system-jazn-data file in Release 11.1.1.5.0.

Before running this command, start WLST as shown below:

On UNIX operating systems:

cd MW_HOME/oracle_common/common/bin
./wlst.sh

On Windows operating systems:

cd MW_HOME\oracle_common\common\bin
wlst.cmd

After WLST is started, run the upgradeOpss() command. The syntax for the command is below:

upgradeOpss(jpsConfig="existing_jps_config_file", jaznData="system_jazn_data_file")

• existing_jps_config_file

  Full path to the location of the existing jps-config.xml file, usually DOMAIN_HOME/config/fmwconfig/jps-config.xml (on UNIX operating systems) or DOMAIN_HOME\config\fmwconfig\jps-config.xml (on Windows operating systems).

• system_jazn_data_file

  Full path to the location of the Release 11.1.1.5.0 system-jazn-data.xml file, usually MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml (on UNIX operating systems) or MW_HOME\oracle_common\modules\oracle.jps_11.1.1\domain_config\system-jazn-data.xml (on Windows operating systems).

For more information, see "Upgrading Policies with upgradeOpss" in Oracle Fusion Middleware Security Guide.

3.8.5.3 Enabling WS-AtomicTransaction

WS-AtomicTransaction is a web services feature which was introduced in Oracle Fusion Middleware Release 11.1.1.3.0 release. If you are upgrading a domain which is at the 11.1.1.2.0 release, then you need to perform the following steps to ensure that WS-AtomicTransactions are enabled:

1. Edit the following file.

   On UNIX operating systems:

   DOMAIN_HOME/config/fmwconfig/policy-accessor-config.xml
   

   On Windows operating systems:

   DOMAIN_HOME\config\fmwconfig\policy-accessor-config.xml
   

2. In the Interceptors section, add the following XML code:

   <interceptor name="ClientWSATInterceptor"
      class="oracle.j2ee.ws.client.transaction.ClientWSATInterceptor"
      category="transaction" />
   <interceptor name="ServerWSATInterceptor"
      class="oracle.j2ee.ws.server.transaction.ServerWSATInterceptor"
      category="transaction" />
   

3. In the Interceptor Chains section:

   • <interceptor-ref name="ServerWSATInterceptor"/> should be added in the existing entry of SOAPServiceBindingInterceptorChain between the Context and RM interceptors. For example:

     <interceptor-chain name="SOAPServiceBindingInterceptorChain"
                           
     @ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">
              <interceptor-ref name="MTOMInterceptor"/>
              <interceptor-ref name="BindingSecurityInterceptor"/>
              <interceptor-ref name="ServerAddressingInterceptor"/>
              <interceptor-ref name="MEXInterceptor"/>
              <interceptor-ref name="WSRMServerInterceptor"/>
     <interceptor-ref name="ServerWSATInterceptor"/>
              <interceptor-ref name="ContextInterceptor"/>    
              <interceptor-ref name="BindingManagementInterceptor"/>
     </interceptor-chain> 
     

   • <interceptor-ref name="ClientWSATInterceptor"/> should be added in the existing entry of SOAPReferenceBindingInterceptorChain between the Context and RM interceptors. For example:

     <interceptor-chain name="SOAPReferenceBindingInterceptorChain"
                           
     @ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">
              <interceptor-ref name="BindingManagementInterceptor"/>
              <interceptor-ref name="ContextInterceptor"/>
     <interceptor-ref name="ClientWSATInterceptor"/>
              <interceptor-ref name="WSRMClientInterceptor"/>
              <interceptor-ref name="ClientAddressingInterceptor"/>
           
              <interceptor-ref name="BindingSecurityInterceptor"/>
              <interceptor-ref name="MTOMInterceptor"/>
     </interceptor-chain>
     

3.8.6.1 Removing the tmp Folder for SOA Composer and BPM Workspace

This manual step must be performed if:

• You are upgrading Oracle SOA Composer from Release 11.1.1.2.0 or 11.1.1.3.0; the SOA Composer login screen may appear blank after you patch to the latest version.

• You are upgrading Oracle BPM Workspace from Release 11.1.1.3.0; the Oracle BPM Workspace application will not start after you patch to the latest version.

To resolve these issues, do the following:

1. Stop all servers (Administration Server and all Managed Servers).

2. Remove the tmp directory in DOMAIN_HOME/servers/AdminServer (on UNIX operating systems) or DOMAIN_HOME\servers\AdminServer (on Windows operating systems).

3. Remove the tmp directory in DOMAIN_HOME/servers/soa_server1 (on UNIX operating systems) or DOMAIN_HOME\servers\soa_server1 (on Windows operating systems).

   If the name of your SOA Managed Server is not soa_server1, replace soa_server1 with the name of your SOA Managed Server.

4. Start all the servers.

3.8.6.2 Updating the soa-infra Application in Warning State

If you have a Release 11.1.1.3.0 Oracle SOA Suite domain with only Oracle SOA configured (no Oracle BAM and no Oracle BPM), or only Oracle SOA and Oracle BAM configured (no Oracle BPM), the soa-infra application (The weblogic server EAR file which contains the underlying logic for the SOA Suite infrastructure) will have a deployment status of Warning which will be visible within the WebLogic Server Administration Console. This state will not cause any loss or degradation in service.

If you want to fix this issue, contact Oracle Support.

3.8.6.3 Run soa-upgrade.py to Update the Policy Store and Deploy a Shared Library

To update your policy store and deploy shared libraries, run the soa-upgrade.py WLST script, which does the following:

• Adds a new Role Grant and Policy grant within the soa-infra application stripe in the Policy Store.

• Deploys the oracle.soa.worklist.webapp shared library to the SOA domain.

The soa-upgrade.py script must be run from the bin directory inside your SOA Oracle home. The syntax for the soa-upgrade.py script is shown below.

On a UNIX operating system:

cd SOA_ORACLE_HOME/bin
../common/bin/wlst.sh soa-upgrade.py
--username admin_username
--password admin_password
--wlsHost wls_host
--adminServerListenPort admin_port
--targetList list_of_SOA_servers_or_migratable_targets

On a Windows operating system, run wlst.cmd from the same directory.

Table 3-6 describes the command line parameters.

After running this command, stop and restart all the servers.

3.8.6.4 Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled

If you are currently using Oracle BAM and Oracle Data Integrator (ODI) integration, you must re-run an installation script to update your ODI clients after patching your software.

The Oracle BAM interface used by ODI has undergone some changes between releases which require an update by all ODI client endpoints. This manual step is only required for domains where a BAM-ODI integration has been configured.

For each such domain, you must run the SOA_ORACLE_HOME/bam/bin/bam_odi_configuration.sh (on UNIX operating systems) or SOA_ORACLE_HOME\bam\bin\bam_odi_configuration.bat (on Microsoft Windows operating systems) script. Use the PATCH command line parameter to copy the Oracle BAM artifacts. For details, see "Using Oracle Data Integrator With Oracle BAM" in Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

If ODI and Oracle BAM Server are installed on hosts in different networks, or for any reason you cannot use the script in your environment, you must manually do the following to update your ODI clients:

1. Using the Middleware home directory under which Oracle BAM is installed, generate a wlfullclient.jar file by using the instructions in "Using the WebLogic JarBuilder Tool" in Oracle Fusion Middleware Programming Stand-alone Clients for Oracle WebLogic Server.

2. Copy wlfullclient.jar to the ODI_ORACLE_HOME/lib/weblogic (on UNIX operating systems) or ODI_ORACLE_HOME\lib\weblogic (on Windows operating systems) directory.

3. Copy the following Oracle BAM .jar files to the lib directory in the ODI Oracle home:

   On UNIX operating systems:

   SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-common.jar
   SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-etl.jar
   SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-adc-ejb.jar
   SOA_ORACLE_HOME/bam/modules/oracle.bam.thirdparty_11.1.1/commons-codec-1.3.jar
   SOA_ORACLE_HOME/bam/modules/oracle.bam.thirdparty_11.1.1/xstream-1.3.1.jar
   oracle_common/modules/oracle.odl_11.1.1/ojdl.jar
   oracle_common/modules/oracle.jps_11.1.1/jps-api.jar
   oracle_common/modules/oracle.dms_11.1.1/dms.jar
   oracle_common/modules/org.jaxen_1.1.1.jar
   

   On Windows operating systems:

   SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-common.jar
   SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-etl.jar
   SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-adc-ejb.jar
   SOA_ORACLE_HOME\bam\modules\oracle.bam.thirdparty_11.1.1\commons-codec-1.3.jar
   SOA_ORACLE_HOME\bam\modules\oracle.bam.thirdparty_11.1.1\xstream-1.3.1.jar
   oracle_common\modules\oracle.odl_11.1.1\ojdl.jar
   oracle_common\modules\oracle.jps_11.1.1\jps-api.jar
   oracle_common\modules\oracle.dms_11.1.1\dms.jar
   oracle_common\modules\org.jaxen_1.1.1.jar
   

4. Copy the following Oracle BAM Knowledge Modules from the SOA_ORACLE_HOME/bam/ODI/knowledge_modules (on UNIX operating systems) or SOA_ORACLE_HOME\bam\ODI\knowledge_modules (on Windows operating systems) directory to the ODI_HOME/lib (on UNIX operating systems) or ODI_HOME\lib (on Windows operating systems) directory:

   KM_CKM Get Oracle BAM Metadata.xml
   KM_IKM SQL to Oracle BAM (delete).xml
   KM_IKM SQL to Oracle BAM (insert).xml
   KM_IKM SQL to Oracle BAM (looksert natural).xml
   KM_IKM SQL to Oracle BAM (looksert surrogate).xml
   KM_IKM SQL to Oracle BAM (update).xml
   KM_IKM SQL to Oracle BAM (upsert).xml
   KM_LKM Get Source Metadata.xml
   KM_LKM Oracle BAM to SQL.xml
   KM_RKM Oracle BAM.xml
   

5. Backup the following ODI_HOME configuration files.

   On UNIX operating systems:

   ODI_HOME/lib/bam_odi.logging.properties
   ODI_HOME/lib/config/BAMODIConfig.xml
   

   On Windows operating systems:

   ODI_HOME\lib\bam_odi.logging.properties
   ODI_HOME\lib\config/BAMODIConfig.xml
   

6. Copy the new version of the ODI configuration files from the SOA_ORACLE_HOME/bam/ODI (on UNIX operating systems) or SOA_ORACLE_HOME\bam\ODI (on Windows operating systems) directory to the ODI_ORACLE_HOME directory as follows.

   Note:

   If you made any changes to the ODI configuration files before you installed the patch set, then you must make those changes again after you copy the new configuration files from the SOA Oracle home.

   On UNIX operating systems:

   SOA_ORACLE_HOME/bam/ODI/config/bam_odi.logging.properties to ODI_HOME/lib/bam_odi.logging.properties
   SOA_ORACLE_HOME/bam/ODI/config/BAMODIConfig.xml to ODI_HOME/lib/config/BAMODIConfig.xml
   

   On Windows operating systems:

   SOA_ORACLE_HOME\bam\ODI\config\bam_odi.logging.properties to ODI_HOME\lib\bam_odi.logging.properties
   SOA_ORACLE_HOME\bam\ODI\config\BAMODIConfig.xml to ODI_HOME\lib\config\BAMODIConfig.xml
   

3.8.6.5 Committing or Reverting Open Edit Sessions in SOA Composer

Before upgrading from a previous release to 11.1.1.5.0, make sure all Edit sessions in SOA Composer are committed or reverted.

SOA Composer provides DT@RT functionality to edit rules dictionaries after deployment. After upgrading to the latest version, all uncommitted sessions in SOA Composer will lost or there can be issues accessing the edit sessions. This is because the MDS sandboxes (used for handling sessions) are not upgraded.

To commit or revert the sessions:

1. Log in to the SOA Composer (/soa/composer) as any user with active sessions.

2. Go to Open > My Edits to view all of your active sessions.

3. Open each documents listed in "My Edits" and do one of the following:

   1. Click Commit to commit the session changes.

   2. Select Revert > Clear all session edits and saved changes to abort the changes.

   Either step will result in the session being closed.

3.8.6.6 Saving and Restoring XEngine Customizations for Oracle B2B

The procedure in this section is needed only if you use custom XEngine configurations in cases where B2B server is integrated with B2B EDI endpoints.

In such cases, all B2B domains created from the same installation share the a single XEngine configuration stored within the following directory:

• On UNIX operating systems:

  MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
  

• On Windows operating systems:

  MW_HOME\SOA_ORACLE_HOME\soa\thirdparty\edifecs\XEngine
  

To preserve your XEngine customizations:

1. Prior to patching Oracle SOA Suite, back up all contents in the following directory:

   MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
   

   For example, on a UNIX operating system:

   cp -pr SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine backup_location
   

2. Run the Patch Set Installer to update the software.

3. Unzip the XEngine ZIP file in the following directory:

   MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
   

   For example, on a UNIX operating system:

   cd SOA_ORACLE_HOME/soa/thirdparty/edifecs
   gunzip XEngine.tar.gz
   tar -xvf XEngine.tar
   

4. Restore only the customized configuration files from your backup location.

   For example, if you made changes to the XERegistry.xml file on a UNIX operating system:

   cp backup_location/config/XERegistry.xml 
        SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine/config
   

3.8.7.1 Updating Oracle I/PM in Oracle Enterprise Content Management Suite

After updating your Oracle Enterprise Content Management Suite software to Release 11.1.1.5.0 from 11.1.1.3.0, the manual steps in this section must be performed to target a newly distributed library to the Oracle Imaging and Process Management (Oracle I/PM) deployment. If these steps are not performed, the Oracle I/PM Managed Server (default of IPM_server1) will not start.

1. Start Oracle WebLogic Server and open the Console:

   http://administration_server_host:administration_server_port/console
   

2. For production systems, go to the "Change Center" portion of the navigation panel on the left and click Lock & Edit.

3. Targeting the Oracle Application Core Stub file:

   1. In the "Domain Structure" portion of the navigation panel on the left, click Deployments.

   2. Above the "Deployments" table, click the Install button.

   3. In the "Path" field, browse to the directory containing the Oracle Application Core Stub file.

      The default location is MW_HOME/oracle_common/atgpf/modules/oracle.applcore.model_11.1.1 (on UNIX operating systems) or MW_HOME\oracle_common\atgpf\modules\oracle.applcore.model_11.1.1 (on Windows operating systems).

   4. Select the oracle.applcore.model.stub.ear file and click Next.

   5. Select Install this deployment as a library and click Next.

   6. Select IPM_server1 as the deployment target and click Next.

   7. Click Finish.

4. Targeting the Oracle SOA Libraries file for BPM:

   Note:

   If oracle.soa.workflow.wc.jar is already installed due to Oracle SOA Suite being a part of the domain, you should skip the following Steps a-f. Instead, navigate to oracle.soa.workflow.wc in deployments, then go into its "Targets" tab and target IPM_server1.

   1. In the "Domain Structure" portion of the navigation panel on the left, click Deployments.

   2. Above the "Deployments" table, click the Install button.

   3. In the "Path" field, browse to the directory containing the Oracle SOA Libraries file.

      The default location is ECM_ORACLE_HOME/soa/modules/oracle.soa.workflow_11.1.1 (on UNIX operating systems) or ECM_ORACLE_HOME\soa\modules\oracle.soa.workflow_11.1.1 (on Windows operating systems).

   4. Select the oracle.soa.workflow.wc.jar file and click Next.

      A message indicating errors while parsing the deployment will appear in the "Messages" box at the top of the screen. The configuration will treat this as a library deployment. This is expected.

   5. Select IPM_server1 as the deployment target and click Next.

   6. Click Finish.

5. For production systems, go to the "Change Center" portion of the navigation panel on the left and click Accept Changes.

6. Any instances of the IPM Managed Server must be restarted for this change to take effect.

7. Redeploy the ECM_ORACLE_HOME/ipm/lib/imaging.ear (on UNIX operating systems) or ECM_ORACLE_HOME\ipm\lib\imaging.ear (on Windows operating systems) file.

   To redeploy this file:

   java weblogic.Deployer -redeploy -name appName
   

   Where appName is the name of the application as defined in the config.xml file.

   You can also redeploy using WLST using the redeploy() command:

   redeploy("appName")
   

3.8.7.2 Updating Oracle Application Adapters for Oracle Enterprise Content Management Suite

The Oracle Enterprise Content Management Suite application adapters as described in Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management contain manual steps for installing the adapters to their respective ERP system (EBS and PeopleSoft). In order to update to from Release 11.1.1.3.0 to Release 11.1.1.5.0, these adapters must be reinstalled.

To reinstall the EBS adapter:

1. Follow the instructions in "Compiling Oracle E-Business Suite Forms" in Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management to update the AXF_CUSTOM.PLL module.

2. Follow the instructions in "Configuring the Integration for SSL" in Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management.

To re-import the PeopleSoft project, follow the instructions (steps 1-6) in "Importing the Oracle PeopleSoft Project" in Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management.

3.8.7.3 Applying Patch 12369706 for Oracle Information Rights Management

The 11.1.1.5.0 Oracle IRM Server Management Console has an issue that requires a patch to be applied to the installed or upgraded system. When rights are being selected for a context, the Properties, Edit, and Remove buttons are always disabled and cannot be used. Selecting one or more rights will not enable the buttons. Patch 12369706 fixes this issue.

To download and apply the patch to Oracle IRM:

1. Log in to My Oracle Support:

   https://support.oracle.com/
   

2. Click the Patches & Updates tab.

3. Enter the patch number, 12369706, in the Patch Name or Number field, under Patch Search.

4. Click Search.

5. Follow the installation instructions provided with the patch.

3.8.9.1 Updating an Oracle Service Bus Domain After Applying the Latest Patch Set

To update your Oracle Service Bus domain configuration information:

1. Make sure you have backed up and shut down all domains to be updated.

2. Under each Oracle Service Bus domain to be updated, open a command window and run the DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems) or DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows operating systems) command.

3. In the command window, switch to the directory in which the update scripts resides:

   OSB_ORACLE_HOME/common/lib/upgrade

4. On the command line, run the appropriate script for your operating system:

   On UNIX operating systems:

   java weblogic.WLST ./domainUpgrade.py
   

   On Windows operating systems:

   java weblogic.WLST domainUpgrade.py
   

3.8.9.2 Additional Post-Update Tasks for Oracle Service Bus

This section describes the required tasks after updating your Oracle Service Bus software to the latest version.

3.8.10.1 Updating Oracle Business Intelligence Code Grants

If you are updating to the latest version of Oracle Business Intelligence (BI) from Release 11.1.1.3.0, you must run the bi-upgrade.py script in each Oracle BI domain. This script configures the code grants necessary to ensure that SSL works correctly for Oracle BI, and must be run even if SSL is not used.

To run the script on UNIX operating systems:

cd MW_HOME/oracle_common/common/bin
./wlst.sh BI_ORACLE_HOME/bin/bi-upgrade.py --bioraclehome BI_ORACLE_HOME  --domainhome bi_domain_home

To run the script on Windows operating systems:

cd MW_HOME\oracle_common\common\bin
wlst.cmd BI_ORACLE_HOME\bin\bi-upgrade.py --bioraclehome BI_ORACLE_HOME  --domainhome bi_domain_home

Replace BI_ORACLE_HOME with the full path to your Business Intelligence Oracle home location, and replace bi_domain_home with the full path to your Business Intelligence domain home location.

3.8.10.2 Updating Oracle Business Intelligence Catalogs

When updating your Oracle Business Intelligence (BI) software from Release 11.1.1.3.0 to 11.1.1.5.0, you must manually update your Oracle BI Presentation Catalogs. Instructions are provided below:

1. Shut down Oracle BI Presentation Services using Oracle Enterprise Manager.

   For details, see "Using Fusion Middleware Control to Start and Stop Oracle Business Intelligence System Components and Java Components" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

2. Back up your Release 11.1.1.3.0 catalogs by using the 7-Zip utility to create a compressed file for it.

3. Create a backup copy of the instanceconfig.xml file.

   The instanceconfig.xml file is located in the ORACLE_INSTANCE/config/OracleBIPresentationServicesComponent/coreapplication_obipsn (on UNIX operating systems) or ORACLE_INSTANCE\config\OracleBIPresentationServicesComponent\coreapplication_obipsn (on Windows operating systems) directory.

4. Change the upgradeAndExit option to true in the instanceconfig.xml file.

   Find the following code:

   <ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">
      <ps:UpgradeAndExit>false</ps:UpgradeAndExit>
   </ps:Catalog> 
   

   Change it to the following:

   <ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">
      <ps:UpgradeAndExit>true</ps:UpgradeAndExit>
   </ps:Catalog> 
   

5. Start Oracle BI Presentation Services using the following OPMN command the update the catalogs:

   opmnctl startproc ias-component=coreapplication_obipsn 
   

   For example, on a UNIX operating system:

   cd ORACLE_INSTANCE/bin
   ./opmnctl startproc ias-component=coreapplication_obips1
   

   On a Windows operating system:

   cd ORACLE_INSTANCE\bin
   opmnctl startproc ias-component=coreapplication_obips1
   

6. After the catalogs are updated, edit the instanceconfig.xml file again and change the upgradeAndExit option back to false.

7. Restart Oracle BI Presentation Services using Fusion Middleware Control.

3.8.10.3 Updating Oracle Real-Time Decisions

This section describes how to upgrade Oracle Real-Time Decisions (RTD). The following steps are required:

• Section 3.8.10.3.1, "Update the rtd_ils Resource Type Using WLST"

• Section 3.8.10.3.2, "Add Permissions to the BIAdministrator Principle Using EM"

• Section 3.8.10.3.3, "Removing JMS"

3.8.11.1 Finalizing Repository Patching

After you have patched the Oracle Data Integrator schemas in your database (Chapter 4, "Updating Your Schemas with Patch Set Assistant"), you must update the following repository objects (technologies, profiles, knowledge modules), which are not updated with Patch Set Assistant:

• Technology Changes

  • Added: ComplexFile and Groovy

  • Changed: Oracle

    • Natural keyword join was added

    • Join capability was extended to BOTH

    • Default table name prefixes were added

  • Changed: Teradata

  • Changed: PostgreSQL

  • Changed: Netezza

  • Changed: OracleBI

  • Changed: Hypersonic In-Memory Engine

  • Changed: PostgreSQL supports SQL for retrieving sequences

• Language Changes: Groovy was added

• Profile Changes

  Changes were made to LoadPlan support in the following profiles:

  • [NG] DESIGNER

  • [NG] REPOSITORY EXPLORER

  • [NG] VERSION ADMIN

  • OPERATOR

  • SECURITY_ADMIN

• Knowledge Modules

  LKM File to Oracle (SQLLDR) works after removing 'import javaos' from KM step 'call sqlldr'. The old LKM no longer works with an upgraded Jython version.

For more information about how to update these repository objects, see "Oracle Data Integrator Post-Upgrade Tasks" in Oracle Fusion Middleware Upgrade Guide for Oracle Data Integrator.

3.8.11.2 Reconfiguring the Java EE Agent

By default, ODI ships a static Java EE Agent deployment template. To reconfigure the Java EE agent:

1. Make sure the Administrator Server and ODI Managed Servers are up and running.

2. Add the WebLogic Server classes to the CLASSPATH environment variable and the WebLogic_Home/server/bin (on UNIX operating systems) or WebLogic_Home\server\bin (on Windows operating systems) directory to the PATH environment variable.

   This can be accomplished by running the setWLSEnv script located in the WebLogic_Home/server/bin (on UNIX operating systems) or WebLogic_Home\server\bin (on Windows operating systems) directory.

3. Undeploy the version 11.1.1.3.0 Java EE agent from your domain using the following command:

   java weblogic.Deployer -url admin_server_url -username admin_server_username -password admin_server_password -targets odi_server_name -name odi_agent_name –undeploy
   

   For example:

   java weblogic.Deployer -url http://examplehost.com:7001 -username exampleuser -password examplepassword -targets odi_server1 -name oraclediagent –undeploy
   

   For more information, see "Managing Deployed Applications" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

4. Run the Configuration Wizard. On the Select Domain Source screen, select the Oracle Data Integrator – Agent – 11.1.1.0 template.

   For more information, see "Configure a WebLogic Domain" in Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.

ODI also enables you to generate a Java EE agent deployment template from ODI Studio. You can customize the Java EE agent with additional data sources and libraries. To do so:

1. Undeploy the version 11.1.1.3.0 Java EE agent from your domain.

   For more information, see "Managing Deployed Applications" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

2. Using ODI Studio version 11.1.1.5.0 or the command line script to generate equivalent Java EE agent template with required data sources and additional libraries.

   For more information on data source declaration, deployment and template generation in ODI Studio, see "Java EE Agent" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

3. Run the Configuration Wizard. On the Select Domain Source screen, select Oracle Data Integrator – Agent Libraries– 11.1.1.0 to deploy the template.

4. Run the Configuration Wizard a second time, and on the Select Domain Source screen, deploy the generated version 11.1.1.5.0 ODI Java EE agent template to the domain.

3.8.11.3 Reconfiguring the ODI Standalone Agent

To reconfigure the ODI standalone agent:

1. Make sure you have backed up the necessary files and directories as described in "Back Up Files for Oracle Data Integrator Java EE Standalone Agent" in Section 3.4.4, "Back Up Additional Configuration Information".

2. Run the Oracle Data Integrator installer.

   On the Configure Repositories Install screen, choose Skip Repository Creation.

3. After the installation is complete:

4. • Restore the ODI_HOME/oracledi/agent/bin/odiparams.sh (on UNIX operating systems) or ODI_HOME\oracledi\agent\bin\odiparams.bat (on Windows operating systems) file.

   • Restore the ODI_HOME/oracledi/agent/drivers (on UNIX operating systems) or ODI_HOME\oracledi\agent\drivers (on Windows operating systems) directory.

For more information, see "Stopping a Standalone Agent" and "Manually Configure the Standalone Agent" in Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.

3.8.11.4 Reconfiguring Oracle Enterprise Manager Properties

After you have patched Oracle Data Integrator, some of the properties in Oracle Enterprise Manager are lost. To restore these properties, set the following property before starting the Managed Server on which the Oracle Data Integrator Console is deployed:

set JAVA_OPTIONS="-Doracle.odi.repex.view.main.init.skipem=false"