Identify FTM objects
FTM objects are defined as objects that have both a state and a
corresponding lifecycle that requires management within the solution.
FTM supports an extensible set of object types. The following object
types are supplied as standard:
- Transmission
- This object represents a physical transmission that is received
or sent by FTM. Some examples of this object type include MQ message,
File, HTTP service call, and e-mail.
Note: The transmission object should represent the physical data received and not the contents of the received message.
- Fragment
- This object represents a fragment of a transmission. Fragments can be used when a transmission is too big to deliver to FTM in one transfer. The transmission can be broken up and sent to FTM in a series of fragments.
- Batch
- This object represents a logical grouping of transactions.
- Transaction
- This object represents a single, general unit of business activity.
- Payment Transaction
- This object represents a single unit of business activity in the context of a payment such as a credit transfer.
- Securities Transaction
- This object represents a single unit of business activity in the context of a securities transaction such as a trade.
- Service Participant
- This object represents an interface with FTM to support the management of that interface. An availability schedule, for example.
- Activity
- This object represents any kind of process or activity that takes place outside of FTM but may need to be recorded or tracked within FTM. This could be a human activity or process.
Transmissions and fragments are normally identified by examining the interfaces between FTM and other systems and the use case workflow diagrams.
Batches are identified by examining the logical structure of the transmission or fragment payload and the groupings of transactions.
Transactions and derived objects are the lowest level of logical entity supported in FTM and represent individual atomic tasks to be processed. These tasks normally have a specific business purpose or concept, such as Payment, Liquidity Check, Gateway Request, Price Request and so on.