Sample Mule flows listed below show the use of Thru MFT connector in interaction with Thru OptiPaaS server :

ProductCatalogUpdates flow :
A Participant (Partner) subscribed to Thru MFT Transport (MFT workflow) ‘Product Catalog Updates’ uploads a file to FTP location, Thru Transport fetches the file from the location and makes it available for Mule flows. Mule flow ‘ProductCatalogUpdates’ picks up the file from Thru MFT server and sends it back to all Participants subscribed to Thru MFT Transport ‘Product Catalog Updates’. Thru MFT connector operations used in this Mule flow: File Pickup, File Dropoff, Flow Outcome.

ProductCatalogUpdatesSelective flow :
A Participant (Partner) subscribed to Thru MFT Transport (MFT workflow) ‘Product Catalog Updates’ uploads a file to FTP location, Thru Transport fetches the file from the location and makes it available for Mule flows. Mule flow ProductCatalogUpdatesSelective picks up the file from Thru MFT server and sends it back to a randomly selected subset of partners subscribed to Thru MFT Transport ‘Product Catalog Updates’. Thru MFT connector operations used in this Mule flow: File Pickup, File Dropoff, Flow Outcome.

ContractRenewal flow :
A file is read from local disk on machine where Mule flow is running and is uploaded to Thru MFT Transport ‘Contract Renewal’. Thru MFT connector operation used in this Mule flow: File Dropoff.

InvoicePrivateExchange flow :
This is a Mule batch job. A Participant (Partner) subscribed to Thru MFT Transport ‘Invoice’ uploads a set of sample files to FTP location. Each file belongs to one of 3 categories: files with correct record information, files where correct and incorrect records are mixed and files with incorrect records. Thru Transport ‘Invoice’ fetches the file from the location and makes the files available for Mule flows. Mule flow InvoicePrivateExchangeStarter picks up the files from Thru MFT server using Thru Connector operation File Pickup and sends the files to the batch job InvoicePrivateExchange. Batch job InvoicePrivateExchange performs the following sequence of demo actions:

  • parses the file into individual records
  • each record is processed by applying a demo record validation in 2 steps:
    • first validation checks if a record has 3 fields. Record with > 3 fields is considered incorrect and causes an exception
    • second validation checks if a record ProductID field contains one of the allowed values “Product001”,“Product002”,“Product003”,“Product005”. Different field value causes an exception.
  • Failure section accumulates all exceptions and passes exception description and list of incorrect records to Thru MFT server. Exception information will be displayed in Transport activity for further analysis by operators. Size of exception information is limited by 10MB.

On completion of batch job, Thru MFT connector operation Flow Outcome sends a summary result of batch job to Thru MFT server with indication of passed/failed/mixed results and number of failed records.

Thru MFT connector operations used in these two Mule flows: File Pickup, Batch Exception Handler, Flow Outcome.

InvoicePrivateExchangeRealDropOff flow :
This Mule batch job is identical to previous flow and also returns a file with incorrect records back to Participant who sent the original file. A Participant (Partner) subscribed to Thru MFT Transport ‘Invoice’ uploads a set of sample files to FTP location. Each file belongs to one of 3 categories: files with correct record information, files where correct and incorrect records are mixed and files with incorrect records. Thru Transport ‘Invoice’ fetches the file from the location and makes the files available for Mule flows. Mule flow InvoicePrivateExchangeRealDropOffStarter picks up the files from Thru MFT server using Thru Connector operation File Pickup and sends the files to the batch job InvoicePrivateExchangeRealDropOff. Batch job InvoicePrivateExchange performs the following sequence of demo actions:

  • parses the file into individual records
  • each record is processed by applying a demo record validation in 2 steps:
    • first validation checks if a record has 3 fields. Record with > 3 fields is considered incorrect and causes an exception
    • second validation checks if a record ProductID field contains one of the allowed values “Product001”,“Product002”,“Product003”,“Product005”. Different field value causes an exception.
  • Failure section accumulates all exceptions and performs 2 actions:
    • passes exception description and list of incorrect records to Thru MFT server. Exception information will be displayed in Transport activity for further analysis by operators. Size of exception information is limited by 10MB.
    • creates a file which contains all incorrect records for each input file and uploads the file back to Thru MFT server which delivers the file to Participant who send the original data.

On completion of batch job, Thru MFT connector operation Flow Outcome sends a summary result of batch job to Thru MFT server with indication of passed/failed/mixed results and number of failed records.

Thru MFT connector operations used in these two Mule flows: File Pickup, Batch Exception Handler, File Dropoff, Flow Outcome.

Payment :
A Participant (Partner) subscribed to Thru MFT Transport ‘Payment’ manually uploads a file to Thru MFT server, Thru Transport ‘Payment’. Mule flow ‘Payment ‘ProductCatalogUpdatesSelective’ picks up the file from Thru MFT server and passes control to Thru MFT connector operation Flow Outcome which always returns a failure flag to Thru MFT Server Thru MFT connector operations used in this Mule flow: File Pickup, Flow Outcome.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment