OpenMFT
  • OpenMFT powered by Agile Messaging Framework (AMF)
  • 1.0 Introduction
    • 1.1 A brief history of Managed File Transfer (MFT)
    • 1.2 Typical routing patterns for MFT/B2B systems
    • 1.3 What is AMF and why OpenMFT?
  • 2.0 OpenMFT Concepts
    • 2.1 Logical view of OpenMFT
    • 2.2 Message Type
    • 2.3 User
    • 2.4 Message Mapping
    • 2.5 Workflow
    • 2.6 User Communication Profiles
    • 2.7 Communication Rules
  • 3.0 Install
    • 3.1 Pre-requisites
    • 3.2 Download & stage OpenMFT
    • 3.3 Install OpenMFT as a standalone server
    • 3.4 Integrate OpenMFT with IBM SFG (Sterling File Gateway)
  • 4.0 Manage OpenMFT
    • 4.1 Login to OpenMFT UI
    • 4.2 Stop, Start or Restart all OpenMFT components
    • 4.3 Stop, Start or Restart OpenMFT UI
    • 4.4 Stop, Start or Restart middle-ware services
    • 4.5 Stop, Start or Restart Vault
  • 5.0 User Manual
    • 5.0 OpenMFT User Manual
  • 6.0 Scenarios
  • Troubleshooting
    • 7.0 Things to do if OpenMFT install fails
Powered by GitBook
On this page

Was this helpful?

  1. 1.0 Introduction

1.2 Typical routing patterns for MFT/B2B systems

There are generally two ways in which most MFT/B2B platforms do routing. They are either routing based on the file pattern or based on some content inside the file or message. This process of looking into the file or message is often referred to as Parsing. Generic Parsers play a key role for a properly engineered middle-ware platform.

Previous1.1 A brief history of Managed File Transfer (MFT)Next1.3 What is AMF and why OpenMFT?

Last updated 5 years ago

Was this helpful?