Before
you invoke an application, make it available in the runtime registry
by deploying it. The application and the assets you want to include
in the deployment must be checked in. You can deploy one or more
applications at a time.
After the initial deployment, if you change parts of the application,
you do not need to redeploy the entire application. Redeploy only
the parts that are changed. When redeploying an updated long-lived
process, the currently running process follows the updated steps
in the new process if they are not already completed.
You can also undeploy the application. This procedure removes
the application from the runtime registry, therefore making it unavailable
for invoking. Use this approach to stop the application from running
and to keep it in the repository. Undeploying is different from
deleting because deleting also removes the application from the
repository.
Note:
Make sure that no instances of the process are
running when you undeploy or delete the application. Otherwise,
these instances will not complete.
Note:
Undeploying the application deletes configurations
that were done for the application in LiveCycle Administration Console.
Therefore, when you deploy this application again, you must reconfigure
it.
To check whether the application is deployed,
pause the pointer on the name of the application in the Applications
view. A tooltip shows either Not Deployed or Deployed. Also, the
deployed applications use this icon
in
the applications tree.
Right-click the application version and select
Undeploy, and then click OK in the Warning message.
