ActiveBPEL® Designer User’s Guide

Previous | Next

Creating a Process Deployment Descriptor File

A Process Deployment Descriptor (.pdd) file describes the information required for a process to execute in the ActiveBPEL server environment. This information includes partner link details, persistence and versioning information, process directives and indexed properties as well as other details. In each step of the procedure below, there are links to the relevant help topics for the deployment details to add.

To create the process deployment descriptor file:

1. In ActiveBPEL Designer, select File>New>Deployment Descriptor.
2. Select a folder and a process deployment descriptor filename, if you want to change the defaults.
3. Select a BPEL file to be described, and select Finish to open the PDD Editor.
4. Select a Deployment Platform. For details see Deployment Platforms.
5. Fill in the Partner Links tab for each partner link as follows.
1. Select a partner link from the list.
2. If the partner link has a Partner Role defined, select the Endpoint Type for the partner link, and optionally, select an Invoke Handler. For explanations and examples of Endpoint Types, see Partner Role Endpoint Types. For explanations of Invoke Handlers, see Partner Role Invoke Handlers. For WS-Policy details, see Endpoint References and WS-Policy.
3. If the Endpoint Type is Static, see the notes below.
4. If the partner link has a My Role defined, select the Binding style and Service Name. Optionally, you can specify Allowed Roles. For explanations of these properties, see My Role Binding, Service Name, and Allowed Roles Options. To add WS Policy assertions to a My Role partner link, see Adding Policy Assertions.
6. For ActiveBPEL Enterprise or Professional only, define Indexed Properties, if desired. An indexed property is a variable property that is populated with the variable (or variable part) value during process execution. On the server Administration Console, you can select indexed properties as a search filter for process instances. For details, see Adding Indexed Properties.

Notes for Static Endpoint Type:

• If you select Static for an Endpoint Type and System Default for the Invoke Handler, WS Addressing is automatically provided, based on the service bindings in the imported WSDL, as the following example shows.



For flexibility, you can specify the address as an URN rather than an URL. For details, see Specifying a Replacable URN/URL for an Endpoint Reference.

• If the WSDL does not include bindings, WS Addressing elements are added with placeholders, as the following example shows. You can edit the placeholders on the Partner Links tab or Source tab. For more information, see Editing a Process Deployment Descriptor File.



• If you want to select a different service, you can. See Selecting a Service for a Deployment Descriptor Partner Link for details.
• To add WS-Policy policy assertions, see Adding Policy Assertions.

Copyright (c) 2004-2008 Active Endpoints, Inc.