[signon]

Use the [signon] section of the dbridge.cfg file to enter information for signing on to the relational database and DATABridge Server on the host.

The configuration file must include the data source (or database, if using Oracle), signon parameters to access the relational database, and a user and a password (unless you use the SQL Server client with Integrated Windows authentication).

Parameter

Description

database

Deprecated in DATABridge 6.0 and later for Microsoft SQL Server client.

Default: None
Command-line option: -D

(Oracle) This parameter is the name that identifies the Oracle instance or the Oracle Net Services node that is being accessed. If the name contains non-alphanumeric characters, you must enclose it in double quotation marks, as follows:

database = "orcl.cin.attachmate.com"

datasource

Default: None
Command-line option: -O

(Microsoft SQL Server) This parameter is the name that identifies the ODBC data source used to access the SQL database. This ODBC data source is configured using the Control Panel during the Client installation procedure.

(DB2/Informix) This is the CLI data source, which typically is the name of the database being accessed.

hostpasswd

Default: None
Range: 17 alphanumeric characters
Command-line option: -X

Use the host password parameter to specify the password associated with DATABridge Server on the host. This parameter must match exactly the KEY parameter defined in the Host Server control file. For example:

DBServer

KEY = "Secret"

dbridge.cfg

hostpasswd = Secret

password

Default: None
Command-line option: -P

Use the password parameter to specify the password associated with the user ID for the relational database. The password must be valid for the user ID or the connection to the relational database server will fail.

Passwords are limited to 30 characters. If your password contains non alphanumeric characters other than the underscore, you must enclose the password in double quotes, as follows:

password = "a$bb%"

Note: Passwords for Oracle 11g release 2 are case-sensitive.

The password is always encoded in both text and binary versions of the client configuration file. For more information, see Export or Import a Configuration File or in the DATABridge Client Console Help, see "Export the Client Configuration to a File." Passwords that are communicated between the DATABridge Client and DATABridge Server are not encoded.

user

Default: None
Command-line option: -U

Use the user parameter to specify the user ID for the relational database. The user ID must have the appropriate resource privileges for the designated relational database, as explained in Setting Up a User ID (Windows) in the DATABridge Installation Guide.

use_nt_authen

Default: False
Range: True or False
Command-line option: -W

The use_nt_authen parameter applies to Microsoft SQL Server clients only.

Use Windows ODBC Data Source Administrator to set the required ODBC data source authentication method. The SQL Server database must be installed with the proper authentication mode selected; either SQL Server, Integrated Windows, or Mixed Mode (that is, using both methods). When using Integrated Windows authentication, Windows Administrators are automatically included in the SQL Server user list. The SYSTEM account is only included in versions of SQL Server older than 2012. For more information, see the DATABridge Installation Guide.

Use this parameter as follows:

  • Set it to True when Microsoft SQL Server is set to use Integrated Windows Authentication for access to the SQL Server database.
  • Set it to False when Microsoft SQL Server is set to use its own SQL Server authentication. The SQL Server verifies the authenticity of the login ID with SQL Server authentication using a Login ID and password entered by the user.

use_odbc_reg

Default: False
Range: True or False

(SQL Server only) Use this parameter when the server name for the data source contains a period (.). This addresses an issue where, by querying ODBC to retrieve the server name for the data source causes the server name to be truncated at the period and the bcp scripts to use the wrong server name. This parameter prompts the client to get the server name from the Windows Registry instead of querying the data source using ODBC.

[signon] parameters with equivalent environment variables

[signon] Parameter

Environment Variable

Option

dbutility Command

database

DBDATABASE

-D

All (only applies to Oracle)

datasource

 

-O

All (does not apply to Oracle)

hostpasswd

DBHOSTPW

-X

define, redefine, process, clone, and switchaudit

password

DBPASSWD

-P

All

user

DBUSERID

-U

All