Deploy objects

You deploy object instances for two reasons:

• Testing.

• Placing the application into production to process field data.

When you are ready to deploy, make sure the following conditions are met:

• Bootstrap software is installed on the target computers.

• The objects being deployed are not in an error state in the Galaxy database.

• You created, configured, and checked in objects to the Galaxy.

• Objects are assigned to a host.

• The object's host is already deployed. A cascade deploy operation, which deploys a hierarchy of objects, deploys all objects in the correct order. This deploys an object’s host before the object is deployed.

• Any associated script libraries are ready for use on the target computer. For more information, see Import script function libraries.

You can tell if you have objects that need to be deployed by looking at the status icons to the right of the object name in Model, Deployment, Derivation or IO Devices view. Deployment status icons include:

For more information about object and status icons, see Application Object Icons.

To deploy objects

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

2. Select Deploy from the ribbon. You can also right-click on the selected object(s) and then select Deploy in the context 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 Currently 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 new configuration data. If you are redeploying an object, it is updated with new run-time data or new configuration data, depending on whether a change was made to a configured value, to a run-time value, and whether or not the Preserve Runtime Changes option is selected.

     • If both Deploy Changes and the Preserve Runtime Changes option are selected, values changed during run time are loaded as the object is redeployed. The new run-time value is used, even if you configure a new value in the IDE.

     • If Deploy Changes is selected but the the Preserve Runtime Changes option is NOT selected, new configured values set in the IDE are used, and will overwrite any changes made during run time.

   • Redeploy Original: 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. If the Preserve Runtime Changes option is selected, the object is deployed with the last run time value, even if you change the configured value in the IDE.

   • 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 run time, and if configuration values were changed in the IDE.

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

     • If a value was not changed during run time 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 run time and Redeploy Original and this option are checked, the object is deployed with the last run time value, even if you change the configured value in the IDE.

     • If a value was not changed during run time 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 Currently undeployed objects area, select the Deploy New Objects check box to start a normal deployment.

6. In the Deploy Status Mismatch area, select the Mark as Deployed check box 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 automatically 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 AVEVA Operations Control Management Console Platform Manager utility to put those objects on scan and to function properly in the run-time environment.

     Note: The Operations Control Management Console controls the state of the host/engine. The Object Viewer 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. Select OK to deploy the objects. The Deploy progress box appears. If you see error messages, see Deployment error messages. When the deploy is complete, select Close.