The connect command has been added to turn Replication Server into a gateway to its RSSD, ID server, or to a remote Replication Server.
Issuing the connect command requires
an sa role for the first login to Replication
Server.
connect [to] [rssd | idserver | srv_name | ds_name.db_name]
Parameters:
rssd – turns Replication Server into a gateway to its RSSD. Allows the gateway to use RSSD_primary_user and RSSD_primary_pw entries in its configuration file.
idserver – turns Replication Server into a gateway to its ID server, providing that the Replication Server itself is not the ID server. Allows the gateway to use ID_user and ID_pw entries in the configuration file.
srv_name – the name of the remote Replication Server you want the gateway to connect to. The Replication Server gateway uses RSI to log into the remote server, and requires a direct route to the remote server.
Replication Server cannot directly connect to itself.
However, you can work around this by using a cascading connection.
ds_name.db_name – the name of the remote data server and database that you want the gateway to connect to. The Replication Server gateway uses the maintenance user to log into the remote data server. This allows you to perform tasks that maintenance users of the designated database are permitted to do. However, you cannot access the other databases defined in the data server you connected to.
Replication Server gateway can directly connect to Adaptive Server, and to Sybase® IQ data servers that do not require Enterprise Connect Data Access (ECDA). For other data servers, Replication Server gateway has to use the ECDA to connect the Replication Server and the remote data server.
