1. Getting Started

1. Getting Started

Part 9: Deploying the Process

Part 9: Deploying the Process

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:
  • tutorial.bpel
    that you created in Part 2
  • tutorialCompleted.bpel
    , 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.
  1. Open
    tutorial.bpel
    .
  2. 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.
  1. Select
    File > New > Deployment Descriptor
    to open the
    New Deployment Descriptor
    dialog.
  2. Select
    tutorial.bpel
    , and click
    Next
    .
  3. Select the
    deploy
    folder to store your deployment descriptor, shown in the example below, and click Finish to open the PDD Editor.
    New Deployment Descriptor wizard, page one
  4. Do not make any changes on the General tab.
  5. On the Partner Links tab, select the
    LoanApproval
    partner link.
  6. Select WSA Address from the Invoke Handlers list. This addressing technique provides flexibility in deploying your processes into different server locations.
  7. Select the dialog (
    ...
    ) button next to the Endpoint Reference text box. In the
    Endpoint Reference
    dialog, notice that
    LoanApproval.wsdl
    is selected, and the matching service is selected as shown. Select
    OK
    .
    Endpoint Referencee selection
    WS-Addressing is automatically added based on the binding information in the WSDL file.
  8. On the Partner Links tab, leave Static as is from the Endpoint Type list, as shown in the example.
    New Deployment Descriptor wizard, partner link definition
  9. Select
    RiskAssessment
    , select
    WSA Address
    as the Invoke Handler, accept the
    riskAssessment.wsdl
    and service as the Endpoint Reference, and leave
    Static
    as the Endpoint Type.
  10. Select
    loanProcessor
    , and in the My Role panel, select Document Literal for the Binding style.
  11. In the Service field, type the name
    TutorialService
    .
  12. Save and close
    tutorial.pdd
    .
Step 3: Starting the Process Server
You will now deploy
tutorial.pdd
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.
  1. 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.
    New Server
  2. In the Server type list, select Process Server, click
    Next
    , and select Finish.
  3. Select the Start the Server button, as shown in the example.
    start the server
  4. 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.
    server started
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 (
.bpr
file), which is similar to a Web archive file.
  1. Select
    File > Export > Orchestration > Contribution-Business Process Archive File
    and click
    Next
    .
  2. Select the
    tutorial.pdd
    file to include in the archive, as shown in the following example.
    Export Business Process Archive dialog
  3. For the export destination BPR file, browse to the deploy folder and name the
    .bpr
    file
    tutorial_completed.bpr
    . Your path should be similar to the following:
    Tutorial/deploy/tutorial_completed.bpr
  4. 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
    .bpr
    file to the Process Server upon completion of the export.
  5. 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.
  6. Select the check box next to Save the contribution specification..., and browse to the
    deploy
    folder.
  7. Name the BPRD file
    tutorial_completed.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.
  8. 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.
Process Console


Updated March 09, 2020