16 Oracle BPEL Process Manager

16.1.1 Callback Not Received When Two Asynchronous Methods Are Invoked Using the Same Partner Link Definition

A BPEL process does not receive a callback when two asynchronous methods are invoked on an external stateless web service using the same partner link definition.

As a workaround, create a separate partner link for each invoke and receive pair in the BPEL process when calling this type of web service. The callback is received and the BPEL process completes successfully when you have more than one method invoked on the same partner link.

16.1.2 Limitations on Using the Identity Lookup in IM and User Notification Activities

The Identity Lookup icon for the TO field of the IM activity is disabled.

As a workaround, perform one of the following actions.

• Manually enter the instant messaging (IM) address in the TO field.

• Click the XPath Expression Builder icon for the TO field to get the IM address of the user (the user name can be provided in the payload).

When you select the Identity Lookup icon for the TO field of the User Notification Activity, the Identity Lockup dialog appears. After performing a search query to display your results in the Search User section, the Select button that you click to move a user to the Selected User section does not work. If you click the Select button, you can receive a popup message similar to the following:

The following user cannot be selected since fax number is not available

As a workaround, perform the following steps:

1. Obtain the user ID you want by performing a search query (for example, jcooper).

2. Do not click the Select button.

3. Click OK to return to the User Notification dialog.

4. Manually enter the user ID in the TO field.

16.1.3 Cannot Upgrade Oracle BPEL Process Manager Client Java API Reference to 11g Release 1

Custom applications coded with the Oracle BPEL Process Manager 10.1.3 Client Java API cannot currently be upgraded to the 11g Release 1 Client Java API. As a workaround, you can use the Infrastructure Management API that is shipped with Release 1. However, note that this API is currently being rationalized and reworked. Periodic updates to the Infrastructure Management JavaDoc are being made available on the Oracle Technology Network. Visit the following URL for details:

http://www.oracle.com/technology/products/soa/bpel/collateral/documentation.html

16.1.4 Boundary on Processing of Large Numbers of Activities in a BPEL Process

There is a limit to the number of activities that can be executed in a BPEL process. When you exceed this limit, system memory fills up, which can cause time outs to occur. For example, with the following parameters, two fault instances occur due to a time out:

• 100 threads

• 1 second of think time

• 1000 incoming request messages

Try to keep the number of incoming request messages at a proper level to ensure system memory stability.

16.1.5 Using a Single Correlation ID Across Multiple Receive Activities is Not Supported

If you use a single correlation ID across multiple receive activities in a BPEL process, more than one instance ID is created.

16.1.6 Vertical Scroll Bar Does Not Display in the Expression Field

The Expression field in the Create Copy Operation dialog of an assign activity does not display a vertical scroll bar if the content of the XPath expression is greater than the size of the field.

As a workaround, use the up and down arrow keys to scroll through the expression.

16.1.7 Bookmarks Folder is Not Deleted from the Manage Bookmarks Dialog

If you create a folder in the Manage Bookmarks dialog in Oracle BPEL Designer, then delete it, the folder continues to display in this dialog.

As a workaround, click OK to close the Manage Bookmarks dialog, then reopen it. The folder is deleted and no longer appears.

16.1.8 Parsing of MIME Attachments is Not Supported

A BPEL process can receive a MIME attachment along with the payload. The attachment can be in any format (for example, doc, PDF, JPEG, XML, text, and so on). If the BPEL process receives an XML attachment and must parse the XML to get an element value, you cannot do it using a single XPath function. This task must be performed in two steps:

1. Use the ora:writeBinaryToFile XPath function.

   <copy> 
        <from expression="ora:writeBinaryToFile('input2','bin',
    'file:///tmp/out/attachment.xml')"/> 
        <to variable="input2" part="bin"/> 
   </copy> 
   

2. Use the doc XPath function to read the XML element from the above file.

   <copy> 
        <from expression="ora:doc('file:///tmp/out/Input.xml')"/> 
        <to variable="DecodedAttachment" query="/ns1:discountandshipping"/> 
   </copy>
   

16.1.9 Viewing Non-English XML Documents in the Audit Trail Page

If the payload XML has non-English characters, you receive a popup with the following error message in the Audit Trail page when you click the View XML Document inline link.

XML Parsing Error: not well-formed

As a workaround, right-click in the Audit Trail page and select the option for viewing the source to see the complete XML.

16.2.1 Changing the Driver Name to Support XA Drivers

If your data sources require support for XA drivers, you must change the driver name on Oracle WebLogic Server. This is particularly true for environments in which BPEL processes assume XA is present when calling database adapters and JMS adapters.

Change the driver name through one of the following methods.

• Edit in Oracle WebLogic Server Administration Console.

  1. Log into Oracle WebLogic Server Administration Console.

  2. In the left pane, select Domain Structure.

  3. Select Services > JDBC > Data Source > SOADataSource > Connection Pool.

  4. For the Driver Class Name, change the value to oracle.jdbc.xa.client.OracleXADataSource.

     This provides support for the XA driver.

  5. Restart the server.

• Edit the soaDataSource-jdbc.xml file.

  1. Open the soaDataSource-jdbc.xml file on Oracle WebLogic Server.

  2. Change the SOADataSource driver name from oracle.jdbc.OracleDriver to oracle.jdbc.xa.client.OracleXADataSource.

     <?xml version="1.0" encoding="UTF-8"?>
     <jdbc-data-source
     /. . .
     . . .
     /  <name>SOADataSource</name>
      <jdbc-driver-params>
           <url>jdbc:oracle:thin:@adc60086fems.us.oracle.com:1537:co0yd570</url>
           <driver-name>*oracle.jdbc.xa.client.OracleXADataSource*</driver-name>
        <properties>
          <property>
            <name>user</name>
            <value>fusion_soainfra</value>
          </property>
        </properties>
     /  . . .
      . . ./
      </jdbc-driver-params>
     /. . .
     . . ./
     </jdbc-data-source>
     

16.3.1 setPriority Method is Not Supported

Section "13.2.5 How to Use bpelx:exec Built-in Methods" of Chapter 13, "Incorporating Java and Java EE Code in a BPEL Process" of the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite describes the setPriority method. This method is not supported in 11g Release 1.