Switch to standard view 
  Sybase logo

Installation and Release Bulletin Replication Server® Messaging Edition 15.2 for Linux, Microsoft Windows, and UNIX


Document ID: DC01091-01-1520-02

Last revised: November 22, 2010


Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase® Product Documentation Web site.

Accessing release bulletins at the Sybase Product Documentation Web site

  1. Go to Product Documentation.

  2. Select a product and language and click Go.

  3. Select a product version from the Document Set list.

  4. Select the Release Bulletins link.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.



The primary goal of a messaging system is to manage communication across heterogeneous systems enabling individuals throughout the enterprise to efficiently access and share information. A messaging solution must seamlessly integrate with your other IT resources and scale to meet your messaging needs, both now and in the future. The Replication Server® Messaging Edition (RSME) provides a messaging solution that addresses these challenges.

RSME captures transactions (data changes) in various databases such as Adaptive Server® Enterprise (ASE) and other non-Sybase databases such as Oracle, IBM DB2, and Microsoft SQL Server, and delivers them as events to external applications, either directly or through a message bus, in real time.


RSME components

The RSME includes these components:


RepConnector provides a nonpolling, nontrigger-based solution to database integration, building on the Replication Server noninvasive system to push database transactions into a traditional integration environment.

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


See the RepConnector 15.0.2 Configuration and Users Guide.

Replication Server

The Replication Server component is used for distribution and synchronization of operational data in a heterogeneous replication environment. Replication Server keeps data up to date in multiple databases so that you can access local data instead of remote, centralized databases.

Replication Server works to distribute data over a network by:

See the Replication Server 15.2 Administration Guide.

Replication Agent

The Replication Agent component captures transactions in a primary database and sends them to a Replication Server for distribution to replicate targets. Replication Agent extends the capabilities of Replication Server by allowing non-Sybase data servers to act as primary data servers in a replication system based on Sybase replication technology.

Replication Agent supports data replication from Oracle, Microsoft SQL Server, and IBM DB2 UDB installed on UNIX, Linux, and Microsoft Windows.

See the Replication Agent 15.2 Administration Guide.


EAServer is an application server that includes an integrated set of development tools that you use to deploy Web applications that support high-volume traffic, dynamic content, and intensive online transaction processing. EAServer provides a framework for deploying the middle-tier logic of distributed component-based applications.EAServer simplifies creating and administering Internet applications that service thousands of clients simultaneously. EAServer components execute on the middle tier between end-user client applications and remote databases. EAServer provides efficient management of client sessions, security, threads, third-tier database connections, and transaction flow, without requiring specialized knowledge on the part of the component developer.

See the EAServer 6.0 Feature Guide.

Supported platforms

Table 1 describes the compatible platform and operating system configurations for RSME.

Table 1: RSME requirements


Operating system version

HP-UX Itanium

HP-UX 11.31 (11i v3) on Itanium (64bit)

IBM RISC System/6000

IBM AIX 5.3 (64-bit)


  • RedHat Advanced Server 4.0, Kernel version 2.6.9-22.ELsmp

  • SuSE Linux Enterprise Server 10.0, Kernel version

Microsoft Windows

  • Microsoft Windows XP Professional Service Pack 2 or later

  • Microsoft Windows Server 2003, Standard Edition or Enterprise Edition

  • Microsoft Vista

Sun Solaris (SPARC)

Solaris version 9.0 or 10.0 (32-bit and 64-bit)

Note:Replication Agent is only supported for Sun Solaris (64-bit).

Note:Replication Agent for Microsoft SQL Server is supported only on Windows platform.

Refer to the individual product’s release bulletin for any patch level information for your operating system. For a complete list of supported operating systems, see the Sybase Platform Certification Web site.


RSME deployment architecture

Figure 1 shows a distributed system that contains the RSME components.

Figure 1: RSME deployment architecture

License requirements

RSME uses the Sybase Software Asset Management (SySAM) licensing mechanism for license administration and asset management tasks. After you purchase RSME components, go to the Sybase Product Download Center (SPDC) Web site to generate and download the licenses. See the Sybase Software Asset Management Users Guide.

