Oracle BPEL Process Manager Release Notes - 10.1.2.0.0 ... · with the RDBMS 10.1.0.4 Patch Set"...

Oracle BPEL Process Manager Release Notes - 10.1.2.0.0 February 3, 2006 1-1

1Oracle BPEL Process Manager Release

Notes - 10.1.2.0.0 February 3, 2006

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

■ Section 1.1, "Installation Issues and Workarounds"

■ Section 1.2, "General Issues and Workarounds"

■ Section 1.3, "Modeling and Design Time Issues and Workarounds"

■ Section 1.4, "Workflow and Worklist Issues and Workarounds"

■ Section 1.5, "Transformation Issues and Workarounds"

■ Section 1.6, "XPath Expression Builder Issues and Workarounds"

■ Section 1.7, "Oracle Application Server Adapter for Files/FTP Issues and Workarounds"

■ Section 1.8, "Oracle Application Server Adapter for Databases Issues and Workarounds"

■ Section 1.9, "Oracle Application Server Adapter for Advanced Queuing Issues and Workarounds"

■ Section 1.10, "Oracle Application Server Adapter for JMS Issues and Workarounds"

■ Section 1.11, "General Adapter and Adapter Partner Link Issues and Workarounds"

■ Section 1.12, "Globalization/Multibyte Character Issues and Workarounds"

■ Section 1.13, "Oracle BPEL Process Manager with BEA WebLogic"

■ Section 1.14, "Oracle BPEL Process Manager with JBoss"

■ Section 1.15, "Documentation Errata"

1.1 Installation Issues and WorkaroundsThis section describes the following issues and workarounds:

■ Section 1.1.1, "Installing Oracle BPEL Process Manager for OracleAS Middle Tier with Oracle Portal and Wireless"

■ Section 1.1.2, "Installing Oracle BPEL Process Manager for OracleAS Middle Tier with the RDBMS 10.1.0.4 Patch Set"

■ Section 1.1.3, "Installing Oracle Java Virtual Machine"

Installation Issues and Workarounds

1-2 Oracle BPEL Process Manager Release Notes

■ Section 1.1.4, "Running Integration Repository Creation Assistant on an Oracle10g Release 2 (10.2) Database"

1.1.1 Installing Oracle BPEL Process Manager for OracleAS Middle Tier with Oracle Portal and Wireless

If you want to install the Oracle BPEL Process Manager for OracleAS Middle Tier installation type into an Oracle home directory that includes the Portal and Wireless middle tier type, ensure that Oracle Internet Directory is already running. Otherwise, Oracle BPEL Process Manager for OracleAS Middle Tier does not install successfully.

1.1.2 Installing Oracle BPEL Process Manager for OracleAS Middle Tier with the RDBMS 10.1.0.4 Patch Set

If you want to install the Oracle BPEL Process Manager for OracleAS Middle Tier installation type on an Oracle Application Server middle tier on which you previously installed the RDBMS 10.1.0.4 patch set, you must first apply ARU patch 7485905. This patch is available at http://metalink.oracle.com.

1.1.3 Installing Oracle Java Virtual MachineIf you want to use Oracle JDeveloper’s CodeCoach and Profiling features on Windows or Linux, you must install Oracle Client Java Virtual Machine (OJVM).

The InstallOJVM script installs OJVM in the specified JDK directory. Once installed, OJVM is the default virtual machine for every new project created in JDeveloper BPEL Designer for the specified JDK.

■ On Windows:

1. Go to Oracle_Home\integration\jdev\jdev\bin.

2. Run InstallOJVM.bat, and specify the JDK root directory. For example:

InstallOJVM C:\OraBPELPM\integration\jdev\jdk

■ On Linux:

1. Go to $ORACLE_HOME/integration/jdev/ojvm_linux_x86.

2. Run installOJVM, and specify the JDK root directory. For example:

InstallOJVM $/OraBPELPM/integration/jdev/jdk

1.1.4 Running Integration Repository Creation Assistant on an Oracle10g Release 2 (10.2) Database

If you want to run the Integration Repository Creation Assistant (IRCA) on an Oracle10g Release 2 (10.2) database, you must manually change the last line in the IRCA’s integration\bpelpm\admin\sql\bpmuser.sql file from:

grant connect, resource to &bpm_user;

to:

grant connect, resource, create view to &bpm_user;

Run the IRCA after making this change. Not performing this change causes the IRCA to fail to create the required views for the orabpel user and the IRCA log file to display the following message:

General Issues and Workarounds


ERROR at line 1: ORA-01031: insufficient privileges create or replace view admin_list_wi * . . .

1.2 General Issues and WorkaroundsThis section describes the following issues and workarounds:

■ Section 1.2.1, "Location of the Most Up-to-Data Samples"

■ Section 1.2.2, "Editing Project Files"

■ Section 1.2.3, "Correlation Sets for Multiple Receives"

■ Section 1.2.4, "Recommended Method for Correcting Validation Errors in Complex Processes"

■ Section 1.2.5, "Cannot Undeploy a Process from Oracle BPEL Console"

■ Section 1.2.6, "Clearing the WSDL Cache When Changing the Default Process"

■ Section 1.2.7, "Handling Long-Running Processes"

■ Section 1.2.8, "XML Validation Failure with Notification and Workflow"

■ Section 1.2.9, "Deploying Oracle JDeveloper-Created Web Services to Oracle BPEL Process Manager OC4J"

■ Section 1.2.10, "Error with opmnctl stopall to Ignore"

■ Section 1.2.11, "Undeploying and Redeploying the OC4J_BPEL System Component Through Oracle Enterprise Manager Is Not Supported"

■ Section 1.2.12, "Number of Events Processed in Oracle Enterprise Manager"

■ Section 1.2.13, "Flow and Audit Links Do Not Show Adapter Header Variables Or States"

■ Section 1.2.14, "JDeveloper BPEL Designer Limitations on Solaris and Linux"

■ Section 1.2.15, "WSDL Exception Error When Trying to Create a Stub to Use a Web Service"

1.2.1 Location of the Most Up-to-Data SamplesSee http://www.oracle.com/technology/bpel for the most up-to-date tutorials and demonstrations.

1.2.2 Editing Project FilesNote the following issues when editing the bpel.xml file, WSDL file, and BPEL files:

■ The bpel.xml file content is only read into memory when the file is opened. Therefore, if you change the content of bpel.xml after the file is opened, the changes are not made in memory. After changing the content of the BPEL file, close and reopen the file for the changes to take effect.

■ Do not edit the bpel.xml file through a combination of JDeveloper BPEL Designer and a text editor such as Notepad or Wordpad. Use only a single editing environment such as JDeveloper BPEL Designer.



■ Do not edit the bpel.xml file, BPEL files, and WSDL files while changing the design of the process. If you want to edit a file:

1. Ensure that the BPEL files are not being edited in JDeveloper BPEL Designer. If they are being edited (that is, a tab for that file is visible), close it and save changes as needed.

2. Edit the required file and save the changes.

1.2.3 Correlation Sets for Multiple ReceivesThe following must be added manually if there is more than one receive for a partner link configured for adapters and a CorrelationSet is used:

<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent"> <property name="wsdlLocation">Dequeuer1.wsdl</property> <property name="portType">Dequeue1_ptt</property> <property name="operation">Dequeue1</property> <property name="partnerLinkName">InboundPartnerLink1</property> <property name="roleName">Dequeue_role1</property> </activationAgent>

1.2.4 Recommended Method for Correcting Validation Errors in Complex ProcessesIf you have complex processes with validation errors (for example, assign activities with multiple copy rules that are embedded inside several scopes), the recommended method for accessing and correcting these errors is as follows:

1. Right-click the error and select Go to Source to access the source code that errored.

2. Review the source code to identify the error.

3. Click Diagram View and go to the graphical view of the error.

4. Make corrections in the graphical view.

1.2.5 Cannot Undeploy a Process from Oracle BPEL ConsoleIf you cannot successfully undeploy a BPEL process from the Manage window of the BPEL Processes tab of Oracle BPEL Console, then manually delete its JAR files. For example, if the process is named OrderBooking, perform the following steps:

1. Delete the following files and directories:

■ Oracle_Home\integration\orabpel\domains\domain_name\deploy\bpel_OrderBooking_*.jar files (for example, bpel_OrderBooking_1.0.jar, bpel_OrderBooking_2.0.jar, and so on)

■ Oracle_Home\integration\orabpel\domains\domain_name/tmp\.bpel_OrderBooking_*.jar directories (for example, bpel_OrderBooking_1.0.jar, bpel_OrderBooking_2.0.jar, and so on)

2. Restart Oracle BPEL Server.



1.2.6 Clearing the WSDL Cache When Changing the Default Process

If you deploy multiple versions of the same BPEL process, the first version of the process is the default version. If you change the default version of the process from Oracle BPEL Console, then you must also clear the WSDL cache by selecting Clear WSDL Cache from the BPEL Processes tab.

For example, assume you compile and deploy versions 1.0 (the default version) and 2.0 of the A.bpel process. You then invoke the B.bpel process to call the A.bpel version 1.0 default process. If you retire A.bpel version 1.0, and change the default process to A.bpel version 2.0, then invoke B.bpel, it again calls the A.bpel version 1.0 and fails because of the WSDL cache. If you clear the WSDL cache, and invoke B.bpel again, it successfully calls A.bpel version 2.0.

1.2.7 Handling Long-Running ProcessesWhen a process has long-standing activity and the server time-out value is set to less than the time that has elapsed since the previous dehydration point has been reached, you can see exception messages similar to the following in the Oracle BPEL Server window.

Message handle error. An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeIns tanceMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is: java.lang.Exception: No Exception - originate from:

As a workaround, increase the transaction-config timeout value in the Oracle_Home\integration\orabpel\system\appserver\oc4j\j2ee\home\server.xml file.

<transaction-config timeout="30000"/>

1.2.8 XML Validation Failure with Notification and WorkflowIf you set the validateXML property to true (the default is false) on the Manage BPEL Domain window of Oracle BPEL Console, each message exchanged with each of the Web services is validated against its schema. However, workflow and notification services fail during XML validity checks at run time. This is because the BPEL variables exchanged with the workflow and notification services are not completely initialized in the BPEL process. Part of the initialization happens in the service itself.

Note: This issue was fixed in Patch 1, which was released on July 12, 2005. For instructions on downloading and applying Patch 1, visit the following URL:

http://www.oracle.com/technology/bpel

See Also: Oracle Application Server Integration Installation Guide for a detailed description on setting this parameter



1.2.9 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 Faulthttp://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.

1.2.10 Error with opmnctl stopall to IgnoreThe 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...

Modeling and Design Time Issues and Workarounds


1.2.11 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.

1.2.12 Number of Events Processed in Oracle Enterprise ManagerThe Number of events processed section of the Performance page in Oracle Enterprise Manager 10g Application Server Control Console only identifies successfully processed events, and does not include the number of events errored for both inbound and outbound adapters.

1.2.13 Flow and Audit Links Do Not Show Adapter Header Variables Or StatesThe Flow and Audit links under the Instances tab of Oracle BPEL Console do not provide details about the actions or states of any header variables you defined during design time. As a workaround, use the Debug link to view header variable details.

1.2.14 JDeveloper BPEL Designer Limitations on Solaris and LinuxRight-clicking the mouse button in the Diagram View window and Structure window of JDeveloper BPEL Designer does not display the menu on Solaris or Linux. JDeveloper BPEL Designer is not officially supported on Solaris.

1.2.15 WSDL Exception Error When Trying to Create a Stub to Use a Web ServiceJDeveloper 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.

1.3 Modeling and Design Time Issues and Workarounds This section describes the following issues and workarounds:

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

See Also: Oracle Application Server Integration Installation Guide for a list of supported Windows operating systems

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



■ Section 1.3.1, "Internal Compilation Error When Using the CTRL and F9 Keys"

■ Section 1.3.2, "Inline Dialogs Can Result in Data Loss in Some Cases"

■ Section 1.3.3, "Cannot Select Property Aliases in project_name.wsdl File"

■ Section 1.3.4, "Correlation on an OnMessage Branch Causes Compiler Error"

■ Section 1.3.5, "Change of Order for bpelx:append Inside an Assign Activity"

■ Section 1.3.6, "Empty BPEL Processes and Imported Schemas"

■ Section 1.3.7, "Correlation Set Property Aliases Defined in Process WSDL Cause Problems"

■ Section 1.3.8, "Changes Made In BPEL Designer Do Not Update Automatically"

■ Section 1.3.9, "readFile() XPath Function Argument"

■ Section 1.3.10, "Do Not Create Multiple Projects of the Same Name, but with Different Capitalization"

■ Section 1.3.11, "Importing Two XSD Files with the Same Name Is Not Supported"

■ Section 1.3.12, "Turn Off Invalid Settings Message for Newly Created Activities"

■ Section 1.3.13, "The ora:mergeChildNodes Function Is Not Supported at Run Time"

■ Section 1.3.14, "Must Enclose the Operation Name with RPC-Style WSDL Messages"

■ Section 1.3.15, "SOAP-Encoded Arrays Are Not Supported"

■ Section 1.3.16, "Class Files Directory Location for Java Embedding Activity"

1.3.1 Internal Compilation Error When Using the CTRL and F9 KeysIf 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.

1.3.2 Inline Dialogs Can Result in Data Loss in Some CasesThe 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.



1.3.3 Cannot Select Property Aliases in project_name.wsdl FileYou cannot select property aliases in the project_name.wsdl file. To use the property aliases in, for example, adapters.wsdl, manually add them.

1.3.4 Correlation on an OnMessage Branch Causes Compiler ErrorIf you add correlations to an OnMessage branch of a Pick activity in JDeveloper BPEL Designer, the correlations syntax is placed after the assign activity syntax. The correlation syntax must go before the assign activity.

As a workaround, perform the following steps:

1. Create a correlation set in JDeveloper BPEL Designer.

2. Assign this to the OnMessage branch.

3. Complete the remaining design tasks.

4. Before making or deploying the BPEL process, move the correlation syntax before the assign activity in the BPEL source code.

1.3.5 Change of Order for bpelx:append Inside an Assign ActivityIf an assign activity contains more than one bpelx:append, it must be split into two assign activities. Otherwise, JDeveloper BPEL Designer moves the bpelx:append to the end of the list each time, which can cause problems. As a workaround, move it manually.

1.3.6 Empty BPEL Processes and Imported SchemasIf you create an empty project (which is common with adapter endpoint projects) and import an XSD file, you cannot deploy the project without editing the project_name.bpel file.

As a workaround, perform the following steps:

1. Create an asynchronous project.

2. Leave the client partner link alone (it enables you to import XSDs because it refers to the process_name.wsdl file that has the necessary imports).

