Importer Activity
The Importer activity is used to import files into Transaction Insight®.
The principle functionality allows for files of different transaction types being imported into Transaction Insight both with and without their original EDI file (InstreamFile plus optional EDIFilename).
Other parameters are considered secondary (Inbound vs Outbound, SaveGoodData, etc.)
General
| Field | Literal Value/Module Property/Process Property? | Description |
|---|---|---|
| Name | No | (Required) The name to be displayed as the label for the activity in the process. |
| TI Binaries Directory | string | (Required) Location of Transaction Insight binaries. |
| Direction | boolean | (Required) Direction (Inbound/Outbound) to be assigned inside Transaction Insight during import. |
| INI Filename | string | Specifes the location of the custom ini file to be used for Importer settings. |
| Save Good Data | boolean | Save both good EDI documents as well as bad?
Checked = Yes Unchecked = No |
| Save Good Data Types | string | List of transaction types for which good data is to be saved, separated by commas.
Example: 837P,837I,834 |
| Save Warnings? | boolean | Store both Errors and Validation warnings in the database?
Checked = Yes (also save warnings) Unchecked = No (only save errors) |
| Skip ISA on Error? | boolean | Prevent interchanges from being imported if their ISA has an error?
Checked = Yes Unchecked = No |
Advanced
The Advanced tab contains the following fields.
Input
The Input tab contains the following fields.
| Input Item | Datatype | Description |
|---|---|---|
| InstreamFile | string | Path and filename of TIBCO Foresight® Instream® detail results file.
Example: "C:\files\My835.dtl" |
| EDIFilename | string | Path and filename of EDI file.
Example: "c:\inbound837s\ K837_5532.edi" |
| LogfileLocation | string | Path and filename of the log file. |
| LogLevel | integer | Select the logging level:
0 = Errors only 2 = Warnings and Errors 3 = Info, Warnings and Errors |
| AppendLog | boolean | Causes logging information to be appended to the existing log, rather than overwriting it.
0 = No 1 = Yes |
| DatabaseConnectString | string | If you want to use a connection string other than the one in Importer.ini, type it here.
Example: Oracle jdbc:oracle:thin:username/password@dbserver:port:instance Example: SqlServer jdbc:sqlserver://dbserver:port;databaseName=dbname;user=myuser;password=mypass; |
| ConnectionAttempts | integer | How many times should Importer try to connect to the database?
Default is 3. |
| AutoCommit | boolean | When shared data is encountered, Importer commits all uncommitted data, reducing the chance of deadlocks or blocking when multiple Importers are running.
0 = No 1 = Yes |
| Name | string | A unique name for this Importer instance, 1 to 50 characters.
This may be useful for your own purposes if you run multiple instances of Importer. |
| SenderLocation | string | Force the new sender partner to be internal or external.
Default lets Importer decide. |
| ReceiverLocation | string | Force a new receiver partner to be internal or external.
Default lets Importer decide. |
| DisplayVersion | boolean | Choose how much information should be written to the log. |
Output
The Output tab contains the following fields.
| Output Item | Datatype | Description |
|---|---|---|
| ReturnCode | string | The Importer return code.
Refer to Error Codes. |
