AMF (Agile Messaing Framework)
  • Agile Messaging Framework
    • Get Started
      • Install
        • Pre-requisites
        • CockroachDB
        • NATS for Queuing
        • Hashicorp Vault
          • Configure Vault
        • Python 3.9
        • AMF Bundle
        • Installation of AMF
          • Configure and install
          • Post Install Steps
        • IBM SFG Integration
          • Configure and Install
            • Install jars in SFG
            • Add amf.properties
            • Add CRDB pool details
            • Import Sterling Artifacts
          • Post Install Steps
            • Create user with API permissions
            • Changes in BPs
    • Concepts
      • Providers
      • Users
      • Message Type
      • Message Mapping
      • Workflow
      • Communication profiles
        • SFTP Profiles
          • Customer Initiated
          • MFT Initiated
            • MFT Initiated Send
            • MFT Initiated Receive
        • Connect Direct
          • Customer Initiated
          • MFT Initiated
        • SharePoint
          • MFT Initiated
            • MFT Initiated Send
            • MFT Initiated Receive
        • S3
          • MFT Initiated
            • MFT Initiated Send
            • MFT Initiated Receive
        • Azure ADLS
          • MFT Initiated
            • MFT Initiated Send
        • HTTP with Token
          • MFT Initiated
            • MFT Initiated Send
        • UFA
          • Customer Initiated
            • Customer Initiated Send
            • Customer Initiated Receive
      • Communication Rules
        • Immediate
        • Scheduled
    • Management
      • AMF UI Operations
      • AMF Services Operations
    • User Manual
      • Signup and Login
      • Dashboard
      • Track N Trace
        • Message Activity
        • Failed Message Activity
        • Onboarding Activity
        • Session Activity
        • Service Availability
        • Scheduler Activity
        • Delivery Queue
        • Audit Log
      • Onboarding
        • Customers
        • Users
          • Communication Profiles
        • Message Types
        • Message Mapping
        • Workflow
          • Definitions
          • Actions
          • Rules
        • Communication Rules
    • Troubleshooting
    • Tutorials
      • UFA Installations
        • Linux Installation
        • Windows Installation
      • Schedules
        • Run based on timer
        • Run daily
        • Run based on day(s) of the week
        • Run based on day(s) of the month
      • UseCases
        • UC01
        • UC02
        • UC03
        • UC04
        • UC05
        • UC06
        • UC07
        • UC08
        • UC09
        • UC10
        • UC11
        • UC12
        • UC13
        • UC14
        • UC15
        • UC16
        • UC17
        • UC18
        • UC19
        • UC20
        • UC21
        • UC22
        • UC23
        • UC24
        • UC25
        • UC26
Powered by GitBook
On this page
  1. Agile Messaging Framework
  2. Tutorials
  3. UseCases

UC17

PreviousUC16NextUC18

Last updated 3 months ago

UFA --> AMF -->S3

Use Case: Partner33 (Sender) send files to AMF via UFA Protocol, we use PGP decrypt, ZIP and Deliver those files to the Partner34 (Receiver) using S3 Protocol via AMF (Agile Messaging Framework).

Sequence Diagram:

Steps:

A. Onboard Partner33 and Partner34 in using AMF

B. Install UFA agent for Partner33.

C. Create Message Type or use the existing one in AMF

D. Onboard Partner33 UFA Upload profile (Customer Initiated Communication Profile (Inbound)).

E. Create PGP Decrypt Action as Action Type

F. Create ZIP Action as Action Type

G. Create Delivery Action or use the predefined one (Deliver as is)

H. Create Workflow Definitions and add Actions (Created in step E, step F and step G) as step1, step2 and step3 respectively.

I. Create Workflow Rule with Sender, Receiver, MessageType and Workflow Definition Name (Created in step H).

J. Onboard Partner34 S3 Profile in AMF (MFT Initiated Communication Profile (Outbound)).

K. Create Communication Rule with Sender, Receiver, Message Type and Comm Profile Name

