Designing processes - EMC Community Network

Chapter 9
Deploying the Application
This chapter discusses the following:
• Deploying the application overview
• The deployment process
• Deployment best practices
Deploying the application overview
After the application has been developed and tested, it is ready for the production environment. The
environment in which process-based applications are put into production generally differs from the
development environment. The production environment usually has more users and, therefore, requires
more hardware components, software modules, and databases. In this document, the term deployment
means the transfer of applications between environments: from development to test or from test to
production, with as many intermediate environments as necessary. In the general setting, you deploy
applications from a source environment to a target environment.
The deployment process begins by preparing the target environment. To prepare the target
environment, EMC Documentum products such as Content Server, Process Engine, Process
Builder, and BAM that were installed in the source environment must also be installed in the target
environment. The next step is to define the users in the target environment. In most cases, the users in
the target environment are different from the users in the source environment.
The deployment process
After you have developed a TaskSpace application with BAM dashboards and have completed testing
the application, you can begin deployment. (If you have not implemented BAM in your solution,
skip steps 3, 4, and 6).
To deploy:
1. Install TaskSpace and other xCP products in the target environment.
2. Create a Composer project. Add the SDTs that you used to create BAM reports to this project.
Build a Documentum Archive (DAR) file. Install it on the target environment.
3. Start BAM in the production environment. The report entities corresponding to the SDTs you
imported in Step 1 will be populated in the Documentum repository.
4. If you created BAM custom entities, they are not migrated by using Composer. When you created
those entities you would have run one or more DQL scripts. Save the DQL scripts as a text file.
EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 107