RepConnector provides a non-polling, non-trigger-based solution to database integration, building on the Repliciation Server non-invasive system to push database transactions into a traditional integration environment. With RepConnector, there is no need to poll a database for changes, or to add triggers for event notification.
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 can 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 WorkSpace 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
Transforms incoming database events into XML messages, and routes them into configured message queues
Can transform incoming database events into their application-specific format
Can route incoming database events to any destination
Detects message events and routes them to database tables
Supports EAServer 6.02 as well as WebLogic 10.0 application servers
