Skip to main content

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:

  1. Manually replace the license file in the \<instance>\license\ directory of each node.

  2. 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 .