Process Developer > Part IV: Testing and Deployment > Process Deployment > Creating and Deploying a Business Process Archive Contribution
  

Creating and Deploying a Business Process Archive Contribution

View the selected deployment descriptor file(s) 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.
To deploy your process to A Process Server, you package a contribution of processes and resources in a business process archive file (.bpr file), which is similar to a Web archive file.
Before creating a .bpr file, you must create a .pdd file, described in Creating a Process Deployment Descriptor File. Optionally, you can additional resources, such as Process Central forms and tasks.
We recommend that you create only one BPR file per project. The processes and resources are managed as a unit of files on the server. For details, see Managing Deployment Contributions.
To create a .bpr file:
  1. 1. If you have created and used a project reference for the current project, be sure to deploy that contribution first. Project dependencies must be deployed to the server first.
  2. 2. Select File > Export > Orchestration > Contribution-Business Process Archive.
  3. 3. Notice that all process deployment descriptor files (.pdd files) are pre-selected to include in the archive, as shown in the following example.
  4. 4. Select the export location and filename for the BPR file.
  5. 5. Select a Server Deployment Type:
  6. 6. If desired, type in a Group name and description for this contribution. On the Process Console you can use the group name as a selection filter for listing files. The description appears on the Contribution detail page of the Console.
  7. 7. If desired, select the option to Save the contribution specification as an Ant script in the workspace, and select a location for this file, such as the Orchestration Folder's deploy folder. For details on this option, see Using a BPRD Script to Regenerate and Deploy a BPR Contribution.
  8. 8. Click Next to view a list of catalog resources. See the following topics.
  9. 9. Click Finish to create and export the .bpr file and optional .bprd file.
  10. 10. Refresh the project to view the new BPR file.
See also Managing Deployment Contributions.

Deploying Project Dependencies and Viewing Excluded Dependencies

As described in Creating and Deploying a Business Process Archive Contribution, you begin a deployment at the project level, by including the process deployment descriptors (PDDs) of the processes in your project. The Export Business Process Archive Wizard then shows you all project resources pre-selected and project references excluded from deployment, as shown in the example.
The parts of this dialog are described as follows:
Project Resource Dependencies
The current project resource dependencies are deployed. They include the following types:
Project Reference Dependencies Excluded from Archive (not deployed)
You must deploy these resources in a contribution prior to deploying this contribution.
Project References specified in the project properties and used within the process are listed on the Catalog Resources page. For example, if you create a participant based on a referenced WSDL, you will see the WSDL listed in the excluded list. For details on the advantage of this approach, see Using Project References.
Additional Resources
Additional resources are automatically pre-selected, based on the Contribution Preference.
You can deploy more resources as described in 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. 1. Ensure that the server is running, and ensure that your resource file is in a Workspace project.
  2. 2. Select File > Export > Orchestration > Contribution- Business Process Archive File.
  3. 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. 4. Select the export location and filename for the .bpr archive.
  5. 5. In the Deployment section, select Web Service as the Type.
  6. 6. On the Catalog Resources page, if needed, select Add.
  7. 7. Select a Resource Type and Location. Select a resource from the Project Explorer.
    8. 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.
    See also Deploying Forms Reports and Configuration Files.
  8. 8. In the Resources list, do the following:
  9. 9. Add additional resources as desired.

Deployment to Informatica Cloud

The business process archive (.bpr file) contains all the resources needed to deploy your project resources to an Informatica Cloud Secure Agent.
When deploying to Informatica Cloud, either to the Cloud Server or to a Secure Agent, there are two requirements not applicable when deploying on-premises:
  1. 1. Specify Allowed Roles.
  2. 2. Set the Server Deployment Option to File.
This topic describes how to set these options in Process Developer and how to:
Specify Allowed Roles
You specify the roles allowed to run the process in the .pdd as follows:
  1. 1. Select a process in which you can specify roles. For example, open the My Role panel, select Document Literal for the Binding style:
    2. loanProcessor selected when creating a PDD
  2. 2. In the Service field, type a name to identify the role.
  3. 3. Add all the allowed roles that will be able to access the process.
    4. Note: You must add at least one allowed role so that users can access your application.
Set the Server Deployment Option to File
When you export your project to a BPR file, you complete a dialog similar to the following. By default, the Server Deployment Option (Type) is set to None.
To deploy to Informatica Cloud, you must change this value. Select File from the Type list:
Export Business Process Archive
Deploy to Informatica Cloud

Deploying to Informatica Cloud Server

To deploy a process to Informatica Cloud after you have created the .bpr file, follow these steps:
  1. 1. Log in to Informatica Cloud. The user must have administrative privileges.
  2. 2. Select Home > Process Monitor.
  3. 3. In the upper-right corner of the Process Console page, click Deploy.
  4. 4. In the dialog, click Browse to select your .bpr file.
  5. 5. From the Deploy Target list, choose Cloud Server:
    6. Deploy dialog
  6. 6. Click Deploy.
  7. 7. Within the Process Monitor, select Catalog > Process Definitions to verify that your process was deployed.

Requirements for Deploying to a Secure Agent

When you deploy a process to a secure agent, the process is similar to deploying on the Cloud Server. In addition, take these steps:
  1. 1. Provide the Endpoint Reference as shown below.
  2. 2. Select these options:
For example:
Partner Link tab showing agent address
The structure of this address is agent:agent_name:agent_service
agent
This tells Process Developer what kind of information follows.
agent_name
Typically, this is the system where the agent runs.
agent_service
The name of the installed service.
When deploying the process in the Process Console, select the same agent name you used in the endpoint reference as the Deploy Target:
Deploy dialog