|
|
Business Process Execution Language (BPEL) is a web service orchestration standard that can be used to define transactional business processes. With BPEL, activities that are part of a business process can be expressed as web services. These services can then be orchestrated to ensure control over the entire process. Processes written in BPEL are stored as .bpel files and can be executed on any platform or product that is compliant with the BPEL specification.
WLI provides BPEL Import and Export tools to enable design-time interoperability with other tools that support the BPEL 1.1 and 2.0 specifications.
In certain cases, however, run-time semantics are not guaranteed, especially when there are functional mismatches between the business process and BPEL, or between various expression languages, including differences between XQuery, XPath, and XSLT. Run-time semantics are also not guaranteed when they involve vendor extensions, external artifacts, or environment settings. For the above reasons, the imported and exported files must be reviewed and modified based on requirements to make sure that they execute correctly.
You can use the BPEL Import tool to import a BPEL 1.1- or 2.0-compliant file into a business process file, where it can be used in Workshop.
While the main orchestration logic of the BPEL file is imported into a business process file, it is not expected that the imported business process file will be immediately executable in Workshop. You will need to manipulate the business process file in the WLI Eclipse IDE, before it can be executed as a business process.
You can use the BPEL Export tool to export the semantics of a business process file into BPEL, where it can be used in a BPEL 1.1- or 2.0-compatible design environment.
While the main orchestration logic of the business process is exported to BPEL, it is not expected that the exported BPEL file will be immediately executable in the target environment. You will need to manipulate the BPEL file in the target environment to execute the exported process or to get close to the run-time semantics.
For more information, see BPEL Import and Export User Guide.
|