Deployment and licensing options for RSME components

Table 2 describes the deployment and license options for RSME components.

Table 2: Deployment and licensing options for RSME components


Deployment and licensing options


  • A SySAM served or unserved license is required.

  • Installation is allowed on as many machines in the distributed environment for which you have purchased licenses.

Replication Server

  • A SySAM served or unserved license is required.

  • Installation is allowed on as many machines in the distributed environment for which you have purchased licenses.


  • Obtain the RSME .tgz file that contains the EAServer license, Replication Agent license, and the Readme file from the SPDC Web site or the Getting Started CD.

  • Installation is allowed on as many machines in the distributed environment for which you have purchased licenses.

    Note:Select Advanced Edition (AE) as your product edition from the drop-down list when installing EAServer 6.2.

Replication Agent

  • Obtain the RSME .tgz file that contains the EAServer license, Replication Agent license, and the Readme file from the SPDC Web site or the Getting Started CD.

  • Installation is allowed on multiple machines that contain the supported database in the distributed environment.

Installing static license for EAServer 6.2 Advanced Edition

This section describes installing the SYBASE_RSME_EAS.lic file that contains a valid SySAM license for EAServer component in RSME 15.2.

  1. Install EAServer 6.2 component from RSME 15.2 release, if not already installed.

  2. Stop EAServer if it is running.

  3. Copy the included EAServer license file to these locations:

    • UNIX – $SYBASE/EAServer/licenses

    • Windows – %SYBASE%\EAServer\licenses

    where $SYBASE or %SYBASE% is the installation directory where EAServer 6.2 Advanced Edition is installed.

  4. Restart EAServer.

  5. Verify the log file to confirm that EAServer has started in advanced mode. In your log file, you should see lines similar to these lines:

    2009-04-30 18:04:22.133 INFO  main
    [ApplicationServer:<servername>] Sybase Enterprise
    Application Server Advanced Edition
    2009-04-30 18:04:22.133 INFO  main
    [ApplicationServer:<servername>] Server license
    notice: Licensed for use with Sybase Replication
    Server Messaging Edition (RSME) under the terms
    specified in the RSME PSLT

Installing static license for Replication Agent 15.2

This section describes installing the SYBASE_RSME_RAX.lic file that contains a valid SySAM license for Replication Agent component in RSME 15.2.

  1. Install Replication Agent 15.2 component from RSME 15.2 release, if not already installed.

  2. Stop Replication Agent if it is running.

  3. Copy the included Replication Agent license file to these location:

    • UNIX – $SYBASE/SYSAM-2_0/licenses

    • Windows – %SYBASE%\SYSAM-2_0\licenses

    where $SYBASE or %SYBASE% is the installation directory where Replication Agent 15.2 is installed.

  4. Restart Replication Agent instance.

  5. Verify the Replication Agent log file to determine if Replication Agent has started successfully. You can access the Replication Agent log files at these locations:

    • UNIX – $SYBASE/RAX-15_2/<instance_name>/log/<instance_name>.log

    • Windows – %SYBASE%\RAX-15_2\<instance_name>\log\<instance_name>.log


Product compatibilities

This section describes the compatibility of RSME components with non-Sybase products.


Table 3 lists the enterprise messaging system versions supported by RepConnector 15.0.2 ESD #1.

Table 3: Enterprise messaging systems compatible with RepConnector

Enterprise messaging system


TIBCO Rendezvous


TIBCO Enterprise for

4.3.0 (JMS version)

TIBCO Active Enterprise




Sonic MQ


See the complete list of supported enterprise messaging systems. Select RepConnector from the product list in Search by Base Product.

Replication Agent

Table 4 lists the primary database server versions supported by Replication Agent 15.2.

Table 4: Databases compatible with Replication Agent



IBM DB2 Universal Database

Enterprise Edition 8.2.2, 9.1, 9.5a

Oracle Server

