Triggered by arrival of a large file, large size in, small size out, Almost always one to many (1-n) with routing based on content. Often each line in the batch is a business transaction (SC-EPT flow) that triggers orchestration (SC-EPO) in an application.
A typical scenario is where large B2B files arrive with transactions that need to be split up and managed separately.
The entire flow often starts on schedule or on arrival of a large file that should be processed. The platform needs to split the file into individual transactions and start transaction flows for each one.
It is very important that there is a system that can orchestrate and monitor the completion of the transactions, also after passing 2-3 systems down the line. To achieve this there needs to be orchestration (SC-EPO) and monitoring (SC-EPM), and all messages in participating interfaces should have common- message-headers all through to passively be tracked.
This monitoring allows alarms to be raised when things do not work. With GUI access, the Operations Team can immediately see how far a transaction has progressed, and which part of the transaction is in-complete or stopped.
Where possible, use this pattern to convert files or batched data into transactional units or messages. Processing unique transactions gives better capability for monitoring and also allows the enterprise to move further into a real time data processing environment.