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

UC04

PreviousUC03NextUC05

Last updated 3 months ago

CD --> SFG --> AMF --> SFG --> MFG

Use Case: Partner07 (Sender) send files to SFG via CD protocol, we mailbox those files to the Partner08 (Receiver) using HTTP (MFG.) protocol from SFG via AMF (Agile Messaging Framework).

Sequence Diagram:

Steps:

A. Onboard Partner07 and Partner08 in SFG using AMF.

B. Onboard Partner07 connect direct nodes in SFG using AMF (Customer Initiated communication profiles (Inbound)).

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

D. Create Message Mapping with Sender, Receiver and Message Type with a file pattern.

E. Create Mailbox Action.

F. Create Workflow definition and add Action (Created in step E) as step1.

G. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in step F).

H. Verify the Message Activity in AMF once Partner07 uploads the file to SFG via CD protocol, if everything was configured correctly, the file will be Mailboxed to Partner08 via HTTP(MFG) protocol.

Process:

A. Onboard Partner07 and Partner08 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 Partner07, select user Type, Authentication Type and click next.

  1. User Type: Which Zone does the partner belongs to send or receive files? (DMZ or Trusted)

  2. Authentication Type: Where do we store the partner’s credentials? (LDAP or local (SFG/AMF) or Both)

Select the provider the Partner belongs 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. Open LDAP: We need to select this if we selected the Authentication Type as LDAP in step2

Verify the partner details and click Onboard User.

Repeat the above steps to onboard Partner08.

B. Onboard Partner07 Connect Direct nodes in SFG using AMF (Customer Initiated Communication Profile (Inbound)).

Double click on the Partner07

Click on + icon in the top right corner

Give details of the Node and click save

  1. Operating System: Operating system of the partner07

  2. SPOE: Option to enable/disable Secure point of entry

  3. Node Name: Node name of Parnter07

  4. Host Name/IP: Host/Ip of the Partner07 CD node

  5. Port: Port of the Partner07 CD node

  6. Alternate Ips: we can give here any alternate IPs for this CD node

  7. Secure+: Option to enable/disable secure+ for SSL

  8. Cert File: Public cert of the Partner07 CD node (In txt format with no headers)

  9. Common Name: Common name of Partner07 CD

  10. TLS Version: TLS version to be used in the communication

  11. Ciphers: Ciphers to be used in the communication

Once the onboarding is done, we can see the status as completed.

C. Create Message Types or use the existing one in AMF:

Go to Message Types under Onboarding

Click on + icon in the right corner

In this scenario we will create the message type CD_UC04_MFG

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 Partner07 will send and click save.

E. Create Mailbox Action

Go to Actions under Onboarding->Workflow

Click on + icon to create new action

  1. Mailbox Path: Path of the receiver (Partner08) mailbox

  2. Extraction Count: Option to add extraction for sent file (default value is 1).

F. Create Workflow Definition and add Action (Created in step E) as step1.

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 and click save

G. Create Workflow Rule with Sender, Receiver, Message Type and Workflow Definition Name (Created in step F).

Go to Rules under Onboarding -> Workflow

Click on + icon at the top right

Give Sender, Receiver, Message Type and Workflow (Created in step F) and click on save

H. Verify the Message Activity in AMF once Partner07 uploads the file to SFG via CD protocol. If everything was configured correctly, the file will be Mailboxed to Partner08 via HTTP(MFG) protocol.

Go to Message activity under Track N Trace