Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for HP-UX PA-RISC (64-bit)
B25187-09
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents
Previous
Previous 		 Next
Next		  

14 Oracle BPEL Process Manager

This chapter describes issues associated with Oracle BPEL Process Manager. It includes the following topics:

14.1 Installation Issues and Workarounds

This section describes the following issues and workarounds:

14.1.1 Message to Ignore During Oracle BPEL Process Manager for OracleAS Middle Tier Installation

You can safely ignore the following message that appears during both Oracle BPEL Process Manager for OracleAS Middle Tier installation and also in the postinstallation log files:

Patch 4869010 not found ... 
WARNING: Patch 4869010 is MANDATORY and must be applied ...

14.1.2 Migrating from Previous Releases of Oracle BPEL Process Manager

To migrate from Oracle BPEL Process Manager release 10.1.2.0.0 to release 10.1.2.0.2, download Patch 5041642 from OracleMetaLink:

http://metalink.oracle.com

This patch includes documentation and a SQL*Plus migration script that enables you to migrate data from release 10.1.2.0.0 to 10.1.2.0.2.

14.1.3 Adding Oracle BPEL Process Manager for OracleAS Middle Tier Memory Settings

After installing Oracle BPEL Process Manager for OracleAS Middle Tier, ensure that you include the following memory settings in the OC4J_BPEL process type section of the Oracle_Home\opmn\conf\opmn.xml file:

<process-type id="OC4J_BPEL" module-id="OC4J"
   <module-data><<category id="start-parameters"> 
      <data id="java-options" value="...
      . . .
      . . .
      -Xms512m -Xmx512m -Xmn300m 
-XX:MaxPermSize=80m .../>

14.2 General Issues and Workarounds

This section describes the following issues and workarounds:

14.2.1 Error with opmnctl stopall to Ignore

The OPMNCTL STOPALL command intermittently fails to perform a graceful shutdown. When this occurs, the process is stopped, but an error similar to the following appears.

/opmn/bin/opmnctl stopall 
opmnctl: stopping opmn and all managed processes... 
============================================================================== 
opmn id=isunbox28:6200 
    2 of 3 processes stopped. 
@ ias-instance id=iasmid.isunbox28.us.oracle.com 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
------------------------------------------------------------------------------
ias-component/process-type/process-set: 
    OraBPEL/OC4J_BPEL/default_island 
Error 
--> Process (pid=9121) 
    time out while waiting for a managed process to stop 
    Log: 
   
/private/jsmith/midtier/opmn/logs/OraBPEL~OC4J_BPEL~default_island~1 
opmnctl: graceful stop of processes failed, trying 
forceful shutdown...

14.2.2 Undeploying and Redeploying the OC4J_BPEL System Component Through Oracle Enterprise Manager Is Not Supported

If you undeploy the OC4J_BPEL system component through Oracle Enterprise Manager, redeploy it, and then restart OC4J_BPEL, the application cannot be accessed.


Caution:

Oracle recommends that you do not undeploy and redeploy the OC4J_BPEL system component of Oracle BPEL Process Manager.

14.2.3 WSDL Exception Error When Trying to Create a Stub to Use a Web Service

JDeveloper BPEL Designer enables you to automatically create a stub to use a Web service. Once you have generated the stub using the Web Service Stub/Skeleton wizard, you can call the methods (proxies to the web service) in your application. When you attempt to validate/parse the WSDL file, you receive a validation error similar to the following:

WSDL Validation failed with the following exceptions 
@ Schema type not found. QNAME (http://schema.xmlsoap.org/soap/encoding/, 
base64)

Similar problems occur with the WSDL for an asynchronous BPEL process generated by JDeveloper BPEL Designer.

As a workaround, use the RMI client interface for BPEL.


See Also:

Oracle_Home\integration\orabpel\samples\tutorials\102.InvokingProcesses for an example of the RMI client interface

14.2.4 Deploying Oracle JDeveloper-Created Web Services to Oracle BPEL Process Manager OC4J

When Oracle BPEL Server attempts to invoke the OC4J service, the OC4J servlet dispatcher invokes the Oracle BPEL Console WAR file instead of the Web service EAR file. This causes the following error during run time:

BPEL Fault
http://schemas.oracle.com/bpel/extension}bindingFault{summary=Cannot lookup 
BPEL domain. 
The BPEL domain "MyWebService1" cannot be found; the domain may not have 
initialized properly. 
Please verify that the BPEL domain loader has a valid set of initialization 
properties in the application properties file.

There are two possible workarounds to this error:

  • If the Oracle_Home\integration\orabpel\system\config\collaxa-config.xml file includes the following settings:

    - <property id="soap-server-url"> <name>BPEL soap server URL</name> @ <value>http://servername.localdomain:9700</value>

    Replace http://servername.localdomain:9700 with http://servername:9700.

  • Change the endpoint in the Oracle JDeveloper-created Web service to point to localhost instead of servername.

14.3 Modeling and Design Time Issues and Workarounds

This section describes the following issues and workarounds:

14.3.1 No Deployment Time Validation Logic with obant

The obant utility does not validate your BPEL process during deployment. If you want to validate your process during deployment, use JDeveloper BPEL Designer to deploy your process.

14.3.2 Do Not Include Blank Spaces in Directory Paths of JDeveloper BPEL Designer Workspaces

Ensure that the directory path of a workspace does not include any blank spaces. For example, the following is not permitted:

C:\Program Files\projects\myWorkspace\Loanflow

Opening a project from a workspace whose directory path contains blank spaces causes problems. For example, the WSDL files do not display in the WSDL Chooser window when creating a partner link.

14.3.3 Using Annotations in JDeveloper BPEL Designer

Note the following issues when using annotations in JDeveloper BPEL Designer:

  • The Annotations tab in activities of JDeveloper BPEL Designer does not provide a method for changing the order of annotations.

    As a workaround, change the order of annotations in the Source view of the project's BPEL file in JDeveloper BPEL Designer.

  • The otherwise branch in a switch activity does not allow you to create annotations. However, the case branch in a switch activity does provide this functionality.

