Skip to main content

setup

Use the setup program, located at the root of the distribution folder, to:

  • Modify (add or remove) features for an instance

  • Repair an instance

  • Upgrade an instance (if your Bravura Security Fabric release supports this action)

  • Uninstall an instance

  • Install a new instance

The setup program gathers initial configuration information, then launches the Bravura Security Fabric installer package file (idm.msi by default).

Requirements

The setup program requires Windows Installer version 3.0.1 or later. This program should be run by a member of the Windows Administrators group.

The setup program calculates required disk space before installation, and will prompt the administrator if more is needed. However, additional space may be required for backups when modifying or upgrading an existing installation. If the system runs out of disk space during installation or backup, you will be prompted to make more space available before continuing.

Backing up files is not supported when upgrading from versions earlier than 10.0.1.

Usage

Use the Windows command prompt to run setup with additional arguments, listed below.

setup.exe [arguments]

Notice

The -queuestrategy option was implemented in Bravura Security Fabric 12.4.0.

Argument

Description

-backup

Backup files before operation.

--createdbuser

Create a database user for the IDMSuite installation.

--dbadmin

Database administrator.

--dbadmpwd

Database administrator password.

-h, --help

Display usage information.

-hidekeys <option>

Hide the Communication and/or Database keys from being displayed in the UI. If this option is not specified, both keys are shown. Options available are:

  • comm to hide the communication key

  • data to hide the database key

  • auth to hide the workstation authentication key

  • idmlib to hide the IDMLib key

  • connector to hide the connector key

  • all to hide all keys

-v, --version

Display version information.

-i, --install

Install a new instance.

-instance <instancename>

Specify the name of the instance.

-loadplt-force

Load both conflicting and non-conflicting connector settings into affected instances.

-loadplt-include <instance names>

Comma-separated list of instances that should be included when running post-installation configuration actions.

-log <logFile>

The location and name of the log file.

If this option is not specified, the default log file name is: <instance>_<action>.log, where:

  • <instance> is the current instance name

  • <action> is one of install, modify, repair upgrade, or uninstall

-m, --modify

Modify an existing instance.

-msi <msiFile>

The MSI file to read.

-opts <msiOptions>

Options and parameters to pass through to msiexec.

See idm.msi for a list of Bravura Security Fabric -specific parameters.

-queuestrategy <strategy>

Specify a strategy for upgrading queue files. A strategy must be specified when upgrading.

Options available are:

  • default to have the installer automatically choose the best strategy to use based on the queue file compatibility.

  • nowait to have the installer use the strategy that does not wait for queues to be flushed.

  • flush to have the installer verify that the queues have been flushed before upgrading.

-r, --repair

Repair an existing instance.

-silent

Suppress the UI when performing actions (no user interaction).

-u, --uninstall

Uninstall an existing instance.

-U, --upgrade

Upgrade an existing instance.

-nodefaultdata

Use when you do not want to populate the tables with default data. Use with -noinstallschema when you want to connect to an existing schema that contains data.

-noinstallschema

Use when you do not want to create a new schema as part of the installation process. The installer will not create database objects (tables, stored procedures) as part of the installation.

Examples

To install a Bravura Security Fabric instance named my_instance :

setup.exe -msi idm.msi -i -instance my_instance
In this section: