Configuring the environment for a custom sender or formatter  Configuring replication information for REPLICATION inbound types

Chapter 5: Configuring RepConnector

Creating RepConnector connections

StepsAdding and configuring a new connection

This procedure includes all the steps required to add a new connection; however, some steps are described only in summary. Subsequent procedures give the details of these steps and are referred to from this procedure.

  1. Right-click the connection profile.

    For example, right-click the EAServer:8080 connection profile to create a RepConnector connection defined by the EAServer:8080 connection profile.

  2. Select Add a New Connection.

    The New Connection wizard starts and the Create a New Connection page appears.

  3. On the Create a New Connection page:

    1. Enter a unique name in the Connection Name field. 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 type options are available.

      Select one of the following 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, or IBMMQ 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 inbound type, you can select only DATABASE as the outbound type.

      • IBMMQ – 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 must select DATABASE as the outbound type.

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

      Select one of the following outbound targets:

      • 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.

  4. Click Next.

  5. 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 host name is “localhost.”

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

      The default URL is:

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

      For example, if the host name is “mymachine,” which is 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 the <AppServer>/repra/logs directory. The default logging level is INFO.

      Choose:

      • FATAL – to see information about very 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 the progress of the application 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 might want to start the connection automatically when the application server starts because you need 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 have established a successful connection, you can change the connection properties so that the connection starts automatically.

      NoteWhen you start a RepConnector connection, Replication Server attempts to connect to it. When a RepConnector connection is stopped, suspend the connection at Replication Server because Replication Server continually attempts to connect to it, even though it 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 Chapter 7, “Customizing the Sender and Formatter Processors,” for information about how creating a user-defined message formatter.

    5. Choose the encrypted data option if the data from the messaging system is encrypted by Adaptive Server 15.0 encryption.

  6. Click Next.

  7. The next page that appears depends on what you selected for inbound type on the Create a New Connection page.

    If you selected:

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

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

    NoteYou must update the repra_env.sh file to include the messaging system’s libraries in the environment and restart your application server before you can use the ping. See “Configuring the RepConnector” for more information.

    Click OK to exit the status window.

  9. Click Next.

  10. The next page displayed depends on what you selected for outbound type on the Create a New Connection page.

    If you selected one of these message queues or topics:

  11. Click Next. The Summary page wizard page appears.

    The Summary page appears, which summarizes the values you entered for the new connection. These values are saved in a properties file on your local machine called connection_name.props, where connection_name is the name of the connection. This file resides in the repra/conf directory in your application server installation directory structure.

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

    To change the 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.




Copyright © 2007. Sybase Inc. All rights reserved. Configuring replication information for REPLICATION inbound types

View this document as PDF