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

Applying the Latest Oracle Fusion Middleware Patch Set 3-23 SOA_ORACLE_HOME bammodulesoracle.bam_11.1.1oracle-bam-common.jar SOA_ORACLE_HOME bammodulesoracle.bam_11.1.1oracle-bam-etl.jar SOA_ORACLE_HOME bammodulesoracle.bam_11.1.1oracle-bam-adc-ejb.jar SOA_ORACLE_HOME bammodulesoracle.bam.thirdparty_11.1.1commons-codec-1.3.jar SOA_ORACLE_HOME bammodulesoracle.bam.thirdparty_11.1.1xstream-1.3.1.jar oracle_commonmodulesoracle.odl_11.1.1ojdl.jar oracle_commonmodulesoracle.jps_11.1.1jps-api.jar oracle_commonmodulesoracle.dms_11.1.1dms.jar oracle_commonmodulesorg.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 bamODIknowledge_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 libbam_odi.logging.properties ODI_HOME libconfigBAMODIConfig.xml On Windows operating systems: ODI_HOME \lib\bam_odi.logging.properties ODI_HOME \lib\configBAMODIConfig.xml 6. Copy the new version of the ODI configuration files from the SOA_ORACLE_ HOME bamODI 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. 3-24 Oracle Fusion Middleware Patching Guide On UNIX operating systems: SOA_ORACLE_HOME bamODIconfigbam_odi.logging.properties to ODI_HOME libbam_ odi.logging.properties SOA_ORACLE_HOME bamODIconfigBAMODIConfig.xml to ODI_ HOME libconfigBAMODIConfig.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 DTRT 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 soacomposer 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: a. Click Commit to commit the session changes. b. 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_HOMEsoathirdpartyedifecsXEngine ■ 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_HOMEsoathirdpartyedifecsXEngine For example, on a UNIX operating system: cp -pr SOA_ORACLE_HOME soathirdpartyedifecsXEngine backup_location