Skip to main content

Database Service (iddb)

The Database Service (iddb) is responsible for connecting Bravura Security Fabric to its backend database.

Dependencies / requirements

The Logging Service must be running before the Database service.

If the Database Service fails or is restarted, several dependent services must also be manually restarted. These dependent services include:

  • Transaction Monitor Service

  • Workflow Manager Service

  • Scheduler Service

  • API Service

  • Privileged Access Manager Service

See Stopping and starting the Database Service for details.

Configuration

The service is automatically installed and started on the Bravura Security Fabric server during setup.

The Database Service uses a configuration file, iddb.cfg , located in the service directory. This file is automatically generated when you install Bravura Security Fabric . It usually does not need to be edited; however you can edit the file for more advanced configuration. Contact support for assistance.

Note

You cannot modify parameters for the Database Service from the Manage the system (PSA) module.

Command-line options for iddb are listed below:

Table 1. iddb service command-line options

Argument

Description

-h

Displays usage information.

-v

Displays version number only.

-cfg <cfgfile>

The path to the iddb.cfg configuration file. The default is \<instance>\service\

-config

Displays service configuration information.

-server

Run the service in server mode.

-start

Starts the service.

-stop

Stops the server/service



See also:

See the Replication and Recovery Guide for information about recovering from network failure, and steps to troubleshoot problems arising from unsynchronized data.

Stopping and starting the Database Service

Unlike other Bravura Security Fabric services, you cannot stop, start, or otherwise manage the Database Service using the Manage the system (PSA) module. You must use the Windows Services snap-in, or the Windows net command.

The Windows Services snap-in’s "Restart" operation can automatically restart dependent services. By default, services are started automatically when the system starts.

Stopping

To stop the Database Service using the Windows net command:

  1. Log into the Windows server that is hosting Bravura Security Fabric as a member of the Administrators group.

  2. Open a command prompt and type:

    net stop iddb_<instance>

    where <instance> is the name of the Bravura Security Fabric instance.

  3. If the net command displays a list of dependent services:

    1. Note which services will be stopped. You will be required to restart them later.

    2. Type Y, then press Enter to continue.

The Windows net command displays a success message after the Database Service is stopped. This process may take several minutes.

Starting

To start the Database Service using the Windows net command:

  1. Log into the Windows server that is hosting Bravura Security Fabric as a member of the Administrators group.

  2. Open a command prompt and type:

    net start iddb_<instance>

    where <instance> is the name of the Bravura Security Fabric instance.

The Windows net command displays a success message after the Database Service is started. This process may take several minutes.

You must also start any services that were stopped as a result of stopping the Database Service. To do this using the above net command, simply replace iddb with the appropriate executable name:

Service name

Executable name

Transaction Monitor Service

idtm

Workflow Manager Service

idwfm

Scheduler Service

psscheduler

API Service

idapi

Privileged Access Manager Service

idarch

For example:

net start idtm_default
net start idwfm_default
net start psscheduler_default