Event replicator software ag

A message is issued indicating which destination was deactivated. When a subscription is deactivated, all files that occur in that subscription and in no other active subscriptions are also deactivated. A message is issued indicating which subscription is deactivated.

Deactivation of a subscription does not cause deactivation of related destinations. Those destinations containing only subscriptions that have been deactivated simply receive no more data. When a file is deactivated, subscriptions containing the file remain active. Subscriptions that contain only files for which replication has been deactivated simply receive no more data. Subscriptions that contain both deactivated files and active files will continue to deliver replication data to the target application, even though only partially replicated data will be delivered.

Once a file has been deactivated, the target application will be responsible for determining what to do with any partially replicated data. The application may decide to keep the partial data, and thus avoid the potentially costly refresh of large files for which replication has or could have remained active all the time.

The target application has the choice to:. Store the partially replicated data in the target database, but deactivate access to that part of the database until full replication has been reestablished. Store the partially replicated data in some temporary file and pick it up once full replication is being reestablished. Meanwhile, access to the replicated data can continue, as of the time when replication for the file was deactivated. Deactivate some or all subscriptions that contain the file for which replication has been deactivated.

Deactivation of a file in the Event Replicator Server causes deactivation of the file in the Adabas nucleus. A message is issued, indicating which file was deactivated. When a database is deactivated, all of its currently active replicated files are also deactivated. Messages are issued indicating which files were deactivated. See the information above on file deactivation for more information on actions that can be taken when a file is deactivated. You can reduce the risk of Event Replicator Server replication pool overflows by requesting that the Event Replicator Server temporarily write replication transactions received from the Adabas nucleus to the SLOG system file.

If any record is modified more than once during a transaction, the nucleus makes available to the outside destination only the final instance of the modification of the record. This is done by consolidating modifications to the same record within the same user transaction, as follows:. For the sake of performance, no data consolidation occurs at the point the modification related data is collected.

Data consolidation occurs after a transaction is committed on WORK. The following rules apply to the consolidation of modifications to the same record during one transaction:. An update followed by another update is treated as one update. When a before image exists for a primary key and a before image exists from data storage, the before image for the primary key is used. Note: This rule is subject to the above rule regarding a before image of a primary key versus the before image from data storage.

There is an exception to these data consolidation rules: a delete followed by an insert to the same record will be treated as two separate modifications. In other words, the chronological order of the updates is maintained for each ISN in a file.

The nucleus notifies the Event Replicator Server when a transaction with replicated data has been committed. The nucleus discards the replication data after it has been fully processed by the Event Replicator Server. Replicated information is buffered in the Adabas nucleus in a new replication pool. The replication pool is updated solely by the code within the Adabas nucleus address space. Adabas temporarily or persistently produces more replication data than the Event Replicator Server or the messaging system can process.

When the Adabas replication pool becomes full, the replication system will deactivate replication for a file and a message is issued indicating which file was deactivated. When replication is inactive for a file, Adabas does not collect any further replicated updates for the file. An initial message will be generated when this value, expressed as a percentage of replication pool usage, is exceeded. When the interval expires, you will receive a message showing how many warning were suppressed, and warning messages can then resume.

The Event Replicator Server parses all replicated data received from the Adabas nucleus and receives inbound initial-state requests from the target application through the messaging system.

The following replication setup should be performed for an Event Replicator Server database. Subscriptions that specify the replication processing, transformation, and filtering that should occur for specific files.

Other definitions can also be specified, but are not required as, in many cases, defaults are provided. Note that if replication is deactivated for specific files, replication data from the Adabas nucleus for those files will not be processed by the Event Replicator Server.

Note that if a destination definition is deactivated, replication data from the Adabas nucleus will not be sent to those destinations. Likewise, if a subscription definition is deactivated, replication data for the files covered by the subscription may not be processed depending on what other subscription definitions are active.

In addition, you will need to activate subscription logging for specific destinations. For more information, read Using the Subscription Logging Facility. The following description summarizes the processing performed by the Event Replicator Server:. If an Adabas nucleus is not yet active, the nucleus contacts the Event Replicator Server during nucleus initialization.

The Event Replicator Server processes the received modified data according to the subscriptions defined in the replication definition parameters. After processing the data, the Event Replicator Server may apply user-customizable logic to the replication process for example, filtering, conversion, or transformation. The Event Replicator Server then delivers the replicated data to the messaging system destination for replication to the target application.

Each replicated transaction delivered to a target is assigned a unique sequence number. This sequence number is generated for each unique subscription-destination combination of the replicated transaction. In other words, if the same replicated transaction is delivered to two different destinations by a subscription, that transaction may have two different sequence numbers one for each destination. Initial-state requests may be needed to resolve an ambiguous state incurred by the target application; the request can contain requests for a single record, a set of records, or an entire file.

Replication data for one Adabas file must be processed by a single Event Replicator Server. No two Event Replicator Servers handle the same set of files from the same database. A replication pool separate from the Adabas replication pool is allocated in the address space of the Event Replicator Server.

This pool is used by the replication code running in the Event Replicator Server address space. It is used to store the decompressed and transformed data, along with other information. The Event Replicator Server temporarily or persistently produces more replication data than the messaging system can process.

An outage of a participating Adabas nucleus or message system occurs. When the Event Replicator replication pool becomes full, the replication system may deactivate its resources, including destinations, subscriptions, files, or databases. The replication system determines and deactivates the resource having the greatest impact on the Event Replicator replication pool usage. When a destination is deactivated, all subscriptions sent to that destination and to no other active destination will also be deactivated.

A message is issued indicating which destination was deactivated. When a subscription is deactivated, all files that occur in that subscription and in no other active subscriptions are also deactivated. A message is issued indicating which subscription is deactivated. Deactivation of a subscription does not cause deactivation of related destinations. Those destinations containing only subscriptions that have been deactivated simply receive no more data.

When a file is deactivated, subscriptions containing the file remain active. Subscriptions that contain only files for which replication has been deactivated simply receive no more data. Subscriptions that contain both deactivated files and active files will continue to deliver replication data to the target application, even though only partially replicated data will be delivered.

Once a file has been deactivated, the target application will be responsible for determining what to do with any partially replicated data. The application may decide to keep the partial data, and thus avoid the potentially costly refresh of large files for which replication has or could have remained active all the time. The target application has the choice to:. Store the partially replicated data in the target database, but deactivate access to that part of the database until full replication has been reestablished.

Store the partially replicated data in some temporary file and pick it up once full replication is being reestablished.

Meanwhile, access to the replicated data can continue, as of the time when replication for the file was deactivated. Deactivate some or all subscriptions that contain the file for which replication has been deactivated. Deactivation of a file in the Event Replicator Server causes deactivation of the file in the Adabas nucleus.

A message is issued, indicating which file was deactivated. When a database is deactivated, all of its currently active replicated files are also deactivated.

Messages are issued indicating which files were deactivated. See the information above on file deactivation for more information on actions that can be taken when a file is deactivated. The target application may send initial-state requests, status requests, and prior-transaction resend buffer requests to the messaging system for delivery to the Event Replicator Server.

For information on integrating the message system with your target application, read Integrating the Messaging System with the Target Application. Normally, only changed data is replicated. Note: On Solaris, the volume management daemon "vold" might be active.

During the installation, the Destination Location panel allows you to specify a different directory for the default Event Replicator Target Adapter source code program files directories. Source code, program files are stored in this location in addition to program data files that might be altered during execution by the product or by you using the Administration tool or other tools, as described in this documentation. The default name is sagenv.

If you would like to change it, type the fully qualified name of the Software AG environment file you want used for this installation, or click the Browse button to locate an existing file. On the Choose Programs panel, you can select the programs that are installed:. The Administration Service Options panel uses a default port number of for the Adabas Administration Service unless you change it.

The Install Service panel allows you specify that the Adabas Administration Service should be installed as a system service. It also allows you to identify the run level at which the service should be activated and to indicate whether the service should be started after installation. The Activate Installed Products panel allows you to select the products for which you want support in the Software AG environment file. The Software AG environment file is called, by default, sagenv.

You must do this before you can use the Event Replicator Target Adapter. To do this, change to the installation directory and run sagenv. Target Adapter Version 2.