3. Edit the receiveInput receive activity of the client partner link and have it point to the new adapter inbound endpoint in the Partner Link field.

1.3.7 Correlation Set Property Aliases Defined in Process WSDL Cause ProblemsIf 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).



1.3.8 Changes Made In BPEL Designer Do Not Update AutomaticallyUpdates 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.

1.3.9 readFile() XPath Function ArgumentThe argument fileName for this function can also be an HTTP URL and not just a file name.

1.3.10 Do Not Create Multiple Projects of the Same Name, but with Different Capitalization

Do not create multiple projects of the same name, but with different capitalization in JDeveloper BPEL Designer (for example, Test1 and test1). This causes problems. Always use completely unique names when creating BPEL projects.

1.3.11 Importing Two XSD Files with the Same Name Is Not SupportedDo not import two schema files with the same name into a project. Ensure that the files have unique names.

1.3.12 Turn Off Invalid Settings Message for Newly Created ActivitiesAs you create and open activities such as scope, assign, and others for the first time, the message Invalid Settings appears at the top of the activity window. This is because you have not yet entered details. You can ignore this message. Appendix B, "JDeveloper BPEL Designer Activities" of the Oracle BPEL Process Manager Developer’s Guide describes how to disable this message for a specific BPEL process. To disable this message for all new projects going forward, perform the following steps:

1. Select Preferences > BPEL Editor from the Tools main menu in JDeveloper BPEL Designer.

2. Deselect the Validate process when loading diagram option.

3. Click OK.

Any projects created after this point do not display the Invalid Settings message.



1.3.13 The ora:mergeChildNodes Function Is Not Supported at Run TimeDo not use the ora:mergeChildNodes function during design time, because it is not supported during run time.

1.3.14 Must Enclose the Operation Name with RPC-Style WSDL MessagesIf you use RPC-style messaging, you must enclose the input XML message with an operation name (in the following example, process):

<process xmlns="http://xmlns.oracle.com/MessageParts_referingToComplexTypes"> <payload xmlns="" xmlns:client="http://xmlns.oracle.com/MessageParts_referingToComplexTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="client:TestInput"> <input xmlns="http://xmlns.oracle.com/MessagePartsreferingToComplexTypes">yoo</input > <input1 xmlns="http://xmlns.oracle.com/MessageParts_referingToComplexTypes">boo</input 1> <input2 xmlns="http://xmlns.oracle.com/MessageParts_referingToComplexTypes">woo</input 2> <input3 xmlns="http://xmlns.oracle.com/MessageParts_referingToComplexTypes">foo</input 3> <input4 xmlns="http://xmlns.oracle.com/MessageParts_referingToComplexTypes">goo</input 4> </payload> </process>

If you want to verify the correctness of the XML file, set the validateXML property to true on the Manage BPEL Domain window of Oracle BPEL Console.

1.3.15 SOAP-Encoded Arrays Are Not SupportedOracle BPEL Process Manager does not support SOAP-encoded arrays (soapenc:arrayType).

Use one of the following workarounds:

■ Apache Axis supports document-literal style services. This means you can change the service to not use soapenc:arrayType.

■ A wrapper can be placed around the service (also using Apache Axis) so that the BPEL process talks to the document literal wrapper service, which in turn calls the underlying service with soapenc:arrayType.

■ Call a service with soapenc:arrayType from BPEL, but construct the XML message more manually in the BPEL code. This enables you to avoid changing or wrapping the service. However, each time you want to call that service from BPEL, you must take extra steps.

See Also: Section 1.3.2, "Inline Dialogs Can Result in Data Loss in Some Cases" on page 1-8 for additional details

See Also: Section 1.2.8, "XML Validation Failure with Notification and Workflow" for additional issues on setting validateXML to true

1.3.16 Class Files Directory Location for Java Embedding ActivityThe "Java Embedding Activity" section of the "JDeveloper BPEL Designer Activities" appendix of the Oracle BPEL Process Manager Developer’s Guide describes where to add JAR files during design time to ensure that your project compiles properly. In addition, place the corresponding class files in the Oracle_Home\integration\orabpel\system\classes directory.

Perform the following Java JAR file configuration steps to ensure correct run time behavior. This example describes the configuration steps for Windows operating systems. Perform similar steps for UNIX operating systems.

1. Add the files into the BPEL client bpelc CLASSPATH:

a. Open Oracle_Home\integration\orabpel\bin\obsetenv.bat. For UNIX operating systems, the file is named obsetenv.sh.

b. Edit the file as follows:

@REM set MY_CLASSES_DIR=%CLASSPATH%set MY_CLASSES_DIR=%OB_HOME%\system\classesset MY_CLASSPATH=%MY_CLASSES_DIR%;your_jar_files

2. Add the files into the Oracle BPEL Server bpelc CLASSPATH in either of two ways:

a. Open Oracle_Home\integration\orabpel\domains\default\config\domain.xml (if the default domain is being used).


<property id="bpelcClasspath"> <name>BPEL process compiler classpath</name> <value>your_jar_files;...</value> <comment>...</comment></property>

c. Restart Oracle BPEL Server.

or

a. Go to Manage BPEL Domain > Configuration on Oracle BPEL Console.

b. Go to the bpelcClasspath property.

c. Enter your_jar_files; in the Value field.

d. Click Apply.

e. Restart Oracle BPEL Server.

3. Add the files into the Oracle Application Server CLASSPATH:

a. Open Oracle_Home\integration\orabpel\system\appserver\oc4j\j2ee\home\config\application.xml.


 <library path="your_jar_files"/> <library path="C:\OraBPELPM_1\integration\orabpel\system\classes"/>

Workflow and Worklist Issues and Workarounds


1.4 Workflow and Worklist Issues and Workarounds This section describes the following issues and workarounds:

■ Section 1.4.1, "Extending Existing Workflows"

■ Section 1.4.2, "Assigning Parallel Tasks to Each User in Multiple Groups"

■ Section 1.4.3, "Compilation Warning Messages That Can Be Ignored"

■ Section 1.4.4, "Deleting an Entire User Task Activity"

■ Section 1.4.5, "Deleting a Scope of a User Task Activity"

■ Section 1.4.6, "Nonexisting Task Payload Elements Cannot Be Updated From the Worklist Application"

■ Section 1.4.7, "Using XSL Style Sheets Generated with External Utilities"

■ Section 1.4.8, "Using the Category List in Oracle BPEL Worklist Application"

■ Section 1.4.9, "Errored Tasks Do Not Display in the Worklist Application"

■ Section 1.4.10, "Sequential Workflow with Automatic Escalation Error with Workflow Wizard"

■ Section 1.4.11, "Long BPEL Process and Workflow Names on Windows Operating Systems"

1.4.1 Extending Existing WorkflowsIf you want to extend the functionality of a previously created workflow, the first workflow from which others are extended must have a union of all the conclusions of all the workflows.

For example, if the first workflow has conclusions of yes and no, the second workflow has conclusions of yes and maybe, and the third workflow has conclusions of no and let’s see, then design the first workflow with conclusions of yes, no, maybe, and let’s see.

1.4.2 Assigning Parallel Tasks to Each User in Multiple GroupsYou cannot use a concat function to assign a parallel task to each user in a group. Instead, use the ora:getUsersInGroup(groupName) extension function to perform this task (for example, assign the parallel task to users fkafka, szweig, and mmitch in group LoanAnalyticGroup). This extension function gets the users in a group as a node-set. In this case, specify the XPath expression as follows in the Dynamic assignment using XPath expression field in the Assignees window of the Workflow wizard:

ora:getUsersInGroup('LoanAnalyticGroup')

The use of the ora:getUsersInGroup function is described on Oracle BPEL Console under Manage BPEL Domain > XPath Library.

Oracle BPEL Process Manager does not provide built-in functionality for explicitly assigning a task to each user in multiple groups. For example, if group LoanAgentRole has users jcooper, jstein, and wfaulk and group Supervisor has users jlondon and cdickens, then creating a parallel task to assign to users jcooper, jstein, wfaulk, jlondon, and cdickens is not directly supported. As a workaround, you can write your own bpelx:exec (Java inside BPEL) to create a node-set that contains all the users from both groups and assign the parallel task to that node-set.



1.4.3 Compilation Warning Messages That Can Be IgnoredWhen 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.

1.4.4 Deleting an Entire User Task ActivityIf 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.

1.4.5 Deleting a Scope of a User Task ActivityA 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.

1.4.6 Nonexisting Task Payload Elements Cannot Be Updated From the Worklist Application

Only existing elements of the task payload can be updated from the Oracle BPEL Worklist Application. Nonexisting elements cannot be updated. To update all elements of the payload, ensure that the task payload is completely initialized before invoking the TaskManager service. For example, if a payload named loanOffer (from LoanFlow.xsd) includes the following elements:

<loanOffer> <providerName>Bank of America</SSN> <selected>false</selected> <approved>false</approved> <APR>100.0</APR> </loanOffer>

then all the child elements of loanOffer are updatable. However, if the payload includes only the following elements:

See Also: Section 1.4.5, "Deleting a Scope of a User Task Activity"



<loanOffer> <providerName>Bank of America</SSN> <selected>false</selected> </loanOffer>

then <approved> and <APR> cannot be updated.

1.4.7 Using XSL Style Sheets Generated with External UtilitiesYou can select an XSL style sheet as the format in which to display the payload data of a task. This selection is made on the Task Details page of the Workflow wizard. If you select to use an XSL style sheet generated by an external utility, you must make the following modifications:

■ Add namespaces relating to the task and its requirements to the generated XSL.

■ Ensure that all XPath queries start with the task payload in place of the root of the XML.

1.4.8 Using the Category List in Oracle BPEL Worklist ApplicationThe 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.

1.4.9 Errored Tasks Do Not Display in the Worklist ApplicationErrored tasks are not assigned to a specific user. They are only assigned to the bpeladmin user. If you are a user other than bpeladmin and want to see these errors, select All in the Category list and Errored or Any in the Status list of the Oracle BPEL Worklist Application.

1.4.10 Sequential Workflow with Automatic Escalation Error with Workflow WizardYou 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.

See Also: Oracle BPEL Process Manager Order Booking Tutorial for an example of using an external style sheet to display tasks

Transformation Issues and Workarounds


1.4.11 Long BPEL Process and Workflow Names on Windows Operating SystemsIf you install Oracle BPEL Process Manager for Developers under a long directory path, create a BPEL process with a long name, or perform both, you can have problems with the sample Oracle BPEL Worklist Application. This is due to a Windows operating system file length limitation of 255 characters. For example, if you perform the following tasks:

■ Install Oracle BPEL Process Manager for Developers under D:\oracle\product\OraBPELPM.

■ Create a BPEL process with a long name, such as BPELProcessOrderApprovalFlow.

■ Add a user task activity in JDeveloper BPEL Designer to start the Workflow wizard.

■ Select Sequential Workflow with Automatic Escalation from the Workflow Patterns list.

■ Add a long name such as ForHighPriorityOrderItems to the pattern name of the Workflow Name field.

■ Use the automatically generated JSP form.

When deploying this process to the local Oracle BPEL server, the full path of the class file corresponding to the JSP is over 255 characters. This results in a "ClassNotFoundException" error occurring when accessing a task details page of the Oracle BPEL Worklist Application. To avoid this issue, use a shorter process name, workflow name, or both. As an alternative option, specify a JSP URL instead of using the automatically generated JSP form.

1.5 Transformation Issues and WorkaroundsThis section describes the following issues and workarounds:

■ Section 1.5.1, "Element with Duplicate Name Is Not Supported in the XSLT Mapper"

■ Section 1.5.2, "Transformation Report Generation Gives Out-Of-Memory Errors"

■ Section 1.5.3, "Existing XSL Files Must Use the Extension .XSL When Used in a Transform Activity"

■ Section 1.5.4, "SetText Introduces a Newline Character After Transformation"

■ Section 1.5.5, "SetText for Attributes"

■ Section 1.5.6, "Inconsistent Behavior for Functions in JDeveloper BPEL Designer"

■ Section 1.5.7, "get-content-as-string Function Introduces a New Line Character After the Output"

■ Section 1.5.8, "Target XSD with Choice May Create Invalid Target Instance at Run Time"

■ Section 1.5.9, "User-Defined Extension Functions At Runtime Require the Class File to be Bundled in a JAR File"

■ Section 1.5.10, "Database Functions with JNDI Names Do Not Work Within a MapTest Window"

■ Section 1.5.11, "Generating Dictionaries of Synonyms"



1.5.1 Element with Duplicate Name Is Not Supported in the XSLT MapperWhen you map duplicate elements in the XSLT Mapper, the style sheet becomes invalid and you cannot work in the Design view. The Log Window shows the following error messages when you map an element with a duplicate name:

Error: This Node is Already Mapped : "/ns0:rulebase/for-each/ns0:if/ns0:atom/ns0:rel" Error: This Node is Already Mapped : "/ns0:rulebase/for-each/ns0:if/ns0:atom/choice_1/ns0:ind" Error: This Node is Already Mapped : "/ns0:rulebase/for-each/ns0:if/ns0:atom/choice_1/ns0:var"

The workaround is to give each element a unique name.

1.5.2 Transformation Report Generation Gives Out-Of-Memory Errors If you attempt to generate a report by right-clicking in the transformation window and selecting Generate Report and receive an out-of-memory error, increase the heap size of the JVM as follows:

1. Open the Oracle_Home\integration\jdev\jdev\bin\jdev.conf file.

2. Go to the following section:

# Set the maximum heap to 512M#AddVMOption -Xmx512M

3. Increase the size of the heap as follows (for example, to 1024)

AddVMOption -Xmx1024M

In addition, you can also uncheck the Open Report option on the Generate Report window before generating the report.

1.5.3 Existing XSL Files Must Use the Extension .XSL When Used in a Transform Activity

The Mapper File field in the Transformation tab of a Transform activity enables you to browse for mapping files (the flashlight icon immediately to the right of this field). If you browse for and select a.xslt file such as xform.xslt, it opens the mapper pane to create a new XSL file named xform.xslt.xsl, even though your intension was to use the existing xform.xslt file. A .xsl extension is appended to any file that does not already have a .xsl extension, and you must create the mappings in the new file.

As a workaround, ensure that your files first have an extension of .xsl. If the XSL file has an extension of .xslt, then rename it to .xsl.

1.5.4 SetText Introduces a Newline Character After TransformationWhen 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.

1.5.5 SetText for AttributesNote the following two issues when using SetText for attributes:

■ If the only mapping you have in an XSL map file is a single setText for an attribute, the value of setText displays incorrectly in the JDeveloper BPEL Designer Source window. For example, if you have setText{oracle} for the attribute InvoiceDate, the following syntax appears:

<xsl:attribute name="InvoiceDate"> <xsl:value-of select="'"oracle"'"/> </xsl:attribute>

