Before you can use the Event Replicator Target Adapter, perform the following steps:

1. Verify the Administration tool preferences and then configure definitions using the Administration tool that specify how Event Replicator Target Adapter processing occurs. To set up Administration tool preferences, read Setting Configuration File and Target Adapter Preferences.

   Once Event Replicator Target Adapter Administration tool preferences have been set, use the tool to set up the following definitions (in this order):

   Note:
   The Event Replicator Target Adapter must be stopped and restarted every time a definition is saved or deleted using the Administration tool. For this reason, we recommend that you shut down the Event Replicator Target Adapter prior to making changes to the definitions and restart the Event Replicator Target Adapter when all definition changes are complete. For information about stopping and starting the Event Replicator Target Adapter, read Shutting Down the Event Replicator Target Adapter and Starting the Event Replicator Target Adapter.

   1. Target definitions: These define the RDBMS data base or web service targets to which the Event Replicator Target Adapter should direct the replicated data. For more information, read Configuring Target Definitions for Event Replicator Target Adapter.

   2. Target database processing option definitions: These define any options regarding how the Event Replicator Target Adapter processes the data submitted to an RDBMS data base. At this time, there are no web service processing options. For more information, read Specifying Target Database Processing Options

   3. Source definitions: These define the messaging systems (webMethods EntireX or WebSphere MQ) from which replicated and associated target definition to use which the Event Replicator Target Adapter should direct the replicated data acquired from the source definition. For more information, read Configuring Source Definitions for Event Replicator Target Adapter.

2. Stop and restart any mainframe or open systems Event Replicator Servers that might be replicating data to your RDBMS. Stopping the Event Replicator Server will also clear out the Event Replicator Server queues so there are no unprocessed transactions in the queue. You will know this has happened when the Event Replicator Target Adapter console or log file displayed a message indicating that the Event Replicator Server has terminated.

3. If any of the source definitions you created are for messaging systems that are also used by an earlier version of the Event Replicator Target Adapter, stop the older version of the Event Replicator Target Adapter prior to starting up this version of the Event Replicator Target Adapter.

   Once all of the definitions are specified and the appropriate Event Replicator Servers have been stopped and restarted, Event Replicator Target Adapter processing can be activated (or may automatically be activated, depending on the settings in the source definitions). For more information, read Activating Event Replicator Target Adapter Processing .

   For information on where the Event Replicator Target Adapter log files are located, read Managing Event Replicator Target Adapter Log Files and Console Messages.