14.3.4 Internal Compilation Error When Using the CTRL and F9 Keys

If you highlight a partner link in JDeveloper BPEL Designer, and press the Ctrl and F9 keys, you receive the following compilation error in the Log Window:

Internal compilation error, terminated with a fatal exception

As a workaround, select the partner link and the project in the Applications Navigator, then press the Ctrl and F9 keys. You receive no compilation errors in the Log Window.

14.3.5 Inline Dialogs Can Result in Data Loss in Some Cases

The Log Window at the bottom of JDeveloper BPEL Designer displays compilation errors. Assume that you double-click an assign activity error in the Log Window. The assign activity opens, and you correct the error and add additional assign copy rules. If you then right-click the error in the Log Window and select Go to Source, the Source view for your process displays without the assign activity or any of the copy rules you added.

If you perform one of the following tasks, this problem does not display so easily:

  • For all new projects going forward, select Preferences > BPEL Editor from the Tools main menu and uncheck Use inline editors.

  • For the current project only, right-click in JDeveloper BPEL Designer, select Diagram Properties, and uncheck Use inline editors.

14.3.6 Do Not Add or Import XSD Files in a ZIP File

Do not add or import XSD files in a ZIP file into a BPEL project. While JDeveloper BPEL Designer enables you to do this, and opens the XSD in read-only mode, you cannot use it within the BPEL process. JDeveloper BPEL Designer cannot parse the file because the file cannot be physically located. Always extract the XSDs from ZIP files before adding or importing them.

14.3.7 Cannot Select Property Aliases in project_name.wsdl File

You cannot select property aliases in the project_name.wsdl file. To use the property aliases in, for example, adapters.wsdl, manually add them.

14.3.8 Correlation Set Property Aliases Defined in Process WSDL Cause Problems

If you create correlation set property aliases in JDeveloper BPEL Designer, the entries are created in the WSDL file of the BPEL process. However, if the process does not use the default client partner link that refers to this WSDL file (for example, the receive activity is invoked by a partner link of an adapter), the correlation set is not validated at compilation time. This is because Oracle BPEL Server cannot find the WSDL file references in the bpel.xml file.

As a workaround, create the property aliases in a neutral WSDL file and reference this file in the bpel.xml file. The BPEL process uses this file at compilation time (the way properties are defined in separate WSDL files).

14.3.9 BPEL Processes Initiated by Partner Links Referring to Adapters

If the BPEL process is initiated by a partner link that refers to an adapter, you may need to import the process_name.wsdl file inside the partner link's WSDL file. This is so that any references to the message types inside process_name.wsdl can be handled during compilation. This may be required in the following cases:

  • When using correlation sets (the property alias is stored in process_name.wsdl)

  • If any message type defined in process_name.wsdl is referred to in the process_name.bpel file

14.3.10 Changes Made In BPEL Designer Do Not Update Automatically

Updates that you make in the BPEL Validation Browser window may not be automatically reflected in the BPEL process. For example, if you perform the following steps:

  1. Create a partner link, do not specify a WSDL file, and click Apply and OK. This error causes an exclamation point icon to display in the upper left corner of the partnerLink icon.

  2. Click the exclamation point to display the BPEL Validation Browser window.

  3. Double-click the partner link in the BPEL Structure section of this window, correctly complete all fields in the Edit Partner Link window that displays, and apply and save your changes.

  4. Right-click the BPEL Structure window and select Refresh Partner Links. Note that the partner link still displays an error.

As a workaround, close the BPEL Validation Browser window, double-click the partnerLink icon in the Diagram View of JDeveloper BPEL Designer, and click Apply and OK. This action causes the error to disappear.

14.3.11 Extra Carriage Return Added When Using XML Literals

When you assign XML fragments in JDeveloper BPEL Designer, an extra carriage return is added for messages. For example:

<Name>QE_ORDER_NBR
</Name>

As a workaround, you must manually remove any unwanted carriage returns.

14.3.12 readFile Function Displays Only One Argument in XPath Expression Builder Window

The function readFile displays only one argument (fileName) in the XPath Expression Builder window (both in its description in the functions list and when you hold the cursor over this function in the Expression Body window). This function can take three arguments:

ora:readFile('fileName','nxsdTemplate'?,'nxsdRoot'?)

See the XPath Extension Functions appendix of the Oracle BPEL Process Manager Developer's Guide for additional details on this function.

14.3.13 Error When Selecting Message Part Elements Using Inline Schemas of a Project

If you add or update a message type to use a message part element that uses the inline schema of the project (for example, by selecting Project WSDL Files > process_name.wsdl > Inline Schemas > schema > process_nameProcessRequest on the Type Chooser window), your process fails during deployment with a null error.

As a workaround, remove the <import> line from the WSDL file of the process:

<import namespace="http://xmlns.oracle.com/testing" location="testing.wsdl"/>

Save your changes and redeploy the process. Deployment succeeds with no null error.

14.4 Workflow and Worklist Issues and Workarounds

This section describes the following issues and workarounds:

14.4.1 Manually Configuring Oracle BPEL Process Manager on Oracle Application Server to Support Identity Management

If you want to install Oracle BPEL Process Manager on an Oracle Application Server to use an Identity Management and Metadata repository, you must manually configure Oracle Internet Directory as a postinstallation step if the underlying Oracle Application Server is not configured with Identity Management.

If you are using an Oracle Application Server middle tier already configured with Identity Management, do not perform this postinstallation step; configuration is automatically performed during installation.

For example, since the Portal and Wireless middle-tier installation type requires Oracle Internet Directory, configuration is automatically performed during installation of Oracle BPEL Process Manager on this type of middle tier.

