Creating and Configuring a New Connection

Add and configure a new RepConnector connection.

1. Right-click the connection profile, then select Add a New Connection.
2. On the Create a New Connection page:
   1. Enter a unique connection name. Do not use dashes or spaces.
   2. Select the inbound type, which is the origin or source of the data.

      The inbound type you select determines what outbound types are available.

      Select one of these inbound sources:

      • REPLICATION – if this connection will accept inbound data from Replication Server. When you select REPLICATION as the inbound type, you can select JMS, TIBCO, IBMMQ, or CUSTOM as the outbound type.

      • JMS – if this connection will accept inbound data from a JMS message queue. When you select JMS as the inbound type, you can select only DATABASE as the outbound type.

      • TIBCO – if this connection will accept inbound data from a TIBCO message queue. When you select TIBCO as the nbound type, you can select only DATABASE as the outbound type.

      • IBM MQ – if this connection is to accept inbound data from an IBM WebSphere MQ message queue. When you select IBM MQ as the inbound type, you can select only DATABASE as the outbound type.

   3. Select the outbound type, which is the target or destination for the data:

      • JMS – if this connection is to push outbound data to a JMS message queue. This option is available when you select REPLICATION as the inbound type.

      • TIBCO – if this connection is to push outbound data to a TIBCO message queue. This option is available when you select REPLICATION as the inbound type.

      • IBM MQ – if this connection will push outbound data to an IBM WebSphere MQ message queue. This option is available when you select REPLICATION as the inbound type.

      • CUSTOM – if this connection will push outbound data to a target other than the specific message queues listed in the outbound types field. This option is available when you select REPLICATION as the inbound type.

      • DATABASE – if this connection will push outbound data to a database. This option is available when you select a message queue (JMS, TIBCO, or IBMMQ) as the inbound type.

3. Click Next.
4. On the General Connection Information page:
   1. Verify or modify the Uniform Resource Locator (URL) in the “DBEventStream XSD URL” field.

      This is the URL for exposing the XML Schema Definition (XSD) over the network.

      The default URL is:

      http://<host_name>:<port_number>/RepraWebApp/dtds/dbeventstream.xsd

      where:

      • <host_name> is the host name of the target server’s http listener. The default name is “localhost.”

      • <port_number> is the port number of the target. The default port number is 8000.

      If the default information is incorrect, change localhost to the host name of the target server’s HTTP listener and 8000 to the port number on which the target server’s HTTP listener is listening.

      For example, if the host name is “mymachine”, listening at port 8090, the URL is:

      http://mymachine:8090/RepraWebApp/dtds/dbeventstream.xsd

   2. Select the logging level to use for this connection. Log Level defines the level, or type, of logging in the RepConnector log file, repra.log. The level you choose depends on whether you want to see only error messages or detailed messages in the log. The log file resides in the <AppServer>\repra\logs directory on Windows and the <AppServer>/repra/logs directory on UNIX. The default logging level is INFO.
      Choose:

      • FATAL – to see information about severe error events that could lead the application to abort.

      • ERROR – to see general errors related to events that could allow the RepConnector environment to continue running, as well as fatal errors.

      • INFO – to see informational messages that highlight application progress at a high level, as well as fatal errors and general errors.

      • WARNING – to see warnings about potentially harmful situations, as well as fatal errors, general errors, and informational messages.

      • DEBUG – to see details about general events that can help during debugging, as well as fatal errors, general errors, informational messages, and warnings.

   3. Choose Autostart Connection, to start the connection automatically whenever the application server starts. By default, this option is not selected.

      In a production environment, you may want to start the connection automatically when the application server starts to do the minimal amount of intervention when restarting servers.

      If you are developing and testing your RepConnector connections, you might not want to start the connection automatically when your application server restarts. Once you establish a successful connection, you may want to change the connection properties to automatically start the connection.

      Note: When you start a RepConnector connection, Replication Server attempts to connect to it. When you stop a RepConnector connection, and suspend the connection at Replication Server, Replication Server continues to attempt to connect to it, even though the connection is stopped.
   4. Choose Custom Plug-in Class to use a user-defined message formatter with RepConnector rather than the RepConnector default XML formatter.

      See Customizing the Sender and Formatter Processors.

   5. Choose the encrypted data option if the data from the messaging system is encrypted by Adaptive Server 15.0 encryption.
5. Click Next.
   The page you see next depends on the inbound type you selected. If you selected:

   • REPLICATION – the Replication Server Inbound Information page appears.

   • JMS – the JMS Information wizard page appears.

   • TIBCO – the TIBCO Messaging Information wizard page appears.

   • IBM MQ – the MQ Messaging Information wizard page appears.

6. Select Ping to verify that you have entered the information correctly.

   A Pinging Connection Status provides status on whether you have configured the information correctly.

   Note: You must update the repra_env.bat file on Windows or the repra_env.sh file on UNIX to include the messaging system’s libraries in the environment and restart your application server before you can use ping.

   Click OK to exit the status window.

7. Click Next.
   The page you see next depends on the outbound type you selected. If you selected:

   • JMS – message queue or topic, the JMS Information page appears.

   • TIBCO RV or RVCM message queue or topic – the TIBCO Messaging Information page appears.

   • TIBCO AECM message queue – the TIBCO Messaging Information page appears.

   • IBM MQ queues – the MQ Messaging Information page appears.

   • CUSTOM – and selected Custom Plug-in Class in the General Connection Information wizard page, the Plug-in wizard page appears.

   • DATABASE – the Database Connection Information page appears.

8. Click Next.

   The Summary page displays the values you entered for the new connection. These values are saved in a properties file called connection_name.props. This file resides in the repra/conf directory in your application server installation directory structure.

9. Verify the connection configuration information and select Finish to create the new connection.

   To change connection configuration information, select Back to return to the specific configuration page you want to modify. When you finish making changes, return to this Summary page and select Finish.

• Configuring Replication Information for REPLICATION Inbound Types
  If you inbound type is REPLICATION, enter the Replication Server inbound information and the Replication Server System Database (RSSD) information.
• Configuring JMS Information
  Define the JMS information using the Create Connection wizard if you are connecting to a JMS message queue or topic.
• Configuring TIBCO Information
  If you are using a TIBCO messaging system, define the TIBCO information using the Create Connection wizard.
• Configuring IBM MQ Information
  Define IBM MQ information.
• Configuring Custom Plug-in Information
  If you are using a custom message formatter or custom message sender processor, define the plug-in class information using the Create Connection wizard.
• Configuring Database Connection Information
  If your outbound connection is to a database, define the database connection information using the Create Connection wizard.