configure replication server

Sets characteristics of the Replication Server, including network-based security. Configures ERSSD.

Syntax

configure replication server {
	set repserver_param to 'value' |
	set route_param to 'value' |
	set database_param to 'value' |
	set logical_database_param to 'value' |
	set security_param to 'value' |
	set id_security_param to 'value' |
	set security_services [to] 'default'}

Parameters

Examples

Usage

  • Each parameter has two values: the configured value and the run value. Replication Server uses the configured value when it restarts. The run value is the value the Replication Server is using currently. When you start Replication Server the values are equal.

  • Configured values are stored in the rs_config system table in the RSSD.
  • Replication Server shuts down automatically when you set the queue block size with the “set block_size to ‘block_size’ with shutdown” Replication Server parameter. The new block size takes effect after you restart Replication Server. See Replication Server Administration Guide Volume 2 > Performance Tuning > Increasing Queue Block Size .

  • varchar_truncation enables truncation of varchar columns at the primary or replicate Replication Server. When incoming varchar data exceeds the column length specified in the replication definition, the following occurs:

    varchar_truncation
     

    varchar_truncation set at primary Replication Server

    varchar_truncation set at replicate Replication Server

    varchar_trunction set to “on”

    Replication Server truncates incoming data to the length specified in the replication definition.

    Replication Server truncates incoming data to the length specified in the replication definition.

    varchar_truncation set to “off”

    RepAgent prints a message in the Replication Server log, and Replication Server ignores rows that exceed the column length specified in the replication definition.

    Replication Server prints a message in the Replication Server log, and the DSI shuts down.

  • Use ha_failover to enable Sybase failover support. In the event of an ASE server failover, all connections from Replication Server to ASE will fail. Replication Server will retry connections. Setting ha_failover to on will allow the new connections to failover to the new ASE server.

  • Use ERSSD configuration parameters to configure backup time, directory location and RepAgent name.

    ERSSD Configuration Parameters

    ERSSD Configuration Parameter

    Value

    Default

    erssd_backup_start_time

    Time the backup starts.

    Specified as: “hh:mm AM” or “hh:mm PM”, using a 12-hour clock, or “hh:mm” using a 24-hour clock.

    Default: 01:00 AM

    erssd_backup_start_date

    Date the backup begins.

    Specified as “MM/DD/YYYY”.

    Default: current date

    erssd_backup_interval

    Interval between backups of database and log.

    Specified as “nn hours” or “nn minutes” or “nn seconds”.

    Default: 24 hours

    erssd_backup_dir

    Location of stored backup files.

    Should be a full directory path. Configuring this path causes immediate backup.

    Default: Same directory as the transaction log mirror; initial value specified in rs_init.

    erssd_ra

    Configures Replication Agent name, in order to create a route from the current site to another Replication Server. This server name must exist in the interfaces name.

    erssd_name_ra

Replication Server Parameters

  • Replication Server parameters specify default values that affect the local Replication Server.

  • Replication Server parameters are static. You must restart Replication Server for them to take effect.

Route Parameters

  • Route parameters specify default values for all routes that originate at the source Replication Server.

  • You can override default values specified using configure replication server by using alter route to set values for individual routes.

  • You must suspend all routes originating at the current Replication Server before executing the configure replication server command. After you have changed the parameter, you must resume all routes for the change to take effect.

Database Parameters

  • Database parameters specify default values for all connections that originate at the source Replication Server.

  • You can override default values specified using configure replication server by using alter connection to set values for an individual connection.

  • You must suspend all connections originating at the current Replication Server before executing configure replication server. After you change the parameter, resume all connections for the change to take effect.

Logical Database Parameters

  • Logical database parameters specify default values for logical connections that originate at the source Replication Server.

  • You can override default values specified using configure replication server by using configure logical connection to set values for a specific logical connection.

  • Logical database parameters are dynamic. They take effect immediately.

Network-Based Security Parameters

  • With the exception of use_security_services and use_ssl, security parameters configured with configure replication server are dynamic; they take effect immediately.

  • use_security_services and use_ssl are static. If you change their values, you must restart Replication Server for the change to take effect.

  • Default network-based security parameters set with configure replication server specify values for all incoming and outgoing pathways related to the current Replication Server.

  • You can override default security settings specified using configure replication server by using alter route or alter connection to reset security values for individual outgoing pathways.

  • If unified_login is set to “required,” only the “sa” user can log in to the Replication Server without a credential. If the security mechanism should go down, the “sa” user can log in to Replication Server with a password and disable unified_login.

  • A Replication Server can support more than one security mechanism. Each supported mechanism is listed in the libtcl.cfg file under SECURITY.

  • Both ends of a route must use compatible Security Control Layer (SCL) drivers with the same security mechanisms and security settings. It is the replication system administrator’s responsibility to choose and set security features for each server. Replication Server does not query the security features of remote servers before it attempts to establish a connection. Network connections fail if security features at both ends of the pathway are not compatible.

  • Message encryption is a costly process with severe performance penalties. In most instances, it is wise to set msg_confidentiality to “required” only for certain pathways. Alternatively, choose a less costly feature, such as msg_integrity, to ensure security.

Permissions

configure replication server requires “sa” permission.

Related reference
admin security_property
admin security_setting
alter connection
alter route
configure connection
configure route
create connection
create route
set proxy