Moving Processes From Dev to Production

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.

h2. 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.

h5. The Steps:

*Step 1: drop it into a process.*


\\
\\
*Step 2: configure it to find the source environment.*

!1.gif!

\\
*Step 3: configure it to find the destination environment.*

!2.gif!

\\

*Step 4: run the process.*

!3.gif!

h2. [Technical API | http://avoka.dnsalias.com/confluence/display/Public/Migration+Utils]