SAP Replication Server Routing

How does it work?

In a "standard" replication - we have a replication definition and subscription that declare the replication between database A to database B (and C, D, ...).

In a routing replication there is one more step before the target replicated database - another RS.

The second RS should know when and what to replicate to it's target DB.

The route from The first RS to the second, and specific between their RSSDs - replicate the required definitions (rep. definition, etc.) from the first RSSD to the second one.

When the second RSSD has these definitions - we can create a subscription on the second RS from the source database to the target database. This is how it works.

Before declare a routing

1. Two replication servers are installed and started.
2. All target databases must have the same columns and Primary key.
3. No identity in the target table (or subscription that know to update identity column).

Importent notes:

1. The passwords to all RSs in the process should be the same.
2. The RepAgent has to use a known servers names (in the ini files).
3. Source and target tables must have a primary keys.

Routing definitions

Init servers

1. Edit the ini file in the new server with:
   
   1. Current (new) RS.
   2. ASE instance of the RSSD.
   3. ASE instance of the replicatec(=target) database.
   4. First (=source) RS.
2. Edit the ini of the first (=source) RS with:
   1. New RS.
   2. ASE instance of the source RSSD.
3. Run rs_init:
   1. Two ways to do that:
      1. run rs_init
      2. create <SAP_RS_FOLSER>/REP-16_0/init/rs/RS2.rs (copied and edited from install.rs) and run it
         1. ./rs_init -r ../init/rs/RS2.rs
   2. In rs_init we define the servers, databases, RSSDs, users, etc.
4. Check that RS is up:
   1. isql64 -S RSFOG2 -Usa -P<password>
   2. admin version
      go
   3. admin who
      go

Manage the route

#		RS1 (source RS)	RSSD of RS1 (RS1_RSSD)	RS2 (second RS)	Target replicated database
1	Create route	alter connection to SERVERNAME.RS1_RSSD set log transfer ON go create route to RS2 set username sa set password PASSWORD go
1.a	Monitor the new route until it became active		1> rs_helproute 2> go  route        route_status                                                                                                   ---------------------------------- RS1 --------> RS2 Route is being created. Destination has not yet finished creating system table subscriptions.  Systable Subs to be created …… (list of what created) * re-run to re-check untio all created.
2	add connection RS2 (second RS) → target database			Use rs_init Declare DATABASE INFORMATION 1. SQL Server name: (target ASE) 2. SA user: sa 3. SA password: ****** 4. Database name: (target database name) 5. Will the database be replicated: no 6. Maintenance user: <target database name>_maint 7. Maintenance password: ****** 8. Is this a Physical Connection for Existing Logical Connection: no Can be done also with "create connection" command.
3	Configure a  rep_agent to the RSSD		1> use RS1_RSSD 2> go 1> sp_config_rep_agent RS1_RSSD , 'enable' , 'RS1' , 'sa' ,'PASSWORD' 2> go Replication Agent enabled for database 'RS1_RSSD'. The Replication Agent thread needs to be started using sp_start_rep_agent. (return status = 0) 1> sp_start_rep_agent RS1_RSSD 2> go Replication Agent thread is started for database 'RS1_RSSD'. (return status = 0)
4	Grant permissions in the target database				1> grant all on FirstTable to  <target database name>_maint 2> go
5	create a subscription to the replicate connection in the second RS			1> create subscription subTest3 for repdefTest with primary at PRIMARYDBSERVERNAME.PRIMARYDB with replicate at TARGETDBSERVER.TARGETDBNAME without materialization 2> go Subscription 'subTest3' is in the process of being created. 1> check subscription subTest3 for repdefTest with primary at PRIMARYDBSERVERNAME.PRIMARYDB with replicate at TARGETDBSERVER.TARGETDBNAME 2> go