1. what is PT wrapper, how channels will be select in PTWrapper.
The Physical Transmission (PT) Wrapper Flow is a custom wrapper that contains the generic PhysicalTransmissionFlow as a subflow. Its job is to handle message inputs from various nodes (like MQInput) and map them for the core flow. A key function is to identify the inbound channel, as this information is required by the generic flow for processing .
2. how select channel subflow works on what bases it will select the channel
3.in what all the tables data will insert when PT log is done
When a physical transmission is logged, data is inserted into key database tables. The transmission details go into TRANSMISSION_BASE. If the transmission is fragmented, details about each piece are stored in the FRAGMENT_BASE table .
4.from where your event will trigger for the first time
Events are typically triggered for the first time by the EventProcessingFlow. This flow processes events raised by FTM to drive the Finite State Machine (FSM) engine. It determines state transitions, evaluates guard conditions, retrieves relevant objects, and calls specified actions .
5. what are the parameters u passed in event from ur action.
Events carry context data needed for processing. A common parameter is the object ID (e.g., Transmission or Batch ID). Events can also include event context data used by object filters to refine which objects are selected for a state transition .
6.what is begin mapper and endmapper how it works
7.what is ISF message what it contents.
ISF (Internal Structured Format) is FTM's internal message format. All external formats are mapped to or from ISF. It can contain all details of a business object, such as payment amounts, debtor/creditor details, and financial institution information .
8.what is batch and transaction
In FTM, a batch is a group of transactions processed together. FTM supports nested batches and fragmentation, where a batch can span multiple fragments. Each transaction is an individual item (like a payment) within a batch .
9. what is state , transtion and event.
These are core Finite State Machine (FSM) concepts in FTM:
· State: A condition in an object's lifecycle (e.g., 'NEW', 'PROCESSED') .
· Event: An occurrence triggering a potential state change (e.g., 'Payment Received') .
· Transition: The movement from one state to another, triggered by an event, possibly executing an action .
10. how ur object filter works.
An object filter is an optional SQL condition added to a transition. It uses event context data to refine the list of objects retrieved by the main object selector, ensuring only relevant objects are transitioned .
11.what is the use master object query.
The master object query (or object selector) is an SQL statement defining how to retrieve objects from the database for a state transition. It must return the object ID and other data needed by subsequent actions .
12.what all the components contains in congfig
FTM configuration includes model changes (formats, channels, mappers) and code changes (implementations in IBM App Connect). These are extracted into a config script for deployment, which contains metadata derived from FSM models .
13. what is service particient and involded parties
Involved parties are external entities (e.g., "Client," "Payments Gateway") that exchange data with FTM via channels. A service participant is likely an external system (like a sanction screening service) that FTM integrates with .
14.how ur RSA and IIB will connect.
Rsa and IIB are different tools. Rsa We use to design and define the configs and will load the details in Database. IIB will access RSA data via Db using Datasources setup.
15.what is business concept what is the role.
A Business Concept (e.g., HVP_SANCTION_RESPONSE) defines the type of business object being processed. It helps determine the operation, status, and behavior in the FSM .
16.how u will loopback in FSM
17.what is classification
18.if something went wrong of the action how ur FSM will behave what will happen with particular state in FSM
19.what ur FSM and CONFIG scripts contains.
FSM Scripts: Contain metadata (states, transitions, events) derived from UML state diagrams that control object lifecycles .
· CONFIG Scripts: Contain definitions for artifacts (formats, channels, mappers) and are deployed to the runtime environment .
20.what is inbound and outbound mappers
Inbound Mapper (External → ISF): Converts incoming messages (e.g., SWIFT MT, XML) into the Internal Structured Format (ISF). It uses the CONFIG channel parameter to look up rules in a value table, determining details like the Business Concept (subType) and Object Class . The core PhysicalTransmissionFlow passes the transmission to this mapper right after logging it .
Outbound Mapper (ISF → External): Converts ISF back to the required external format. It searches its configuration based on the ISF business concept to find the correct output format (e.g., pacs.002.001.10) and manages datetime formatting based on channel settings .
