Specify the Update Method

When a version is delivered to a deployment client, the Runtime Manager needs to be restarted to apply the included changes. The Update Method allows you to specify how a restart will be initiated.

There are three options you can use for the Update Method.

• Prompt

  When the Update Method is set to Prompt, the client machine accepts the project and a message box will display prompting the operator to restart Runtime Manager.

  

  Note: To use your own prompt instead of the default prompt, you can create custom Cicode and implement it with the parameters [Deployment]AskRestartFunc and [Deployment]AskRestartArgs. Refer to Create a Custom Deployment Prompt for more information.

• Notify

  When the Update Method is set to Notify, the client machine accepts the project and a notification is added to the system tray indicating a new project has been deployed and that Runtime Manager needs to be restarted.

  

• Force

  When the Update Method is set to Force, the client machine accepts the project and restarts Runtime Manager automatically.

  Note: If you do not restart the Runtime Manager after using "Prompt" or "Notify" updated method, it will continue with the older version and project. If you have installed Industrial Graphics server and/or OPC UA Server in the same machine, then the Industrial Graphics Server and/or OPC UA Server automatically activates the newly deployed project and version. So, the Runtime manager and Industrial Graphics Server and/or OPC UA Server may not synch with each other.

If Runtime Manager is not running on a deployment client, a deployed project will be transferred but will not run. You will need to start Runtime Manager to launch the project.

See Also

Deploy a Version