About BI Gateway model deployment

You deploy the AVEVA BI Gateway model, which includes the DataSource, Dimension, and Measure objects to the AVEVA BI Gateway. The deployment provides the AVEVA BI Gateway model to the AVEVA BI Gateway.

AVEVA BI Gateway objects with invalid configurations are not deployed. An AVEVA BI Gateway object configuration is considered invalid if the configuration has changed from a previously deployed state, or if the representation is not created in the datastore during run time.

The Explorer view shows an icon indicating the deployment status of the AVEVA BI Gateway objects. When a new AVEVA BI Gateway object is created, it is shown as "not deployed" and is updated to "deployed" after deployment.

Once an Object is deployed to the Runtime, you cannot make changes to the deployed object. A copy of the object is created if it detects any requested changes to allow users to continue working with the object, even though it is deployed.

When you open an object in the AVEVA BI Gateway, it references and displays as applicable, the latest version of all of its dependee objects, regardless of the deployment state.

This is based on the assumption that only one Object can be loaded at a time by the AVEVA BI Gateway. When a dependee object that is deployed is further modified and saved, and a dependent object is opened, the dependent object will automatically load the dependencies based on the latest version of the dependee object and not the deployed version. This implies that there is not a way to view the dependent object along with its dependencies from a version of the dependee object that is not the latest.

Any saved modifications done to the dependee object, as seen from within a dependent object, will need to be reconciled with a dependent object as required. Further, a dependent object cannot be deployed when a corresponding dependee object is in an undeployed state or is in "Deployed with pending changes" state. A message is shown to the user indicating the dependee objects that should be in the deployed state. Similarly, an object cannot be deleted if it has one or more dependent objects. The dependencies will first need to be removed to delete the object.

Even if a dependee object has a change that is not directly related to changes done in a dependent object, a dependee object cannot be in an undeployed or deployed with pending changes state when a dependent object is deployed.