For reading entries from a data queue on an AS/400 system.
A data queue is checked in a specifiable interval. Note: If a data queue is read at intervals of more than one minute, all entries in the data queue are read and processed. If the interval is less than one minute, a maximum of 50 entries is read and processed per readout operation.
Each read-out data queue entry leads to a separate job.
Afterwards, you can, for example, use an ID read from the data queue to read the actual data from a database via SQL.
Settings
(1) Start on IS only: Only relevant for the add-on module "Load Balancing" to start the profile on a specific node.
(2) Host, User, Password: DNS name or IP address of the AS400 host, the user and the password.
(3) DataQueue: Name of the data queue to be queried.
Example: "/QSYS.LIB/FRED.LIB/MYDTAQ.DTAQ".
(4) Key: If it is a keyed data queue, the key of the values to be queried must be entered here.
(5) Check DataQueue (in ms): Interval in which the data queue is queried.
(6) Check connection: Testing access to the configured data queue.
(7) Use DataQueue values for SQL: See the section below with the same name.
(8) No execution at: The querying of the data queue can be suspended for defined periods of time. Example:
|
Day
|
From hour
|
Minute
|
Duration in minutes
|
|
Sunday
|
12
|
0
|
60
|
Use DataQueue values for SQL
The string read from the data queue can be used by the Input Agent in a subsequent SQL query.
Settings
(9) Empty SQL result set is treated as error: If this checkbox is set, the profile will be aborted with an error if the SQL query does not return any data.
(10) Custom class: You can specify a custom class to handle the data retrieved from the data queue. The default custom class specified here ("
DefaultAS400DataHandler"
) replaces the placeholder &1 of the SQL query with the value read from the data queue. Note: You have the option of implementing your own classes. There is a programming interface (API) that also allows you to develop your own classes in Java. We offer in-depth training for this. If you are interested, please contact our support or sales staff.
(11) DB alias: The selection menu contains all existing database aliases. A database alias is a previously configured connection to a database. Note: For details about database connections, see the Admin Console documentation.
(12) SQL query: SELECT query to read data from the database. Only a single SELECT query can be specified.
Example: "SELECT * FROM table_1 WHERE id=&1".
(13) Test SQL: Executes the SQL query. If the SQL query contains a * for all columns, the actual names of the columns are read from the database and are used to substitute the * in the SQL query. Example: SELECT * FROM table_1 might become SELECT col1, col2, col3 FROM table_1.
(14) Create structure: The columns of the SQL statement are created as fields below a newly created node in the source structure. Existing mapping instructions are retained. The data types and field lengths of the columns are taken from the database.