Progress Fathom Replication
User’s Guide

> ## Server properties

> Table 3–1 is a list of server properties and their values.

> Server properties are found after the `[server]` directive in the Fathom Replication source properties file. The properties file must be stored in the directory where the source database resides.
> Property names and values are separated by an equals sign. For example: `transition=auto`.

> Table 3–1: Server properties
> Property name | Value | Description
> --- | --- | ---
>     control-agents
>     agent_name[, agent_name]
> | Specifies a comma-separated list of Fathom Replication agent names. The comma must be followed by a space. The agent name must match the control agent name specified in the control-agent properties section head. `ALL` is not allowed as an agent name. Each agent must have a unique name.
>     database
>     db_name
> | Specifies the source database name.
>     defer-agent-startup
>     minutes
> | Specifies the length of time that the server attempts to connect to an agent if first connection attempt is unsuccessful. `minutes` is a value>= 0 and <= 1440.
>     maximum-polling-delay
>     milliseconds
> | Specifies the maximum value for a polling delay. By default, the polling delay starts at 5 ms and automatically increases during periods of inactivity to a maximum of 500 ms. `milliseconds` is a value >500 and <1000.
>     minimum-polling-delay
>     milliseconds
> | Specifies the minimum value for a polling delay. By default, the polling delay starts at 5 ms and automatically increases during periods of inactivity to a maximum of 500 ms. `milliseconds` is a value >=1 and <=10.
>     Repl-Keep-Alive
>     seconds
> | Specifies a time-out period for communications between a server and its agents. If a connection between the server and agent is not verified before the time out expires, failure recovery begins. By default, this property is enabled and has a value of 300 seconds. The minimum value is 60 seconds. There is no maximum value.
>     Schema-Lock-Action
>     wait | force
> | Specifies the action an agent takes if an exclusive schema lock is not granted. Possible actions are: wait—The agent waits until the exclusive schema lock is granted. The server blocks until the exclusive schema lock is granted. force—The agent attempts to acquire the exclusive schema lock 5 times. If the fifth attempt fails, the agent disconnects all users from the target and makes another attempt. If the last attempt fails, the server and all agents terminate. When schema update activity completes, the server and target can be restarted. Note: Values are case sensitive. Use `wait` or `force`, but not `Wait` or `Force`.
>     transition
>     auto | manual
> | Specifies how to transition the target database to a normal database. If a synchronous agent or an asynchronous critical agent cannot reconnect with the source database within the time specified in the `transition-time-out` property, the following will occur: auto—The agent automatically transitions the target database to a normal database. manual—The agent listens for the server until it reconnects with the source database or the `DSRUTIL` command is executed. The `DSRUTIL -C` `transition` command transitions the target database to a normal database. Note: Values are case sensitive. Use auto or manual, but not Auto or Manual.
>     transition-timeout
>     seconds
> | Specifies he number of seconds the target database waits before it transitions itself to a source database. This property is ignored when `transition=manual`. The value is incremented by the sum of the `connect-time-out` for all configured agents.

Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095