mq admin demo class_ppt

5/21/2018 MQ Admin Demo Class_PPT

1/37

MQ Overview


2/37

What is MQ?

What is Message?

What IBM says about MQ?


3/37

What is MQ? A member of websphere family from IBM. Websphere MQ

(formally MQseries) is the standard for messaging acrossmultiple platforms, including windows, linux, IBM mainframeand midrange and Unix flavors.

A middlewareproduct that implements a messaging andqueuing framework

Middleware- an intermediate software component that

bridges dissimilar computing environments.


4/37


5/37


6/37

A Brief History of MQ

1992 Systems Strategies(SSI) develops ezBridge, a messaging and

queuing product for VMS, Tandem, and Unix

IBMannounces Networking Blueprint defining three standard APIs

for program to program communication: CPI-C, RPC, MQI

1992-3

State Street Bank(Boston) evaluates IBM messaging product

(code name Victory) for IBM CICS/ESA and SSIs ezBridge on

VMS and Tandem.State Street Bank would like to announce the wedding of

IBM and Systems Strategies!

1993

IBM buys intellectual property rights for ezBridge from SSI


7/37

MQSeries Platform Rollout

Initially, IBMs version of MQSeries ran only on mainframe (CICS/ESA, IMS/ESA, and eventually VSE).

SSI version (called MQSeries Version 1) initially released on: VMS, Tandem, AS/400, and Unix (SCO, UnixWare).

1994/1995 -IBM releases the first three distributed platforms: AIX, OS/2, and AS/400. The AIX version becomes the reference port.

Over time, IBM replaced SSI versions with ports of its referencesystem.

Today - MQ runs on over 80 platforms & support more and moreprogramming techniques.


8/37

MQ support to different programmodels


9/37

Platforms

OS/390, zOS AIX Windows NT, 2000,

2003, XP, Vista Solaris: Intel & SPARC

HP-UX OS/400 OS/2 Compaq Open VMS Compaq NSK Compaq Tru64 UNIX VSE/ESA

Digital UNIX SunOS Dynix/ptx NCR TPF

SCO: Openserver,UnixWare

IRIX

DC/OSx

NUMA-Q Sinix

Linux (Intel,zSeries)

PalmOS (MQe)

EPOC (MQe)

Java (MQe) Unisys 2000

Hitachi


10/37

How Messaging & Queuing Works

Programs communicate by putting

messages on queues. Here, program

A puts a message on Queue1, which

is read by program B.

Note:A and B need not be

on the same machine!


11/37

How Messaging & Queuing Works(2)

Communication can be one-

way or two-way. Here, A

sends to B on Queue1, and B

responds to A on Queue2


12/37

Messaging and QueuingCharacteristics

Three key facts about Messaging and

Queuing differentiate it from other

communication styles:1) Communicating programs can run at different times.

2) There are no constraints on application structure.

3) Programs are insulated from environmental differences.


13/37

Applications Can Run at DifferentTimes

Either program can

be unavailable

Key Concept:

message queue existsindependently from

programs that use them!


14/37

No Constraints on ApplicationStructure

There can be a one to many

relationship between

applications

Or a many to one

relationship between

applications

MQ Supports Client-server

architecture for applications


15/37

Applications Shielded fromEnvironmental Differences

Dont care what OS is used.

Dont care what language theyrewritten in

Dont care what the underlyingcommunication protocol is used.


16/37

Applications Shielded fromEnvironmental Differences

Applications

Programmatic

API

Communications using

Message Channels

Queue Manager

Queue Manager

Message Queue


17/37

Supports synchronous/Asynchronous

communication Synchronous:App sends request, then blocks until request is

processed.

Requires service available at EXACTLY same time as client

needs service.

Asynchronous:App sends request and checks at some future

time if complete.

Service need not be available when client sends request

MQ Supports Message driven Processing

Makes use of triggering concept to achieve it


18/37

Synchronous: good/bad

Easy to program

Outcome is knownimmediately

Error recoveryeasier (usually)

Better real-time

response (usually)

Service must be upand ready

requestor blocks,held resources are

tied up

Usually requires

connection-oriented protocol

Good Bad


19/37

Requests need notbe targeted tospecific server.

Service need not beavailable whenrequest is made

No blocking, so

resources could befreed

Could useconnectionless

protocol

Response times areunpredictable

error handlingusually morecomplex

Harder to designapps?

Good Bad

Asynchronous: good/bad


20/37


21/37

What is Message?

Its a representation of data to be exchanged between

applications.

It can be,

Binary

Text (Raw text, XML)

Structured data (C structures, Cobol copybooks,

Serialized Java Objects)

Swift messages

Anything!!


22/37

Types of messages

Datagram

Request

Reply

Report

Persistence

Non persistence


23/37

Request message contains name of the queue andowning queue manager to which response should be

delivered.


24/37

Message partsMessage Descriptor (MQMD)

Message Body


25/37

MQMD

Expiry

Message ID

Correlation ID

Group ID

Message Sequence number offset

Persistence

Priority

Reply to Queue/Queue manager User identifier

Put Application name

Put date/time


26/37


27/37

MQ allowable message sizes

Increased with versions MQ v5.X

MQ V6.X

Disadvantage of bigger Messages Network bandwidth consumption

Processing of messages slows

Segmenting of messages

Grouping of messages


28/37

VERSIONS:- 5.0, 5.1, 5.3, 6.0,

