Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

Creating a Process Deployment Descriptor File

Creating a Process Deployment Descriptor File

A Process Deployment Descriptor (.pdd) file describes the information required for a process to execute in the Process Server environment. If you are deploying a process to a production server, you can specify process version and other details to override the server defaults.
A Process Deployment Descriptor (.ppd) file describes the information required for a process to execute in the Process Server. 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 Process Developer, 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 General options. For details see
    General Deployment Options
    .
  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 Process Server, 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. In the Process Console, you can select indexed properties as a search filter for process instances. In addition, you can use indexed properties for the event tracking. For details, see
    Adding Indexed Properties
    .
For details on adding Human Tasks Logical People Groups, refer to Human Tasks elsewhere in this help.
Notes for Static Endpoint Type:
  • For flexibility, you can specify the address as a URN rather than a URL, supplying WSA Address for the Invoke Handler. For details, see
    Specifying a Replaceable 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. For more information, see
    Using the PDD Editor Source View
    .
  • 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
    .

0 COMMENTS

We’d like to hear from you!