Using the create route command

You can create routes in Sybase Central or with the create route command.

The syntax for the create route command is:

create route to dest_replication_server{
	set next site [to] thru_replication_server|
	[set username [to] user]
	[set password [to] passwd]
	[set route_param to 'value']
	[set security_param to 'value']}

When creating routes:

Supply the login name, password, and other parameters for direct routes only.

Before you create a direct route, create its login name and password in the destination Replication Server. Optionally, you can have the rs_init utility create this user.

If you are enabling network-based security and unified login, user name and password are optional. The default user name is the principal user name, which is specified by the -S flag when you log in to Replication Server or start Replication Server. Refer to “Establishing the principal user” for more information about network-based security and the principal user.

If you create a route with a user and passwd that do not exist at the destination Replication Server, add or change the user and password at that destination. See also “Changing an indirect route to a direct route”.

If you are establishing a direct route from the current Replication Server to the destination Replication Server, do not use the next site clause.
Enter one create route command at a time, to ensure you have made no mistakes. Wait for a route to become valid before creating the next one.

If you do make a mistake, drop the route and re-create it only as a last resort. Include the with nowait option with the drop route command. Since the route has not been created, its current state requires that you use the with nowait option to drop it. See “Dropping routes”.

When you create a route, you can accept the default values for configuration parameters that manage memory size, the size of the amount of data that can be sent over the route at one time, time-outs, and synchronization intervals. You can also set your own values when you create or alter the route.

Table 6-2 displays the route configuration parameters. If network-based security is enabled at your site, you can also configure security parameters for routes. Refer to “Managing network-based security”. See “Configuration parameters that affect performance” on page 139 in the Replication Server Administration Guide Volume 2 for a list and discussion of route parameters that affect performance.

**Table 6-2: Configuration parameters affecting routes**
route_param	value
disk_affinity	Specifies an allocation hint for assigning the next partition. Enter the logical name of the partition to which the next segment should be allocated when the current partition is full. Values are “partition_name” and “off.” Default: off
rsi_batch_size	The number of bytes sent to another Replication Server before a truncation point is requested. Default: 256K Minimum: 1K Maximum: 128MB
rsi_fadeout_time	The number of seconds of idle time before Replication Server closes a connection with a destination Replication Server. Default: -1 (Replication Server does not close the connection)
rsi_packet_size	Packet size, in bytes, for communications with other Replication Servers. The range is 1024 to 16384. Default: 2048 bytes
rsi_sync_interval	The number of seconds between RSI synchronization inquiry messages. The Replication Server uses these messages to synchronize the RSI outbound queue with destination Replication Servers. The value must be greater than 0. Default: 60 seconds
rsi_xact_with_large_msg	Specifies route behavior if a large message is encountered. This parameter is applicable only to direct routes where the site version at the replicate site is 12.1 or earlier. Values are “skip” and “shutdown.” Default: shutdown
save_interval	The number of minutes that the Replication Server saves messages after they have been successfully passed to the destination Replication Server. Default: 0 minutes