Introduction

With RepConnector, there is no need to poll a database for changes, or to add triggers to notify of events.

Configuring RepConnector requires the configuration of other servers and software in your RepConnector environment.

RepConnector provides adapters for sending to TIBCO, IBM MQ, SonicMQ, or any J2EE-compliant JMS messaging system. It also allows you to send messages to virtually any other user or application.

RepConnector:

• Delivers database events and metadata from Replication Server to the configured destination.

• Follows transactional behavior

• Manages connections using

  • RepConnector Manager, which is a GUI in the Eclipse framework

  • ratool, which is a command line utility

• Groups database events into a single transaction

• Supports text and image datatypes

• Parses replication events and generates XML documents

• Shares a queue among multiple RepConnnectors

• Transforms incoming database events into XML messages, and routes them into configured message queues

• Transforms incoming database events into their application-specific format

• Routes incoming database events to any destination

• Detects message events and routes them to database tables

• Supports EAServer 5.2 and WebLogic 8.1 application servers