If you have followed all tutorial parts so far, you have designed and debugged a BPEL process. You are now ready to deploy your process. Deployment is the act of publishing your BPEL process to the Process Server where it can run. In the deployment procedure, you use the WS-Addressing specification to define endpoint references.
It is time to deploy the process to the ActiveVOS embedded server. Deployment is the act of publishing your BPEL process to the ActiveVOS server where it can run. In the deployment procedure, you use the WS-Addressing specification to define endpoint references.
In the Project Explorer view of Process Developer, you should have the following files:
that you created in Part 2
, a completed version of the file created in Part 2 (optional)
After completing Part 9 of the tutorial, you will be able to:
Complete the prerequisite checklist for deployment.
Create a process deployment descriptor file.
Create a business process deployment archive.
Deploy the business process archive to the server.
Step 1: Complete the Prerequisite Checklist for Deployment
A BPEL file is ready for deployment to the Process Server when there are no errors in the Problems view and when a simulated execution of the process terminates normally.
Step 2: Create a Process Deployment Descriptor File
A Process Deployment Descriptor (
file describes the relationship between the participant partner links defined in the BPEL file and the implementation required to interact with actual partner endpoints. You create a
file to add address information about your endpoint references. The
file is an integral part of the deployment package for the process.
Recall that the loan approval process has the following definitions for partner links:
is the process service consumer. In BPEL terminology, the My Role partner.
are partner service providers. In BPEL terminology, the Partner Role partners.
You will assign an endpoint type for each partner role and will provide access protocol information for the process role (My Role). An endpoint type is a binding property that indicates the actual service the process interacts with. Different types give you control over specifying services you work with now and in the future. In this tutorial, you will indicate a static reference to partner services.
File > New > Deployment Descriptor
to open the
New Deployment Descriptor
, and click
folder to store your deployment descriptor, shown in the example below, and click Finish to open the PDD Editor.
Do not make any changes on the General tab.
On the Partner Links tab, select the
Select WSA Address from the Invoke Handlers list. This addressing technique provides flexibility in deploying your processes into different server locations.
Select the dialog (
) button next to the Endpoint Reference text box. In the
dialog, notice that
is selected, and the matching service is selected as shown. Select
WS-Addressing is automatically added based on the binding information in the WSDL file.
On the Partner Links tab, leave Static as is from the Endpoint Type list, as shown in the example.
as the Invoke Handler, accept the
and service as the Endpoint Reference, and leave
as the Endpoint Type.
, and in the My Role panel, select Document Literal for the Binding style.
In the Service field, type the name
Save and close
Step 3: Starting the Process Server
You will now deploy
and its resources to the server. The first step is to start the server.
The Process Server consists of an engine running under Apache Tomcat. Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies.
Select the Servers view in the lower right of the workspace and then right-mouse click within it. Select New > Server as shown in the illustration.
In the Server type list, select Process Server, click
, and select Finish.
Select the Start the Server button, as shown in the example.
As the server starts up, you see start up tasks scroll in the Process Console. Files are deployed to the embedded server each time you start it. Many of these files are for BPEL for People activities that you may want to create for your next project. After the server starts, you'll see the message at the bottom of this figure.
Step 4: Create a Business Process Deployment Contribution Archive
To deploy your process to the Process Server, you must add all relevant files to an archive file (
file), which is similar to a Web archive file.
File > Export > Orchestration > Contribution-Business Process Archive File
file to include in the archive, as shown in the following example.
For the export destination BPR file, browse to the deploy folder and name the
. Your path should be similar to the following:
In the Type field, select Web Service. The engine's default address is automatically filled in for the Deployment URL. If you changed your host and port information during installation, change the URL here.)
Selecting this option automatically deploys your
file to the Process Server upon completion of the export.
Type in the Group name Tutorials and
Description Process Developer Tutorials
. These properties help you identify groups of processes on the server as you develop many types of processes.
Select the check box next to Save the contribution specification..., and browse to the
Name the BPRD file
. This file is an Ant script which you can run to re-deploy the
file whenever you modify a
Select Finish. A deployment details dialog shows the results.
Your BPR file has been automatically deployed to the server, as indicated by the information dialog. You can also see the results in the Process Console.