Previous Topic Next topic Print topic

Micro Focus Visual COBOL 2.3 Update 1 for Eclipse (UNIX) > Welcome > Product Information > Installation > Advanced Installation Tasks > Installing on Microsoft Terminal Server and Citrix > Configuring SQL Option for DB2 (XDB) for Multi-User Environments > Creating a Private XDB Configuration File in a Multi-User Environment

Creating a Private XDB Configuration File in a Multi-User Environment

Before using XDB Server on a TS/Citrix machine, all users must first run the XDBSetup utility to create a private XDB Server configuration file, xdb.ini, in their local Windows folders.

To run the utility:

  1. Log in to the TS/Citrix machine using the Windows Remote Desktop Connection.
  2. Execute the following from an Enterprise Developer command prompt: 
    XDBSetup

    See Syntax of the XDBSetup command for more details.

This creates a standard xdb.ini file in the user's Windows home directory, in c:\Users\username\AppData\Roaming\Micro Focus\Enterprise Developer\mfsql\, for which the user does not need administrator's credentials to change the file.

This also creates some registry entries in the user's specific area which point to the location of the private xdb.ini file. When any of the XDB tools are executed, they check the user's registry settings for whether there is a private configuration file before they check the local machine registry settings which store the location of the main XDB Server configuration file.

Syntax of the XDBSetup command

The XDBSetup utility can run in either an interactive or unattended mode. Use the following syntax to execute the utility: 

XDBSetup [-u|--unattended]

Where you can specify the following options:

No options
XDBSetup executes in an interactive mode. You receive some pop-up windows confirming whether the operation completed successfully, prompting whether to overwrite a previously installed xdb.ini, and possibly showing any status or error messages.
-u, --unattended
XDBSetup executes in an unattended mode.

Log files:

  1. A log of the commands activity is output to the standard error output handle.
  2. If you need to receive any standard errors, specify ">" to redirect the standard output. To redirect any standard errors, use "2>" as a redirection symbol. If this is not specified, any messages are displayed in the command prompt.
Parent topic: Configuring SQL Option for DB2 (XDB) for Multi-User Environments
Previous Topic Next topic Print topic