Publishing a Project

To publish a project is to make it available for deployment in ALBPM Enterprise. You can deploy a project from the publication process, or you can deploy it separately.

To publish a project:

  1. In the Navigator pane, click Projects ().

    The Published Projects pane will appear, with a list of published projects.

  2. In the Published Projects pane, click Publish.

    The Publication Source pane will appear.

  3. Set the Publication Source, which can be a Project at Web Server host, an Exported Project or a VCS (Version Control System). For a project at a Web server host, you must also specify the URL of the project. For an exported project, specify the file of a project exported from Studio. CVS is currently the only supported VCS provider.
  4. Set the options in the Publication Properties section as desired.
  5. You can deploy the processes you are publishing by checking the Deploy processes after publishing them checkbox. If you opt to deploy, you can also import the project's custom views and custom presentations by checking the Import the project's custom views and presentations after the deployment checkbox.
  6. Click OK The Publish Process pane will appear.
  7. Add any notes you may have about the project in the text box in the Remarks section.
  8. In the Role Mapping section, you can specify which real role (as defined in Process Administrator) will take on which abstract role (as defined in Studio). One or more abstract roles can be assigned to the same real role.
  9. If there are process variables in the project, the Variable Mapping section will be present. In this section, you can specify which real variable (as defined in Process Administrator) will take on which process variable (as defined in Studio).
  10. If there are external resources in the project, the External Resource Mapping section will be present. In this section, you can specify which real external resource (as defined in Process Administrator) will be mapped to which process configuration (as defined in Studio).
  11. Click Publish. If you chose to deploy the project in step 5, the Deploy pane will appear. If not, go to step 17.
  12. In the Deployment Topology pane, select how you want to see the list of projects by selecting from the Show the deployment grouped by: drop-down list. The choices are by Server, or by Organizational Unit. The list shows the projects in the requested order.
  13. For each project you will deploy, determine the organizational unit (OU) the project will be available in. The project will also be available in all organizational units below the selected organizational unit. If you don't select an OU, the project will be available to the entire organization.
  14. You can also select the views that will be generated for WorkSpace users, in the Views Generation column. The options are Unified inbox (the default), By process, and By process and activity. In most cases the default value is used.
  15. Set the archiving option as desired in the Enable Archiving checkbox.
  16. In the Action column drop-down list, select Deploy.
  17. Click OK.

The project is deployed.

If you did not opt to deploy the project in step 5, you will need to deploy the project separately. To do so, see Deploying a Project.