Skip to main content

Messaging Queue and Transaction Flow

Messaging Queue and Transaction Flow​

Slide 4

Queueing System​

Application
↔
Queueing System
(Actions)
↔
Process Connection Diagram
Queue Provider
Queue Reader
Queue Writer
↔
Queue
1
Application requests a queue from the Queueing System (Actions)
2
Queueing System resolves the queue details via the Process Connection Diagram
3
Process Connection Diagram returns details of a Queue Provider that knows how to connect to the queue
4
Queue Provider creates a Queue Reader and Queue Writer
5
Queueing System returns the Reader and Writer to the Application
6
Application uses the Reader and Writer to interact with the Queue

Transaction Flow - Two-Tier​

POS
POS sale process
→
XML Basket
↓
PosTransactions Queue
Local Transaction Processing
↓
Reporting
Queue Connector →
Back Office / Estate Manager
ServerTransactions Queue
→
Queue Connector
Inbound Documents Queue
→
Transaction Processing
↓
Reporting
Inventory
Order Processing
CRM Loyalty
Trans. Export

Transaction Flow - Three-Tier​

POS
POS Sale Process
→
XML Basket
↓
POS Transactions
Queue Connector →
Back Office
Server Transactions
Queue Connector
Inbound Documents
↓
Transaction Processing
Store Reports
Local Archive
Other Reporting Tables
TransactionsOut →
Estate Manager
EstateManager Transactions
Queue Connector
Inbound Documents
↓
Transaction Processing
Central Reports
Transaction Archive
Other Reporting Tables
TransactionsOut
Feeds to external systems

Central Transaction Flow​

Feeds from Enactor POSs
Feeds from other systems
→
Server Transactions
Estate Manager (Central)
Retail Transaction Processing
Sales Figures
Transaction Archive
Other Reports
File System Queues
Retail Transactions →
Secondary Archive → Feeds to External Sinks
Retail Transactions feeds downstream processing ↓
CRM Processing
Loyalty
Customer Txns
Inventory Processing
Inventory Levels
Order Manager
Customer Orders

Resilience and Extensions​

  • Every distributed element has DB backed queues
  • HTTP/Remote connectors will retry until remote system available
  • Remote systems can be 'Busy'
  • There are no theoretical limits on the number of transactions that can be held in the queue. Limits come from disk space and software enforced limits.
  • Adding new outputs via Configuration - to Drives, Data Sinks, Service Endpoints and Queues

Further Reading​

For additional information and further reading on Messaging Queue and Transaction Flow, please see the following guides:

DocumentDescription
Outbound Integration Guide - IntroductionMessage queue architecture and transaction flow