Command-Line Client Operations

This section describes the tasks required to clone a DMSII database and track changes using the DATABridge Client from a command line. This sequence assumes that the relational database is properly configured and the required DATABridge software is installed and running.

1

Update the configuration file

Because the Client reads the Client configuration file before writing the script files and the log file, you may need to modify this file. To edit the configuration file, you must export it to an editable format and then import it after you make your changes. For more information, see Export or Import a Configuration File.

2

Run the dbutility configure command

In a first-time installation, you must run the dbutility configure command. This creates the DATABridge client control tables that will hold the layout information for the DMSII database and corresponding relational database tables.

3

Run the dbutility define command

This command creates an entry in the DATASOURCES client control table that contains the data source name, the host name and the port number on which DBServer or DBEnterprise listen. It also populates the client control tables with the DMSII layout and creates the corresponding table layout for the relational database.

dbutility define datasourcename hostname portnumber

4

Create user scripts

To customize the client control tables, you must create user scripts. Or, you can use the default mapping that the DATABridge Client produces. Creating user scripts is an iterative process that involves writing scripts to select and map data sets and customizing data tables, and then testing and updating the scripts until the resulting data table layout meets your specifications.

When you are satisfied with the results of your user scripts, re-run the define command with the -u option.

5

Run the generate command

This command creates scripts that the DATABridge Client uses to create and populate the data tables from the data sets that you selected for cloning. You can modify the configuration of your data tables by adding optional parameters to the end of the create table and create index statements.

Do not directly modify scripts created by the generate command; your changes will be lost the next time your run this command.

dbutility generate datasourcename

6

Review the bulk loader options

Review the sections on the bulk loader utilities and their related options, making changes to the bulk loader parameters in the configuration file as needed.

7

Clone the database

To clone the DMSII database, run the process command. If you want to clone only a few data sets, use the clone command. This step populates the DATABridge data tables in the relational database with actual DMSII data.

dbutility process datasourcename

8

Update the database

To update the relational database with changes made to the DMSII database, run the process command. Or, to make DBEngine wait for updates when it reaches the end of the audit trail, set the configuration parameter use_dbwait to true or use the command-line switch /w.