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

Deploying Additional Resources

Deploying Additional Resources

Add resources to deploy to the server. View the selected deployment descriptor files and other project resources to deploy. On the Catalog Resources page, view the list of selected and excluded resources to ensure your contribution contains all files to be managed as a unit. Upon export, deploy the file and save a script to redeploy the .bpr file.
For an overview of best practices for deployment, see Deploying Project Dependencies and Viewing Excluded Dependencies.
As you develop a process, there are two kinds of resources you can add: dependent and non-dependent resources. Dependent resources include WSDL, schema, human task forms, XSL for doXSLTransform, and Java jars specified in the PDD. Dependent resources can be deployed in the same BPR contribution containing the process PDD or in a referenced project.
You may want to deploy XQuery modules in a separate BPR.
The resources you may want to deploy in a separate BPR include:
To deploy additional resources to the server:
  1. Ensure that the server is running, and ensure that your resource file is in a Workspace project.
  2. Select
    File > Export > Orchestration > Contribution- Business Process Archive File
    .
  3. If the resources are not directly imported into the process, you can skip the process deployment descriptor files (.pdd files) to include in the .bpr archive.
  4. Select the export location and filename for the .bpr archive.
  5. In the Deployment section, select Web Service as the Type.
  6. On the Catalog Resources page, if needed, select
    Add
    .
  7. Select a Resource Type and Location. Select a resource from the Project Explorer.
    For Other, add a URI. The URI can be any reference desired, preferably related to the resource type. For example, an XML resource URI should be the root namespace of the XML document.
  8. In the Resources list, do the following:
    • Optionally, type in a new or existing Group Name. The Server can display resources by groups.
    • Optionally, type in a Description. The description is displayed in the Catalog Resources list on the server.
  9. Add additional resources as desired.

0 COMMENTS

We’d like to hear from you!