Last updated
Last updated
Use Case: Partner A (Sender) sends files to AMF via HTTP (UFA) protocol, We Unzip, Route, do EOL and Mailbox those files to Partner B (Receiver) via AMF.
Sequence Diagram:
Steps:
A. Onboard Partner A in AMF and Partner B in SFG using AMF.
B. Install UFA agent (Partner A).
C. Create Message Type or use the existing one in AMF.
D. Create Partner A Customer Initiated Upload profile.
E. Create Unzip as Action type.
F. Create Route with adding file name format.
G. Create EOL Conversion as Action type.
H. Create Mailbox Action as Action type.
I. Create Workflow definition and add Actions (Created in step e, step f, step g, step h) as step1 step2, step3 and step4.
J. Create Workflow Rule with Sender, Receiver, Message Type and Workflow definition name (Created in step i).
K. Verify the Message activity in AMF once Partner A uploads the file to SFG via UFA protocol. If everything is configured correctly, the file will be Mail boxed to Partner B via HTTP protocol (MFG).
Process:
A. Onboard Partner A in AMF and Partner B in SFG using AMF:
Login to AMF
Go to Onboarding -> Users
Click on + icon at the top right corner
Note: For convenience we will use the below users instead of PartnerA and PartnerB
PartnerA = Partner23
PartnerB = Partner24
Select Customer and give details of Partner A(Partner23), select User Type, Authentication Type and click next.
UserType: Which Zone does the partner belongs to send or receive files? (DMZ or Trusted)
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
AMF: AMF provider is used to onboard partners which use UFA
IBM: The details 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 4-ii.
Verify the Partner details and click Onboard User.
Repeat the same steps for PartnerB (Partner24). Using AMF provider for UFA User
B. Install UFA agent Partner A (Partner23).
Please refer the UFA installation document for this step
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 Partner A Customer Initiated Upload profile:
Double click on Partner23
Click on + icon at the top right corner
Select the protocol as UFA, operation as Upload, give the remaining details and click save
Upload Folder: Folder where the files will be placed to deliver to AMF.
File Pattern: File pattern to filter the files.
Sender: Sender name who is sending files (Partner23 in this case)
Receiver: Receiver name to whom we are delivering files via AMF (Partner24 in this case).
Message Type: Message type we used in this case (GENERIC)
Polling Interval: The polling interval between the sync i.e., UFA agent and server.
Archive Flag: Option to enable or disable the archives.
Archive Folder: Folder to archive the files if we enabled step vii
Run Script Before Upload: Script name with path if we want to run any scripts before the file is uploaded.
Chunk Size: Size of the files that will be transferred in bits when there is a large file transfer
Pgp Encrypt: Option to encrypt the uploaded file.
Validate MD5 Check Sum: Option to validate the MD5 Checksum on uploaded files.
E. Create Unzip as Action type
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
Give name and create Unzip Action as Action type as clicks save.
F. Create Route with adding file name format
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
Give name and create Route Action with adding file name format and clicks save.
G. Create EOL Conversion as Action type.
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
Give name and create EOL Conversion, select message type and click save.
H. Create Mailbox Action as Action type.
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
Give name and Mailbox as action type and clicks save.
Mailbox Path: Path of the receiver (Partner24) mailbox.
Extraction Count: Option to add extraction for sent file (default value is 1).
I. Create Workflow definition and add Actions (Created in step e, step f, step g and step h) as step1, step2, step3 and step4.
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, step f, step g, step h as step1, step2, step3 and step4 and click save
Select the Unzip action created in step e as step1 and click save.
Select the Route action created in step f as step2 and click save.
Select the Route action created in step g as step3 and click save.
Select the Mailbox action created in step h as step4 and click save.
J. Create Workflow rule with Sender, Receiver, MessageType and Workflow definition name (Created in step i).
Go to Rules under Onboarding -> Workflow
Click on + icon at the top right
Give Sender, Receiver, MessageType, Workflow (Created in step i) and click on save
K. Verify the Message activity in AMF once the Partner A(Partner23) uploaded the files to his upload folder. If everything is configured correctly, the file will be Mail boxed to Partner B(Partner24) via HTTP protocol (MFG).
Go to Message activity under Track N Trace
Here we can see the details for the file Mailboxed to the Partner24.
