Copyrighted material John Tullis 10/2/2015 page 1 04/02/00 MQ Series Middleware Presentation John Tullis DePaul Instructor [email protected]

Copyrighted materialJohn Tullis

04/19/23page 1

04/02/00 MQ Series Middleware Presentation

John TullisDePaul [email protected]


04/19/23page 2

Extranet Middleware - MQSeries

System Integration• Interfaces

• Access to legacy applications

• Specific interfaces

• Complexity

• Inflexibility

• Once built, infrastructure can be difficult to change

• Maintenance

• All of the above leads to high costs

Companies are spending 40% of development dollars on integration, and...

it's difficult to maintain, doesn't scale, is hard to manage, and is unreliable, so...

it takes too long to get information to the right place and the integration backlog gets longer

Source - a Gartner Group report


04/19/23page 3


Typical environment

SUN SPARC

CUSTOMERSSUPPLIERS

ENTERPRISE

I BM

TANDEM

AS/ 400APPN

OS/ 2LAN

OSITCP/ I P RI SC

SYSTEM6000

EDIVAX

S/ 390

NOVELLDECNET

SUN

HP

DEC AS/ 400

Link Islands Together

I mprove Productivity

I mprove Effi ciency

I mprove Customer Service

Reduce Costs


04/19/23page 4


Typical environment

• Systems integration is required to link these “islands of automation”.• Middleware is a solution to deal with the growth of “point to point” links.

LogisticsServices Retailers

Wholesalers Distributors

Logistics ServicesManufacturer


04/19/23page 5


Point to Point Links


04/19/23page 6


Financial Services Company using Point to Point

Management Systems

KEY:

Automatic Feed

Manual Entries

Deposits/Receipts

SpotFixed

IncomeEquities Payroll

ManualTX

FixedAssets

Loans

FX Option

Swaps

Cash FlowSystem

G/L IRS

FundsManager

Futures

AS/400 AS/400 AS/400 DOSDOSDOS

DOS

AcctsPayable

MS Access

MS Access

Sybase

SQL

Sybase


04/19/23page 7


Financial Services Company using MiddlewareTransaction Systems

Management Systems KEY:

Automatic Feed

Manual Entries

Deposits/Receipts

SpotFixed

IncomeEquities Payroll

ManualTX

FixedAssets

Loans

FX Option

Swaps

Middleware

Cash FlowSystem

G/L IRSRecon-ciliation

AcctsPayable

FundsManager

Futures


04/19/23page 8


What are some Middleware choices?• Microsoft - Message Queue Server• BEA Tuxedo (Hewlett-Packard - Tuxedo/Q)• DEC MessageQ• TSI Mercator• IBM MQSeries


04/19/23page 9


Microsoft• Provides transactional messaging in an NT Server-only

environment Non-NT platforms require a gateway product

• MSMQ-MQSeries Bridge, part of SNA Server• Microsoft 'Interoperability' is connecting to MQSeries• Client support for Windows 95/98/NT only• Good integration with other Microsoft products

Support for C, C++, COM+, Visual Basic, etc.• NT Standard Edition allows NT to NT messaging only• NT Enterprise Edition must be used when messages go NT to

non-NT


04/19/23page 10


Tuxedo• Provides Maximum of 80 servers per domain• Inter-domain communication requires administrator work to

import / export services• Each application requires a process, not multi-threaded• Lack of multi-threading consumes machine resources as load

grows• 95% of Tuxedo sales are for single machine (host)

applications.• Does not (yet) run on mainframe 390 systems, nor can it be

invoked by CICS transactions.


04/19/23page 11


DEC MessageQ• Targeted at VMS and Alpha systems.• DEC no longer exists as a separate company, acquired by

Compaq for their services organization.


04/19/23page 12


MQSeries• MQSeries allows programmers to focus on the Business logic

rather than communications, sharply reduces the application development cycle, reduces risk, enables faster response to unexpected changes in business needs, provides proven robustness and improves ROI

• 1998 Market share: 65% and growing• Over 100,000 licenses and 7,000 customer sites• De-facto standard• Scalable from Windows to the Mainframe• Transaction and Messaging Support• URL: www-4.ibm.com/software/ts/mqseries/library/ mqpdfs.html


