BPEL Import and Export User Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Using the BPEL Export Tool

This section describes how to use the BPEL Export tool in BEA Workshop for WebLogic, to export BPEL 1.1 compliant code from a JPD file.


Topics Included in This Section

Introduction to BPEL

Provides a brief background on BPEL and how it evolved.

BPEL Export Tool

Provides an overview on how the BPEL Export tool works.

Exporting a BPEL File to JPD

Describes how to export a BPEL file using BEA Workshop for WebLogic.

Known Limitations and Issues

Provides information on the export tool that will enable you to use is more effectively and efficiently.


Introduction to BPEL

BPEL4WS (Business Process Execution Language for Web Services, commonly referred to as "BPEL") defines a language for the formal specification of automated business processes. Processes written in BPEL can orchestrate interactions between Web services using XML documents in a standardized manner. These processes can be executed on any platform or product that complies with the BPEL specification. BPEL therefore enables customers to protect their investment in process automation by allowing them to move these process definitions between a wide variety of authoring tools and execution platforms. While there have been previous attempts to standardize business process definitions, BPEL has attracted an unprecedented level of interest and is the first to gain critical mass among software vendors.

BPEL4WS 1.1 is the latest published specification from BEA, Microsoft, and IBM, but it does not reflect the upcoming BPEL standard, which is still under development by the OASIS standards organization. It is important to bear in mind that the final standard will be different from BPEL4WS 1.1, and therefore this tool is provided largely to enable design-time interoperability with other tools that support the 1.1 specification.

For more information on the BPEL language, refer to the BPEL4WS specification v1.1, published by BEA, IBM, and Microsoft and submitted to OASIS for standardization, which is available at:


and the official Home page for the BPEL standardization effort, hosted by OASIS at:


In BEA WebLogic Integration™, a business process is defined using BEA Process Definition for Java (JPD). The BPEL export tool is a design-time aid to help convert a JPD file into a BPEL file.


BPEL Export Tool

You can use the BPEL Export tool to export the semantics of a JPD file into BPEL where it can be used in a BPEL design environment. BPEL code that is exported using the BPEL Export tool is BPEL 1.1 compliant and can be used in design environments compliant with BPEL 1.1. While the main orchestration logic of the JPD is exported to BPEL, it is not expected that the exported BPEL will be immediately executable in the target environment. You will need to manipulate the BPEL in the target environment to get the exported process to run, or to get close to the run-time semantics.

This is due to the fact that some executable call-outs from the JPDs will be opaque to the exported BPEL code. These executable units generally include controls, code written in perform nodes, and XQuery transformations. The BPEL Export tool copies the Java code and the XQuery code as extension nodes in BPEL. As a result, you must re-implement the logic in the target BPEL environment, since JPD provides a superset of the functionality provided by BPEL.

One Web Service Definition Language (WSDL) file defines the WSDL interface of the business process and defines a partner-link type for the interface. The other file defines the WSDL interface and partner-link types of the partners. Partners are the artifacts interacting with the business process. These artifacts are either consumers or providers of services to the business process.

These WSDL files are not the same as the WSDL that BEA Workshop for WebLogic would generate for the corresponding JPD or JCX files. The differences are described in detail in Known Limitations and Issues on page 2-9.

The relevant XSD schema files (which must be located in a schema folder in the WebLogic Integration application) are needed in the target environment, along with the WSDL and BPEL files.


Exporting a BPEL File to JPD

  1. In BEA Workshop for WebLogic, right click on a JPD file in the Package Explorer pane. For example, in Figure 2-1, right click on Process.java Export.
  2. Figure 2-1 JPD Location

    JPD Location

  3. The Export pane appears. Select BPEL Process from JPD and click Next to proceed as shown in Figure 2-2.
  4. Figure 2-2 BPEL Export Selection

    BPEL Export Selection

  5. Choose the destination directory where the BPEL Export tool will create BPEL and WSDL files as shown in Figure 2-3.
  6. Figure 2-3 BPEL Export Pane

    BPEL Export Pane

  7. Select Finish to complete the export process. You can view the progress of the export as shown in Figure 2-4.
  8. Figure 2-4 Progress of BPEL Export

    Progress of BPEL Export

  9. When the export is complete, the BPEL Export log displays the message Done! as shown in the lower right hand corner of Figure 2-5.
  10. Figure 2-5 Generated Files

    Generated Files

  11. You can view the log containing the complete details of the export as shown in Figure 2-6. This log also tells you if the export was successful or not. The logs are located in %workspace%/.metadata where workspace refers to where the WebLogic Process application resides.
  12. Figure 2-6 Export log

    Export log


Known Limitations and Issues

This section provides some notes on the export process and details some known limitations of the BPEL Export tool.

Notes: The section details information that you should remember when using the BPEL Export tool.

Limitations While Importing WebLogic Integration 9.2 Generated BPEL Files Into AquaLogic Business Process Management

Other Known Limitations

This section details some of the known JPD export limitations.

Table 2-1 details how various JPD file attributes, nodes, and so on are converted to a BPEL file.

Table 2-1 JPD File to BPEL File Conversion
In the JPD file
converted to in a BPEL file
clientRequest and controlReceive nodes
receive activity
clientCallback and controlSend nodes
invoke activity
synchronous returnMethod attribute
reply activity
onMessage paths
onMessage event handlers
onTimeout paths
onAlarm event handlers
eventChoice node
pick activity
Parallel node
flow activity
onException blocks
perform node
empty activity with the java code from the perform method copied into the body of a JPD namespace javaCode element
control flow nodes:
  • decision
  • switch
  • forEach
  • doWhile
  • whileDo
to the equivalent BPEL activities.

  Back to Top       Previous  Next