Post-Upgrade Steps for Projects That Use WSIF Bindings to EJBs

10-6 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF 10.2.4 Verifying the Properties File Name When Upgrading Projects That Use Correlation Sets in an Asynchronous Service. If you created an Oracle BPEL Process Manager 10g project that used correlation sets in an asynchronous service, as described in the Oracle BPEL Process Manager 10g Release 3 10.1.3 Developer’s Guide, make sure that the correlation set properties file uses the following proper naming convention: BPEL_FILE_NAME _Properties.wsdl If this file naming convention is not followed in the Oracle BPEL Process Manager 10g project, the properties will not be upgraded correctly. If you need to change the name to meet the file naming conventions, then also update the wsdl file that imports the property file name, accordingly.

10.2.5 Upgrading Projects With the transaction=participate Property

If you open and upgrade an Oracle BPEL Process Manager 10g project that has a configuration property, transaction=participate, then that property will not be migrated to 11g when you open the application in Oracle JDeveloper 11g. This configuration property is no longer supported in Oracle Fusion Middleware 11g. If you open and upgrade an Oracle BPEL Process Manager 10g project has a partnerLink binding property, transaction=participate, then that property will be dropped on the caller side. The callee project instead should have the property setting bpel.config.transaction=required. This caller to callee setting propagation is not performed by upgrade and must be performed manually after you upgrade the application and before you attempt to deploy it on Oracle Fusion Middleware 11g.

10.2.6 Specifying Domain Descriptor Properties in Oracle BPEL Process Manager 11g

In Oracle BPEL Process Manager 10g, you specify domain properties in the domain.xml descriptor file. In Oracle BPEL Process Manager 11g, you specify Oracle BPEL Process Manager engine properties in bpel-config.xml and soa-infra-config.xml both are accessible as MBeans. Table 10–1 compares the domain descriptor properties available in Oracle BPEL Process Manager 10g and Oracle BPEL Process Manager 10g. There is only one domain in Oracle BPEL Process Manager 11g, which means that these properties will affect the entire server. Upgrading Oracle BPEL Process Manager Applications 10-7 Table 10–1 Domain Descriptor Properties in Oracle BPEL Process Manager 10g and 11g Oracle BPEL Process Manager 10 g in domain.xml file Oracle BPEL Process Manager 11 g MBean Property Description auditDetailThreshold auditDetailThreshold The maximum size in bytes of an audit trail details string before it is stored separately from the audit trail. If a details string is larger than this threshold, then it will not be immediately loaded when the audit trail is initially retrieved; a link will be displayed with the size of the details string. Typically, the details string will contain the contents of a BPEL variable. In cases where the variable is very large, performance may be severely impacted by logging it to the audit trail. The 10g default value is 50 kilobytes. auditLevel auditLevel Controls the amount of audit events logged by a process. The supported logging levels are: ■ off - absolutely no logging performed whatsoever; may result in a slight performance boost for processing instances. ■ minimal - all events are logged; however, no audit details are logged. ■ production - all events are logged. The audit details for assign activities are not logged; the details for all other nodes are logged. ■ development - all events are logged; all audit details for all additives are logged. The 10g default value is development. bpelcClasspath bpelcClasspath Server-side BPEL process compiler classpath. Any user-specific classes or libraries used by a BPEL java exec node that have not been packaged in the BPEL archive need to be specified here so that the server-side BPEL process compiler can successfully compile the BPEL process. datasourceJndi datasourceJndi Moved to soa-infra-config.xml The JNDI name for the domain data source. This data source may refer to any data source JTA not required. deliveryPersistPolicy deliveryPersistPolicy Changes whether the delivery messages are persisted. Delivery messages include invoke message, callback message and subscription message. ■ on - delivery messages are persisted ■ off - delivery messages are kept only in memory. ■ off.immediate - applicable for asynchronous processes only; messages are delivered synchronously regardless of the interface. The 10g default value is on.