Defining a Data Source via the Configuration File
Follow these steps to define a data source and populate the client control tables.
To define a data source
Note: This procedure assumes that DBServer or Enterprise Server is running and the signon parameters are configured appropriately.
- Because the following dbridge.cfg parameters are difficult to change later without redefining and recloning, make sure that they're set appropriately before you run the define command:
use_bigint (SQL Server only)
use_clob (Oracle only)
use_clustered_index (SQL Server only)
use_date (SQL Server 2008 only)
use_datetime2 (SQL Server 2008 only)
use_nullable_dates (Miser databases only)
use_time (SQL Server 2008)
For information on setting these parameters, see Appendix C: Client Configuration.
- Enter the following command:
dbutility [signon_options misc_options] define datasource hostname portnumber
For each DATABridge Client type, the following command-line options sign on to the relational database (and DBServer):
DB2 and Informix:
[-U userid] [-P password] [-O ODBCdatasource]
[-U userid] [-P password] [-D database]
[-U userid] [-P password] [-W] [-O ODBCdatasource]
Any of the following miscellaneous command-line options:
-L forces the client to use a new log file for this run.
-T forces the client to use a new trace file for this run, if tracing is enabled.
-f filename to specify a configuration file other than the default dbridge.cfg file in the working directory.
-u allows the command to delete client control table entries for a data source that already exists.
For DBServer: The name that matches the entry for SOURCE in the DBServer control file. You can enter the data source name in uppercase or lowercase.
For DBEnterprise: The name of a source (base or filtered) defined in Enterprise Server.
The domain name or IP address of the appropriate DATABridge server (DBServer or DBEnterprise).
The TCP/IP port number on which the appropriate DATABridge server (DBServer or DBEnterprise) listens for incoming calls.
For DMSII databases that have a large number of data sets and data items, the process of retrieving the layout information may take several minutes.
- Read the following section, Results of the Define Command, and then specify which data sets and data items you do not want to be cloned or updated, as explained in Customizing with User Scripts.
Assuming the DBServer control file contains SOURCE ORDDB and PORT=5001 on the host "OURHOST.CIN.AAA.COM", you would enter the following:
dbutility define ORDDB OURHOST.CIN.AAA.COM 5001
The DATABridge Client makes remote procedure calls to DBServer to get DMSII database layout information. DBServer returns the DMSII layout information to the Client. The Client populates the control tables with the DMSII layout information and creates the corresponding relational database table layout.
The empty control tables (that were built during the dbutility configure command) are now populated.
For example, this SQL statement
select data_source, hostname, hostport from DATASOURCES
would yield a table similar to the following. Only the selected columns are shown.
data_source hostname hostport
------------ --------------------- ------
ORDDB OURHOST.CIN.AAA.COM 5001