04/19/23page 13


MQSeries

WinterGreen Research

Message-Engine Market Share

64.5%8.3%

10.5%

1.5%

15.2%

1998 MARKET SIZE $210M

MQSeriesTIBCOBEALvl8/Mom.Other

54.6%

14.9%

10.9%

5.0%

14.5%

1997 MARKET SIZE $160M

MQSeriesTIBCOBEALvl8/Mom.Other


04/19/23page 14


MQSeries - platforms

UnixWare

DOS

Windows 95 or 3.1MQSeries

InterfaceOS/2

AIX/6000

Clients

SCO UNIX

HP-UXDigital VAX/VMS

OS/2

AIX/6000

SunOS

OS/400VSE/ESA

MVS/ESA

MQSeriesInterface

NCR

Sun Solaris

Tandem NSK

Servers

NCRHP-UX

SINIX + Pyramid DC/OSx

TPF

SunOS

SINIXSUN Solaris

Pyramid DC/OSx

Server withClient Support

Windows NT (Intel)

Windows NT (Intel)

Linux

SCOUNIX

DECUNIX

MQSeries Platform Coverage

Windows (95 or 3.1)


04/19/23page 15


MQSeries - Gartner Group viewpoint:

• MQSeries is ..."the undisputed leader in the Messaging Middleware market" • "More than half of midsize enterprises (enterprises with $100 million to $1,000 million in revenue) and more than 85 percent of large enterprises (enterprises with more than $1,000 million in revenue) will have at least one message-queuing middleware product by 2000 (0.8 probability)."


04/19/23page 16


MQSeries - example

• Example - one program, called CO (for customer order) transmitting order information via the MQI to another host. On that host, another program CB (for customer billing) gets the message, does processing (stores the order and handles credit validation), and possibly returns a response.


04/19/23page 17


MQSeries - the basics•Links "nearly everything to almost anything..."

•Loosely-coupled flexibility via queuing

•Faster and safer application development

•Common, ease-to-use, multi-platform API

•Assured message delivery

Queue

1

A

B

Queue

2


04/19/23page 18


Routing messages

A B

1. Program A puts a msg onto Q1

3. Program B puts a reply msg onto Q2

4. Program A gets the reply msg from Q2

2. Program B gets the msg from Q1


04/19/23page 19


Some definitions & conceptsA Message is:

• A Unit of Information

• A Request for Service

• A Reply or Report

• An Announcement or Broadcast

• Audio or Video

A Queue is:

• A Safe Place to hold Messages

A Message can be protected:

• Across the network or System failures


04/19/23page 20


Header: A series of message attributes understood and augmented by the Queue Manager, such as: target queue name, length of user data, message priority, reply-to queue name....etc.

User Data: Any sequence of bytes• Private to the sending and receiving programs• Not meaningful to the Queue Manager

Message = Header + User Data

Header User Data

What does a message look like?


04/19/23page 21


Deeper look at how it works...

Message Queue Manager

MessageChannelAgent

Message Queue Manager

MessageQueuingService

MessageChannelAgent

MQSeriesI nterface

MQSeriesInterface

Q1 Q2

XMIT

QNetwork

MessageQueuingService

Appl A

PUT MSG

Appl B

GET MSG

Appl C

GET MSG


04/19/23page 22


MessagesMessage Types

• Persistent

• Non-Persistent

Message Access

• FIFO

• Priority

• Direct


04/19/23page 23


TriggeringProgram A

Program B

Trigger Monitor

ProcessDefinition

Queue Manager

1

2

4

6

3

5

I nitiationQueue

ApplicationQueue

MQPUT A- Q

MQGET A- Q

MQGET I - Q

Triggering allowsI nstantiation as requiredConservation of system resourcesAutomation of flow

FirstEveryDepthPriority


04/19/23page 24


Message styles

ProgramA

ProgramB

Put I nvoice-Q

Get I nvoice-Q

I nvoice-Q

"Send and Forget"

TargetQueue

Reply-toQueue

ProgramA

ProgramB

"Request/Response"

Documents

Copyrighted material John Tullis 10/2/2015 page 1 04/02/00 MQ Series Middleware Presentation John Tullis DePaul Instructor [email protected]