About the provisioning Deploy process

The Upgrade, Downgrade, and Redeploy provisioning commands all use the same deployment process. This section describes what happens programmatically during this process.
  1. Upon clicking Commit during the upgrade, downgrade, or redeploy provisioning procedures, a Commit Template confirmation window alerts you that this process removes the existing template and installs a different version, and prompts you to click Yes to confirm that you wish to continue.
  2. If the target is an online station (this is handled by an Upgrade Job in the station).
    1. For each template that you selected to be upgraded, downgraded, or redeployed the following steps occur:
      1. The template .ntpl file is copied to the target station's file system at: ^template/"+vendor. If it already exists (validated with crc check), the file is not copied.
      2. Adds a reference to the template root to be updated to a BVector that will be an argument to the Upgrade Job.
    2. Submits an Upgrade Job with a list of template roots to be upgraded.
    3. The Upgrade Job runs in the station.
      1. For each template identified to be upgraded the following occurs:
        1. Get a reference to the .ntpl pushed to the station’s file system (which was pushed by client prior to launching this job)
        2. Get a reference to the deployed template root component's parent.
        3. Save the current state of the deployed template:
          • Save the location of the deployed template root component (BWsAnnotation)
          • Save persistent properties of the template root component.
          • Save the location and values of any BPassword slots.
          • Save the current value of template configuration properties
          • Save any input links to the template root component.
          • Save any output knobs from the template root component
          • Save any input relations to the template root component
          • Save any output relations from the template root component
          • Save the location and value of any tags in the template component tree that aren't defined in the template definition and namespace is not "ntpl".
          • Save the location and current value of any slots defined as an editable slot in a PxView.
          • Save any external links and relations to or from internal template components.
          • Save current state of any BHistoryExt's
        4. Remove the existing template root component from its parent.
        5. Using the .ntpl reference deploy the template to the template's parent.
        6. Restore the values saved in the previous Save step.

          In general, the restoration of saved property values is done by property name and value. If the template property has been renamed and it is one of the saved properties, its value will not be restored.

          • Restore the location of the deployed template root component (BWsAnnotation)
          • Restore persistent properties of the template root component. If properties have been removed from the template they will not b restored.
          • Restore the location and values of any BPassword slots. If BPassword properties have been removed from the template they will not be restored.
          • Restore the current value of template configuration properties If a template configuration property has been removed it will not be restored.
          • Restore any input links to the template root component.
          • Restore any output knobs from the template root component
          • Restore any input relations to the template root component
          • Restore any output relations from the template root component
          • Restore any save component tags.
          • Restore the saved values of any slots defined as an editable slot in a PxView.
          • Restore the saved external links and relations.
          • Restore the saved state of BHistoryExt's.

  3. The online station deployment is complete.