1. Active BPEL Engine ( v5.0.2)
1.1 In servlet container
Deploying a BPEL process against Active BPEL Engine, it needs you to create a deployment archive file ( a JAR with an extension of ".bpr"). In the .bpr archive, it includes following files:
| File | Description | Type |
|---|---|---|
| bpel/*.bpel | This is BPEL file format. | 0 |
| META-INF/catalog.xml | The WSDL catalog provides a way for the BPEL engine to find WSDL files within a .bpr deployment archive. | 1 |
| META-INF/pdd/*.pdd | Process Deployment Descriptor, This XML file tells the BPEL engine about your BPEL processes. Each process (each .bpel file) has its own .pdd file. | 1 |
| wsdl/*.wsdl | Contains neccessary wsdl files that the bpel file used. | 0 |
| partners/*.pdef(optional) | Partner links describe relationships between partners. Partner definition files are not necessary for all BPEL processes, just those with principal-based enpoint reference mapping. | 1 |
Note: 0: BPEL common deployment file. 1: Active BPEL specific deployment file.
Detail please refer to $activebpel/doc.
2. Apache ODE (v1.2)
2.1 In servlet container
Deploying a BPEL process against Apache ODE enginee, it needs you to create a folder, which includes following files into $Ode/WEB-INF/process of your servlet container.
| File | Description | Type |
|---|---|---|
| *.bpel | This is BPEL file format | 0 |
| *.wsdl | Contains neccessary wsdl files that the bpel file used. | 0 |
| deployment.xml | The deploy.xml file configures one or several processes to use specific services. For each process, deploy.xml must supply binding information for partner links to concrete WSDL services. | 1 |
Note: 0: BPEL common deployment file. 1: Apache ODE specific deployment file.
Detail please refer to http://ode.apache.org/user-guide.html#UserGuide-ProcessDeployment .
Comments