Enterprises are adopting more agile, cost-effective, business technologies to keep pace with rapidly-changing expectations and requirements. According to Gartner more than 60% of midsize and large organizations will deploy Managed File Transfer (MFT) technologies to support a growing number of digital business use cases.
However, it is difficult to integrate MFT processes into a business’ ecosystem due to various factors, including:
- Difficult partner management (access, endpoint configuration, process subscription, etc.)
- Inadequate monitoring and control (centralized visibility into activity)
- Inflexible connectivity to business process flows
Thru MFT Connector for MuleSoft and the Thru platform revolutionize enterprise file exchange by providing the first cloud-native MFT as a Service (MFTaaS) solution that delivers frictionless “plug-and-play” functionality to the MFT ecosystem.
A common use case for managed file transfer today is B2B file exchange with external partner organizations. Previously, when enterprises needed to connect new partners or manage existing partner connections to file exchange processes, they needed to share and configure endpoints for each point-to-point exchange of documents.
In today’s API economy, file exchange partners expect to be onboarded to business processes quickly, in minutes – not days. As a result, enterprises are driven to orchestrate business solutions quickly, while eliminating the redundant maintenance activities that are consuming valuable resources and improving visibility and tracking of file exchange activity across all file exchange partners.
The Solution: Thru MFT Connector for MuleSoft
By connecting Mule flows in Anypoint Platform to Thru’s MFTaaS service offerings of its platform, enterprises are now able to:
- Onboard new customers and complete setup in a matter of minutes
- Enable “self-service” for partners so they self-manage common tasks such as maintaining user access, endpoints and subscriptions to published business processes etc.
- Enable a “single pane of glass” view into all enterprise wide file transfer activity through centralized real-time dashboards for increased visibility and governance
- Decouple partner specific parameters (endpoints, FTP locations, etc.) from Mule flows for increased robustness and lower maintenance costs
As illustrated below, Thru’s MFTaaS solution reduces complexity and improves process agility by separating business process logic in MuleSoft from partner management on the Thru platform.
Use Case: Send Purchase Order with Thru & MuleSoft
The configuration needed for a Managed File Transfer use case can be broken down into a series of steps performed by two stakeholders:
- The enterprise: e.g. ACME Corp
- The partner: e.g. Joe’s Supply
In our example, we will look at a scenario where ACME Corp sends Purchase Orders to the various suppliers for part shipment and receive invoices. In this article, we focus on the first half of the transaction, ACME sending the purchase order file to one specific partner: Joe’s Supply.
1. ACME Corp Activities:
Step 1. Define logic in Thru’s platform (i.e. a transport) that publishes the file to any/all of its subscribing partners.
Step 2. Define a sample partner organization, e.g. Joe’s Supply.
Step 3. Define a Mule flow that is responsible for the pre-work of generating the file. In this example, the flow will simply read from a folder.
2. Joe’s Supply Activities:
Someone from Joe’s Supply can log in to Thru and subscribe to the transport and then define how they would like to receive the purchase order in a self-service manner.
Step 1. Add and configure Transport in Thru
The first step is for ACME Corp to define logic that publishes file(s) to any/all of its subscribing partners.
Click on “Add a Transport” from the main Transport home page.
Give it a name, e.g. “Send Purchase Order.”
Select “Push” as the transport type, since ACME corp will be pushing the purchase order file to its suppliers.
Select “MuleSoft – Anypoint Flow” which is where the flow will be defined.
Click on “Add a system” and type “Joe’s Supply” as the system, click “Next.”
Click on “Create Transport” to complete this process.
The next step is the define and capture credentials for flow access; this will be through a Mule flow.
Click on the newly created Transport to view its details.
Click on the “Flow Access” icon to configure Access Type.
Click on “Choose Access Type.”
Click on “Web API Secret Key,” which will create and display all access configuration values that will be used during the Thru MFT Connector setup in the Mule flow.
Please note that you need to copy all the flow access information to configure the connector in Anypoint Studio.
Step 2. Defining a Partner (Onboarding Joe’s Supply)
The second step is for ACME Corp to setup a partner (e.g. Joe’s Supply), so they can log in to the platform and self-configure how they want to receive the file.
Click on the second icon on the left to view the Organization List.
Click on “Add an Organization.”
Give it a name, e.g. Joe’s Supply.
Click on the newly created Org to view the details.
Click on “Users” and the icon to Add a user record for Joe. This will allow Joe to log in and subscribe to specific transports that are available to his organization.
Step 3. Defining a Mule Flow
The third step is for ACME Corp to define and configure the Mule flow that will pick up the file from the source system. Then, the flow will perform all the necessary operations and call Thru to initiate the transfer of the file.
Create a new Mule project and drag-and-drop the Thru MFT Connector into the Mule flow, as needed.
Define the location of where the purchase file will be picked up by the Mule flow.
Configure each instance of the Thru MFT Connector in your Mule flow using the captured Flow Key that was generated in Thru.
Step 4. Partner Organization (Joe’s Supply) Activities
The last step is for Joe to subscribe to Thru transports and define how he would like to receive the published purchase order from ACME Corp.
Open the landing page setup for the partner org.
Click on “End points” and then click on “+ Add an End Point.”
There are various ways to receive the file. For example, organizations can set up multiple defined endpoints that are reusable across various subscriptions. In this example, we will opt to receive the files through email.
Select “Mail with file links” as the option to receive the files.
Provide the email where you want to receive the file.
Click on “+ Add a subscription” and select the “Send Purchase Order” that we created earlier.
Click on the “Play” icon to view the details of the process.
Click on “Add a target end point” and select the email endpoint configured earlier to complete the setup process.
Lastly, drop any file to the location configured in the File Connector Path in the Mule flow; this will be picked up and sent to Thru’s system, which will deliver to Joe’s Supply via the defined endpoints. All activities can be monitored in real-time via the File Delivery dashboard and by inspecting endpoints.
In summary, Thru’s new MFT connector for MuleSoft enables organizations to quickly and efficiently implement file exchange processes across the entire enterprise and drastically reduces the resources required to maintain point-to-point integrations.
How to Get Started with Thru MFT Connector for MuleSoft
To get started, follow these two simple steps: