Try OpenEdge Now
skip to main content
Configuration
Configuring OpenEdge Databases : Configuring an OpenEdge Replication-enabled database : Setting OpenEdge Replication Server properties
 

Setting OpenEdge Replication Server properties

You set the OpenEdge Replication Server properties to specify server and agent property values.
Note: If you are not familiar with OpenEdge Replication and its configuration, see OpenEdge Replication: User Guidebefore setting the properties.
The server properties are divided into the following categories:
*General
*Advanced
To set the OpenEdge Replication Server properties:
1. Click Resources in the management console menu. All resources managed by your console appear in the grid frame.
2. Filter or search for the database whose Replication Server properties you want to set.
3. Click the Edit icon. The Database details page appears.
4. In the Command and control section of the page, click Configuration. The Database Configuration page appears.
5. In the OpenEdge Replication Group Links section, click Server. The Database Replication Configuration page opens.
6. Set the following General properties:
*Database — Specifies the source database name.
*Defer agent startup — Specifies for how long, in minutes, the server attempts to connect to an agent if the first connection attempt is unsuccessful. The minutes value must be greater than or equal to zero and less than or equal to 10080.
*Keep alive — Specifies a timeout period for communications between a server and its agents. If a connection between the server and the agent is not verified before the timeout 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.
*Server transition timeout — Specifies the number of seconds the target database waits before it performs auto-transition. This property is ignored when transition is set to manual.
The value is incremented by the sum of the connect-timeout for all configured agents.
*Server transition — 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-timeout property, the following occurs:
*auto — The agent automatically transitions the target database.
*manual — The agent listens for the server until it reconnects with the source database or the DSRUTIL command is executed. The DSRUTIL db-name -C transition command transitions the target database.
7. Set the following Advanced properties:
*Other arguments — Any other arguments for which there is no defined property available.
*Schema lock action — 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 five 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.
*Polling delay minimum — Specifies the minimum value, in milliseconds, for a polling delay. By default, the polling delay starts at 5 milliseconds and automatically increases during periods of inactivity to a maximum of 500 milliseconds.
The value must be greater than or equal to one and less than or equal to ten.
*Polling delay maximum — Specifies the maximum value, in milliseconds, for a polling delay. By default, the polling delay starts at 5 milliseconds and automatically increases during periods of inactivity to a maximum of 500 milliseconds.
The value must be greater than 500 and less than 1000.
*Server port minimum — The minimum port available.
*Server port maximum — The maximum port available.
*Agent shutdown action — Specifies the action an agent takes during a shutdown when the Replication server ends. Possible actions are:
*recovery — The agent remains active but in a standby state waiting for the replication server to reconnect.
*normal — The agent terminates; the target database stays up.
8. Click Save.