Replace the values shown in italics below with ones appropriate to your environment.

  1. Ensure that Oracle_Home\j2ee\OC4J_BPEL\config\jazn.xml contains the following jazn provider element entries:

    <jazn provider="LDAP" location="ldap://host:port" default-realm="us">    <property name="ldap.user" value="cn=orcladmin"/>          
   <property name="ldap.password" value="!welcome1"/> </jazn>

  2. Ensure that Oracle_Home\integration\orabpel\system\services\config\is_config.xml contains the following provider element entries:

    <provider providerType="JAZN" name="oid"> 
   <connection url="ldap://host:port" binddn="cn=orcladmin" password="welcome1"
   encrypted="false"/> </provider>

  3. Ensure that Oracle_Home\j2ee\OC4J_BPEL\application-deployments\hw_services\orion-application.xml contains the following jazn provider element entries:

    <jazn provider="LDAP" location="ldap://host:port" default-realm="us" > 
   <jazn-web-app auth-method="SSO"/> 
</jazn>

  4. If the bpelportlet.ear Web provider is to be deployed through Oracle Enterprise Manager, manually configure Oracle_Home\j2ee\OC4J_BPEL\application-deployments\bpelPortlet\orion-application.xml as follows:

    <jazn provider="LDAP" location="ldap://host:port" default-realm="us" > 
   <jazn-web-app auth-method="SSO"/> 
</jazn>

14.4.2 Default Account Does Not Initially Display in Notification Service Page of Oracle Enterprise Manager

The Notification Service page in Oracle Enterprise Manager 10g Application Server Control Console does not display the default account after you initially install BPEL Process Manager for OracleAS Middle Tier. As a workaround, create a new e-mail account. This causes the default account to appear. If you then delete the new e-mail account, the default account continues to appear.

14.4.3 Always Deploy BPEL Projects with Workflow from JDeveloper BPEL Designer

BPEL projects with workflow must always be deployed from JDeveloper BPEL Designer. Do not use a command line tool such as obant. Command line deployment causes JSP features such as the payload display to not work.

14.4.4 Workflow Names Must Not Include Periods

Do not enter a name that includes periods in the Workflow Name field of the Workflow Pattern window of the Workflow wizard.

14.4.5 Compilation Warning Messages That Can Be Ignored

When you compile a BPEL process with a user task activity, warnings similar to the following appear in the Log Window of JDeveloper BPEL Designer:

Warning(443): 
 [Error ORABPEL-10041]: Trying to assign incompatible types 
 [Description]: in line 443 of
 "C:\apr20\integration\jdev\jdev\mywork\Application1\BPELProcess4\BPELProcess4. 
