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

UC06

PreviousUC05NextUC07

Last updated 3 months ago

SFTP --> SFG --> AMF --> SFG --> CD

Use Case: Partner11 (Sender) send files to SFG via SFTP protocol, we deliver those files to Partner12 (Receiver) using CD protocol from SFG via AMF (Agile Messaging Framework).

Sequence Diagram:

Steps:

A. Onboard Partner11 and Partner12 in SFG using AMF.

B. Onboard Partner11 SFTP profile in SFG using AMF (Customer Initiated Communication Profiles (Inbound)).

C. Onboard Partner12 connect direct node in SFG using AMF (Customer Initiated Communication Profiles (Inbound)).

D. Create Message Types or use the existing one in AMF.

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

F. Create EOL Conversion Action with adding file name format.

G. Create Delivery 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. Create MFT Initiated CD profile for outbound delivery in Partner12.

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

L. Verify the Message Activity in AMF once Partner11 uploads the file to SFG via SFTP protocol. If everything was configured correctly, the file will be delivered to Partner12 via CD protocol.

Process:

A. Onboard Partner11 and Partner12 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 Partner11, select User Type, Authentication Type and click next.

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

  2. 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

  1. AMF: AMF provider is used to onboard Partners which use UFA

  2. IBM: This will come from the provider’s config. We can choose several types based on the provider's config.

  3. OpenLdap: 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.

B. Onboard Partner11 SFTP in SFG using AMF (Customer Initiated Communication Profiles (Inbound)).

Double click on the Partner11

Click on + icon in the top right corner

Give details of the SFTP Inbound and click save

Once the Onboarding was done, we can see the status as completed.

C. Onboard Partner12 CD profile in SFG using AMF (Customer Initiated Communication Profiles (Inbound) and MFT Initiated Communication Profiles (Outbound)).

Double click on the Partner12

Click on + icon in the top right corner

Give details of the CD Profile and click save

  1. Operating System: Operating system of the Partner12

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

  3. Node Name: Node name of Partner12 CDNode

  4. Host Name/IP: Host/IP of the Partner12 CDNode

  5. Port: Port of the Partner12 CDNode

  6. Alternate IPs: we can give there are any alternate IPs for this CD node

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

  8. Cert File: Public cert of the Partner12 CDNode (In txt format with no headers)

  9. Common Name: Common name of the CD_PARTNER12

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

  11. Ciphers: Ciphers to be used in the communication

Once the Onboarding was done, we can see the status as completed.

D. 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 type (GENERIC)

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

F.. Create EOL Conversion Action with adding file name format.

Go to Actions under Onboarding-> Workflow

Click on + icon at the top right corner

Give Name, select EOL Conversion as Action Type, and in the file name format give the required name (NewFileName.txt)

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

Go to Actions under Onboarding-> Workflow

Click on + icon at the top right corner

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

H. Create Workflow Definition and add Actions (Created in step Fand step G) as step1 and step2.

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 F as step1 and click save.

Select the 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 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. Create MFT Initiated CD profile for outbound delivery in Partner12.

click on + icon at top right corner.

1. SPOE: Option to know if user will use SPOE or not (If SPOE was not used then we need to give Remote user ID and Remote Password)

2. Submitter User ID: Option to pass submitter user ID

3. Remote User ID: Remote User ID in the user node

4. Use Source File Name: Option to use source filename.

5. Remote File Name: Remote file name if you disabled the Use Source File Name in the 3-iv.

6. Remote Path: Path for the file to be placed.

7. Disposition: dropdown to select disposition of the file

8. Binary mode: Option to enable or disable binary mode for file transfer.

9. Copy Statement Sys opts: Option to execute copy step Sys opts. If we enable that we need to give the Sys opts to run

10. Run Task: Option to execute run task Sys opts. If we enable that we need to give the Sys opts to run

11. Run Job: Option to execute run job Sys opts. If we enable that we need to give the Sys opts to run

12. Send Email Notifications: Option to send email notifications for successful.

13. Receivers Mail Ids: Recipients mail addresses if we enable Send Email Notifications

14. Clean-up 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 Partner11 uploads the file to SFG via SFTP protocol. If everything was configured correctly, the file will be delivered to Partner12 via CD protocol.

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 Process Name, Process Number, Message ID, DDSN etc. for the file delivered to the Partner12

Graphical user interface, application Description automatically generated
Graphical user interface, application, table Description automatically generated