10g (10.1, 10.2), 11g (11.1)

Microsoft SQL Server


a. Replication Agent support for UDB 9.5 is limited to the same features that Replication Agent supports for UDB 9.1. Replication Agent does not support the following features added in UDB 9.5: large identifiers, DECFLOAT datatype, and XML datatype.

Replication Agent requires a JDBC™ 3.0-compliant driver for the primary data server. Table 5 lists the JDBC driver versions required to support connectivity between Replication Agent 15.2 and the primary data server.

Table 5: Drivers compatible with Replication Agent



DB2 Universal Database Administration Client

8.2, 9.1 (64-bit on all UNIX platforms; 32-bit on Linux and Windows platforms)

Oracle JDBC driver

10.2 or 11.1 for JDK 1.4 and 1.5

Microsoft SQL Server JDBC driver


For Replication Server 15.2 and EAServer 6.2 product compatibilities, see the release bulletins for the appropriate platforms for these two products.


Installing RSME components

Install each RSME component separately, following the instructions in each product's installation guide.

Be aware of these considerations:


Configuring and administering RSME components

This section describes how to configure and administer the RSME components.

RepConnector configuration and management

RepConnector Manager is a plug-in to the Eclipse framework that you can use to manage RepConnector runtime component activity. You can run RepConnector Manager on the local machine where the RepConnector runtime component is installed, or on any remote machine that can access the machine on which the RepConnector runtime component is installed. To access the remote machine, verify that the HTTP connection to the application server on which the RepConnector runtime component is deployed and running, is available throughout the network. Use the RepConnector Manager to configure the RepConnector connections.

See the RepConnector 15.0.2 Configuration and Users Guide.

Replication Server and Replication Agent configuration and management

Use the Replication Manager (RM) plug-in to manage and monitor Replication Server and Replication Agent instances.

You can also configure, manage, and monitor a Replication Agent instance using any Open Client™ application (such as isql) that is capable of communicating with the Sybase Tabular Data Stream™ (TDS) protocol.

For more information on using Replication Manager, see the Replication Manager online help.

Additionally, see the Replication Server 15.2 Configuration Guide and the Replication Agent 15.2 Administration Guide.


Sample scenarios

This section shows through a variety of samples, various ways you can use RSME components to meet the needs of your enterprise.

Scenario: Managing risks in financial services

A trading company wants to offer proactive notifications of changes to customer data and securities data. For example, if the buy limit for a security is reached, the company wants to immediately send this information to all trading systems. The system that is currently in place must poll the securities operational database, which introduces information lag, which in turn, introduces the likelihood of credit limit breaches. The current implementation does not allow the company lessen this risk, or to identify security breaches early.

The current system periodically polls the database that holds credit limit thresholds resulting in performance degradation to the operational systems. The frequency of polling determines how quickly the trading company can identify whether there is a credit-limit break.

The trading company wants to automatically prevent trading once a customer’s credit limit has been reached. Polling the securities operational database is not frequent enough to accomplish this goal

At various locations, customer and securities data are stored in Sybase Adaptive Server Enterprise (ASE) and Oracle databases.

RSME pushes time-critical data from heterogeneous databases to the messaging architecture, eliminating the information lags created by batch updates or intermittent polling processes.

When a customer places a trade request, the trading company uses RSME to send messages from their customer and securities databases to a message bus. The trade request is read by a client application that computes credit risk. If the credit limit is not reached, the customer trade is allowed. If the buy limit has been reached, all trading systems connected to the message bus are immediately notified to take the necessary precautionary measures.

The events, or messages are delivered to external applications in real time through a message bus such as IBM WebSphere MQ or JMS.

Figure 2: RSME data flow

Scenario: Publishing from a database to a message bus

This scenario shows how you can use RSME to capture events from various databases and publish the events in real time over a message bus. In Figure 3, events are published from different database systems to a number of applications. Inventory management is running on ASE. A customer relationship management (CRM) application is running on an Oracle database, and a manufacturing quality control system is running on IBM DB2.