@ bpel", <from> value type "{http://www.w3.org/2001/XMLSchema}anyType" is not 
@ compatible with <to> value type "{http://www.example.org}book anonymous 
type".

This indicates that an anyType is being assigned to an anonymous type. These warnings can be ignored. Ensure that the return value of the from-spec query is compatible with the to-spec query.

14.4.6 Deleting an Entire User Task Activity

If you want to delete and re-create a user task activity, perform the following steps:

  1. Go into the Diagram View of the BPEL project.

  2. Delete the scope activity and switch activity of the user task activity. These activities were created in the project when you ran the Workflow wizard of the user task activity.

  3. Delete the partner links.

  4. Delete the WSDL/XSD files from the project (recommended, but not required).

  5. Create a new user task activity in which to design the workflow.


See Also:

Section 14.4.7, "Deleting a Scope of a User Task Activity"

14.4.7 Deleting a Scope of a User Task Activity

A workflow scope activity is automatically created when you use the Workflow wizard of the user task activity. If you delete this scope activity, the related config.xml, _form.jsp, and _fields.xml files are not removed. You must manually remove these files. If you do not remove these files, they do not cause any subsequent compilation or deployment errors.

14.4.8 Using the Category List in Oracle BPEL Worklist Application

The Category list of Oracle BPEL Worklist Application enables you to select the category of users, groups, or titles to search (Group, Reportees, and others). Note that the values of previous search results are also displayed. For example, assume that you first search on the Group category and that the results are displayed. If you next search on Reportees, then both the initial search results and the next search results are displayed. This is the expected behavior. Use Check All and Uncheck All to do a bulk select or unselect of the selections. Note that both these buttons only appear when there are two or more users in the selected list.

14.4.9 Sequential Workflow with Automatic Escalation Error with Workflow Wizard

You receive an error if you use the Workflow wizard to create the following type of workflow:

  1. Make the following selections:

    • Sequential Workflow with Automatic Escalation workflow pattern on the Workflow Pattern window

    • List of users on the Assignment policy window

  2. Expand the RoutingWithEscalation scope created by the Workflow wizard.

  3. Double-click the setRoutingPolicy assign activity.

  4. Select the second copy rule and click Edit.

    orcl:create-delimited is underlined in blue, indicating an error.

14.4.10 Getting Task Details with the getWorklistTaskDetails API

When you get a task listing, each task object contains only summary information, and not detailed information such as payload, attachments, history, and so on. To get the details of a task, explicitly call the getWorklistTaskDetails() API inside a loop.

Note that looping while getting task details is a resource intensive action. You typically view details one task at a time. Call this method only for the task in which you are interested. Modify your for loop code as follows (adding one extra line to get the task details):

for (int i=0; i<tasks.size(); i++)
  { 
      IWorklistTask thisTask = (IWorklistTask)tasks.get(i); 
      if ( <condition> ) { // task matches some condition 
          thisTask = wlSrvc.getWorklistTaskDetails(ctx, thisTask.getTaskId()); 
          .... 
          Form form = null; 
          form = PayloadFormGenerator.getMappingForm(thisTask); 
          .... 
      } 
  }

14.4.11 Adding Delays to Task Operations

In some cases, automated clients can perform task operations faster than Oracle BPEL Server. This can potentially result in messages being lost. While this issue is being addressed, the workaround is to add a small delay (about five seconds) between the task operations, as shown in the following example:

client.updateTask(ctx, task);Thread.sleep(5000); // sleep for 5000 millisecondsclient.customTaskOperation(ctx, taskId, "DONE");

14.4.12 Using the Custom Identity Service Provider Plug-in Sample on the Middle Tier

To use the custom identity service provider plug-in sample on the Oracle Application Server middle tier, you must make the following edits to the build.xml file:

  1. Open the Oracle_Home\integration\orabpel\samples\hw\isplugin\db\build.xml file.

  2. Change line 15 from:

    <pathelement location="${classpath}" />

    to:

    <pathelement location="${client.classpath}" />

  3. Change line 67 from:

    <sysproperty key="java.naming.provider.url" value="ormi://${hostname}"/>

    to:

    <sysproperty key="java.naming.provider.url" value="${jndi.url}"/>

14.4.13 Configuring the TaskActionHandler and TaskManager Services to Support SSL

If you configure Oracle BPEL Process Manager for OracleAS Middle Tier with Secure Socket Layer (SSL) support, you must make the following changes to ensure that the TaskActionHandler and TaskManager services load correctly for BPEL processes.

  1. Delete the .bpel_TaskManager_1.0.jar and .bpel_TaskActionHandler_1.0.jar directories under Oracle_Home\integration\orabpel\domains\domain_name\tmp.

  2. Restart Oracle BPEL Server.

These steps recreate the correct service bindings and WSDL files for TaskManager and TaskActionHandler processes and make them available from HTTP/S-based endpoints.


Note:

If your Oracle BPEL Process Manager installation exists as part of a BPEL cluster, you must perform these steps on each BPEL cluster node after you create a BPEL cluster.

14.5 Transformation Issues and Workarounds

This section describes the following issues and workarounds:

14.5.1 SetText Introduces a Newline Character After Transformation

When you use setText on an element or attribute, the value contains a newline character after a transformation. The output is valid XML; however, the newline character has an undesired effect when translating the XML to a native format using Native Format Builder wizard translation or when doing a database INSERT operation.

Use one of the following methods as a workaround (assuming that Oracle is the static or constant value you want to assign to an element):

  • Use the xpath expression advanced function:

    1. Select Advanced Functions > xpath expression from the Component Palette.

    2. Enter Oracle in the XPath Expression field.

      The mapper generates <xsl:value-of select="'Oracle'"/> and the output does not have any spaces.

  • Use the normalize-space string function:

    1. Select String Functions > normalize-space from the Component Palette.

    2. Enter (" Oracle ").

    This removes both leading and trailing spaces from the argument.

14.5.2 Inconsistent Behavior for Functions in JDeveloper BPEL Designer

The following concat function:

concat(bpws:getVariableData('variablename','partname','/PO/ShipTo/First'), 
       bpws:getVariableData('variablename','partname','/PO/ShipTo/Last'))

works as expected. However, a left-trim function such as the following:

orl:left-trim(bpws:getVariableData('variablename','partname','/PO/ShipTo/First'))

does not work.

However, left-trim works correctly in the following scenario:

orl:left-trim(string(bpws:getVariableData('variablename','partname','/PO/ShipTo/
First')))

Both the concat function and left-trim function expect a string value as an argument, but left-trim fails if bpws:getVariableData is passed as an argument. This is because bpws:getVariableData returns a node set and left-trim is unable to handle it. concat can handle a node set and it works.

As a workaround, explicitly chain a string() function to getVariableData before using it with any functions that come from the namespace prefixes xp20 and orcl expecting a string parameter. For functions expecting numbers, you must convert them using the number() function.

14.5.3 get-content-as-string Function Introduces a New Line Character After the Output

The function get-content-as-string incorrectly introduces a newline character in the output. As an example, assume that the source element is:

<ID xmlns="">Mapper1000</ID>

The following XSL code results from using the function get-content-as-string:

<inv:Invoice>
   <ID>
      <xsl:value-of
      select="orcl:get-content-as-string(/po:PurchaseOrder/ID)"/>
   </ID>
</inv:Invoice>

The output is as follows (when using Xalan as the XSL processor):

<ID>&lt;ID&gt;Mapper1000&lt;/ID&gt;&#13;
</ID>

Ideally, it should display without a newline character:

<ID>&lt;ID&gt;Mapper1000&lt;/ID&gt;&#13;</ID>

To achieve this, chain a right-trim function after get-content-as-string.

14.5.4 Target XSD with Choice May Create Invalid Target Instance at Run Time

Note the following source and target XSDs:

Source XSD:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
           xmlns="http://www.example.org" 
           targetNamespace="http://www.example.org" 
            elementFormDefault="qualified" > 

  <xsd:element name="choiceSrc"> 
    <xsd:complexType> 
      <xsd:choice> 
        <xsd:element name="Street" type="xsd:string"/> 
        <xsd:element name="Street1" type="xsd:string"/> 
      </xsd:choice> 
    </xsd:complexType> 
  </xsd:element> 
</xsd:schema>

Target XSD:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
           xmlns="http://www.example.org" 
           targetNamespace="http://www.example.org" 
            elementFormDefault="qualified" > 

  <xsd:element name="choiceTgt"> 
    <xsd:complexType> 
      <xsd:choice> 
        <xsd:element name="Street" type="xsd:string"/> 
        <xsd:element name="Street1" type="xsd:string"/> 
      </xsd:choice> 
    </xsd:complexType> 
  </xsd:element> 
</xsd:schema>

If you do not automatically map the root or manually map source Street to target Street and source Street1 to target Street1, the generated XSL creates an invalid XML instance at run time.

While mapping manually, you must know the schema. If there is a choice, then you must manually use an xsl:if.

14.5.5 Database Functions with JNDI Names Do Not Work Within a MapTest Window

When you use JNDI names for database functions such as query-database(), lookup-table(), or sequence-next-val(), and try to test the map using the MapTest utility, no output is returned. The workaround is to use a JDBC string, instead of a JNDI name.

14.6 XPath Expression Builder Issues and Workarounds

If you use the XPath Building Assistant to create an XPath expression with hyphens (for example, on the Create Copy Rule window of an assign activity), a blue line displays under the hyphenated element and an error message similar to the following appears:

(34) Message part of name xyz-pqr- xyz not found

If the hyphenated elements are nested, the XPath Building Assistant does not allow you to proceed with bpws:getVariableData(). For example:

bpws:getVariableData('ug_in_var','users-and-groups','')

This error is most likely encountered when using the Native Format Builder wizard with the file adapter, where the element name defaults to the hyphenated name of Root-Element.

In addition, if elements have long names that wrap such as root = "publicKeyInfrastructureCertificateAuthorities" and element = "publicKeyInfrastructureCertificateAuthority", XPath expression building also fails. You receive the following error message:

"publicKeyInfrastructureCertificateAuthorities" not found

Instead, click the Expression Builder icon on the Create Copy Rule window to display the XPath Expression Builder window. This window enables you to create an expression that includes hyphens in elements and enables long names to wrap. For example, for hyphens:

bpws:getVariableData('ug_in_var','users-and-groups','/ns2:users-and-groups/ns2 :user-or-group/ns2:name')

14.7 General Adapter and Adapter Partner Link Issues and Workarounds

This section describes the following issues and workarounds:

14.7.1 Case of Property Names in ra.xml and oc4j-ra.xml Files Must Match

The case for all property names must exactly match in the ra.xml and oc4j-ra.xml files. Otherwise, you receive an error message similar to the following during run time in the domain.log file:

Type=Dequeue_ptt, operation=Dequeue 
<2005-03-14 15:20:43,484> <ERROR> <default.collaxa.cube.activation> 
<AdapterFram 
ework::Inbound> Error while performing endpoint Activation: ORABPEL-12510<br> 
Unable to locate the JCA Resource Adapter via WSDL port element jca:address. 
The Adapter Framework is unable to startup the Resource Adapter specified in 
the WSDL jca:address element:
@ {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address:
location='eis/aqSample' 
.
.

For example, if the userName property in the Oracle_Home\integration\orabpel\system\appserver\oc4j\j2ee\home\application-deployments\default\AqAdapter\oc4j-ra.xml file for the AQ adapter uses the following upper and lower case convention:

<config-property name="userName" value="scott"/>

Then this case must match the userName property in the corresponding Oracle_Home\integration\orabpel\system\appserver\oc4j\j2ee\home\connectors\default\AqAdapter\AqAdapter\META-INF\ra.xml file for the AQ adapter.

<config-property-name>userName</config-property-name>

14.7.2 Deleting Header Variables

Assuming that you have created a header variable for an adapter as follows, you cannot subsequently delete that variable through the same receive window. The workaround is to delete the header variable in the BPEL source code.

  1. Create a BPEL project.

  2. Double-click the receive activity.

  3. Click the Adapters tab and define a header variable for the adapter.

14.7.3 Moving to the Next Window in the Adapter Configuration Wizard for Oracle Applications Adapter

If you select the Oracle Applications adapter in the Adapter Configuration wizard and click Next on the Database Objects window, moving to the next window can take some time. This is because a connection is being made to the database. The amount of time that it takes is based on your network connection to the database.

14.7.4 Configuring Multiple Adapters in the Inbound Direction Using Correlation Sets

When multiple adapter-based receive activities in the inbound direction use correlation sets in a process, the wrong property alias query is evaluated and the process fails at run time with the error:

Failed to evaluate correlation query

As a workaround, ensure that the port type and operation values are unique between the two adapter WSDL files. For example, ensure that each adapter WSDL file has a unique operation name.

14.8 Sensor Issues and Workarounds

This section describes the following issue and workaround:

14.8.1 Sensor Integration with Oracle Application Server Integration Business Activity Monitoring

You can create sensor actions in Oracle BPEL Process Manager to publish sensor data as data objects on an Oracle BAM Server. To use this functionality, you must install Oracle BAM 10.1.2.1.0 (also known as Oracle BAM 10.1.2 Patch 1). For details about obtaining Oracle BAM 10.1.2.1.0, see the 10.1.2 Patches section at the following URL:

http://www.oracle.com/technology/products/integration/bam/htdocs/1012_support.html#patches

14.9 Oracle BPEL Console and Oracle BPEL Server Issues and Workarounds

This section describes the following issues and workarounds:

14.9.1 Configuring Mozilla Firefox for Oracle BPEL Console Support

  1. Select New > Navigator Tab from the File main menu in your Mozilla Web browser.

  2. Enter about:config in the URL address field.

  3. Highlight the new address and press Ctrl and then Enter.

  4. Find the signed.applets.codebase_principal_support preference parameter in the Preference Name list.

  5. Double-click this parameter to display the Enter boolean value window.

  6. Enter true in the field and click OK.

14.9.2 Oracle BPEL Console Reports

Note the following issues when using Oracle BPEL Console reports:

  • The End Date field format in the Query section is mm/dd/yy for all languages.

  • Activity sensor reports show only variables of type number (for example, integer, double, decimal, and float). Nonnumeric types are not supported for this release. In addition, data is only shown for activity sensors with Evaluation Time set to All in the Create Activity Sensor window of JDeveloper BPEL Designer.

  • If Albany fonts are not installed, fonts may not display properly for Asian languages in graphs (appear as squares). Albany fonts are automatically installed if you select the proper Asian language during installation.

  • Validation does not work in the Mozilla Firefox browser. For example, if you enter -1 in the Number of Time Intervals field, it is not validated. In addition, process time distribution report bars appear as lines in Mozilla Firefox.

  • When clicking a bar in the performance report graph, the Instances page that appears sometimes does not display the correct list of instances. This is because the service level agreement (SLA) value in decimals is rounded off to the nearest integer. For example, assume there are two instances: one completes in three seconds and the other completes in two seconds. The SLA value is 2.6 seconds. The graph displays one instance in the green portion (indicating that the SLA value was satisfied) and the other in the red portion (indicating that the SLA value was not satisfied). Clicking the red portion does not show any instances. This is because the SLA value is rounded off to three seconds and therefore becomes equal to the completion time of the first instance.

  • The default SLA value is shown in performance reports only when at least one instance of the business process is created.

  • Reports exported to CSV format do not display Japanese or Asian characters. Fault sensor reports exported to CSV format with the fault message having multiple lines are unreadable in Microsoft Excel.

  • When instances are purged, sensor data is not purged. Therefore, activity and fault sensor reports show data even if corresponding instances are not found.

  • The End Hour field is used only for hourly reports, and not daily or weekly reports. For example, if you enter 07/29/05 as the end date, 22:00 as the end hour, Weekly as the time interval, and 3 as the time interval, the report is generated between 07/08/05 and 07/29/05. Instances in any hour (even at 23:00 or 0:00) are also considered even though the end hour is 22:00. The same case exists for daily reports. Only with hourly intervals is report generation stopped at 22:00 hours.

14.9.3 Unable to Delete a Domain or Recreate a Domain with the Same Name

If you are unable to delete a domain or recreate a deleted domain with the same name in Oracle BPEL Admin Console (a message indicates the domain already exists), perform the following steps:

  1. Go to Oracle BPEL Console.

  2. Select the BPEL Processes tab, then select Clear WSDL Cache.

14.9.4 Large Binary Attachments in SOAP Messages Can Fail with Oracle Database Lite

If you use large binary attachment files in SOAP messages with Oracle Database Lite, your BPEL process may not complete processing, which can cause you to run out of system memory. Note that Oracle Database Lite is largely for testing purposes. To use large binary attachment files in SOAP messages, use an Oracle Database or the Oracle Application Server Metadata Repository as your dehydration store.


See Also:

Oracle BPEL Process Manager Installation Guide for information about supported Oracle Databases and Oracle Application Server Metadata Repository

14.9.5 SOAP Attachment DIME Service Callback Does Not Include the Attachment Key

The optSoapShortcut parameter value defaults to true in Oracle BPEL Console. This setting causes BPEL processes with SOAP message binary attachments that use the Direct Internet Message Encapsulation (DIME) protocol to not display their attachment key in the Oracle BPEL Console audit trail for the process instance. This is because the binary attachment file is not saved to the dehydration database. Instead, an HTML file displays in the audit trail. For example:

<PutCompanyInfo>
. . .
. . .
<report href="C:\orabpel\domains\default\tmp\.bpel_DIMERequester_1.0.jar\report.html"/> </PutCompanyInfo>

As a workaround, set optSoapShortcut to false in Oracle BPEL Console. This enables the file to be saved to the dehydration store and the attachment key to display in the audit trail for the instance (instead of the HTML file). Copy and paste the attachment key into the Attachment Key field at the bottom of the audit trail window and click download to save it as a file for viewing. If you do this, note that the File Download message initially prompts you to save the attachment key as a JSP file type. Instead, save the file as an HTML file type.

14.10 Oracle BPEL Portlets Issues and Workarounds

This section describes the following issues and workarounds:

14.10.1 Oracle BPEL Console Report Portlets

Note the following issues when using Oracle BPEL Console report portlets:

  • To use Oracle BPEL Console report portlets, move the uix2.jar file from ORACLE_HOME\integration\orabpel\lib to a different directory (for example, C:\OraMidTier\integration\orabpel\temp-lib) and include this library path in the ORACLE_HOME\j2ee\OC4J_BPEL\config\application.xml file:

    <library path="C:\OraMidTier\integration\orabpel\temp-lib"/>

  • If you want to map portlet parameters with page parameters in Oracle Application Server Portal, the default value for the Oracle BPEL Console report portlet page parameter Time Interval parameter must always be in capital letters (for example, DAILY, WEEKLY, or HOURLY). Mapping portlet parameters with page parameters is described in section "Step 5: Mapping Portlet Parameters with Page Parameters" of the chapter "Oracle BPEL Portlets" of the Oracle BPEL Process Manager Developer's Guide.

14.10.2 Oracle BPEL Worklist Application Portlets

Note the following issues when using Oracle BPEL Worklist Application portlets:

  • After deploying the Oracle BPEL Portlets with dcmctl, you must configure the Web provider with Oracle Internet Directory by ensuring that Oracle_Home\j2ee\OC4J_BPEL\application-deployments\provider\orion-application.xml includes the following settings:

    <jazn provider="LDAP" default-realm="idc"><jazn-web-appauth-method="SSO"/></jazn>

    See the Oracle BPEL Process Manager Developer's Guide for instructions on deploying the Oracle BPEL Portlets with dcmctl.

  • To use the Oracle BPEL Worklist Application portlets, move the uix2.jar file from ORACLE_HOME\integration\orabpel\lib to a different directory (for example, C:\OraMidTier\integration\orabpel\temp-lib) and include this library path in the ORACLE_HOME\j2ee\OC4J_BPEL\config\application.xml file:

    <library path="C:\OraMidTier\integration\orabpel\temp-lib"/>

  • Long strings of more than 360 characters in portlet titles are not handled properly

    When specifying parameter values in the BPEL Worklist Portlet and BPEL Worklist Analysis Portlet, do not use long titles such as URL addresses in the Title field of the Display Customization sections. Long titles can disturb the portlet layout and cause the Personalize link in the upper right corner to not work.

  • Worklist portlet title bar does not display the first time

    When you initially install Oracle Application Server Portal, register the Web provider, create an initial page group, and add the Oracle BPEL Worklist Application portlets to the page group, the title bar does not appear. This means you cannot access the Personalize link that appears in the upper right corner of the title bar. As a workaround, create a second page group and add the Oracle BPEL Worklist Application portlets to the group. This group, and all subsequent groups you create, display the title bar and the Personalize link.

  • All task states display in BPEL Worklist Portlet

    When you select All or Previous in the Category list and Assigned in the Status list of the Task Customization sections of the BPEL Worklist Portlet, you see the state of all tasks, not just those identified as Assigned.

14.11 High Availability Issues and Workarounds

This section describes the following issues and workarounds:

14.11.1 Oracle BPEL Process Manager and Real Application Clusters Databases

You can use a Real Application Clusters (RAC) database as a dehydration store or as a data source for the database adapter with Oracle BPEL Process Manager. However, RAC setup requires manual steps and some patches. Contact Oracle Support Services for assistance.

14.11.2 Disaster Recovery of Oracle BPEL Process Manager

Disaster recovery (DR) functionality is not supported for the 10.1.2.0.2 phase 2 release of Oracle BPEL Process Manager.

14.11.3 Oracle BPEL Process Manager Backup and Recovery with Oracle Enterprise Manager

You must perform the following procedures to correctly back up and recover Oracle BPEL Process Manager through Oracle Enterprise Manager:

  1. Open the Oracle_Home\backup_restore\config\config_IPbpm_files.inp file of your BPEL Process Manager for OracleAS Middle Tier installation.

  2. Substitute the following directory path lines in place of the current lines in this file:

    # Orabpel 
# 
${OH}/integration/orabpel/system/config/collaxa-config.xml
${OH}/integration/orabpel/system/config/* 
${OH}/integration/orabpel/system/logs/* 
${OH}/integration/orabpel/system/xmllib/* 
${OH}/integration/orabpel/domains/*/archive/* 
${OH}/integration/orabpel/domains/*/config/* 
${OH}/integration/orabpel/domains/*/deploy/* 
#${OH}/integration/orabpel/domains/*/logs/*

  3. Modify the Oracle_Home\backup_restore\config\config.inp file by appending config_IPbpm_files.inp to the end of the config_files_list parameter. For example:

    config_files_list=config_ohs_files_nt.inp,...,config_iaspt_files.inp,config_IPbpm_files.inp

14.12 Globalization/Multibyte Character Issues and Workarounds

This section describes the following issues and workarounds:

14.12.1 Encoding Restrictions in E-Mail Subject Field

The encoding for the SUBJECT field in an e-mail message is always set to the language of Oracle BPEL Server, and cannot be changed. If the subject of an e-mail notification is in a different language than that of Oracle BPEL Server, unreadable characters appear in the SUBJECT field of the e-mail client. However, the actual body content of the e-mail message is readable.

14.12.2 UTF-8 Encoding Always Used in XSLT Mapper

In the Test XSL Map window, the source and target XML files are always saved in UTF-8 encoding even if you specify a different encoding in the XML header. This eliminates the risk of incorrectly editing the encoding value in the header.

14.12.3 XML Mapper Must Use the Encoding Specified in the XSL When Reading a File

The XML mapper uses UTF-8 encoding for your operating system to read XSL content from files. Therefore, parsing errors can occur if encoding of XSL content is different from UTF-8.

The workaround is to perform one of the following:

  1. Save the old map file as a different map file in UTF-8 encoding and open it in the mapper.

  2. Open the old map file, and change the encoding to UTF-8 in the source view. After that, you can switch to the Design view.

14.12.4 Multibyte Project Name Causes WSDL File to Be Invalid

If you create a BPEL project with a multibyte name, the automatically generated WSDL file name and its referenced namespace URL do not correctly process, which causes the BPEL process to be invalid.

As a workaround, use the ASCII character set for process file names and namespaces.

14.12.5 Ruler Scale Is Not Multibyte-compliant in the Native Format Builder Wizard

If you select the fixed length file type in the Native Format Builder wizard, the ruler on the Field Lengths window that enables you to specify field length for each record is not multibyte-compliant.

14.12.6 Encoding Issue for ora:readFile

The extended XPath function ora:readFile requires a file directory path as the first parameter. These functions read the specified file by using OS-default encoding. This is not an issue if the specified file is in the local file system. However, if the specified path is a URL, the target file is not always encoded in OS-default encoding.

14.12.7 Data Consumed as a Text Message May Have Problems

When you configure the JMS adapter in the inbound direction to consume text messages, the data received may be unusable. To avoid this issue, you can use the XSD schema created by the Native Format Builder wizard and select UTF-8 as the character set when prompted.

If you use standard XSD, you expect that the text message in the JMS queue/topic is an XML string. It can contain an XML header string with the encoding attribute, but to avoid the above-mentioned problem, keep enqueuing it without the XML header or with "encoding=UTF-8".

If the JMS message is a bytes message, this problem does not occur.

14.13 JBoss Issues and Workarounds

This section describes the following issues and workarounds:

14.13.1 Cannot Migrate From Oracle BPEL Process Manager 10.1.2.0.0 to 10.1.2.0.2 with JBoss Application Server

You cannot currently migrate from the 10.1.2.0.0 release of Oracle BPEL Process Manager with the JBoss Application Server to this 10.1.2.0.2 release. Instead, install a completely new version of Oracle BPEL Process Manager release 10.1.2.0.2 with the JBoss Application Server.


See Also:

Oracle BPEL Process Manager Installation Guide for Oracle BPEL Process Manager release 10.1.2.0.2 installation instructions with the JBoss Application Server

14.13.2 Increasing Connection Pool Settings for Oracle BPEL Process Manager

If Oracle BPEL Server displays a "cannot fetch datasource" error, increase the maximum number of connections value in the database connection pool. For example:

<max-pool-size>30</max-pool-size>

Increase this parameter value in the following locations:

  • The <local-tx-datasource> and <no-tx-datasource> sections of oracle-ds.xml

  • The <local-tx-datasource> section of oracle-sample-bpel-ds.xml

These files are located in the Oracle_Home\system\appserver\jboss\server\default\deploy directory.

If you are using Oracle Database Lite, do not set the max-pool-size parameter value higher than 25. This is a limitation of Oracle Database Lite. If you need a higher value, use an Oracle Database.


See Also:

Oracle BPEL Process Manager Installation Guide for details about using an Oracle Database

14.13.3 OracleAS Integration B2B and OracleAS Integration InterConnect Interoperability with Oracle BPEL Process Manager is Not Supported

You cannot configure the following components on the JBoss Application Server to communicate with Oracle BPEL Process Manager release 10.1.2.0.2:

  • OracleAS Integration B2B

  • OracleAS Integration InterConnect

14.13.4 Oracle Workflow Bridge is Not Supported

Oracle Workflow Bridge cannot be used with Oracle BPEL Process Manager and the JBoss Application Server.

14.13.5 Identity Service Plug-in for Database Providers Sample is Not Supported

The identity service plug-in for database providers sample available in Oracle_Home\integration\orabpel\samples\hw\isplugin\db does not currently work with the JBoss Application Server.

14.14 BEA WebLogic Issues and Workarounds

This section describes the following issues and workarounds:

14.14.1 Unsupported Upgrade and Migration Scenarios

The following upgrade and migration scenarios are not supported. Instead, install a completely new version of Oracle BPEL Process Manager release 10.1.2.0.2 with the BEA WebLogic Application Server.

  • Oracle BPEL Process Manager 10.1.2.0.2 is only certified on BEA WebLogic Application Server 8.1.5. Therefore, you cannot currently upgrade from the 10.1.2.0.0 release of Oracle BPEL Process Manager on BEA WebLogic Application Server release 8.1.4 to the 10.1.2.0.2 release of Oracle BPEL Process Manager on BEA WebLogic Application Server release 8.1.5.

  • You cannot currently migrate from the 10.1.2.0.0 release of Oracle BPEL Process Manager with the BEA WebLogic Application Server to this 10.1.2.0.2 release.


See Also:

Oracle BPEL Process Manager Installation Guide for Oracle BPEL Process Manager release 10.1.2.0.2 installation instructions with the BEA WebLogic Application Server

14.14.2 owf.ear File Not Included with Installation Software

The owf.ear file that is used to install Oracle Workflow Bridge on the host on which Oracle BPEL Process Manager is installed is not included with the BEA WebLogic Application Server and Oracle BPEL Process Manager installation software.

14.14.3 Identity Service Plug-in for Database Providers Sample is Not Supported

The identity service plug-in for database providers sample available in Oracle_Home\integration\orabpel\samples\hw\isplugin\db does not currently work with the BEA WebLogic Application Server.

14.14.4 OracleAS Integration B2B and OracleAS Integration InterConnect Interoperability with Oracle BPEL Process Manager is Not Supported

You cannot configure the following components on the BEA WebLogic Application Server to communicate with Oracle BPEL Process Manager release 10.1.2.0.2:

  • OracleAS Integration B2B

  • OracleAS Integration InterConnect

14.15 Microsoft SQL Server Issues and Workarounds

This section describes the following issues and workarounds:

14.15.1 Oracle BPEL Process Manager for OracleAS Middle Tier Installations and Sensors

If you install Oracle BPEL Process Manager for OracleAS Middle Tier, ensure that you manually add the bc4jdomgnrc.jar line above the BC4J/lib line in the Oracle_Home\j2ee\OC4J_BPEL\config\application.xml file:

<library path="../../../BC4J/jlib/bc4jdomgnrc.jar"/>
<library path="../../../BC4J/lib"/>

This action ensures that any sensors in your process correctly load when you deploy the process to Oracle BPEL Server.

14.15.2 SOAP with Binary Attachments Not Supported

Using SOAP with binary attachments is not supported on Microsoft SQL Server. For example, the DIME samples under Oracle_Home\integration\orabpel\samples\demos\Attachment cannot complete successfully. This is because binary large objects (BLOB) are not supported in Microsoft SQL Server.

14.15.3 Reports Feature of Oracle BPEL Console and BPEL Reports Portlets Not Currently Working

The Reports link for a deployed BPEL process in the BPEL Processes tab of Oracle BPEL Console is not currently enabled with Microsoft SQL Server. In addition, the BPEL Reports Portlets accessible from Oracle Application Server Portal cannot be used with Microsoft SQL Server.

14.15.4 Identity Service Plug-in for Database Providers Sample Not Currently Working

The identity service plug-in for database providers sample available in Oracle_Home\integration\orabpel\samples\hw\isplugin\db does not currently work with Microsoft SQL Server.

14.16 Oracle BPEL Process Manager Samples Issues and Workarounds

The Oracle_Home\integration\orabpel\samples\demos\OWFBridge sample includes an Oracle Workflow process named WFDemo. This process is part of the Oracle Workflow sample and must be loaded into Oracle Workflow before you run this sample. Otherwise, you receive Oracle BPEL Console errors if you try to build the sample.


See Also:

Oracle BPEL Process Manager Developer's Guide for additional Oracle Workflow Bridge details, including information on adding a data source definition

14.17 Documentation Errata

This section describes known errors in the documentation. It includes the following topics:

14.17.1 Oracle Application Server Administrator's Guide

Chapter: 19, "Introduction to Backup and Recovery"

Header: "Oracle Application Server Component Backup Input Files"

Pages: 19-5 and 19-6

Table 19-1 on page 19-5 lists the Oracle BPEL Process Manager backup input file name as config_ip_files.inp. The correct name is config_IPbpm_files.inp.

In addition, the following line on page 19-6 can be ignored:

Component Name column: Business Integration Process Manager

Backup Input File column: config_IPbpm_files.inp

14.17.2 JMS Performance Patch Mentioned in Oracle BPEL Process Manager Developer's Guide

Appendix: A, "Troubleshooting and Workarounds"

Header: "Poor JMS Performance When Creating or Destroying Connections"

Page: A-2

The solution section states to use the rollup patch included on the software CD and to see the readme file. This solution can be ignored.

14.17.3 Reassign Component Definition in Oracle BPEL Process Manager Developer's Guide

Chapter: 17, "Worklist Application"

Header: "Overview of Worklist Application Concepts"

Page: 17-3

The following paragraph:

Reassign — A manager can delegate a task to reportees. Similarly, the process owner or a user with BPMWorkflowReassign privileges can delegate a specific task to any other person in the organization.

should read as follows (without mention of the process owner):

Reassign — A manager can delegate a task to reportees. Similarly, a user with BPMWorkflowReassign privileges can delegate a specific task to any other person in the organization.

  Previous
Previous 		 Next
Next
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents