Last updated
Last updated
UFA-->AMF -->Azure Blob
Use Case: PartnerA (Sender) send files to AMF via HTTP (UFA) Protocol. We Unzip, PGP Encrypt and deliver those files to PartnerB (Receiver) via Azure Blob protocol.
Sequence Diagram:
Steps:
A. Onboard PartnerA and PartnerB in AMF
B. Install UFA Agent (PartnerA).
C. Onboard PartnerA Customer Initiated Send Profile.
D. Onboard PartnerB MFT Initiated Send Profile.
E. Create Message Type or use the existing one in AMF.
F. Create Message Mapping with Sender, Receiver and Message Type with a file pattern.
G. Create Unzip Action as Action Type.
H. Create Open PGP Encrypt Action as Action Type.
I. Create Delivery Action or use the predefined one (Deliver as is).
J. Create Workflow Definition and add Actions (Created in step G, step H and step I) as step1, step2 and step3.
K. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in step J).
L. Verify the Message Activity in AMF once the PartnerA Send the file to AMF via HTTP Protocol (UFA). If everything was configured correctly means they got processed and delivered to PartnerB (Azure Blob).
Process:
A. Onboard PartnerA in AMF and PartnerB in SFG.
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 = Partner39
PartnerB = Partner40
Select Customer and give details of Partner39, 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 belong 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.
Select AMF Provider for PartnerA which Use UFA Protocol (Partner39)
Select IBM Provider for PartnerB which use Azure Blob Protocol (Partner40).
Verify the Partner details and click Onboard User.
B. Install UFA agent (PartnerA).
Please refer the UFA installation document for this step.
C. Onboard PartnerA Customer Initiated Send Profile.
Double click on Partner39
Click on + icon at the top right corner
Select the Protocol as UFA, Operation as upload, give the remaining details and click save.
Give 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 (Partner39 in this case)
Receiver: Receiver name to whom we are delivering files via AMF (Partner40 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.
Archive Flag: Option to enable or disable the archives.
Archive Folder: Folder to archive the files if we enabled 7
Run Script Before Upload: Script name with path if we want to run any scripts before the file upload.
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.
Once the onboarding was done, we can see the status as completed.
D. Create PartnerB MFT Initiated Send Profile.
Double click on Partner40.
Click on + icon at the top right corner.
Select the Protocol as Azure Blob, operation as upload give the remaining details and click save.
Give details and click save
Access Token Url: Using the url property of the client object.
SAS Token Url: URL to get the SAS token.
Upload Url: A hyperlink that points to a location within the Internet where the user can upload a file.
File Pattern: Pattern to filter the files.
Backup Path: A backup path that contains a copy of the files in the security path.
Error Path: Error where users are putting in the wrong path or name on the command line.
File Format: The extension is separated by a period from the name and contains three or four letters that identify the format.
Folder Name: The name of the corresponding Active Directory object.
Token Details: A token is an object that represents something else, such as another object.
Proxy Required: Option to open connections via proxy server.
Proxy URL: Proxy server URL (If proxy was enabled)
Proxy Username: Proxy username (If proxy was enabled)
Proxy Password: Proxy password (If proxy was enabled)
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.
E. Create Message Type or use the existing one in AMF:
Go to Message Types under Onboarding.
Click on +icon at the top right corner
Note: In this scenario we will use the existing Message Type (GENERIC).
F. 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 Partner39 will send and click save
G. Create Unzip Action as Action Type.
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
Give Name, select Unzip as Action Type.
H. Create Open PGP Encrypt Action as Action Type
Go to Actions under Onboarding->Workflow
Click on + icon to create new action
Give Name, select Open PGP Encrypt as Action Type and select Public Key and Clicks 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
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.
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 Unzip Action that we created in Step G as step1.
Select the PGP Encrypted Action that we created in step H as step2.
Select the Deliver Action or use the predefined one (Deliver As is) in step I as step3.
K. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in step J).
Go to Rules under Onboarding -> Workflow
Click on + icon at the top right
Give Sender, Receiver, Message Type and Workflow (Created in step J) and click on Save.
L. Verify the Message Activity in AMF once the Partner39 (PartnerA)Send the file to AMF via HTTP Protocol (UFA). If everything was configured correctly means they Got processed and Delivered to Partner 40 (Partner B).
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 Partner40.(PartnerB)
