> For the complete documentation index, see [llms.txt](https://amfdocs.mftlabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amfdocs.mftlabs.io/agile-messaging-framework/tutorials/usecases/uc08.md).
# UC08
### **SFTP --> SFG --> AMF --> UFA**
**Use Case:** Partner15 (Sender) send files to SFG via SFTP protocol, We Zip and Deliver those files to the Partner16 (Receiver) via UFA protocol using AMF (Agile Messaging Framework).
**Sequence Diagram:**
**Steps:**
A. Onboard Partner15 in SFG using AMF and Partner16 in AMF.
B. Onboard Partner15 SFTP Customer Initiated Communication Profiles (Inbound).
C. Create Message Types or use the existing one in AMF.
D. Create Message Mapping with Sender, Receiver and Message Type with a file pattern.
E. Install UFA agent (Partner16)
F. Onboard Partner16 Customer Initiated Download Profile.
G. Create Zip Action as Action type.
H. Create Deliver Action or Use the predefined one (Deliver As is).
I. Create Workflow Definition and add Actions (Created in **step G** and **step H)** as step1 and step2.
J. Create Workflow Rule with Sender, Receiver, MessageType and Workflow Definition Name (Created in **step I**).
K. Verify the Message Activity in AMF once the Partner15 uploads the file to SFG via SFTP protocol. If everything was configured correctly, the file will be delivered to Partner16 via UFA protocol.
**Process:**
**A. Onboard Partner15 in SFG using AMF and Partner16 in AMF:**
Login to **AMF**
Go to Onboarding -> **Users**
Click on + icon at the top right corner
Select Customer and give details of partner15, select UserType, AuthenticationType and click next.
1. **UserType**: Which Zone does the partner belong to send or receive files? (DMZ or Trusted)
2. **Authentication Type**: Where do we store the partner credentials? (LDAP or local (SFG/AMF) or Both)
Select the provider the partner belongs to and click next
1. **AMF:** AMF provider is used to onboard partners which use UFA
2. **IBM:** This will come from the provider’s config. We can choose several types based on the provider's config.
3. **Open Ldap:** We need to select this if we selected the Authentication Type as LDAP in step **2.**
Verify the partner details and click **Onboard User**.
Repeat the same steps for Partner16. Using AMF Provider for UFA user.
**B. Onboard Partner15 SFTP Customer Initiated Communication profiles (Inbound).**
Double click on Partner15
Click on + icon at the top right corner
Select the protocol as SFTP Inbound and click save.
Once the on boarding was done, we can see the status as completed.
**C. Create MessageTypes or use the existing one in AMF:**
Go to MessageTypes under Onboarding
Click on + icon in the right corner to add a new Message Types
**Note**: In this scenario we will use the existing Message Type (GENERIC)
**D. Create Message Mapping with Sender, Receiver and Message Type with a file pattern:**
Go to Message Mapping under Onboarding
Click on + icon at the top right corner
Select Sender, Receiver, and Message Type give pattern of the files that Partner15 will send and click save.
**E. Install UFA agent (Partner16).**
Please refer the UFA installation document for this step
**F. Onboard Partner16 Customer Initiated Download profile:**
Double click on Partner16
Click on + icon at the top right corner
Select the protocol as UFA, Operation as download, give the remaining details and click save.
1. **Download Folder**: Folder where the files will come from AMF.
2. **Sender**: Sender name who is sending files (Partner15 in this case)
3. **Receiver**: Receiver name to whom we are delivering files via AMF (Partner16 in this case).
4. **Message Type:** Message type we used in this case (GENERIC)
5. **Polling Interval:** The polling interval between the sync between UFA agent and server.
6. **Run Script After Download:** Script name with path if we want to run any scripts after the file was downloaded.
7. **Chunk Size:** Size of the files that will be transferred in bits when there is a large file transfer
8. **PGP Decrypt:** Option to decrypt the downloaded file.
9. **Cleanup on delivery:** Option to clean the files from filesystem after successful delivery
10. **Clean Large Files:** Option to clean only large file that meets the threshold given (Sample shown below).
11. **Validate MD5 Check Sum:** Option to validate the MD5 Checksum on uploaded files.
**G. Create ZIP Action as Action type**
Go to Actions under Onboarding-> Workflow
Click on + icon to create new action
Give Action Name, select ZIP as Action type.
**H. Create Deliver Action or Use the predefined one (Deliver As is**).
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
**Note**: In this scenario we will use the existing Action (Deliver as is)
**I. Create Workflow Definition and add Actions (Created in step G and step H) as step1**
**and step2**
Go to Definitions under onboarding**-> Workflow**
Click on + icon at the top right corner.
Give Workflow Name, Description and clicks save**.**
Double click on the Workflow Definition Name.
Click on the + icon at the top right corner.
Select the zip action that we created in **step G** as step1 and click save.
Select the Deliver As Is that we created in **step H** as step2 and click save.
**J. Create Workflow Rule with Sender, Receiver, MessageType and Workflow Definition Name (Created in step I).**
Go to Rules under Onboarding -> **Workflow**
Click on + icon at the top right
Give Sender, Receiver, MessageType and Workflow (Created in **step I**) and click on save
**K. Verify the Message activity in AMF once Partner15 uploaded the files to SFG via SFTP protocol. If everything is configured correctly, the file will be delivered to Partner16 via UFA protocol.**
Go to Message activity under Track N Trace
Here we can see the file delivered to the Partner16
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://amfdocs.mftlabs.io/agile-messaging-framework/tutorials/usecases/uc08.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.