UC26
Last updated
Last updated
MFG --> AMF -->UFA
Use Case: Partner51 (Sender) send files to SFG via HTTP (MFG) Protocol. We PGP decrypt those files and Deliver to the Partner52 (Receiver) via HTTP (UFA) Protocol using AMF (Agile Messaging Framework).
Sequence Diagram:
Steps:
A. Onboard Partner51 and Partner52 using AMF.
B. Create Message Type or use the existing one in AMF:
C. Create Message Mapping with Sender, Receiver and Message Type with a file pattern.
D. Install UFA agent (Partner52)
E. Onboard Partners Customer Initiated Download Profile.
F. Create Open PGP Decrypt Action as Action type.
G. Create Deliver Action or use the predefined one (Deliver as is).
H. Create Workflow Definition and add Actions (Created in step F and step G) as step1 and step2.
I. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in step H).
J. Verify the Message Activity in AMF once the Partner51 uploads the file to SFG via HTTP (MFG) Protocol. If everything was configured correctly; the file will be delivered to Partner52 via HTTP (UFA) Protocol.
Process:
A. Onboard Partner51 and Partner52 in SFG via AMF:
Login to AMF
Go to on boarding ->Users
Click on + icon at the top right corner
Select Customer and give details of Partner51, 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 we store the Partner credentials? (LDAP or local (SFG/AMF) or Both
Select the provider the 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 the step -2.
Verify the Partner details and click Onboard User.
Repeat the same steps for Partner52. Use AMF Provider for UFA User.
B. Create Message Types 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 Types (GENERIC)
C. 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 Partner51 will send and clicks save.
D. Install UFA agent (Partner52).
Please refer the UFA installation document for this step
E. Onboard Partner52 Customer Initiated Download Profile:
Double click on Partner52
Click on + icon at the top right corner
Select the Protocol as UFA, Operation as download give the remaining details and click save.
Download Folder: Folder where the files will come from AMF.
Sender: Sender name who is sending files (Partner52 in this case)
Receiver: Receiver name to whom we are delivering files via AMF (Partner51 in this case).
Message Type: Message type we used in this case (GENERIC)
Polling Interval: The polling interval between the sync between UFA agent and server.
Run Script After Download: Script name with path if we want to run any scripts after the file was downloaded.
Chunk Size: Size of the files that will be transferred in bits when there is a large file transfer
PGP Decrypt: Option to decrypt the downloaded file.
Cleanup on delivery: Option to clean the file in file system after successful delivery
Clean Large Files: Option to clean only large file that meets the threshold given (Sample shown below).
Validate MD5 Check Sum: Option to validate the MD5 Checksum on uploaded files.
F. Create Open PGP Decrypt Action as Action Type.
Go to Actions under onboarding->Workflow
Click on + icon to create new Action
Give Name select Open Pgp Decrypt as Action Type and clicks save.
G. Create Deliver as Action Type or use the predefined one (Deliver as is)
Go to Actions under on boarding-> Workflow
Click on + icon to create new Action
Give Name and select Deliver as Action Type and clicks save.
H. Create Workflow Definition and add Actions (Created in step F and step G) as step1 and step2.
Go to Definitions under on boarding->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 Open Pgp Decrypt Action that we created in step F as step1 and click save.
Select the Deliver Action that we created in step G as step2 and click save.
I. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in step H).
Go to Rules under on boarding -> Workflow
Click on + icon at the top right
Give Sender, Receiver, Message Type and Workflow (Created in step H) and click on save
J. Verify the Message Activity in AMF once the Partner51 uploads the file to SFG via HTTP (MFG) Protocol. If everything was configured correctly, the file will be delivered to Partner52 via HTTP (UFA) Protocol.
Go to Message Activity under Track N Trace
Here we can see the details for the file Delivered to the Partner52
