Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 9 Exporting and Importing Orchestration Processes : Exporting Orchestration Processes

Exporting Orchestration Processes
The following types of files are created during the export operation:
WS-BPEL process files — each orchestration process in your project becomes one WS-BPEL file in the specified target export location. WS-BPEL files comply with the schema of the WS-BPEL 2.0 specification.
WSDL files — any WSDL resources required to execute the orchestration processes are exported as WSDL files. Both abstract and concrete WSDL files are exported, whether they are used as interface descriptions for services or for bindings to external partner services. These WSDL files may also contain WS-BPEL specific extensions.
XSD files — any schemas referenced by orchestration processes or WSDL resources are exported as XSD files. The export operation includes any schemas defined within activities of your orchestration process, such as a fault schema defined in the Throw activity (or any other referenced inline schemas). The export operation also includes input and output schemas for any invoked TIBCO ActiveMatrix BusinessWorks automated business processes.
Services and Partner Link Configurations are not part of the WS-BPEL specification, and therefore these are not exported as WS-BPEL-compliant files. If you wish to export the other resources in your project for use by another TIBCO ActiveMatrix BusinessWorks project, you must use either the Project > Export Full Project or Project >Export Resources to File menu options. See TIBCO Designer User’s Guide for more information about exporting TIBCO ActiveMatrix BusinessWorks projects.
Exporting SetContext and GetContext Activities
The GetContext and SetContext activities are exported as BPEL extension activities. The XML syntax of a BPEL extension activity is as follows:
<extensionActivity name =
...
...
</extensionActivity>
A sample XML snippet for Get Context is shown below:
<extensionActivity name = "GetContext">
<tibco-bpws:layout X = "187" Y = "41" iconType = "getContextIconType"/>
<tibco-bpws:getContext>
<tibco-bpws:contextConfiguration>/context/InputHdrContext.contextResource</tibco-bpws:contextConfiguration>
</tibco-bpws:getContext>
</extensionActivity>
 
A sample XML snippet for Set Context is shown below:
<extensionActivity name = "SetContext"
tibco-bpws:input_mapping_xslt_assoc = "BPEL_Proc/Orch_Proc_For_Service_BPEL1-SetContext.xsl">
<tibco-bpws:layout X = "367" Y = "35" iconType = "setContextIconType"/>
<tibco-bpws:setContext>
<tibco-bpws:contextConfiguration>/context/OutputHdrContext.contextResource</tibco-bpws:contextConfiguration>
<tibco-bpws:showResult>false</tibco-bpws:showResult>
</tibco-bpws:setContext>
</extensionActivity>
To export WS-BPEL-compliant files from a project:
1.
Create or choose a directory to hold the exported files. Existing files with the same name as the exported files in the specified directory are overwritten by the export process.
2.
Open a TIBCO ActiveMatrix BusinessWorks project containing orchestration processes and choose Tools > BPEL > Export from the menu in your project.
3.
In the Export BPEL dialog, choose the directory in step 1 to store the exported files. If the directory does not exist (because you did not pre-create the directory in step 1 or you chose a different directory), an error is returned stating that the directory path does not exist. If the directory is not empty, a warning is given asking if you wish to proceed.
4.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved