Page 1 of 1

Using GoAnywhere for AS2 with Inovis TrustedLink

Posted: Wed Nov 16, 2016 10:46 am
by jreed
I just started my demo of GoAnywhere MFT. I am looking to integrate it with Inovis TrustedLink. Has anyone done this or have information on the best way to go about it?

Re: Using GoAnywhere for AS2 with Inovis TrustedLink

Posted: Tue Nov 29, 2016 5:23 pm
by Support_Rick
We have customers that use it with TrustedLink as well as Gentran as well as Extol. it's easy to integrate the communication into the DB2 tables or MSSQL and trigger CLP or Stored Procedures.

Is there something specific you're needing?

Re: Using GoAnywhere for AS2 with Inovis TrustedLink

Posted: Thu Dec 01, 2016 9:12 am
by jreed
Support_Rick wrote:
We have customers that use it with TrustedLink as well as Gentran as well as Extol. it's easy to integrate the communication into the DB2 tables or MSSQL and trigger CLP or Stored Procedures.

Is there something specific you're needing?
Rick,

Like I said we are using trustedlink. TrustedLink creates the EDI files and places them on a folder on the IFS. We then send them on to the trading partner. TrustedLink sends all docs to a folder on the IFS and I need GoAnywhere to read the file and decide which trading partner to send to.

Re: Using GoAnywhere for AS2 with Inovis TrustedLink

Posted: Thu Dec 01, 2016 9:22 am
by Support_Rick
OK, with that being defined, you will need to parse out directional information from the EDI doc (EDIID or ISA number or something) which GoAnywhere can do if you know the location and or triggers to find that.

GoAnywhere is not an X12 translation reader. But, we can take the contents of a file an read them (readFlatFile) or we can assign the contents of a file to a variable and see if it "contains" a value or parse a value from that value to determine direction.

I know that trustedlink places files in the IFS, but it also has data in a DB2 table (if you're using iSeries) so there are multiple ways you can get the data, create the EDI Doc and transfer it.

We can handle either way...