# UC25
**Azure Blob --> SFG --> AMF --> SFG -->** **CD**
**Use Case:** We run Schedule to get file from Partner49 (Sender) folder to SFG via Azure blob Protocol, we use Actions Unzip, EOL Conversion and Deliver those files to the Partner50 (Receiver) using CD Protocol via AMF.
**Sequence Diagram:**
**Steps:**
A. Onboard Partner49 and Partner50 in SFG using AMF.
B. Onboard Partner49 Azure Blob receives profile in SFG using AMF (MFT Initiated Communication Profile (Download)).
C. Create Communication Rule with Sender, Receiver, Message Type and Comm. profile Name Select Delivery Type as Schedule.
D. Onboard Partner50 Connect Direct node in SFG using AMF (Customer Initiated Communication Profile (Inbound)).
E. Create Message Type or use the existing one in AMF.
F. Create Message Mapping with Sender, Receiver and MessageType with a file pattern.
G. Create UNZIP Action as Action Type.
H. Create EOL Conversion Action as Action Type.
I. Create Delivery Action or use the predefined one (Deliver as is).
J. Create Workflow Definitions and add Actions (Created in **step G** and **step H** and **step I**) as step1, step2 and step3 respectively.
K. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in **step J**).
L. Onboard Partner50 Connect Direct node Profile in SFG using AMF (MFT Initiated Communication Profile (Outbound))
M. Create Communication Rule with Sender, Receiver, Message Type and Comm. profile Name.
N. Verify the Message Activity in AMF once the Partner49 uploads the file to SFG via Azure blob Protocol. If everything was configured correctly, the file will be delivered to Partner50 via CD Protocol.
**Process:**
**A. Onboard Partner49 and Partner50 in SFG using AMF**
Login to AMF
!\[Graphical user interface, application
Description automatically generated]\()
Go to Onboarding -> Users
!\[Graphical user interface, application
Description automatically generated]\()
Click on + icon at the top right corner
Select Customer and give details of Partner49, 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 providers 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 step **-2.**
Verify the partner details and click **Onboard User**.
!\[Graphical user interface, text, application
Description automatically generated]\()
Verify the Partner details and click Onboard User.
Repeat the above steps to Onboard Partner50.
**B. Onboard Partner49 Azure blob receives profile in SFG using AMF (MFT Initiated Communication Profile (Download)).**
Double click on the Partner49
Click on + icon in the top right corner
Give details of the Azure blob MFT Initiated Download Profile details and click save
1.**Access Token Url**: Using the url property of the client object.
2**.SAS Token Url**: URL to get the SAS token.
3\. **Download Url:** A hyperlink that points to a location within the Internet where the user can download a file.
4\. **File Pattern**: Pattern to filter the files.
5\. **Archive Path:** The given archive file should be one of .zip, .tar, .tar. gz, .tgz and .jar. To list the archive files that have been added, use LIST ARCHIVE.
6\. **Error Path:** Error where users are putting in the wrong path or name on the command line.
7\. **File Format:** The extension is separated by a period from the name and contains three or four letters that identify the format.
8\. **Token Details**: A token is an object that represents something else, such as object.
9\. **Container:** A container organizes a set of blobs, similar to a directory in a file system
10\. **Download Folder**: Folder to download files.
11\. **Proxy Required**: Option to open connections via proxy server.
12\. **Proxy URL**: Proxy server URL (If proxy was enabled)
13\. **Proxy Username**: Proxy username (If proxy was enabled)
14\. **Proxy Password**: Proxy password (If proxy was enabled)
Once the onboarding was done, we can see the status.
**C. Create Communication Rule with Sender, Receiver, Message Type and Comm Profile Name. Select Delivery Type as Schedule.**
Go to Comm. Rule under Onboarding
Click on + icon in the top right corner
Select Delivery Type as Schedule
**D. Onboard Partner50 Connect Direct node in SFG using AMF (Customer Initiated Communication Profile (Inbound)).**
Double click on the Partner50
Click on + icon in the top right corner
Give details of the CD node in Customer Initiated Communication Profile (Inbound)).
1. **Operating System:** Operating system of the CD Partner50
2. **SPOE:** Option to enable/disable Secure point of entry
3. **Node Name:** Node name of Partner50 CD Node
4. **Host Name/IP:** Host/IP of the Partner50 CD Node
5. **Port:** Port of the Partner50 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 Partner50 CD Node (In txt format with no headers) (If secure+ was enabled)
9. **Common Name:** Common Name of the Partner50 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)
**E. Create Message Type or use the existing one in AMF:**
Go to Message Type 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)
**F. Create Message Mapping with Sender, Receiver and MessageType with a file pattern**
Go to Message Mapping under Onboarding
!\[Graphical user interface, application, Teams
Description automatically generated]\()
Click on +icon at the top right corner
Select Sender, Receiver, and Message Type give pattern of the file that Partner49 will send and Click Save.
!\[Graphical user interface, application
Description automatically generated]\()
!\[Graphical user interface, application, table
Description automatically generated]\()
**G. Create UNZIP Action as Action Type.**
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
!\[A screenshot of a computer
Description automatically generated]\()
Create UNZIP Action as Action Type and click save
!\[A screenshot of a computer
Description automatically generated]\()
**H. Create EOL Conversion Action as Action Type.**
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
!\[A screenshot of a computer
Description automatically generated]\()
Create EOL Conversion Action as Action Type and click save
**I. Create Delivery Action or use the predefined one (Deliver as is):**
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
!\[A screenshot of a computer
Description automatically generated]\()
Create Deliver Action as Action Type and click save
!\[A screenshot of a computer
Description automatically generated]\()
**Note**: In this scenario we will use the existing Action (Deliver as is)
**J. Create Workflow Definition and add Actions (Created in step G, step H and step I) as step1, step2 and step3 respectively.**
Go to Definitions under Onboarding->Workflow
!\[Graphical user interface, application, table
Description automatically generated]\()
Click on + icon at the top right corner
!\[Graphical user interface, application
Description automatically generated]\()
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 G** as step1 and click save.
!\[A screenshot of a computer
Description automatically generated]\()
Select the Action that we created in **step H** as step2 and click save
!\[A screenshot of a computer
Description automatically generated]\()
Select the Action that we created in **step I** as step3 and click save
!\[A screenshot of a computer
Description automatically generated]\()
!\[A screenshot of a computer
Description automatically generated]\()
**K. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in step J).**
Go to Rules under Onboarding -> Workflow
!\[Graphical user interface, application, table
Description automatically generated]\()
Click on + icon at the top right
!\[Graphical user interface, application
Description automatically generated]\()
Give Sender, Receiver, Message Type Workflow (Created in **step J**) and click on save
!\[A picture containing text, indoor, screenshot
Description automatically generated]\()
**L. Onboard Partner50 Connect Direct Node Profile in SFG using AMF (MFT Initiated Communication Profile (Outbound))**
Double click on the Partner50
Click on + icon in the top right corner
Give details of the Node and click save
Give the details and clicks save
1. **SPOE:** Option to know if user 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 in the user 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 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 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.
**L. Create Communication Rule with Sender, Receiver, Message Type and Comm Profile Name:**
Go to Rules under onboarding-> Communication
!\[Graphical user interface, text, application
Description automatically generated]\()
Click on + icon at top right corner
!\[Graphical user interface, application
Description automatically generated]\()
Select Sender, Receiver, Message Type and Comm. Profile name and click save
!\[Graphical user interface, application
Description automatically generated]\()
**M. Verify the Message Activity in AMF once the Partner49 uploads the file to SFG via Azure blob Protocol. If everything was configured correctly, the file will be delivered to Partner50 via CD Protocol.**
Go to Message Activity under Track N Trace
!\[Graphical user interface, application
Description automatically generated]\()
To see more details of the Delivery double click on the record
!\[A screenshot of a computer
Description automatically generated]\()
Here we can see the Process Name, Process Number, Message ID, DDSN etc. for the file delivered to the Partner50
