The Lost Hours : Moving Service Configurations from Dev to Production
Adobe's LiveCycle Archive files (LCAs) greatly reduce the effort required to migrate a process, and all of its Forms & DSCs, from Dev to Test/Production. And while the LCA technique can help migrate components (such as DSCs) it doesn't touch their configuration.
In my experience a lot of hours of service configuration effort goes into one LiveCycle environment to ensure it sings and dances properly with all of the back-office systems in the organisation. For example:
- The configuration settings for connecting to each of an email/JMS/LDAP server must all be correct, tested, and working.
- The licence keys for the many Avoka DSCs must all be installed.
So, at migration time, the configuration has to be rediscovered on one environment and manually transferred, line by line, to the next environment. This can take hours for large solutions, is painstaking work, and is susceptible to human error. Which can significantly add to the stress and pressure of migrating from Test to Production.
The Solution
The Migration Utils component eases this burden by enabling any service configuration setting to be automatically copied from one LiveCycle environment to another.
The Steps:
Step 1: drop it into a process.
Step 2: configure it to find the source environment.
Step 3: configure it to find the destination environment.
Step 4: run the process.
Moving Processes From Dev to Production
