Designing processes - EMC Community Network
Designing processes - EMC Community Network
Designing processes - EMC Community Network
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 10<br />
Archiving the Application<br />
This chapter discusses the following:<br />
• Manually Archiving TaskSpace Applications<br />
Manually Archiving TaskSpace Applications<br />
This section provides step-by-step instructions on manually archiving and installing a TaskSpace<br />
application. However, it does not address automatic builds with Apache Ant. Since the incorporation<br />
of importArtifacts in Composer version 6.6, it is possible to build TaskSpace applications with Ant.<br />
This approach can be preferable if you are packaging with any frequency (daily, weekly, or bi-weekly<br />
builds).<br />
Manual archiving uses a zipped composer project file, rather than a DAR file, to enable you to fix any<br />
problems when reinstalling the target side application.<br />
The following are examples of when to archive a TaskSpace application manually:<br />
• Moving an application from one environment to another<br />
• Saving an application for later use or reference<br />
Do not use manual application archiving as part of the development process of a project, try to use<br />
automatic builds instead.<br />
Best practices before and after archiving<br />
When you decide to create a TaskSpace application, the following best practices can make archiving<br />
the application quicker and easier.<br />
• When you decide to archive an application, consider Composer only as a transport or archiving<br />
utility. Do not modify your Composer project after you have imported your artifacts. If you created<br />
your types or objects in a Composer project, consider it only as a bootstrapping project to create the<br />
artifacts for your application archive.<br />
• Always define your folder structure for your TaskSpace application so that you can simply archive<br />
the whole cabinet or folder with the workflows already in there. This way you avoid archiving the<br />
workflows separately.<br />
• Store workflows for a specific application in their own folder to make them more recognizable.<br />
Archive this folder manually. DO NOT archive it in a cabinet or folder that needs a manual archive.<br />
• Organize your Structured Data Types under a category to make them easier to identify when<br />
archiving.<br />
<strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 111
Change language