Introduction to multisite control

This module is used to control the exchange of data between multiple sites.

You can, for example:

  • At one site: run the export and the import in virtually one process, and the latter can be run based on the results of the first.
  • At multiple sites: run the export at the source system, move or copy the resulting ASCII files to the target system and then run the import there.

The export batch and an import batch are linked. The exchange link links the batches from the source and target site at batch level. The link is set up according to the local autonomy model. This means that each site controls its own export procedure and import procedure. There is no master or slave.

The exchange links are stored at the target and point to the export batch at the source site. If an exchange link is defined, a subscription is stored at the source site, which points to the import batch at the target site. The link is active when both the exchange link at the target site and the subscription at the source site are available.

During a regular export, the Exchange module checks for subscriptions. In this case, a message is sent to the target site that defines which files are exported and where they are stored. The target site stores that information when the message is received. the Exchange module checks the received information from the source sites during a regular import to see if there is any data waiting to be imported. If this is the case, the files are copied from the source site to the target site and then they are imported. Finally the target reports to the source that the data has been imported.

Note: The figure only shows one exporting batch and one importing batch, but you can also define multiple targets per source or multiple sources per target.

To be able to use multisite control it is important that:

  • remote users are available for both systems (refer also to the Systems (ttaad0550m000) and Remote User Data (ttaad2501m000) sessions).
  • the Receive Remote Procedure Calls (daxch4200m000) session is running on both systems.