BPEL4WS

[Former Member]

Hi Friends,

How to import and export the integration process using BPEL4WS

[Former Member · Accepted solution]

Dear Vijay,

Business Process Management supports the process definition part of BPEL4WS 1.1 (Business Process Execution Language for Web Services 1.1). For more information about BPEL4WS, see http://ifr.sap.com/bpel4ws.

You can use BPEL4WS as the exchange format for exporting an integration process to a non-SAP system and executing it there. Conversely, you can use BPEL4WS to import an integration process from a non-SAP system to SAP Exchange Infrastructure and execute it there. For information about restrictions to the BPEL4WS import and export functions, see SAP Note 709650.

BPEL4WS is not intended for importing or exporting integration processes between Integration Repositories. For this purpose, use the Integration Repository import function instead (see also: Transporting XI Objects).

Features

Export

The export exports the integration process definition as a BPEL4WS representation. Additionally, data types, message types, and operations referenced in the process definition are exported as a WSDL description.

You can display the BPEL4WS representation of the process definition to be exported in the Process Editor at any point (see also: Process Editor). You can display the corresponding data type definitions in the form of a WSDL description in the output area.

Export Files

The process definition displayed in the Process Editor is exported as a file. The export file is a .zip file that contains the following files:

· .wsdl).

The three files must have the same name. The .zip file must not contain any path specifications or directories.

5. Choose Continue.

The assistant displays all container elements that reference a message.

6. Assign the relevant abstract message interfaces.

7. Choose Continue.

The assistant displays all container elements that are used in correlations and that reference messages.

8. Assign the relevant abstract interfaces.

9. Choose Finish.

To ascertain whether the import was successful or whether errors occurred, check the resulting messages.