Understanding integrations that include transformations

What is it?

One typical type of integration is the endpoint > transformation > endpoint, which includes processing through the CIC transformation engine. This type of integration includes two or more data flows - one to transfer the data to the transformation engine and one or more to transfer the data to its ultimate destination after transformation processing. In a real-world scenario, this might reflect a particular document from the source endpoint that is parsed in the transformation engine, and the resulting output data delivered to the destination endpoint.

For the first data flow, the From endpoint type can be File System, FTP, AS2, SFTP, or Partner Mailbox and the To endpoint type must be Transformation.

For the second data flow, the From endpoint type must be Transformation and the To endpoint type can be File System, FTP, AS2, SFTP or Partner Mailbox.

What happens inside the integration

The following sequence takes place inside an integration that includes a transformation.

  1. The first data flow runs, started either automatically or by clicking Run Now.
  2. CIC receives the file to be transferred, creates a job for the integration, and sends the data to the transformation engine.
  3. The transformation engine processes the data and creates one or more files to send to the destination endpoint of secondary data flows.
  4. For each file it creates, the transformation engine starts a secondary data flow, which sends the processed files to their destinations.

For example, the illustration below shows what you see when you click an integration with a transformation on the Actvity > Integrations page.

In this case, a data flow (AS2-to-Transformation) was run to send an EDI file from Rick's Sporting Goods via AS2 to the transformation engine. CIC created Job 48 for the integration and passed the job on to the transformation engine, which performed the transformation processing required for the data flow. When transformation processing completed, the transformation engine triggered a separate secondary data flow (Transformation-to-FS) for each document that the transformation created, and delivered the documents to the FS endpoint(s). If you clicked the File System link in the illustration above, you would see the documents extracted from the original EDI file, that is, POs, invoices, and so forth.