L. Verify the Message Activity in AMF once the Partner33 uploads the file to AMF via UFA Protocol. If everything was configured correctly, the file will be delivered to Partner34 via S3 protocol.

Process:

A. Onboard Partner33 and Partner34 in AMF:

Login to AMF

Go to Onboarding -> Users

Click on + icon at the top right corner

Select Customer and give details of Partner33, select User Type, Authentication Type and click next.

  1. UserType: Which Zone does the Partner belong to send or receive files? (DMZ or Trusted)

  2. AuthenticationType: 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. OpenLdap: We need to select this if we selected the AuthenticationType as LDAP in the step2.

Verify the Partner details and click Onboard User.

Repeat the same steps for Partner34 using AMF.

B. Install UFA agent Partner33.

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. Onboard Partner33 UFA Upload profile (Customer Initiated Communication Profile (Inbound)).

Double click on Partner33

Click on + icon at the top right corner

Select the protocol as UFA, operation as Upload, give the remaining details and click save

  1. Upload Folder: Folder where the files will be placed to deliver to AMF.

  2. File Pattern: File pattern to filter the files.

  3. Sender: Sender name who is sending files

  4. Receiver: Receiver name to whom we are delivering files via AMF (Partner34 in this case).

  5. Message Type: Message Type we used in this case (GENERIC)

  6. Polling Interval: The polling interval between the sync between UFA agent and server.

  7. Archive Flag: Option to enable or disable the archives.

  8. Archive Folder: Folder to archive the files if we enabled vii

  9. Run Script Before Upload: Script name with path if we want to run any scripts before the file upload.

  10. Chunk Size: Size of the files that will be transferred in bits when there is a large file transfer

  11. PGP Encrypt: Option to encrypt the uploaded file.

  12. Validate MD5 Check Sum: Option to validate the MD5 Checksum on uploaded files.

E. Create PGP Decrypt Action as a Action Type

Go to Actions under Onboarding-> Workflow

Click on + icon to create new action

Give Action Name Select PGP Decrypt as Action Type and click save.

F. Create ZIP Action as a Action Type

Go to Actions under Onboarding-> Workflow

Click on + icon to create new action

Give Action Name Select ZIP as Action Type and click save.

G. Create Delivery Action or use the predefined one (Deliver as is):

Go to Actions under Onboarding->Workflow

Click on + icon to create new action

Give Action Name Select Deliver as Action Type and click save.

Note: In this scenario we will use the existing Action (Deliver as is)

H. Create Workflow Definitions and add Actions (Created in step E, step F and step G) as step1, step2 and step3 respectively.

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

Select the Action that we created in step G as step3 and click save

I. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition name (Created in step H).

Go to Rules under Onboarding -> Workflow

Click on + icon at the top right

Give Sender, Receiver, Message Type and Workflow (Created in step H) and click on Save

J. Onboard Partner34 S3 Profile in AMF (MFT Initiated Communication Profile (Outbound)).

Double click on the Partner34

Click on + icon in the top right corner

Give details of the S3 and click save

Give details and click save

  1. S3 bucket: S3 Bucket name

  2. S3 Region: Region where S3 belongs

  3. S3 Access Key ID: Access key ID of the S3 bucket

  4. S3 Secret Key: Secret key of S3 bucket

  5. Message to Process: Option to process the original or current message

  6. Proxy Required: Option to open connections via proxy server

  7. Proxy URL: Proxy server URL (If proxy was enabled)

  8. Upload Path: Path to upload files

  9. 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)

K. Create Communication Rule with Sender, Receiver, Message Type and Comm Profile Name:

Go to Rules under onboarding-> Communication

Click on + icon at top right corner

Select Sender, Receiver, Message Type and Comm. Profile name and click on save

L. Verify the Message Activity in AMF once the Partner33 uploads the file to AMF via UFA Protocol. If everything was configured correctly, the file will be delivered to Partner34 via S3 Protocol.

Go to Message Activity under Track N Trace

To see more details of the delivered double click on the record.