The
LiveCycle ES2.5 Process Upgrade Tool runs on a process to create
a new version of the process and replace any QPAC-based actions
that it includes with equivalent LiveCycle ES operations. The result
is a new process that includes the equivalent operations. The results
of executing the upgraded process are equivalent to the results
of executing the old process.
Note:
Upgrades use operations that were equivalent
in LiveCycle ES. Those operations can be deprecated in LiveCycle
ES2.5.
The tool runs on one process at a time and provides a wizard-like
interface that steps you through the upgrade.
When the tool encounters a QPAC-based action, it replaces the
action with one or more LiveCycle ES2.5 operations that perform
an equivalent task. The tool configures the operation properties
by using values from the properties of the action and the corresponding
QPAC. The way the configuration is performed is defined in an upgrade
configuration file. (See
Upgrade definition files
.)
For information about which service operations replace which
QPAC actions, and how the operations are configured, see
QPAC mappings reference
.
If the Process Upgrade Tool cannot upgrade an action, the tool
displays a status message to inform you. You may need to manually
replace the action with an operation. (See
Upgrading custom QPACs
.)
Options
When
you run the tool, you get the following options:
-
Whether
you want the resulting upgraded process to be added to the Processes
view as a new version of the existing process or as a new process
in a specified category.
-
For each action, whether you want to upgrade the action.
-
For each action, which operation to use to replace the action
if multiple activated instances of the service exist.
If
you want to upgrade only part of a process now and other parts later,
you can upgrade processes in stages. For example, to upgrade only
a specific type of action in a process, indicate that only that
action is upgraded. You can later run the tool on the resulting
process to upgrade the other actions that it contains.
Status messages and upgrade problems
When you run the
Process Upgrade Tool, some dialog boxes provide status messages,
depending on the process that is being upgraded and the options that
are selected. These messages are useful for monitoring the tool’s
interpretation of processes and for anticipating the results of
the upgrade.
For example, if you did not correctly prepared for the upgrade,
the status messages provide related information. You can cancel
the Upgrade Process Tool, perform the required tasks, and then run
the tool again. (See
Performing upgrades
.)
Status messages appear in a Status box near the bottom of the
dialog box. Not all of the dialog boxes that the tool provides include
a Status box.
The final dialog box of the Process Upgrade Tool provides a summary
of the upgrade. The summary includes status messages about upgrade
tasks that the tool could not perform.
Status message severity
The description of each status message
includes an icon that represents the message severity:
-
Error icon
:
-
Represents a critical failure of the Process Upgrade Tool
to successfully complete the procedure.
-
Warning icon
:
-
Indicates that the Process Upgrade Tool encountered a non-critical
problem while performing the upgrade procedure.
-
Information icon
:
-
Indicates results and events that do not require further investigation.
Errors
and warnings can indicate that the upgrade is not complete and requires manual
intervention. You must carefully review all warnings and errors.
You
can see warning and error messages after you close the tool by using
the LiveCycle ES2.5 Process Upgrade Problems view. (See
Reviewing upgrade problems
.)
Subprocesses as action replacements
There may be cases in which no
single service operation in LiveCycle ES existed that provided the
equivalent function of an action. However, multiple operations can
be used to duplicate the function of the action. In this situation,
the invoke operation of a process’s service can be used to replace
the action, and the Process Upgrade Tool performs the following
steps:
-
Creates a process that produces the equivalent result
of the action to be upgraded.
-
Activates the process so that its service is created and
available to other processes.
-
Replaces the action with the invoke operation of the process’s
service.
If the Process Upgrade Tool replaces an action with the invoke
operation of a process, the tool automatically imports the process
to the Processes view and activates it.
Note:
When the Process Upgrade Tool attempts to import
a process that has the same name as an existing process, an error
occurs. When this situation occurs, you need to change the name
of the process and manually deploy it.