In this configuration, a Sybase certified message bus can be used. A business activity monitoring application requires real-time notification of critical events from all three of the source databases. The customer event management application enables the organization to notify customers proactively based on critical events. The organization may also want to, for example notify customers if they have been sent defective items as identified by the quality control system. An operational data store is updated in real-time from all three of the source systems.

Figure 3: Publishing from any database to any message bus

Known issues

For known issues concerning RepConnector, Replication Agent, Replication Server, and EAServer see the appropriate product and version release bulletin.

The known issues for Replication Server and Replication Agent below, are in addition to those described in the individual product release bulletins.

IBM AIX licensing on Replication Server 15.2 and Replication Agent 15.2

[CR #570705] In Replication Server 15.2 and Replication Agent 15.2 on IBM AIX, there is a change to the process of how Replication Server and Replication Agent determines the number of CPUs available to it. Customers running Replication Server, or Replication Agent on IBM AIX with logical partitions may find that the number of CPUs reported has changed with 15.2. This happens because Replication Server and Replication Agent now counts the total number of CPUs available to the partition. This may prevent these products from starting.

Replication Server and Replication Agent does not currently support subcapacity licensing for IBM LPAR. If you believe you may encounter this issue, contact Sybase Customer Support to raise a support incident.

Known issues for the Sybase installer

This section describes known issues with the Sybase installer that are not specific to a particular data server type.

Cannot view text fields properly when using Hummingbird Exceed from Windows

If you use Hummingbird Exceed from a Windows workstation to install Replication Agent on a UNIX host, you might not be able to view all of the text fields on the Sybase installer screens.

Workaround: Either use a native X-Windows session to run the Sybase installer, or run it in console or silent mode. See the Replication Agent Installation Guide.

Sybase Central fails to open after uninstalling Replication Agent

[CR# 399954] Uninstalling Replication Agent removes the SYBASE system environment variable. Consequently, Sybase Central™ cannot open.

Workaround: Redefine the SYBASE system environment variable.


Documentation updates and clarifications

RepConnector only supports Sybase certified J2EE-compliant JMS messaging systems. Any reference in the RepConnector Configuration and Users Guide that implies that RepConnector supports any J2EE-compliant JMS messaging system is in error.

RepConnector Configuration and Users Guide

Chapter 1, “Overview”

Replace this text in the “Introduction” section:

The corrected text is:

Chapter 4, “Configuring RepConnector”

The text in the last Note of the “Configuring the RepConnector” section is incorrect. The corrected text is:

Note:To set the environment for the messaging system, you must modify the %REPRA_HOME%\bin\repra_env.bat file on Windows, and $REPRA_HOME/bin/repra_env.sh file on UNIX, where %REPRA_HOME% or $REPRA_HOME is the RepConnector installation directory.

Chapter 7, “Customizing the Sender and Formatter Processors”

The text in the first paragraph of the “Customizing the sender processor” section is incorrect. The corrected text is:

RepConnector has built-in senders that can post replication events to Sybase certified JMS, TIBCO, and IBM MQ messaging systems. It also provides an API for creating custom senders that can route replication events to anywhere that is accessible to Java, such as e-mail applications, files, or printers.


Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.


Other sources of information

Use the Sybase Getting Started CD and the Sybase Product Documentation Web site to learn more about your product:

Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications

  1. Point your Web browser to Technical Documents.

  2. Click Partner Certification Report.

  3. In the Partner Certification Report filter select a product, platform, and timeframe and then click Go.

  4. Click a Partner Certification Report title to display the report.

Finding the latest information on component certifications

  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.

Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.

Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance

  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.


Accessibility features

This document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology, such as a screen reader, or view it with a screen enlarger.

The HTML documentation has been tested for compliance with the U.S. government Section 508 Accessibility requirements. Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites.

For a section 508 compliance statement for Sybase products, go to the Voluntary Product Assessment Template

Note:You might need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool.

For information about how Sybase supports accessibility, see Sybase Accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.

Back to Top
© Copyright 2010, Sybase Inc.