RepConnector Architecture

RepConnector is based on the JCA (Java Connector Architecture) 1.5 specification of Java EE 6. It runs in a Java EE-compliant application server environment.

The architecture consists of three modules:
  • Event Capture – listens for events from Replication Server or from the messaging system. Event Capture provides a TCP socket that listens for Replication Server events, and acts as a client for the messaging system, listening on the message bus for messaging events.

  • Event Transformation – transforms an event before it is routed to its destination. In real-time messaging, RepConnector transforms the event to XML. You can also customize the module to add a customized transformer plug-in. When you send a message to the database, RepConnector transforms the event to a SQL statement.

  • Event Sender – by default, routes the event to a messaging system or to a database. You can customize the Event Sender to send events to virtually any endpoint.

For real-time messaging, RepConnector uses Replication Server technology to detect business events as they 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 either SQL commands or an XML representation of SQL commands.

RepConnector Architecture
This figure depicts the architecture for RepConnector.