This rule imports change history records from the subscriber database files to the publisher database files.
When to use this rule
Cayosoft Administration Services can be combined for a load balancing and fault tolerance as a replication group. For more information, please see the High availability & replication article.
All records related to change history are stored on the same service where the operation is performed and are not replicated. For example, if delegated administrator performs reset password operation on a Subscriber 1, he can see the record about this operation only in the change history in Web Portal connected to Subscriber 1. Other subscribers and publisher service don't know about this operation.
Starting with Cayosot Administrator Service 6.x version, the database on publisher service becomes a single database to store change history records and work items for the entire replication group. All requests from subscriber services to perform CRUD operations (create, read, update, delete) are redirected to publisher service. Databases that store change history on subscribers are not used anymore. Thus, the administrator has access to change history records and work items regardless of which service he is connected.
Use this rule after upgrade to 6.x version to import change history records from subscriber service to publisher service:
- When you already have the replication group configured in your environment
- When you are going to configure the replication group
This rule copies change history records from all subscriber services databases to publisher service database.
Folder with DB files
This section defines the output format of this rule.
To get more information about this section, please see the Output section article.
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Enforce/Schedule section article.
|6.0.0||The rule was introduced in the product.|
Please sign in to leave a comment.