Resolving JDBC Errors in Oracle Reports and Oracle Portal

Applying the Latest Oracle Fusion Middleware Patch Set 3-19 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_commoncommonbin .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: upgradeOpssjpsConfig= 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 configfmwconfigjps-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_commonmodulesoracle.jps_11.1.1domain_ configsystem-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 configfmwconfigpolicy-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: Note: If you are patching Oracle WebCenter, you do not need to run this script if you follow the directions in Chapter 5, Patching Oracle WebCenter. 3-20 Oracle Fusion Middleware Patching Guide 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 Post-Patching Tasks for Oracle SOA Suite

This section contains the following topics: ■ Section 3.8.6.1, Removing the tmp Folder for SOA Composer and BPM Workspace ■ Section 3.8.6.2, Updating the soa-infra Application in Warning State ■ Section 3.8.6.3, Run soa-upgrade.py to Update the Policy Store and Deploy a Shared Library ■ Section 3.8.6.4, Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled ■ Section 3.8.6.5, Committing or Reverting Open Edit Sessions in SOA Composer ■ Section 3.8.6.6, Saving and Restoring XEngine Customizations for Oracle B2B