Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Engineering

Distributed Extract Hierarchy

  • Last UpdatedJan 26, 2022
  • 1 minute read

Where work needs to be execute on one database by two locations a Leaf Extract organisation is required. Below is a sketch that outlines how in a 2 level extract organisation this should be set up:

In this scenario the SAT2 users working on the EX2_SAT1 db are claiming objects from EX1 Primary at SAT1.

This can be done dynamically in Explicit Claim mode over the Daemon. However, the response can be variable causing the SAT2 users to be unsure as to the status of their claim. Therefore it is recommended that the project is organised in such a way that the EX1: Primary objects to be worked on at SAT2 are identified and marked by the SAT1 users and then an Admin process is run to Extract Claim the collection to the EX2_SAT1 Primary db at SAT2. When the work on the objects is complete the SAT2 users mark the objects as ready to be Issued and an Admin process is run to Extract Issue the collection back to EX1: Primary.

TitleResults for “How to create a CRG?”Also Available in