The summarized overview of the different components from the back-end server, Adaptive Server® Enterprise, and Replication Server, as well as the information in configuring the RepConnector to deliver a TIBCO AE message to a TIBCO message bus are described.
There is a table called REP4 in a database called repdb that resides in Adaptive Server Enterprise. This table contains two columns called repName and repCode.
Inbound Type=REPLICATION Outbound Type=TIBCO TIBCO Message Type=AECM AEConfiguration=d:\sybase\appserver\repra\conf\ae.props AE Message Generator =MyMsgGenerator
The SDK application configuration file contains information that is required to connect to the SDK repository, and user-defined parameters that can be used by the customized message generator.
application_name=simpleSDK_adapter application_version=1.0 application_info=fileadapterinfo config_URL=/tibco/private/adapter/sdkTest_Adapters/simpleSDK_adapter remote_repository=F:/appserver/repra/conf/sampleSDK.dat data_publish_name=myPub pub_subject=repraTest.subject1 pre_registered_subscribers=myCmListener,myCmListener2 command_args=-system:repourl ../repra/conf/sampleSDK.dat -system:configurl /tibco /private/adapter/sdkTest_Adapters/simpleSDK_adapter context_schema_class=SybContext native_schema_class=SybNATIVEMSG commonmsg_schema_class=SybCommonMSG_UDS ContextKeys=repName,repCode
The example defines three schema class names and the context keys that map to the definition in the customized SDK repository design.
See the %REPRA_HOME%\sample\client\MyMsgGenerator.java file on Windows or $REPRA_HOME/sample/client/MyMsgGenerator.java file on UNIX for an example for the customized AE message generator class.