> 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/uc16.md).
# UC16
**CD --> SFG --> AMF --> S3**
**Use Case:** Partner31 (Sender) send files to SFG via CD protocol, we use GZIP and Deliver those files to the Partner32 (Receiver) using S3 protocol via AMF (Agile Messaging Framework).
**Sequence Diagram:**
**Steps:**
A. Onboard Partner31 in SFG via AMF and Partner 32 in AMF.
B. Onboard Partner31 connect direct node in SFG using AMF (Customer Initiated Communication Profile (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 GZIP Action as Action Type.
F. Create Delivery Action or use the predefined one (Deliver as is).
G. Create Workflow Definitions and add Actions (Created in **step E** and **step F**) as step1 and step2 respectively.
H. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition name (Created in **step G**).
I. Onboard Partner32 S3 Profile using AMF (MFT Initiated communication Profile (Outbound))
J. Create Communication Rule with Sender, Receiver, Message Type and Comm Profile Name.
K. Verify the Message Activity in AMF once the Partner31 uploads the file to SFG via CD protocol. If everything was configured correctly, the file will be delivered to Partner32 via S3 protocol.
**Process:**
**A. Onboard Partner31 and Partner32 in SFG via AMF:**
Login to AMF
!\[Graphical user interface, application
Description automatically generated]\(/files/hgD6zTgGkDrpPnOc2YH6)
Go to Onboarding -> Users
!\[Graphical user interface, application
Description automatically generated]\(/files/ZX64qPfovwhol78uKo9A)
Click on + icon at the top right corner
!\[Graphical user interface, text, application, Word
Description automatically generated]\(/files/f5oxlLNfyhd1K1wEvJ1l)
Select Customer and give details of Partner31, 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 we store the partner credentials? (LDAP or local (SFG/AMF) or Both)
Select the provider the Partner belong 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 the step2**.**
Verify the Partner details and click **Onboard User**.
!\[Graphical user interface, text, application, email
Description automatically generated]\(/files/NYbjINw63dOW3zPTPt8i)
Repeat the above steps to Onboard Partner32.
**B. Onboard Partner31 Connect Direct nodes in SFG using AMF (Customer Initiated Communication Profile (Inbound)).**
Double click on the Partner31
Click on + icon in the top right corner
Give details of the Node and click save
Once the onboarding was done, we can see the status as completed.
Give the details and click Save
1. **Operating System:** Operating system of the Partner31
2. **SPOE**: Option to enable/disable Secure point of entry
3. **Node Name:** Node name of Partner31
4. **Host Name/IP:** Host/IP of the Partner31 CD node
5. **Port:** Port of the Partner31 CD node
6. **Alternate IPs:** we can give there are any alternate IPs for this CD node
7. **Secure+:** Option to enable/disable secure+ for SSL (If secure+ was enabled)
8. **Cert File:** Public cert of the Partner31 CD node (In txt format with no headers) (If secure+ was enabled)
9. **Common Name:** Common name of the Partner31 CD (If secure+ was enabled)
10. **TLS Version:** TLS version to be used in the Communication (If secure+ was enabled)
11. **Ciphers:** Ciphers to be used in the Communication (If secure+ was enabled)
**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 Partner31 will send and Click Save.
**E. Create GZIP Action as Action Type.**
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
Create GZIP Action as Action Type and click save
**F. Create Delivery 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)
**G. Create Workflow Definition and add Actions (Created in step E and step F) as step1 and step2 respectively.**
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 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
**H. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition name (Created in step G).**
Go to Rules under Onboarding -> Workflow
Click on + icon at the top right
Give Sender, Receiver and Message Type and Workflow (Created in **step G**) and clicks save
**I. Onboard Partner32 S3 profile in SFG using AMF (MFT Initiated Communication Profile (Outbound))**
Double click on the Partner32
Click on + icon in the top right corner
Give details of the Node and click save
Give details and click save
1. **S3 bucket**: S3 Bucket name
2. **S3 Region**: Region where S3 belongs
3. **S3 Access Key ID:** Access key ID of the S3 bucket
4. **S3 Secret Key:** Secret key of S3 bucket
5. **Message to Process**: Option to process the original or current message
6. **Proxy Required:** Option to open connections via proxy server
7. **Proxy URL:** Proxy server URL (If proxy was enabled)
8. **Proxy User Name**: Proxy user name (If proxy was enabled)
9. **Proxy Password**: Proxy password (If proxy was enabled)
10. **Upload Path:** Path to upload files
11. **Cleanup on Delivery:** Option to clean the file in file system after the file was delivered (Once the file is cleaned, we cannot redeliver the file again)
Once the onboarding was done, we can see the status.
**J .Create Communication Rule with Sender, Receiver, Message Type and Comm Profile Name:**
Go to Rules under onboarding->communication
Click on + icon at top right corner
Select Sender, Receiver, Message Type and Comm. Profile name and click on save
**K. Verify the Message Activity in AMF once the Partner31 uploads the file to SFG via CD protocol. If everything was configured correctly, the file will be delivered to Partner32 via S3 protocol.**
Go to Message activity under Track N Trace
To see more details of the delivery double click on the record
Here we can see the details for the file delivered to the Partner32.