7.0,7.5(Latest version). Currentlywidely used version is 7.0


29/37

MQ Objects: - objects are used to handle the transactions withthe help of services.

QUEUE MANAGER maintains all the objects and services.

QUEUE: it is a database structure which stores messages untilthe application or program receives messages

TYPES OF QUEUES:-

Local Queue Alias Queue Model Queue Remote Queue Repository Queue


30/37

Local Queue:-A queue is local if it is owned by the queue manager to which theapplication program is connected. It is used to store messages forprograms that use the same queue manager.

DEFINE QLOCAL(QUEUE NAME)Remote Queue:-The queue which holds the address of the remote queue managerwhere the message has to be sent or delivered. It is a logical queuewhere we cannot store the messages and get the

messages.

DEFINE QREMOTE(QUEUE NAME) XMITQ(TRANSMISSION QUEUE)RQMNAME(REMOTE QUEUE MANAGER NAME) RNAME(REMOTE QUEUENAME)

Model QueueA model queue is not a real queue. It is a collection of attributes thatare used when a dynamicqueue is created.

DEFINE QMODEL(QUEUE NAME) DEFTYPE(PERMDYN)


31/37

Repository Queue:-These are used in conjunction with clustering and hold either a full or apartial repository of queue managers and queue manager objects in acluster (or group) of queue managers.

Alias Queue :-Alias queues are not real queues but they aredefinitions. They are used to assign different names to the samephysical queue. Advantages of alias queue allow multiple programs towork with the same queue but with different attributes or properties.

Example:Alias for LQ with different parametersDEFINE QALIAS (PQ) TARGQ (LQ) GET (DISABLED) PUT (ENABLED)DEFINE QALIAS (PQ) TARGQ (LQ) PUT (ENABLED) GET (DISABLED)

TYPES OF LOCAL QUEUE:-

Dead letter Queue Transmission Queue Initiation Queue


32/37

Listener

Its a process which listens continuouslyon to a queue manager port.

Default port 1414

Define listener(my.listener.12345)trptype(tcp) port(12345)


33/37

MQI COMMANDS:-MQI Commands are of three types. CONTROL COMMANDS SCRIPT COMMANDS

PCF (programmable command format) COMMANDS.

CONTROL COMMANDS :-( case sensitive) Dspmqver :-to display MQ version Dspmq :- to view all queue managers of MQ. Crtmqm :- to create a queue manager

Strmqm :- to start queue manager Runmqsc :- to enter in to particular queue manager Endmqm :- to end a queue manager Dltmqm :- to delete a queue manager Dspmqcsv :-to display command server Endmqcsv :-to end command server

Strmqcsv :- to start command server Runmqlsr :- to run listener service Endmqlsr :- to end listener service Runmqchl :-to run a channel out of queue manager Runmqdlq :-to execute dead letter handle with the help of rule table


34/37

Setmqaut :-to set authorizations for particular objects likequeuemanager,queues channels,listeners to user or group.

Dspmqaut :-to display authorization for particular user

Dmpmqaut :-to dump authorization for particular user

Runmqchi :-to run a channel initiator for particular queue manager

Runmqtrm :-to run trigger monitor on initiation queue for particularqueue manager

Rcdmqimg :-to take objects (or) record image of a particular queuemanager objects

Rcrmqobj :-to recreate the mq objects which are already recorded


35/37

SCRIPT COMMANDS:-After entering in to queue manager we can find script commands.Script commands are same for every queue manager. (TheseCommands should be used in CAPITAL LETTERS)

DEFINE :-To define/create MQ manager objects like queue,Channels, process, and listener.

DISPLAY :-to view all the properties of a particular object or toDisplay all objects DELETE :-to delete created objects CLEAR :-to clear the message from the queue

END :-to come out of the queue manager PING :-to check whether other side channel / queue manager isready to accept our request. START :- to start the particular channel or listener STOP :-to stop particular channel or listener REFRESH :-used to refresh the security every time after giving or

executing, set mgr orcommand for queue manager or object RESET :-used to reset channel,cluster,queue manager RESOLVE :-to resolve the channel which is in indoubt state SUSPEND :-to suspend a queue manager from a clusterenvironment

RESUME :-to remove a queue manager from a cluster environment


36/37

WMQ Course content daywise (Message Queuing)

Day 1: introduction to EAI, ESB, WMQ and WMB

Role of MQ administrator.

Day2 :Installation WMQ softwarePlaying with Websphere MQ Explorer.

Day 3 :Point to point communication.

Day 4: Distributed Setup.(one to many, many to one & many tomany)

Day 5:Multihopping(gateway)

Day 6: Triggering (channel & Application)

Day 7:Logs (error logs & transmission logs)

Day 8:Cluster Setup ,Load Balancing.


37/37

Day 9: Application of clustering

Day 10: WMQ Installation on Linux OS

Day 11: Security (object authority management)

Day 12: Backup & Restore ,Fixpack installation and migration

Day 13:Publish and Subscribe

Day 14:SSL (Secure Socket Layer)

Day 15:Dead letter Queue , Model queue ,Alias queue.

Day 16:Client Server Architecture

Day 17:SDLC ,Ticketing tools(remedy) ITIL process ,Monitoring tools

Day 18: Trouble shooting ,Interview Questions.

Day 19 to 25: Basic Unix/Linux commands

mq admin demo class_ppt

Documents