The Confirmation page shows all the values configured for this deployment. For Manual and Automatic Deployments, this page shows the name of the package, the version number of the package, the schedule selected for the package, the expiration date selected for the package, and the notification(s) selected for the package. It also includes any Routing Criteria that was defined.
For an Automatic Deployment, this page also shows the Deployment Type, the Priority, and the number of Estimated Assets for the deployment. The number in the Estimated Assets field is a link to a popup window that displays a list of the assets to which the package would be deployed, if they are all online and meet any package dependencies at the time of deployment.
1. Review the information.
2. If necessary, click the Back button to return to previous pages to make corrections.
3. Click
Deploy to create the deployment.
Alternatively, to discard the changes to the deployment and exit the wizard,
click Cancel.
When you click Deploy, what happens
next depends on the Schedule for the deployment and the Type of deployment:
§ Manual Deployment
Start Immediately -- If the selected
assets meet the pre-process dependencies, the package is deployed to the
assets the next time their Axeda® Agents contact the
Axeda® Platform.
Start at Scheduled Time -- At
the scheduled time for the deployment, the Platform checks the selected
assets to see if they meet the pre-process dependencies, and if so, deploys
the package to the selected assets, using the specified interval between
deployments to the assets.
§ Automatic Deployment
Start Immediately -- The Platform starts
the evaluation task that checks which assets are currently online and
meet the pre-process dependencies. Once the evaluation task has determined
the assets for the deployment, the deployment task starts the deployment.
Start at Scheduled Time -- At the scheduled time, the Platform checks the
priorities of automatic deployments. Based on the priorities, the evaluation
task checks which assets are currently online and meet the pre-process
dependencies for the highest priority package deployment. The deployment
task then deploys the package to the assets selected by the evaluation
task. If additional deployments with lower priorities are scheduled for
the same time, the system runs the evaluation and deployment tasks for
those package deployments, based on the priorities.
4. To review the status of a deployment, select View | Deployments.