Modifying node settings
To modify a node:
Click Manage the system > Maintenance > Database replication.
Select a node.
Select the Configuration tab.
Modify the node’s settings.
You can change the:
Description
External address
Any URLs returned to client workstations can use a separate, externally addressable name, such as when downloading packages from session monitor or redeeming one-time use tokens. This address can only be modified for the replication node it is accessed from, otherwise the option will be disabled.
See also: Modifying the external address in a single-node environment.
Mode
Queue size limit
If the replication is suspended on a node, then changes made on other replication nodes will not be propagated to this node.
Warning
Do not make any changes to a replication node while it is suspended.
Click Update.
If the External address is modified, restart the Database Service in order for the changes to take effect.
To delete a node, check the box next to the node on the Database replication page, then click Delete. You can also delete the node from its information page.
If the current node’s server clock is different from that local node’s clock by 60 seconds, a warning message is displayed, noting the time difference.
Propagate replication changes
Once you have modified the configuration of a node in a replication environment, you must propagate the node configuration to all connected servers. The status for the nodes will change to "Reload required" on the Select a replication node page.
To do this:
Ensure all nodes can successfully communicate with each other. When propagating changes, the system checks that all nodes can connect, and if any connection issues are detected, propagation will fail.
If adding a new database node, verify there is enough space available on:
The source application node (the one from whose web-based interface the propagation is triggered)
The target nodes (the ones where the propagation goes)
Their respective backend databases. See Resynchronizing databases for details.
On the Database replication page, click:
Propagate and reload replication configuration on all servers (without resynchronizing nodes)
This is recommended when wanting to replicate changes without dropping data on the newly added node and replacing it with data from the current node.
Or
Propagate and reload replication configuration on all servers to propagate changes
When adding a new node this propagate changes and replicates the entire database to the new node.
Wait while the Database Services reload the changes and possibly builds queue files.
Click Refresh to check progress, as indicated in the status column.
Note
If a node is in "Reload in progress" status, or is running auto discovery, you cannot make any changes to the replication nodes until the reload is complete. The Propagate and reload replication configuration on all servers option only appears if a change in the configuration has occurred.