|
Migrating libraries of templates and modifying related
data sources can be the largest part of any migration effort. Using
the Central Migration Bridge service, you can migrate an application
from Central to Output in stages.
- Initial stage:
- Move the invocation and run-time aspects from the Central environment
to the LiveCycle environment. You can continue to use existing Central
templates and data assets. If you use Central Job Management Database (JMD),
replace it with LiveCycle processes. Output does not support JMD,
and it does not provide tools for converting JMD.
If your
existing Central templates were saved with a version of Output Designer earlier
than 5.7, they may work as is. However, in some instances (especially
with pre-5.4 templates), you may need to migrate your existing Central
templates by using Output Designer 5.7. When you use that application
to open and save a template, it automatically migrates the template.
Use Output Designer 5.7 to test migrated templates to ensure that
they work as expected.
- Subsequent stages:
- Over time, convert templates and non-XML data assets for use
with Output. You can simultaneously use new and converted processes
on the same LiveCycle server. Over time you can convert all of your
assets and become independent of the Central Migration Bridge service.
You
can use Designer to import Output Designer templates. To enable
this feature, install Output Designer with Designer. To use this
feature, open a file of type Adobe Output Designer template (*.ifd).
Designer performs a basic conversion. The degree of completeness
of the conversion depends on the complexity of the incoming form.
Use Designer to complete the conversion process. (See Designer Help.)
|
|
|
