Designing processes - EMC Community Network

Deploying the Application
At deployment time, manually run those scripts in the target environment to create your custom
entities in the BAM database.
5. In Composer, create a new TaskSpace application project. Select the TaskSpace application name
from the list of available TaskSpace applications.
This action automatically pulls in all related artifacts:
• The associated process (from Process Builder), associated forms, roles, tabs
• Associated BAM dashboards (defined as tabs in TaskSpace)
• First-level BAM reports on these dashboards (First-level reports are not defined as drilldown
reports)
6. Manually import the drilldown reports. This action is required because the drilldown reports you
created in your dashboards are not automatically imported into the project. Also, import the
BAM Configuration artifact that contains various settings used by BAM (such as time settings for
the gap filler).
7. If you are using headless Composer, build the DAR file for this project.
Composer builds the DAR automatically. It is located in the bin-dar folder of the project root.
8. Install the Composer project into the target environment.
Deployment best practices
This section lists some best practices to follow for deployment:
Composer version
Use the latest version of Composer including any hot fixes that are available.
Linking process templates to your application
When constructing your TaskSpace application, it is best to link the process templates to your
application. This causes the linked process templates to import automatically into your Composer
Project when your TaskSpace application is imported into your Composer Project. Processes required
by your application that are not linked to your TaskSpace application are not imported automatically
when the TaskSpace application is imported and must be added individually to your Composer project
or they will not be available in the production environment after the Composer project is installed.
Database references
Whenever database references change as you move from the source to the target environment, these
references must be manually updated to the new database reference. Do this after you install your
application into the production environment.
Specific performers in processes
When processes contain specific performers, reference those performers as process parameters.
Process parameters become installation parameters in the Composer project. This enables you to make
the replacement in your Composer project once for each process rather than once for each activity in
108 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide