Once Event Replicator Target Adapter has been installed and your relational database has been set up properly, you can activate Event Replicator Target Adapter processing.
To activate Event Replicator Target Adapter processing:
Verify that you have proper authorization privileges to maintain the RDBMS tables.
Effective with Event Replicator Target Adapter 2.7, user authorization to maintain any new RDBMS tables via Event Replicator Target Adapter is inherited from the site's privilege settings for the database. Authorization is managed by the user's RDBMS privileges and not by Event Replicator Target Adapter. Event Replicator Target Adapter will no longer grant RDBMS privileges to the user. Therefore, if you want to use Event Replicator Target Adapter to maintain tables in an RDBMS, verify that your RDBMS authorization privileges are correct for the maintenance you want to perform.
Verify that appropriate target definitions and target database processing option definitions have been created in the Event Replicator Target Adapter Administration tool. One target definition should be created for each RDBMS target to which you want data replicated. A target database processing option definition is only necessary if the settings in the default target database processing option definition are not sufficient. For more information, read Configuring Target Definitions for Event Replicator Target Adapter and Specifying Target Database Processing Option Definitions.
Verify that appropriate Event Replicator Server queue definitions have been set up for the messaging system (webMethods EntireX or WebSphere MQ) you are using. For more information about maintaining queue definitions, read the documentation at one of the following links:
Verify that you have corresponding source definitions created in the Event Replicator Target Adapter Administration tool for every IQUEUE definition you need to use to replicate data from your mainframe Adabas to your relational database. For information on configuring source definitions in the Event Replicator Target Adapter Administration tool, read Configuring Source Definitions for Event Replicator Target Adapter.
Verify that appropriate Event Replicator Server subscription definitions have been set up for data replication to your relational database. For more information about maintaining subscription definitions, read the documentation at one of the following links:
Verify that a global format buffer and field table (GFFT) have been generated for the subscription definition. To use Event Replicator Target Adapter, you must use generated global format buffers. To generate a global format buffer and field table (GFFT) using the Adabas Event Replicator Subsystem, read Generating a GFB.
If you want to use UTF-8 character encoding, you must verify that your GFB field lengths are increased as required to accommodate the character set referenced by the code page you select and the data requested in the GFB. You can increase these field lengths manually by editing the GFB itself or by editing the Predict file or data definition module (DDM) used when the GFB is generated.
Save the subscription definitions.
Edit the destination definitions used by the subscriptions you modified in the previous steps.
Verify that the destination class (DCLASS parameter) is specified as "SAGTARG" for each destination.
DCLASS=SAGTARG cannot be specified for Adabas or file destinations (DTYPE=ADABAS or FILE). It is only valid for webMethods EntireX, WebSphere MQ, or NULL destinations. When DCLASS=SAGTARG is specified, the ADARUN RPLPARMS parameter must be set to "FILE" or "BOTH" to provide access to any field table (GFFT) definitions.
Optionally, specify keyword "NOSPRE" for the destination class parameter (DCLASSPARM parameter) if you do not want the subscription name to prefix the names of the tables produced by the Event Replicator Target Adapter. When "NOSPRE" is specified, the schema file name (Predict view name) alone is used for the table names; when "NOSPRE" is not specified, the subscription name prefixes the Predict view name in the table names.
For more information about specifying the destination class in a destination definition, read the documentation at one of the following links:
Save the destination definitions.
Stop and restart the Event Replicator Server or refresh the destination and subscription definitions, as described in RPLREFRESH Command.
Activate the destination definitions and the subscription definitions you modified in the previous steps. For more information, read one or more of the following documents:
To activate destination and subscription definitions using Adabas Online System (AOS), read Managing Replication Definitions from AOS.
To activate destination definitions using an Event Replicator Target Adapter batch utility, read Controlling Event Replicator for Adabas Destination Definitions.
If the subscription definitions are already activated, deactivate them first and then reactivate them to pick up the changes made in these steps.
Verify that the message systems referenced by your Event Replicator Server queue definitions and your Event Replicator Target Adapter source definitions are started or that their associated source definitions in the Administration tool have Autostart selected (checked).
If it is not already started, start the Event Replicator Target Adapter.
Event Replicator Target Adapter processing is activated and replicated Adabas data will be transformed and applied to your RDBMS.
The Event Replicator Target Adapter will not process updates for a field that is the primary key for an RDBMS table or for any fields that comprise a composite key for the table.