Configuring the Resources in the Deployment Project

When you have added the projects and other resources that you want the deployment project to contain, you must configure those resources and generate a DAA for each of the resources. Depending on the state of the BPM projects, you may also need to specify some other details.

This is similar to the deployment process described in Deploying an Application Using the Deployment Wizard.

Note:

Prior to configuring the resources, you may need to refresh the deployment server to ensure that its current state is known (for more information, see Refreshing a Deployment Server).

Also note that if the projects in your Deployment Project are using virtualized bindings, you may need to deploy some the projects first, then configure and deploy the other projects (that are dependent on the earlier deployed projects). You must do it this way so that the virtual bindings are available in the pick list when you are configuring the projects that are dependent on those bindings.

Procedure

  1. For each resource in turn, select it in the Projects Configuration panel and select New from the Deploy Action dropdown (replacing the default Don’t Deploy).
    You can specify Don’t Deploy in the Deploy Action field for resources that you do not want to deploy (this can be useful when you need to deploy a subset of resources that failed initially and have been reconfigured to run the deployment scripts again).
  2. In the Status column, which was initially blank, the status Not Configured displays. The Status column can have one of the following values:
    Status Description
    <blank> The initial state when a resource is added, or has Don’t Deploy specified.
    Configured The resource is configured for deployment.
    Not Configured The resource is not configured for deployment. Click Configure Application to configure it.
    Missing Dependency The resource is missing one or more dependencies. Click Add Resources to select and add the items that this resource depends upon.
    Inconsistent Order The selected resource is out of sequence, that is some of the resources it depends on are listed below it in the table. Use the Move Up, Move Down, or Reset Order buttons to rectify the order.
    Not Accessible The selected resource is not accessible in the workspace. It is either deleted, closed or does not have any deployable artefacts.

    Click Configure Application.

  3. The DAA Generation Page displays. For scripted deployment to work, a DAA must exist in the deployment project.

    Click Generate DAA, and then click Next.

    Note: If a DAA for this resource already exists within the deployment project, the button on this page shows Re-Generate DAA instead. You can ignore this and click Next if you are confident that the resource has not changed since the existing DAA was generated, or you can re-generate the DAA now. If the source as changed, you must re-generate the DAA.
  4. The Application Configuration page displays. This shows the default deployment information for the server that you selected in Specifying the Server. This is some of the information that you entered in the RuntimeServer Parameters dialog when creating the deployment server - see Creating a New Deployment Server. Amend the Environment Name, Application Folder and other information displayed if you want to use values different from the defaults that you set up for this deployment server or if the server that you specified is offline.
  5. At this point you may be able to click Finish. However if the resource needs any further configuration, the Finish button will not be available. You should click Next and complete any further dialogs that display.
  6. When you click Finish, the value in the Status column changes to Configured. Repeat the configuration for each resource in the deployment project.

Result

Distribution

The Distribution page may then be displayed. Select whether you wish the resources to be deployed to one node or more, and then select the node from the drop downs provided.

Click Next.

The Property Configuration page is displayed if any property mappings are required.

Select a property and click Override to change the specified value assigned to any of the properties in the Name column. The Property value page displays.

By default, the properties are mapped to substitution variables, which provide a level of indirection. To change this, specify the new value in the Property value dialog and click OK.

The Wiring Configuration page is displayed if the resource contains unresolved promoted references.

  1. Click -add wire- in the row containing the unresolved promoted reference. A drop-down listing the available applications, services, and bindings appears.
  2. Select the application, service or binding that you want to wire the promoted reference with, and click outside the text
  3. When you have done this for all the listed references, click Finish.

The Deploy Project Editor for the project is now populated.