UC07
Last updated
Last updated
Use Case: Partner13 (Sender) send files to SFG via SFTP protocol, We Zip and deliver those files to the Partner14 (Receiver) using HTTP protocol (MFG) from SFG via AMF (Agile Messaging Framework).
Sequence Diagram
Steps:
A. Onboard Partner13 and Partner14 in SFG using AMF.
B. Onboard Partner13 SFTP profile in SFG using AMF (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. Create Zip Action as Action type.
F. Create Mailbox Action as Action type.
G. Create Workflow Definition and add Actions (Created in step E and step F) as step1 and step2.
H. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in step G).
I. Verify the Message activity in AMF once Partner13 uploads the file to SFG via SFTP protocol. If everything was configured correctly, the file will be Mailboxed to Partner14 via HTTP protocol (MFG).
Process:
A. Onboard Partner13 and Partner14 in SFG via AMF:
Login to AMF
Go to Onboarding -> Users
Click on + icon at the top right corner
Select Customer and give details of Partner13, select User Type, Authentication Type and click next.
User Type: Which Zone does the Partner belong to send or receive files? (DMZ or Trusted).
Authentication Type: Where do we store the Partner’s credentials? (LDAP or local (SFG/AMF) or both.
Select the provider Partner belongs to and click next
AMF: AMF provider is used to onboard Partners which use UFA
IBM: This will come from the provider’s config. We can choose several types based on the provider's config.
Open Ldap: We need to select this if we selected the Authentication Type as LDAP in step 2.
Verify the Partner’s details and click Onboard User.
B. Onboard Partner13 SFTP in SFG using AMF (Customer Initiated communication profiles (Inbound)).
Double click on the Partner13
Click on + icon in the top right corner
Give details of the SFTP Inbound and click save
Once the Onboarding was 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 Partner13 will send and click save.
E. Create Zip Action as Action type
Go to Actions under Onboarding-> Workflow
Click on + icon to create new action
Give Name, select ZIP as Action Type.
F. Create Mailbox Action as Action Type.
Give Name, select Mailbox as Action Type.
Mailbox Path: Path of the receiver (Partner14) mailbox
Extraction Count: Option to add extraction for sent file (default value is 1).
G. Create Workflow definition and add Actions (Created in step E and step F) as step1 and step2.
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.
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, Message Type and Workflow (Created in step G) and click on save
I. Verify the Message activity in AMF once the Partner13 uploads the file to SFG via SFTP protocol. If everything was configured correctly, the file will be Mailboxed to Partner14 via HTTP Protocol (MFG).
Go to Message activity under Track N Trace
Here we can see the file Mailboxed to the Partner14
