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 Import Tool

This section describes how to use the BPEL Import tool in BEA Workshop for WebLogic to import a BPEL file.

 


Topics Included in This Section

Introduction to BPEL

Provides a brief background on BPEL and how it evolved.

BPEL Import Tool

Provides an overview on how the BPEL Import tool works.

Importing a BPEL File

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

Known Limitations and Issues

Provides information on the import 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:

http://dev2dev.bea.com/webservices/BPEL4WS.csp

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

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel

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

 


BPEL Import Tool

You can use the BPEL Import tool to import a BPEL file into a JPD file, where it can be used in the BEA Workshop for WebLogic design environment. While the main orchestration logic of the BPEL file is imported into a JPD file, it is not expected that the imported JPD file will be immediately executable in BEA Workshop for WebLogic. You will need to manipulate the JPD file in BEA Workshop for WebLogic to get the imported process to run.

In certain cases, runtime semantics are not guaranteed, due to the functional mismatches between the JPD and BPEL languages, or between various expression languages including differences between XQuery, Xpath, and XSLT. Runtime semantics are also not guaranteed when they involve vendor extensions, external artifacts, or environment settings. For the above reasons, the imported JPD file should be reviewed and tested with any required changes that were made to ensure that it runs properly.

In general, the BPEL Import tool expects complete BPEL and WSDL artifacts as input. To some extent, the tool also handles incomplete BPEL and WSDL artifacts, so that in-progress BPEL files can be imported as JPD, and then completed in the WebLogic Integration environment. Incomplete cases are numerous and may include missing WSDL files, missing type definitions, missing port type definitions, or incomplete constructs of <while>, <switch>, <invoke>, <receive>, <reply>, <onMessage>, <onAlarm>, <throw>, as well as other cases. If the BPEL Import is not able to import the input artifacts into a JPD file, error messages appear that enable you to correct the input artifacts for future imports.

 


Importing a BPEL File

  1. In BEA Workshop for WebLogic, create or open a BEA Workshop for WebLogic application.
  2. In the Package Explorer pane, open the workspaceArrow symbolWeb ProjectArrow symbolSrcArrow symbolImport to import the BPEL file, as shown in Figure 1-1. The Import pane appears.
  3. Figure 1-1 Location for Imported File


    Location for Imported File

Note: The BPEL Import tool does not support importing to Schemas/Project root directories. If you try to import into a root directory, you get the following error message (Figure 1-2).
Figure 1-2 Error Message

Error Message

If you try and import into a directory which is not in the source path, you get the following error message (Figure 1-3).

Figure 1-3 Error Message 2

Error Message 2

  1. Select BPEL Process and click Next to begin the import as shown in Figure 1-4.
  2. Figure 1-4 Import BPEL Option


    Import BPEL Option

  3. Choose the files to be imported as shown in Figure 1-5 and click Open to use the file.
  4. Figure 1-5 Select BPEL Source Window


    Select BPEL Source Window

  5. Locate the BPEL file that you want to import and click OK to proceed as shown in Figure 1-6.
  6. Figure 1-6 Select the File to Import


    Select the File to Import

  7. Specify the location of the folder containing the Web Services Description Language (WSDL) files as shown in Figure 1-7.
  8. Figure 1-7 WSDL Location


    WSDL Location

  9. Select the required folder and click Open. The BPEL Import tool will pick up all WSDL and XSD files in the selected folder.
  10. The import begins and you can view the progress of the import as shown in Figure 1-8.

  11. Enter an appropriate package name as shown in Figure 1-8.
  12. Figure 1-8 BPEL Import Progress


    BPEL Import Progress

  13. Select the Util project folder. Preferably the make it point to the Util project created while reacting the Weblogic Process Application.
  14. You can view the log containing the complete details of the import as shown in Figure 1-9. This log also tells you if the import was successful or not.
  15. Figure 1-9 Import log


    Import log

    Note: The Build pane below the Design pane displays diagnostic messages about the schema import process as shown in Figure 1-10. The log files are stored in the workspace/.metadata folder (workspace indicates your Weblogic Process Application workspace).
    Figure 1-10 Build Pane - Schema Diagnostic Messages


    Build Pane - Schema Diagnostic Messages

    Note: A log file for the import process, named BpelImport.log, is stored in %BEA_HOME%\weblogic81\workshop where %BEA_HOME% is the directory in which you installed BEA Workshop for WebLogic. This log file provides information about the import process.

    The new JPD file appears in the folder specified in step 2 and the WSDL files are copied and placed in the Schemas folder, as shown in Figure 1-11.

    Figure 1-11 New JPD and WSDL Files


    New JPD and WSDL Files

This completes the import process and your new JPD file is located in the folder specified in step 2.

 


Known Limitations and Issues

This section details some known limitations and issues of the BPEL Import tool. The majority of these issues exist because of the inherent differences between the JPD and BPEL languages.

It is very important that you confirm that the generated JPD file corresponds semantically with the input BPEL file.


  Back to Top       Previous  Next