Correspondence Management Solution 3.0 provides this great ability to transport, via an intuitive user interface, not just the entire set of assets across environments, but also selective assets. This is one of the uber cool enhancements from how the same is achieved in the previous version of the solution, where this was somewhat limited and cumbersome.
Right from the Manage Assets user interface itself, you can now select any asset or set of (possibly related) assets, that you wish to take over or move to another environment (or physical server), and export them as a ZIP. This ZIP can then be imported over to the desired target system, and voila!…you’ll have your assets in place. Indeed! it is as simple as this.
Please take a moment to read through the published documentation to guide you through the step by step process.
Transporting assets in the Correspondence Management Solution Accelerator 2.5 across systems is a common requirement and a frequent activity.
Exporting assets from the source system
CMSA being based on LiveCycle Content Services as the content repository, assets are exported as an ACP from the source system using steps documented in the CMSA guide. Such an exported ACP will contain ALL assets on the source system, and their relationships.
Importing assets to the target system
Importing assets (ACP exported above) on the target system will be largely driven by the intention, and desired behavior.
If the intention is to *create a replica of the source system* (and ignore whatever is on the target system), then perform the following on the target system:
- Delete DataStore (under Company Home).
- Ensure to delete the same from Deleted Itemsas well. To do so :
- Go to User Profile.
- Click Manage Deleted Items
- Click Show All
- Click Delete Listed Items
- Click Yes
- Delete files within Models (under Company Home > Data Dictionary).
- DO NOT delete the Models space itself.
- Delete files within lcc_persistence (under Company Home)
- Restart your server
- Bootstrap CMSA (http://server:port/cmsa/Bootstrap)
- Use the Import Utility to import the source system’s ACP
- “importWithDD” or “importWithoutDD” would depend on which Data Dictionaries do you wish to honor. The ones from the source system (use ‘importWithDD’) or the ones on the target system (use ‘importWithoutDD’).
- Restart your server
However, if the intention is to *keep the existing assets* and import whatever is in the ACP from the source system, then you should IGNORE steps 1. to 6., and simply execute step 7. (i.e., “Use the Import Utility to import the source system’s ACP”) and 8.
It is important to note that in such cases there could be a possibility of duplicate assets in the system, if the source and target systems contain assets by the same ‘name’; since we enforce the uniqueness in asset names via the CMSA interface only, but here we are directly importing assets onto the repository (bypassing the solution’s constraints).