RepConnector is designed based on the JCA (Java Connector Architecture) specification of J2EE. It runs in the J2EE-compliant application server environment. The architecture consists of three modules:
Event Capture Module – listens for events from Replication Server or from the messaging system. For Replication Server, the module provides a TCP socket that listens for Replication Server events. For the messaging system, the module acts as a client and listens on the messaging bus for messaging events.
Event Transformation Module – transforms an event before the event is routed to its destination. In real time messaging, RepConnector transforms the event to XML. Alternatively, you can customize the module to add a customized transformer plug-in. In the reverse case (messaging to database), RepConnector transforms the event to a SQL statement.
Event Sender Module – routes the even to a messaging system, in the case of real time messaging, or to a database for reverse direction. Alternatively, you can customize the module to add a customized message sender plug-in.
For real-time messaging, RepConnector uses Replication Server technology to detect business events that occur in the database. Upon receiving events from Replication Server, RepConnector transforms those events to XML-formatted messages, then sends the XML messages to the configured messaging systems. RepConnector guarantees that the message routing is transactional.
In the reverse direction, RepConnector detects events from any of the supported messaging systems, transforms those events to SQL statements, and sends them to the configured database. These incoming events are in either SQL commands or an XML representation of SQL commands.
