Appendix B - Integration with TIBCO Foresight Transaction Insight

Foresight REST API could send validation results file and the EDI file to the inbound or outbound folder of the Foresight Transaction Insight importer. To support the function, two new job POST parameters are added publishReport and createTrk. For more information, see Processing and Output Resources.

The following properties are set in the FSREST.ini file by default, for the directories to copy the EDI file and Details file. Foresight Transaction Insight importer should be able to access this location. Once a JOB request is done, the EDI file and details file get copied to the folders. The directories can be sub-folder under mount_path (for example, /tmp) set in the standalone-deployment\config\deployment.properties file.

TIInboundPath and TIOutboundPath can be set via system variables FSREST_TIInboundPath and FSREST_TIOutboundPath, with higher priority, and can be updated using PUT updateEnv request as well, see the following sections:

TIInboundPath=/tmp/inbound

TIOutboundPath=/tmp/outbound

For Inbound transactions, the B2B Gateway needs to send the files to the inbound folder defined by TIBCO.

For Outbound files, an internal application sends the files to the outbound folder defined by TIBCO.

The EDI data is renamed to JobID.edi and the details file is renamed to JobID.dtl. The EDI file can be passed via Data and InDatafileRef parameters. To skip one or multiple transaction set types for the copy operation, a new property skipTS is added in the FSREST.ini file, with the default value none, the valid values are none, or the transaction set names, separated by commas. For example, 837, 850.

If you need to set the values, you can set the system variable FSREST_SKIPTS, or update the values with a PUT updateEnv request.

You can check the status of the copy operations in logs.