Deploy a ViewApp

Video Tutorial: Deploy a ViewApp in AVEVA OMI

To deploy a ViewApp

1. Select the object or objects that you want to deploy in an Application view.

   Note: Deployment view is often best for this purpose, as it shows which objects, if any, are beneath the selected object in the deployment order.

2. On the Home ribbon, in the Deploy area, select Deploy.

   You can also deploy a selected object by right-clicking and selecting Deploy from the shortcut menu.

   The Deploy dialog box appears.

   

3. Select one or more of the following:

   • Cascade deploy: Select this check box to deploy the object selected for deployment as well as any objects it hosts. This option is selected by default if the object is a host. If you are deploying an individual host object, clear the check box. Objects being deployed across multiple platforms are deployed in parallel.

   • Include redundant partner: Select this check box to also deploy an AppEngine’s redundancy partner object. This option is selected and unavailable when the redundant engine has pending configuration changes or software updates.

4. In the Deployed objects area, select one or more of the following options. These options are not available if the selected object has not been deployed before.

   • Skip: If one of the objects you are deploying is currently deployed, selecting Skip makes no changes to the already-deployed object.

   • Deploy changes: If one of the objects you are deploying is currently deployed, this option updates the object in question with new configuration data. The runtime state from the runtime file is preserved and the state is modified with any changes.

   • Redeploy: If one of the objects you are deploying is currently deployed, this option deploys the same version as previously deployed. For example, use this option to redeploy an object that is corrupted on the target computer.

   • Force off scan: If one of the objects you are deploying is currently deployed, this option sets the target object to off scan before deployment occurs.

   • Preserve runtime changes: Selecting this option will produce different results, depending on whether you have chosen Deploy changes or Deploy original, if values were changed at runtime, and if configuration values were changed in the IDE.

     • If a value was changed in runtime and Deploy changes and this option are checked, the object is deployed with the last runtime value, even if you change the configured value in the IDE.

     • If a value was not changed during runtime and Deploy changes and this option are checked, the object is deployed with the last configured value from the IDE.

     • If a value was changed in runtime and Redeploy original and this option are checked, the object is deployed with the last runtime value, even if you change the configured value in the IDE.

     • If a value was not changed during runtime and Redeploy original and this option are checked, the object is deployed with the original configured value from the IDE. If you configured a new value in the IDE, the prior configured value is used.

5. In the Undeployed objects area, select Deploy new objects to start a normal deployment.

6. In the Deploy status mismatch area, select Mark as deployed to mark the object as deployed in the Galaxy. A mismatch happens when the object is previously deployed to a target node, but the Galaxy shows the object is undeployed. Clear this option to redeploy the object to the target node.

7. In the Initial scan state area, select one of the following:

   • On Scan: Sets the initial scan state to on scan for the objects you are deploying. If the host of the object you are deploying is currently off scan, this setting is ignored and the object is deployed off scan. When you are deploying multiple objects, the deploy operation deploys all of the selected objects "off-scan." After all of the objects are deployed, the system sets the scan-state to "on-scan."

     Objects can run only when both the host/engine is "on scan" and the object is "on scan." If either the host/engine or the object is "off scan," the object cannot run.

     Always deploy Areas to their host AppEngines on scan. Because Areas are the primary providers to alarm clients, deploying Areas off scan results in alarms and events not being reported until they are placed on scan.

   • Off Scan: Sets the initial scan state to off scan for the objects you are deploying. If you deploy objects off scan, you must use the ArchestrA System Management Console Platform Manager utility to put those objects on scan and to function properly in the runtime environment.

     Note: The System Management Console controls the state of the host/engine. The ObjectViewer controls the state of the objects.

     The default scan setting is set in the User Default settings in the Configure User Information dialog box. For more information, see Configure user preferences.

8. Click Deploy to deploy the objects. The Deploy progress box appears. When the deploy is complete, click Close.