> 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/uc13.md).
# UC13
### **MFG** **--> SFG --> AMF --> SFG -->CD**
**Use Case:** Partner25 (Sender) sends files to SFG via HTTP (MFG) protocol, we change file name, GZIP and deliver those files to Partner26 (Receiver) using CD protocol from SFG via AMF (Agile Messaging Framework).
**Sequence Diagram:**
**Steps:**
A. Onboard Partner25 and Partner26 in SFG using AMF.
B. Onboard Partner26 Connect Direct Node in SFG using AMF (Customer Initiated Communication profiles (Inbound)).
C. Create Message Type or use the existing one in AMF.
D. Create Message mapping with Sender, Receiver and Message Type with a file pattern.
E. Create Route Action with Changing file name, date format.
F. Create GZIP Action as Action Type.
G. Create Deliver Action as Action Type or use the predefined one (Deliver as is).
H. Create Workflow definitions and add Actions (Created in **step E, step F and step G)** as step 1, step2 and step3 respectively.
I. Create Workflow Rule with Sender, Receiver, Message Type and Workflow definition name (Created in **step H**).
J. Create MFT Initiated profile for outbound delivery in Partner26 with CD Protocol.
K. Create Communication Rule with Sender, Receiver, Message Type and Comm. Profile Name.
L. Verify the Message Activity in AMF once Partner25 uploads the file to SFG via HTTP (MFG) Protocol. If everything was configured correctly, the file will be delivered to Partner26 via CD Protocol.
**Process:**
**A. Onboard Partner25 and Partner26 in SFG via AMF:**
1. Login to AMF
Go to Onboarding ->**Users**
Click on + icon at the top right corner
Select Customer and give details of Partner25, select User Type, Authentication Type and click next.
1. **User Type**: 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:** The details 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 **4-ii.**
Verify the Partner details and click **Onboard User**.
Repeat the above steps to Onboard Partner26.
**B. Onboard Partner26 Connect Direct Node in SFG using AMF (Customer Initiated Communication Profiles (Inbound)).**
1. Double click on the Partner26
Click on + icon in the top right corner
Give details of the Node and click save
1. **Operating System:** Operating system of the Partner26
2. **SPOE:** Option to enable/disable Secure point of entry
3. **Node Name:** Node name of Partner26
4. **Host Name/IP:** Host/IP of Partner26 CD node
5. **Port:** Port of Partner26 CD node
6. **Alternate IPs:** we can give here any alternate IPs for this CD node
7. **Secure+:** Option to enable/disable secure+ for SSL
8. **Cert File:** Public cert of Partner26 CD node (In txt format with no headers)
9. **Common Name:** Common name of Partner26 CD
10. **TLS Version:** TLS version to be used in the communication
11. **Ciphers:** Ciphers to be used in the communication
12. Once the onboarding is done, we can see the status as completed.
**C. Create Message Type or use the existing one in AMF:**
Go to Message Types under Onboarding
Click on + icon in the right corner to add a new message type
**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 Partner25 will send and click save.
**E. Create Route Action as Action Type**.
Go to Action under Onboarding->Workflow
Click on + icon to create new action
Create Route Action with Changing file name, date format and click save.
**F. Create GZIP Action as Action Type**
Go to Action under Onboarding->Workflow
Click on + icon to create new action
Create GZIP Action as Action Type and click save
**G. Create Deliver Action as Action Type or use the predefined one (Deliver as is).**
Go to Action under Onboarding->Workflow
Click on + icon to create new action
Create Deliver Action as Action Type and click save
**H. Create Workflow definitions and add Actions (Created in stepE, stepF and step G) as step1, step2 and step 3 respectively.**
Go to Definitions under Onboarding->Workflow
Click on + icon at the top right corner
Give Workflow Name, Description and click save
Double click on the Workflow Definition name
Click on the + icon at the top right corner
Select the Action that we created in (**step E)** as step1 and click Save.
Select the Action that we created in (**step F)** as step2 and click save.
Select the Action that we created in (**step G)** as step3 and click save.
**I. Create Workflow Rule with Sender, Receiver, Message Type and Workflow definition name (Created in step H).**
Go to Rules under Onboarding -> Workflow
Click on + icon at the top right
Give Sender, Receiver, Message Type, Workflow (created in **step H**) and click on save
**J. Create MFT Initiated profile for outbound delivery in Partner26 with CD protocol.**
Select MFT initiated and give the details
1. **SPOE:** Option to know if Partner26 will use SPOE or not (If SPOE was not used then we need to give **Remote user ID** and **Remote Password**)
2. **Submitter User ID:** Option to pass submitter user ID
3. **Remote User ID:** Remote User ID of Partner26 node
4. **Use Source File Name:** Option to use source filename.
5. **Remote File Name:** Remote file name if you disabled the **Use Source File Name** in the step 3-iv.
6. **Remote Path:** Path for the file to be placed.
7. **Disposition:** dropdown to select disposition of the file
8. **Binary mode:** Option to enable or disable binary mode for file transfer
9. **Copy Statement Sys opts:** Option to execute copy step Sys opts. If we enable that we need to give the Sys opts to run
10. **Run Task:** Option to execute Run task Sys opts. If we enable that we need to give the Sys opts to run
11. **Run Job:** Option to execute run job Sys opts. If we enable that we need to give the Sys opts to run
12. **Send Email Notifications:** Option to send email notifications for successful delivery
13. **Receivers Mail Ids:** Recipients mail addresses if we enable **Send Email Notifications**.
14. **Clean up on Delivery:** Option to clean the file system after the file was delivered (Once the file was cleaned, we cannot redeliver the file again)
**K. Create Communication Rule with Sender, Receiver, Message Type and Comm. profile Name.**
Go to Rules under Onboarding -> Communications
Click on + icon at the top right
Select Sender, Receiver, Message Type, Comm. profile name and click on save
**L. Verify the Message activity in AMF once Partner25 uploads the file http (MFG) to SFG via HTTP protocol. If everything was configured correctly, the file will be delivered to Partner26 via CD protocol.**
Go to Message activity under Track N Trace
To see more details of the delivered double click on the record
Here we can see the Process Name, Process Number, Message ID, DDSN etc. for the file delivered to the Partner26
---
# 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/uc13.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.