Note the double quotes surrounding oracle.

As a result, the value of InvoiceDate displays as follows after transformation:

InvoiceDate=""oracle""

If you have any other mappings in the XSL map file, this problem does not occur.

■ The Disable Escape check box of the Set Text window does not work for attributes. The XSLT Mapper does not create the disable-output-escaping attribute in the source code for attributes.

1.5.6 Inconsistent Behavior for Functions in JDeveloper BPEL DesignerThe 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.

1.5.7 get-content-as-string Function Introduces a New Line Character After the OutputThe 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><ID>Mapper1000</ID> </ID>

Ideally, it should display without a newline character:

<ID><ID>Mapper1000</ID> </ID>

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

1.5.8 Target XSD with Choice May Create Invalid Target Instance at Run TimeNote 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>

XPath Expression Builder Issues and Workarounds


<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.

1.5.9 User-Defined Extension Functions At Runtime Require the Class File to be Bundled in a JAR File

How to use the user-defined extension function is demonstrated in the XSLTMapper sample under Oracle_Home\integration\orabpel\samples\demos\XSLMapper\ExtensionFunctions\README.txt.

1.5.10 Database Functions with JNDI Names Do Not Work Within a MapTest WindowWhen 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.

1.5.11 Generating Dictionaries of SynonymsYou can create a dictionary of synonyms from the XSL map. Use the dictionary as a map preference on the Auto Map Preferences window that appears when you right-click in the transformation window and select Auto Map Preferences. The XSLT Mapper uses the rules defined in the dictionary when attempting to automatically map source and target elements. To generate a dictionary, right-click in the transformation window and select Generate Dictionary.

1.6 XPath Expression Builder Issues and WorkaroundsIf 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','')

See Also: The Online help available in the Generate Dictionary window

Oracle Application Server Adapter for Files/FTP Issues and Workarounds


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')

1.7 Oracle Application Server Adapter for Files/FTP Issues and Workarounds

The section describes the following issues and workarounds:

■ Section 1.7.1, "Multiple Batching Invokes from the Same BPEL Process"

■ Section 1.7.2, "Editing the Existing Logical Name Removes the Mapping in the bpel.xml File"

■ Section 1.7.3, "Determining Values for the File Modification Time Window of the FTP Adapter"

■ Section 1.7.4, "Purging Files"

■ Section 1.7.5, "Use Short File Names with the File and FTP Adapters"

1.7.1 Multiple Batching Invokes from the Same BPEL ProcessIf you do multiple batching file adapter invokes from the same BPEL process, your data is not correctly batched.

If you must have multiple batching file adapter invokes from the same BPEL process, perform the second (and subsequent) invoke through another shell BPEL process. This invokes the file adapter. That is, change your second partner link in the original BPEL process to point to a small BPEL process instead of the file adapter service.

This BPEL process can perform the file adapter invoke for you without issues.

1.7.2 Editing the Existing Logical Name Removes the Mapping in the bpel.xml FileThe File Directories window of the Adapter Configuration wizard enables you to specify logical names instead of physical directory paths for both the incoming files directory and archive directory when using the FTP or File adapter. You must also provide corresponding property settings in the bpel.xml file (either manually or through the Property tab of the partner link activity).

If you later rerun the Adapter Configuration wizard and change the logical name of either the physical directory path or the archive directory, both properties are removed from the bpel.xml file. You must update both of these properties in the bpel.xml file.



1.7.3 Determining Values for the File Modification Time Window of the FTP AdapterWhen you make either of the following selections in the File Polling window of the Adapter Configuration wizard for the Get File operation:

■ Select a value greater than 0 in the Minimum File Age list.

■ Uncheck the Delete files after successful retrieval check box.

the File Modification Time window appears and provides three options for obtaining the file modification time on the FTP server:

■ File System

This option enables you to obtain the date/time format of the file modification time with the file system listing command. However, this option is rarely used and not supported by all FTP Servers. See your FTP server documentation to determine whether your server supports the file system listing command, which command line syntax to use, and how to interpret the output.

For example, if the file system listing command quote mdtm filename is supported and returns the following information:

213 20050602102633

specify the start index, end index, and date/time format of the file modification time in the Data/Time Format field as a single value separated by commas (for example, 4,18,yyyyMMddHHmmss).

Where:

– 4 is the start index of the file modification time.

– 18 is the end index of the file modification time.

– yyyyMMddHHmmss is the data/time format of the file modification time obtained with the quote mdtm filename command.

The resulting service_name.wsdl file includes the following parameters and values:

FileModificationTime="FileSystem"ModificationTimeFormat="4,18,yyyyMMddHHmmss"

To handle the time zone issue, you must also be aware of the time stamp difference. The time zone of the FTP Server is determined by using the Windows date/time properties (for example, by double-clicking the time showing in the Windows task bar). You must then convert the time difference between the FTP Server and the system on which the FTP adapter is running to milliseconds and add the value as a property in the bpel.xml file:

<activationAgents> <activationAgent ...> <property name="timestampOffset">2592000000</property>

■ Directory Listing

This option enables you to obtain the date/time format from the file modification time with the FTP directory listing command. For example, if the directory listing command (ls -l) returns the following information:

12-27-04 07:44AM 2829 NativeData2.txt

specify the start index, end index, and date/time format of the file modification time as a single value separated by commas in either the Old File Date/Time



Format field or the Recent File Date/Time Format field (for example, 0,17, MM-dd-yy hh:mma).

Where:

– 0 is the start index of the file modification time.

– 17 is the end index of the file modification time.

– MM-dd-yy hh:mma is the data/time format of the file modification time obtained with the ls -l command. For this example, the value is entered in the Recent File Date/Time Format field. This field indicates that the format is obtained from the most recent file adhering to the naming convention, whereas the Old File Date/Time Format field obtains the format from the oldest file.


FileModificationTime="DirListing"ModificationTimeFormat="0,17, MM-dd-yy hh:mma"

To handle the time zone issue, you must also be aware of the time stamp difference. The time zone of the FTP Server is determined by using the Windows date/time properties (for example, by double-clicking the time showing in the Windows task bar). You must then convert the time difference between the FTP Server and the system on which the FTP adapter is running to milliseconds and add the value as a property in the bpel.xml file:

<activationAgents> <activationAgent ...> <property name="timestampOffset">2592000000</property>

■ File Name Substring

This option enables you to obtain the modification time from the file name. For example, if the name of the file is fixedLength_20050324.txt, you can specify the following values:

– The start index in the Substring Begin Index field (for example, 12).

– The end index in the End Index field (for example, 20).

– The date and time format in the Date/Time Format field conforming to the Java SimpleDateFormat to indicate the file modification time in the file name (for example, yyyyMMdd).


FileModificationTime="Filename"FileNameSubstringBegin="12"FileNameSubstringEnd="20"ModificationTimeFormat="yyyyMMdd"

Oracle Application Server Adapter for Databases Issues and Workarounds


1.7.4 Purging FilesYou cannot purge control files specific to a BPEL process. For example, you cannot start anew with sequence number 1 for outbound files or reprocess a (debatching) file with errors from the beginning instead of from the last published message.

1.7.5 Use Short File Names with the File and FTP AdaptersEnsure that you limit the length of outbound file names (the file name, plus the complete directory path). When an outbound file name is long (for example, 215 characters), a blank file with that name is created in the outbound directory.

1.8 Oracle Application Server Adapter for Databases Issues and Workarounds

This section describes the following issues and workarounds:

■ Section 1.8.1, "Database Adapter Throws an Exception for SYS.XMLTYPE"

■ Section 1.8.2, "Cannot Import a Table Containing VARCHAR Datatype from DB2"

■ Section 1.8.3, "NCLOB Data Read by the Outbound Database Adapter Contains Invalid Characters"

■ Section 1.8.4, "Timestamp with Local Timezone, and Timestamp with Timezone are Not Supported in ADT"

■ Section 1.8.5, "Date/Time Format Values Not Displayed as Expected"

■ Section 1.8.6, "SELECT Query Does Not Work for Multiple AND Conditions for DEPT:EMP Table"

■ Section 1.8.7, "XML WSDL XSD Files Remain After the Partner Link Is Deleted"

■ Section 1.8.8, "XML File Stored as a CLOB Is Returned as a String, Not as an XML Node"

■ Section 1.8.9, "Cannot Query on Multiple Views"

■ Section 1.8.10, "Using Function Calls Inside a SQL Query"

1.8.1 Database Adapter Throws an Exception for SYS.XMLTYPEOracleAS TopLink does not support SYS.XMLTYPE.

1.8.2 Cannot Import a Table Containing VARCHAR Datatype from DB2This is a known issue. As a workaround, you can change VARCHAR to VARCHAR2 in the offline table.

1.8.3 NCLOB Data Read by the Outbound Database Adapter Contains Invalid Characters

When you configure two processes to perform the following tasks, invalid characters appear when the data is read from the inbound database adapter:

■ A File adapter reads a Word document (in opaque format) and sends it in the database outbound direction. The data is inserted into the table.

■ The database inbound direction reads the same data and sends it to the outbound File adapter, which writes to a document.

Oracle Application Server Adapter for Databases Issues and Workarounds


The workaround is to use a CLOB instead of NCLOB.

1.8.4 Timestamp with Local Timezone, and Timestamp with Timezone are Not Supported in ADT

The AQ Adapter does not currently support the following data types for ADT columns:

■ TIMESTAMP WITH LOCAL TIMEZONE

■ TIMESTAMP WITH TIMEZONE

Only the TIMESTAMP data type is currently supported.

1.8.5 Date/Time Format Values Not Displayed as ExpectedWhen you use datatypes such as DATE, TIMESTAMP, TIMESTAMP WITH TIME ZONE, and TIMESTAMP WITH LOCAL TIMEZONE, for which they are providing specific values, you do not see the expected formats. This is because the database adapter maps these database types to the XML type dateTime. For both incoming values in the instance XML and for outgoing values in the generated XML, dateTime is used. This is consistent with the ISO 8601 standard.

1.8.6 SELECT Query Does Not Work for Multiple AND Conditions for DEPT:EMP TableConsider the following SELECT query:

select dept.*,emp.* from departments dept,employees emp wheredept.department_id='50' and emp.manager_id=dept.MANAGER_ID;

which can be worded as follows:

Find department 50 where any employee in that department has the same manager_id as the department itself.

Note that the above SQL command returns only those departments and employees that match the query. To get this same result with the adapter, you must choose Employee as the root table. If you chose Department as the root table, the adapter logically reads the employees in a separate relationship query:

select dept.* from departments dept,employees emp wheredept.department_id='50' and emp.manager_id=dept.MANAGER_ID;

select emp2.* from departments dept, employees emp, employees emp2 wheredept.department_id='50' and emp.manager_id=dept.MANAGER_ID and emp2.department_id = dept.department_id;

The adapter returns the matching departments, plus all the employees for each matching department, even those whose mangager_id != dept.MANAGER_ID.

Remember this simple rule: The SQL syntax only determines which rows from the root table get returned. The detail rows that are returned depend only on which root and master rows were returned. The above SQL syntax was difficult to express in the adapter because it returned columns from two tables that were both part of the WHERE clause. Selecting Employees as the root table instead of Department worked, but not vice versa.

Oracle Application Server Adapter for Advanced Queuing Issues and Workarounds


1.8.7 XML WSDL XSD Files Remain After the Partner Link Is DeletedAfter deleting a database adapter partner link from the Diagram View of JDeveloper BPEL Designer, the toplink_mappings.xml, the XSD, and the WSDL file remain in the Application Navigator, even after refreshing. This is a known issue.

1.8.8 XML File Stored as a CLOB Is Returned as a String, Not as an XML NodeWhen an XML file (stored as a CLOB) is read and assigned to a variable whose type conforms to the schema, then the database adapter returns the contents of the CLOB as a string and not as an XML document/node. This is the expected behavior because XMLType is not supported.

1.8.9 Cannot Query on Multiple ViewsQuerying on multiple views when using the database adapter is not supported because you cannot create relationships between views. No option for doing so is provided in JDeveloper BPEL Designer.

1.8.10 Using Function Calls Inside a SQL QueryEntering the following type of SQL query:

sqlquery : 'select count(*) from user_objects' rowset : false() row : false() datasource : 'jdbc:oracle:thin:system/welcome1@localhost:1521:ORCL'

Results in the following exception error:

oracle.xml.sql.OracleXMLSQLException: Character ')' is not allowed in an XML tag name.

If you use function calls inside a SQL query string such as count(*), sum(price), or avr(price), include a pseudo-alias name. For example:

sqlquery : 'select count(*) as pseudo_alias_name_XXX from user_objects'

or

sqlquery : 'select sum(price) as total_price from user_objects

1.9 Oracle Application Server Adapter for Advanced Queuing Issues and Workarounds

This section describes the following issue and workaround:

■ Section 1.9.1, "Processing Large Numbers of Messages with the Oracle Application Server Adapter for AQ"

1.9.1 Processing Large Numbers of Messages with the Oracle Application Server Adapter for AQ

If you want to process large numbers of messages with the Oracle Application Server Adapter for AQ, ensure that you set the cacheWSIFOperation property to true in the bpel.xml file:

<BPELSuitcase> <BPELProcess id="HelloWorld" src="HelloWorld.bpel">

Oracle Application Server Adapter for JMS Issues and Workarounds


<partnerLinkBindings> <partnerLinkBinding name="Dequeue"> <property name="wsdlLocation">fileService.wsdl</property> </partnerLinkBinding> <partnerLinkBinding name="Enqueue"> <property name="wsdlLocation">fileWriteService.wsdl</property> *<property name="cacheWSIFOperation">true</property>* </partnerLinkBinding> </partnerLinkBindings>

Set this property through the Property tab of the Create Partner Link or Edit Partner Link window for the partner link.

1.10 Oracle Application Server Adapter for JMS Issues and WorkaroundsThis section describes the following issues and workarounds:

■ Section 1.10.1, "Setting IsTransacted to true in oc4j-ra.xml File with OC4J JMS for Outbound Connections Is Not Supported"

■ Section 1.10.2, "Configuring Tibco JMS in the oc4j-ra.xml file"

■ Section 1.10.3, "RAC/HA Functionality Is Not Supported by the JMS Adapter"

■ Section 1.10.4, "AQ JMS Compliant and Noncompliant Mode Issues"

1.10.1 Setting IsTransacted to true in oc4j-ra.xml File with OC4J JMS for Outbound Connections Is Not Supported

If you are using OC4J JMS, and set isTransacted to true in the oc4j-ra.xml file for an outbound connection, you receive an error. Do not set this value to true.

1.10.2 Configuring Tibco JMS in the oc4j-ra.xml fileWhen using Tibco JMS, always set the ClientID property as follows in the Oracle_Home\integration\orabpel\system\appserver\oc4j\j2ee\home\application-deployments\default\FtpAdapter\oc4j-ra.xml file:

