High volume and High performance messaging Hub that synchronizes input multi-messages

Publishing Venue

IBM

Abstract

A program is disclosed that invents messaging HUB system satisfies two conflicting requirements, (1) High volume transaction processing, (2) Synchronized transaction processing. Synchronized transactions are plural transactions that are waiting for each other , in order to be processed at the same time. This invented message HUB system consists of (1) main HUB system and (2) synchronizing HUB system. The main HUB system control all input messages, and delegates synchronizing functions to the synchronizing HUB system.

High volume and High performance messaging Hub that synchronizes input multi-messages

A program is disclosed that the invented message HUB system satisfies conflicting critical requirements, (1) High volume transaction processing,

(2) Synchronized transaction processing.

1. Background of Invention

Evolutionary changing business environment makes companies to add new front channels to back end systems in mission critical systems. If number of front channels and back end systems are M and N, then the number of interface applications becomes M X N.

M Front Channels N Back End Systems M X N Interfaces

Front Channel 1

Back End System 1

Front Channel 2

Back End System 2

Front Channel M

Back End System N

M Front Channels N Back End Systems

M + N Interfaces

Front Channel 1

Back End System 1

Messaging HUB System

Routing Formatting

Front Channel 2

Back End System 2

Front Channel M

Back End System N

Fig.1 M X N Interfaces vs M + N Interfaces

Main functions of messaging HUB system are (1) routing messages, (2) formatting messaging. This function decreases the number of interface applications from M X N to M + N, and enables easy to add front channels and back end systems flexibly (Fig.1).

Mission-critical system requires high performance to process huge number of transactions. In case of simple transactions, clustering method makes Messaging HUB system scalable. But there are not simple transactions, for example transactions that are waiting for other related transactions. In this article we call these kind of transactions "synchronized transactions" . Synchronized transactions consume the resources of message HUB system, these resource consumption makes high volume transaction processing slower than simple transaction case.

2. Invented HUB system

Our invention is dividing messaging HUB systems into two subsystems, one is the main HUB system,

1

the second one is synchronizing HUB system.

M Front Channels

Synchronizing HUB System

N Back End Systems

Front Channel 1

Back End System 1

 Delegate Synchronizing Functions

Front Channel 2

Back End System 2

 Main HUB System

Back End System N

Front Channel M

Fig 2. Main HUB system and Synchronizing HUB system and

When main HUB system receives synchronized transaction, it immediately sends the transaction to synchronizing HUB system without data processing and comes back to high volume transaction processing machine.

S ynchronizing H U B System

Input M essages O utput M essages

Message1'

M e ssa ge1

M essage2

P rocess 1

P rocess 2

 Main HUB System

M e ssa ge2 '

Synchronizing HUB System

Process 3

Message1'

Input Messages Output Messages

Message２'

Message３

Message1

Message2

Process 1

Process 2

Process 4

 Main HUB System

Message３'

2

Fig 3. Simple Transactions and synchronizing transaction

On the other hands, synchronizing HUB system maintains the received transaction...