Deploying an instance

This topic provides information about deploying an instance for a package or repository.

Before you begin

You must have packages (or repositories) created. For more information about creating packages or repositories, see:

To deploy an instance

  1. You can use one of the following ways to deploy an instance:
    • From the packages (or repositories) list on the Deploy tab, click Deploy on the Actions menu associated with the latest instance of the package that you want to deploy.
    • From the packages (or repositories) list on the Deploy tab, click (for the particular instance) to quick-start the package (or repository)  instance deployment into the suggested next environment.
    • From the package (or repository) instances pane, click the Deploy link associated with the instance to deploy.
  2. (Optional) Select an alternative instance from the Instance menu.
    The route appears preselected, since you selected it during instance creation.
  3. Select the target environment to deploy into.
    Only the environments permitted by the configured route policy are available as deployment targets.
  4. From the Review After menu, select one of the following options:
    • Environment Preprocessing: The deployment triggers the environment preprocessing that you selected during environment definition in the Pre-Deploy field under Topology > Environment. The deployment then moves to the paused state until the instance references are examined to determine to which channels the application should deploy them.

    • Content Analysis: The deployment moves to the paused state after the application determines where the references will be deployed to within the environment (channels).

    • Content Processing: The almost completed deployment pauses after the processing on the reference is complete.

  5. Click Deploy.

    To deploy only files that have changed, click the Toggle Changed Content button. You can track all the changes on the Content and Properties tabs. For information about the changes in the files, see  Instance delta report.
    (click the image to expand it)



    The results page for the configured deployment appears. For more information, see Viewing deployment results.

Notes

  • When you deploy an instance for a package or repository that has references to a server that was added to the default "Undefined" zone, then only engines assigned to the "Undefined" zone perform the instance creation tasks for those references.
  • When you deploy an instance for a package or repository that has references to server added to some custom zone, then only engines assigned to that custom zone perform the instance creation tasks for those references. 
  • When you deploy an instance with the Invoke Remote Action activity library that has a reference to a remote server (other than the one used in your topology), the deployment tasks for that actitity are executed by the engine from the zone to which the remote server is added (and not from the target server's zone). If those engines cannot perform a task at a specific moment, that task waits in a queue until the engine can perform it. For more information about zones, see Zones and Managing zones.

Where to go from here

Viewing deployment results

Monitoring and managing server configurations

Was this page helpful? Yes No Submitting... Thank you

Comments