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.
Modifying the external address in a single-node environment
In single-node environments, you are currently unable to change the node's external address using the Manage the system console as described above. If you try, a warning is displayed and there is no button to propagate the change.
To modify a node's external address in a single-node environment:
Open the Windows Registry Editor and locate the instance's base registry key.
Create a REG_SZ entry named
serveraddressexternal-- and populate it with the required value on each node.Restart the database service .
Configuring replication event actions (exit traps)
Replication-related events can trigger external notification programs.
The following database replication options can be accessed by navigating to Manage the system > Maintenance > System variables or Manage the system > Maintenance > Options:
Replacing the license
Bravura Security Fabric license files occasionally need to be replaced. There are considerations to make when doing this in a replication environment. The license file is read by the Database Service (iddb) when it starts up.
When manually replacing the Bravura Security Fabric license files in a replication environment, you must:
Manually replace the license file in the \<instance>\license\ directory of each node.
Restart the Database Service service on every node.
The downtime should be minimal. If access to the nodes is slow or otherwise inconvenient, but you have administrative access to the nodes, you could put the license on the primary node and synchronize files (Maintenance > File synchronization) wait for it to end (look at idmsuite.log until updinst ends), and then start the Database Service remotely from the primary on all other nodes.
This has to be done on each application node.
Before restarting iddb ensure that psupdate or some other form of discovery (LWS, manual) is not currently running or scheduled for the next few minutes.
Alternatively, you can use Windows’ Command Prompt to stop and start iddb services, either locally or remotely, and all other services dependent on it that are not disabled on purpose. Start Command Prompt as Administrator and run:
restart-service iddb_<instance_name>
This will first stop all services depending on iddb , then iddb , start iddb and start the other dependent services which were stopped.
If you want to do the operation remotely, add - ComputerName <servername> to the commands above or below.
There's also the option to stop iddb first, which will stop the other dependencies first, and then start all non-disabled services in the given instance. Start Command Prompt as Administrator
stop-service iddb_<instance_name> start-service *_<instance_name>
You can also use SysInternals’ PsService to restart iddb:
psservice \\server restart iddb_<instance_name>
Using PsService is the simplest and fastest solution, although it requires placing the PsService utility on the primary node, from Windows’ SysInternals. See https://docs.microsoft.com/en-us/sysinternals/downloads/psservice .