ActiveVOS Designer User’s Guide
Previous | Next
Tutorial Part 9: Deploying the Process
To start at the beginning of the tutorial, see Introduction to ActiveVOS Tutorial.
If you have followed all tutorial parts so far, you have designed
and debugged a BPEL process.
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 ActiveVOS, you should have
the following files:
- tutorial.bpel that you created
in Part 2
- tutorialCompleted.bpel, a completed version of the file
created in Part 2 (optional)
By 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 ActiveVOS Server
when there are no errors in the Problems view and when a simulated
execution of the process terminates normally.
- Open tutorial.bpel.
- Simulate the process, as described in Tutorial Part 8: Simulating the Process, and test all
execution paths.
Step 2: Create a process deployment descriptor file
A Process Deployment Descriptor (.pdd) 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 .pdd file to add address information
about your endpoint references. The .pdd 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:
- loanProcessor is the process service consumer. In
BPEL terminology, the My Role partner.
- RiskAssessment and LoanApproval 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.
- Select to open the New Deployment Descriptor dialog.
- Select tutorial.bpel, and click Next.
- Select the deploy folder to store
your deployment descriptor, shown in the example below, and click to
open the PDD Editor.
- On the tab, do not make any
changes.
- On the tab, select
the
LoanApproval partner link.
- Select 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 text box. In the Endpoint Reference Dialog,
notice that LoanApproval.wsdl is selected,
and the matching service is selected as shown. Select OK.
WS-Addressing is automatically added based on the binding
information in the WSDL file. Note that a URN is supplied as the
address. On the server we have already mapped this URN to a URL
for the tutorial.
- On the Partner Links tab, leave as
is from the Endpoint Type list, as shown in the example.
- Select
RiskAssessment, select as the Invoke Handler, accept the riskAssessment.wsdl and
service as the Endpoint Reference, and leave as
the Endpoint Type.
- Select
loanProcessor, and in the panel, select for
the Binding style.
- In the field, type the name TutorialService.
- Save and close tutorial.pdd.
Step 3: Starting the ActiveVOS Server
We will deploy tutorial.pdd and its resources to the server.
To do so, we will start up the server.
The ActiveVOS Server consists of the ActiveVOS 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 view
in the lower right of the workspace.
- Right-mouse click within the Servers view and select as
shown in the illustration.
- In the Server type list, select ,
click Next, and select .
- Select the button,
as shown in the example.
- As the server starts up, you see start up tasks scroll
in the Console. Several 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. When
the server is started, the message indicates this, as shown.
Step 4: Create a business process deployment contribution
archive
To deploy your process to the ActiveVOS Server, you must add
all relevant files to an archive file (.bpr file), which is similar
to a Web archive file.
- Select and click Next.
- Select the tutorial.pdd file to include
in the archive, as shown in the following example.
- For the export destination ,
browse to the deploy folder and name the .bpr file tutorial.bpr.
Your path should be similar to the following:
Tutorial/deploy/tutorial.bpr
- In the field, select . The engine’s default address is automatically
filled in for the . If you changed
your host and port information during installation, change the URL
here.)
Selecting this option automatically deploys your .bpr file
to the ActiveVOS server upon completion of the export.
- Type in the name Tutorials and ActiveVOS
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 , and browse to the
deploy folder.
- Name the BPRD file tutorial.bprd.
This file is an Ant script which you can run to re-deploy the bpr file
whenever you modify a .bpel or .pdd file.
- Select . 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 Console.
Continue to Tutorial Part 10: Creating a Request to Run the Process.
Copyright (c) 2004-2011 Active Endpoints, Inc.