|
Context Copy operation is sometimes referred as Replication in this manual. |
The Copy configuration operation is used to configure one context similarly to another. It can be a User account, a Device, an Event Filter, an Alert, etc. This operation can be initiated through the AggreGate Client User Interface, for example, by dragging one System Tree node and dropping it on another node of the same type.
Internally, this operation modifies the values of the variables (properties) of the target context (the copy destination) according to the values of the variables in the source. A given value is copied from the source context only if the variable supposed to contain it (i.e, a variable with the same name) already exists on the destination context. The replication operation flows like this:
| • | If a variable is not readable in the source context, operation with this variable is aborted |
| • | If a variable is not writable in the target context, operation is aborted too |
| • | The server reads the variable value from the source context into the Data Table A |
| • | Then it reads the variable value from the target context into the Data Table B |
| • | Data from the Data Table A is copied into the Data Table B using Data Table Smart Copy operation |
| • | The server rewrites value of the variable in the target context by the Data Table B |
If an error occurs on any step, operation with the current variable is aborted. The copy process proceeds to the next variable.
Just before the operation begins, users may select variables to be copied. It is also possible to prevent certain fields from being replicated. In plus, new value of every variable may be corrected:
The copy operation returns a report in the following format:
Variable description |
Copy successful (yes or no) |
List of errors encountered during copy if this variable |
Here's what a report looks like:
Copy Configuration to Children Operation
The Copy to children operation is similar to the normal context copy operation, but it copies variable values from the source context to every child of the target context, not to the target context itself. This operation can be initiated, for example, by dragging a System Tree node representing some context, and dropping it on a node representing a group of contexts of the same type. In this case all contexts in the group will be configured like the object that was dropped.
Copy to children operation outputs a report in the following format:
Target context |
Variable name |
Copy successful (yes or no) |
List of errors encountered during copy if this variable |
Here's a sample report:
