User Tools
Add this page to your book 
Remove this page from your book 
Manage book (
Help Manager for data import
Transaction IMPTSK
This transaction is used to import data into the system.
It is possible to import various types of data.
For each type, one line in the import grid needs to be defined.
Data can be retrieved from the file system or using IBM MQSeries messaging.
This data will be passed as files to an existing import transaction.
A new import can be defined using the “Add Imp.” Button.
Configuration of the MQ interface
Manager = MQSeries Queue Manager
Queue = MQSeries Queue
The connection can be set using the environment variable MQSERVER, or can be set for each import type with the following values; Checkbox “Set Connection” must be checked.
Channel
Type
Connection
If the connection is to be encoded, checkbox “Use SSL” has to be checked; key repository and cipher must be defined.
Technical requirements
The sender has to set the format field in the MQ Series message to MQFMT_STRING. Sender and receiver have to set the CCSID to 1208.
Configuration of the Kafka interface
The following fields have to be specified, when using the Kafka interface
Ini file: Ini file with the consumer settings
Topic: The topic from which the import data is received
Configuration of the ftp interface
The following fields have to be specified, when using the Kafka interface
Ini file followed by the section name ( <Ini file>.<section> ) containing the ftp settings for this service.
Remote directory: the directory on the remote server, containing the files to import.
Configuration of the file interface
In this case only file input directory and the file extension have to be specified.
IPC Commands
If the import manager runs in the background, it accepts the following commands via IPC (e.g. sent by the transaction SYSMGR running on the same system)
| Command | Argument | Meaning | |
|---|---|---|---|
| D | Shutdown process | ||
| F | Shutdown process | ||
| S | <filename> | Write status to <filename> | |
| TAPPL | <level> | Control trace information in process log | |
| <level> | Meaning | ||
| 0 | Switch off application trace | ||
| >= 1 | Minimum trace (i.e. Start, Stop, Reception of IPC commands) | ||
| 2…6 | Stronger trace information | ||
| T+ | <level> | Set server execution debug level (cf. td2 server documentation) | |
| T- | <level> | Reset server execution debug level (cf. td2 server documentation) | |
Tracing of Transactions
Transactions which are being run via the import manager can be traced by starting the import manager in the foreground and activating the desired debug switches. The import manager will pass its own debug switches as command line parameters to the transactions which have been initiated by the import manager.
Managers running in foreground mode always need to be started manually.
Transaction Panels
Configuration
Datafields
| Datafield | Description |
|---|---|
| Start Time of Job Date | This field displays the date and time the Task Manager was started. |
| Automatic Termination Flag | This field defines the reason for terminating the Task Manager - at a predefined time. In this case enter the time in the field on the right side - if list empty. The Task Manager will then stop when the list of open transactions is empty. - manually only. In this case the Task Manager will stop in case the “stop” button is pressed. |
| Redotime | This field contains the restart time of the Task Manager in seconds. If processing is set to 'automatic', the Task Manager will restart after this time selected. If 'manual' any time period entered is irrelevant. |
| Application Trace Flag | This option sets the trace level of the transaction. Higher values mean more details. |
Adress Import