<config-property name="factoryProperties" value="ClientID=clientId{time}"/>

The substring {time} instructs the run time to replace it with the value of Java System.currentTimeMillis(). The other supported substitutions are:

■ {checksum}

A checksum based on the values of the oc4j-ra.xml connection factory properties (referenced through jca:address).

■ {sequence}

Next member of an increasing series of integers starting at zero.

These settings enable you to specify a fixed or a variable ClientID in oc4j-ra.xml.

1.10.3 RAC/HA Functionality Is Not Supported by the JMS AdapterReal Application Clusters (RAC)/high availability functionality is currently not supported by the JMS adapter.

General Adapter and Adapter Partner Link Issues and Workarounds


1.10.4 AQ JMS Compliant and Noncompliant Mode IssuesIn AQ JMS compliant mode, the JMS priority setting is in accordance with JMS specs, where 0 is the lowest priority and 9 is the highest. This differs from AQ JMS noncompliant mode, where 0 is the highest priority and 9 is the lowest.

Set the isTransacted value in the oc4j-ra.xml file to true. Setting it to false leads to exception errors.

To configure the adapter to use a remote database, the entries in the application.xml file must look as follows:

<resource-provider class="oracle.jms.OjmsContext" name="ojmsdemo"> <description>OJMS/AQ</description> <property name="url" value="jdbc:oracle:thin:@remote-host:remote-port:remote-sid" /> <property name="username" value="jmsuser" /> @ <property name="password" value="jmsuser" /> </resource-provider>

1.11 General Adapter and Adapter Partner Link Issues and WorkaroundsThis section describes the following issues and workarounds:

■ Section 1.11.1, "Case of Property Names in ra.xml and oc4j-ra.xml Files Must Match"

■ Section 1.11.2, "Cannot Map to an Adapter Partner Link in the OnMessage Branch of a Pick Activity"

■ Section 1.11.3, "Deleting Header Variables"

■ Section 1.11.4, "Moving to the Next Window in the Adapter Configuration Wizard for Oracle Applications Adapter"

■ Section 1.11.5, "Configuring Multiple Adapters in the Inbound Direction Using Correlation Sets"

1.11.1 Case of Property Names in ra.xml and oc4j-ra.xml Files Must MatchThe 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"/>

Globalization/Multibyte Character Issues and Workarounds


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>

1.11.2 Cannot Map to an Adapter Partner Link in the OnMessage Branch of a Pick Activity

Selecting a partner link that maps to a WSDL file created by the Adapter Configuration wizard on the onMessage branch of a pick activity is not supported. If you do so, the following error displays when the process is deployed to Oracle BPEL Server:

java.lang.Exception: No jca:operation defined/found!

1.11.3 Deleting Header VariablesAssuming 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.

1.11.4 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.

1.11.5 Configuring Multiple Adapters in the Inbound Direction Using Correlation SetsWhen 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.

1.12 Globalization/Multibyte Character Issues and WorkaroundsThis section describes the following issues and workarounds:

■ Section 1.12.1, "Use Binary Mode for Multibyte Text Files with FTP Adapter"

■ Section 1.12.2, "FTP Adapter Does Not Provide Character Set Property"

Globalization/Multibyte Character Issues and Workarounds


■ Section 1.12.3, "Database and AQ Adapters Fail To Read and Write Characters of Types NCHAR and NCLOB"

■ Section 1.12.4, "UTF-8 Encoding Always Used in XSLT Mapper"

■ Section 1.12.5, "XML Mapper Must Use the Encoding Specified in the XSL When Reading a File"

■ Section 1.12.6, "Multibyte Project Name Causes WSDL File to Be Invalid"

■ Section 1.12.7, "Ruler Scale Is Not Multibyte-compliant in the Native Format Builder Wizard"

■ Section 1.12.8, "Encoding Issue for ora:readFile"

■ Section 1.12.9, "Data Consumed as a Text Message May Have Problems"

1.12.1 Use Binary Mode for Multibyte Text Files with FTP AdapterWhen transferring multibyte text files in the inbound direction with the FTP adapter, you must use binary mode.

1.12.2 FTP Adapter Does Not Provide Character Set PropertyThe FTP adapter does not provide a character set property for the target host. This causes encoding problems when you get and put files with multibyte names.

1.12.3 Database and AQ Adapters Fail To Read and Write Characters of Types NCHAR and NCLOB

In a single byte database, you can set the NCHAR and NCLOB types to store multibyte characters. This enables data to be read and written using the database national character set, instead of the database character set. If you want the database and AQ adapters to successfully read and write characters of type NCHAR and NCLOB, you must perform the following steps:

1. Add the following line to the oc4j-ra.xml file:

<config-property name="defaultNChar" value="true" />

2. Add the following lines to the ra.xml file:

<config-property> <config-property-name>defaultNChar</config-property-name> <config-property-type>java.lang.Boolean</config-property-type> <config-property-value></config-property-value> </config-property>

Do not use this parameter unless you must store multibyte characters in a single byte database, as there are performance issues related to setting defaultNChar to true.

1.12.4 UTF-8 Encoding Always Used in XSLT MapperIn 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.

Oracle BPEL Process Manager with BEA WebLogic


1.12.5 XML Mapper Must Use the Encoding Specified in the XSL When Reading a FileThe 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.

1.12.6 Multibyte Project Name Causes WSDL File to Be InvalidIf 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.

1.12.7 Ruler Scale Is Not Multibyte-compliant in the Native Format Builder WizardIf 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.

1.12.8 Encoding Issue for ora:readFileThe 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.

1.12.9 Data Consumed as a Text Message May Have ProblemsWhen 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.

1.13 Oracle BPEL Process Manager with BEA WebLogicThis section describes the following issues and workarounds:

■ Section 1.13.1, "User Name and Password for Default Domain"

■ Section 1.13.2, "Windows 2000 CLASSPATH"

■ Section 1.13.3, "Changing Adapter Deployment Configuration Details"

■ Section 1.13.4, "Manually Adding Adapter JAR Files to the CLASSPATH"

Oracle BPEL Process Manager with BEA WebLogic


■ Section 1.13.5, "Oracle BPEL Server Shutdown Script on Solaris and Linux Must Be Edited"

■ Section 1.13.6, "Human Workflow Identity Service and LDAP Server"

■ Section 1.13.7, "Displaying Sensors Values in Oracle BPEL Console"

1.13.1 User Name and Password for Default DomainDuring installation, you are prompted to accept the default domain name of myorabpel or specify a different domain name. The user credentials for accessing the BEA WebLogic administrator’s console for this domain after installation are as follows:

■ User name: system

■ Password: collaxa1

1.13.2 Windows 2000 CLASSPATHIf you are using Oracle BPEL Process Manager on Windows 2000, ensure that your system CLASSPATH is less than 255 characters. Otherwise, Oracle BPEL Server fails to start.

1.13.3 Changing Adapter Deployment Configuration DetailsSee the README_JBoss_WebLogic.txt file located in the Oracle_Home\samples directory for complete details.

1.13.4 Manually Adding Adapter JAR Files to the CLASSPATHWhen you start the BEA WebLogic Server for the first time after installation and deploy a BPEL process that uses an inbound adapter, you receive a ClassNotFoundException error. This is because the adapters have not yet been deployed and the adapter JAR files are not available in the CLASSPATH. You must manually add the adapter JAR files to the CLASSPATH. If you then restart the BEA WebLogic Server, the BPEL process is correctly loaded.

