Replication Server Manager (RSM) consists of:
RSM Client (Sybase Central and the Replication Server plug-in), an Open Client application that lets you monitor, diagnose, and manage a replication system. The RSM Client includes a graphical user interface (GUI) integrated with Sybase Central.
RSM Server, an Open Server application that translates and communicates requests from an RSM Client. The RSM Server performs the following tasks:
Retrieves metadata from data servers
Manages and monitors Replication Agents, Replication Servers, Open Servers, and other RSM servers
Monitors and responds to replication system events
RSM, as a client, can log in to one or more RSM Servers. Each server, in turn, can have a relationship with any data server, Replication Server, and Replication Agent that you want RSM Server to manage.
At least one RSM Server is required. The RSM Server must run somewhere on your network. The RSM Server is available on both UNIX and Microsoft Windows platforms.
If RSM is used to access the system log of a Sybase replication system component (Replication Server, Sybase Replication Agent, or DirectConnect gateway), an RSM Server must have access to the log file from the server where the RSM Server is running.
You must have the following information for each server to be added to the RSM Server domain:
The server name
The type of server
If you are adding a non-Sybase data server, you need to know:
The access server you will use to obtain metadata from the non-Sybase data server (a Replication Agent or a DirectConnect gateway)
The name of the server or the name of the Replication Agent that you use to manage the server
The user ID and password used to administer the server
The user ID must have System Administrator privileges
on the server.
The user ID and password of the RSSD primary user (Replication Server only)
The user ID and password of the RSSD Database Owner, if it is different from the RSSD primary user (Replication Server only)
The location of the log file to monitor
Before an RSM Server can interact with the servers in a replication system, you must define the RSM Server domain. The RSM Server domain is the set of Replication Servers, data servers, Replication Agents, RSM Servers, and Open Servers that you want an RSM Server to manage.
The servers that you add to a RSM Server domain can be anywhere in your network. This allows you to manage replication systems that are distributed worldwide.
An RSM Server must have an entry in its interfaces file (interfaces for UNIX or sql.ini for Windows) for every server (data server, Replication Server, Replication Agent, and so on) in its domain.
If the RSM Client and the RSM Server run on different machines, the sql.ini file on the RSM Client machine needs entries only for the RSM Servers to which the RSM Client will connect.
An RSM Client must have an entity in its interfaces
file for every RSM Server that it connects to.
The following limitations apply to Replication Server Manager version 12.6:
The RSM Client (Sybase Central) is available only on Microsoft Windows platforms.
Support for Adaptive Server Anywhere (ASA) as a data source is not provided in RSM. RSM supports ASA as a generic Open Server component, meaning it cannot be managed or configured, but it can be tested to determine if it is active.
RSM does not manage or monitor the Replication Agent for DB2 UDB for OS/390. RSM can manage a replication system where DB2 for OS/390 is either a primary or replicate data server.
RSM cannot invoke the Sybase Replication Agent pdb_xlog command. For more information about the pdb_xlog command, see the Sybase Replication Agent Administration Guide.
Online help is the primary documentation for Replication Server Manager. You can also find RSM information in Chapter 3, “Managing Replication Server with Sybase Central” in the Replication Server Administration Guide.
