Data Transformation Engine Resource Adapter Reference Guide

Chapter 2 - Resource Adapters Use On the Command Line
Resource Adapters Reference Guide
26
100 seconds for a message receipt, as specified using the Listen adapter
command (-LSN 100).
On the Command Line
In addition to using a command string on the command line, you can also use
adapter commands in command files, batch files, shell scripts, or with the Platform
API.
Use adapter-specific execution commands to:
Override particular settings for an existing source (such as a user ID and
password for database adapters)
Override an existing source or target (using file, application, message or
another entity)
Specify the preferred adapter commands using an execution command string on
the command line or create a command file that contains adapter commands
dictating the desired execution settings.
For information on adapter-specific input and output execution command
overrides, see the Execution Commands Reference Guide.
Database-specific Adapter Commands on the Command Line
For a database-specific adapter, an existing data source which is a file, can be
overridden and specified to be a database using the Input Source Override -
Database execution command (
-ID). Or, you can override an existing data target
that is a table in one database with a table in a different database using the
Output Source Override - Database execution command (
-OD). For information
about all of the options to use within these database execution commands, refer
to the Execution Commands Reference Guide.
The values specified using the Input Source Override - Database execution
command (
-ID) and the Output Source Override - Database execution command
(
-OD) can be used to designate a query or table to be used as the data source or
target, or to override one or more of the adapter commands of an existing
database definition as follows:
using an .mdq file
Specify the name of an .mdq file and the name of a particular database that
will override the appropriate adapter settings. In this usage, the .mdq file must
be available at map execution time. The values in the .mdq file will override all
values defined in the map.