1.13.5 Oracle BPEL Server Shutdown Script on Solaris and Linux Must Be EditedThe shutdownorabpel.sh file in the $Oracle_Home/bin directory on Solaris and Linux has an extra line feed after -pass:

java weblogic.Admin -url myhostname-pc:9700 FORCESHUTDOWN -username system -password password

The -password option must be on one line. As a workaround, open the file with a text editor and make the following changes:

java weblogic.Admin -url myhostname-pc:9700 FORCESHUTDOWN -username system -password password

1.13.6 Human Workflow Identity Service and LDAP ServerAn LDAP server is not included with the BEA WebLogic Application Server. To use the role-based access control features of the identity service in human workflow, you must install and configure an LDAP server.

Oracle BPEL Process Manager with JBoss


1.13.7 Displaying Sensors Values in Oracle BPEL ConsoleIf a sensor action with a database publish type is defined for a variable sensor of a complex type (that is, the output namespace is not http://www.w3.org/2001/XMLSchema), then the Oracle BPEL Console Sensor Values page displays an incorrect value for the variable sensor.

As a workaround, define sensors for each of the complex type attributes and elements. In this case, the output namespace of all the attributes/elements is http://www.w3.org/2001/XMLSchema. The sensor values display correctly in Oracle BPEL Console.

1.14 Oracle BPEL Process Manager with JBossThis section describes the following issues and workarounds:

■ Section 1.14.1, "Exception Error with Advanced Queuing Adapter Samples That Can Be Ignored"

■ Section 1.14.2, "Exception Error with File Adapter FlatStructure Sample That Can Be Ignored"

■ Section 1.14.3, "Increasing Connection Pool Settings for Oracle BPEL Process Manager"

1.14.1 Exception Error with Advanced Queuing Adapter Samples That Can Be IgnoredWhen running the advanced queuing (AQ) adapter samples under Oracle_Home\samples\tutorials\124.AQAdapter, you can receive the following exception error. This message can be ignored. The samples are running correctly.

12:35:59,602 INFO [STDOUT] <2005-07-20 12:35:59,602> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: AQ Exception (error=17008) alive: true enabled: true 12:35:59,602 INFO [STDOUT] <2005-07-20 12:35:59,602> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> oracle.AQ.AQOracleSQLException: Closed Connection at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1795) at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1290) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:368) at . . .

1.14.2 Exception Error with File Adapter FlatStructure Sample That Can Be IgnoredWhen running the File adapter FlatStructure sample under Oracle_Home\samples\tutorials\121.FileAdapter, you can receive the following exception error. This message can be ignored. The sample is running correctly.

6:03:03,670 INFO [STDOUT] <2005-06-29 16:03:03,670> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Done with Input Record 16:03:04,011 INFO [CachedConnectionManager] Closing a connection for you. Please close them yourself: oracle.tip.adapter.file.FileConnection@1a1ad24

See Also: Oracle BPEL Process Manager Workflow Services chapter of Oracle BPEL Process Manager Developer’s Guide for information about the identity service and LDAP

Documentation Errata


java.lang.Exception: STACKTRACE at org.jboss.resource.connectionmanager.CachedConnectionManager.register Connection(CachedConnectionManager.java:319) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateC onnection(BaseConnectionManager2.java:525) at org.jboss.resource.connectionmanager.BaseConnectionManager2$Connectio nManagerProxy.allocateConnection(BaseConnectionManager2.java:887) at . . .

1.14.3 Increasing Connection Pool Settings for Oracle BPEL Process ManagerIf 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.

1.15 Documentation ErrataThis section describes known errors in the documentation. It includes the following topics:

■ Section 1.15.1, "Online Help for JMS Adapter of Adapter Configuration Wizard"

■ Section 1.15.2, "Online Help for FlowN Activity"

■ Section 1.15.3, "Oracle BPEL Process Manager Developer’s Guide Documentation"

■ Section 1.15.4, "Installation Documentation"

■ Section 1.15.5, "HTML of Installation Documentation"

1.15.1 Online Help for JMS Adapter of Adapter Configuration WizardNote the following updates to the JMS adapter online help:

■ Use SQL92 syntax in the Message Selector field of the Consume Operation Parameters window.

■ The online help for the Destination Name field of the Produce Operation Parameters window lists SEND.QUEUE as an example of the name of the JMS queue or topic. Note that this format example is Tibco JMS-specific.

See Also: Oracle Application Server Integration Installation Guide for details about using an Oracle Database



■ The online help for the Priority drop-down list of the Produce Operation Parameters window says to select a value between 0 (lowest) and 9 (highest). The default is 4. This range is JMS-provider specific. For example, the default priority for AQ JMS is just the reverse (0 is the highest and 9 is the lowest).

1.15.2 Online Help for FlowN ActivityThe online help for this field is incorrect. The index variable indicates a number associated with each branch.

1.15.3 Oracle BPEL Process Manager Developer’s Guide DocumentationChapter: 13, "Interaction Patterns"

Header: "One Request, a Mandatory Response, and an Optional Response"

Page: 13-9

The pick activity in the illustration can be replaced with a switch activity, which is a more logical activity to use in this scenario.

This section describes corrections and clarifications to the Oracle BPEL Process Manager Developer’s Guide.

Chapter: 14, "Oracle BPEL Process Manager Workflow Services"

Header: "Multibyte Payload in the Task Detail JSP"

Page: 14-71

Note the following changes in bold to this section:

To ensure that a multibyte payload is correctly displayed on the Task Detail page, modify the TaskConfigtask_name.xml file that is generated during design time by adding the following element as a child element of payloadDisplay:

<encoding>charset_used_for_JSP</encoding>

If this element is not specified, UTF-8 is used by default.

Chapter: 14, "Oracle BPEL Process Manager Workflow Services"

Header: "Prerequisites"

Page: 14-98

The user-properties.xml and ns_emails.xml files are located in the Oracle_Home\integration\orabpel\system\services\config directory. They are incorrectly listed as being located in the Oracle_Home\integration\bpm\runtime\config directory.

1.15.4 Installation DocumentationThis section describes corrections and clarifications to the Oracle Application Server Integration Installation Guide.

Chapter: 1, "Oracle BPEL Process Manager Installation"

Heading: "Postinstallation Verification Tasks for Oracle BPEL Process Manager"

Table: Table 1-8, "Accessing Oracle BPEL Process Manager Components"

Page: 1-20



The first row in this table describes how to access Oracle BPEL Process Manager on Windows and Unix. On Unix, start and stop the Oracle BPEL Server from the following directory:

$ORACLE_HOME/integration/orabpel/bin

instead of from this directory:

$ORACLE_HOME/integration/bin

1.15.5 HTML of Installation DocumentationThe HTML of the Oracle Application Server Integration Installation Guide in the /doc directory on the software CD-ROM includes external links to several documents that do not work, including the Oracle BPEL Process Manager Developer’s Guide, Oracle Database Installation Guide 10g, and the Oracle Application Server Installation Guide. To access this documentation, see the Oracle Technology Network (OTN) documentation section at http://www.oracle.com/technology/documentation.

Oracle BPEL Process Manager Release Notes - 10.1.2.0.0 ... · with the RDBMS 10.1.0.4 Patch Set"...

Documents

Transcript of Oracle BPEL Process Manager Release Notes - 10.1.2.0.0 ... · with the RDBMS 10.1.0.4 Patch Set"...