mq7

IBM Software Group

WebSphere Support Technical Exchange

WebSphere MQ V7 Client Enhancements

Lauranette Wheeler [email protected]

IBM Software Group

WebSphere Support Technical Exchange 2 of 56

MQ V7 Client Enhancements

This presentation will cover the new client enhancements introduced in MQ V7.0 and V7.0.1.

IBM Software Group


Agenda

MQ V7.0 Enhancements Conversation Sharing

Client Connection Limiting

Connection Groups

Message Properties

New MQ APIs

IBM Software Group


Agenda

MQ V7.0.1 Enhancements Multi-Instances Queue Manager

Automatic Client Reconnect

Enhanced SSL Security

Enhanced .NET support

IBM Software Group


Agenda

MQ V7.0.1 Enhancements Log Compression

GROUP Units Of Recovery

Generic Application Structure Backup

Admin Structure Recovery

IBM Software Group


Conversation Sharing Multiple instances of an MQI channel can be made to share a

single TCP/IP connection.

If a channel is defined with the SHARECNV parameter set to a value greater than 1, then that number of conversations can share a channel instance.

IBM Software Group


Conversation Sharing

Server

MQCONNMQOPENMQPUT

Q2

One socket for n conversationsSocket is bi-directionalHeartbeats occur at all times

Client

Q3

Q1

MQCONNMQOPENMQPUT

MQCONNMQOPENMQPUT

IBM Software Group


Conversation Sharing New SHARECNV channel attribute

0 All sharing is off ; channel operates in MQ V6 mode1 Sharing is off; channel still operates in MQ V7 mode>1 Channel sharing up to negotiated value. Value negotiated down. Default 10.

Can be overridden at MQCONNX time: MQCNO_NO_CONV_SHARING

equivalent to SHARECNV(1) MQCNO_ALL_CONVS_SHARE (default)

IBM Software Group


Limiting client connectionsTwo New SVRCONN Channel attributes Restrict the number of client-connection.

Helps eliminate maximum number of channels.

MAXINST restricts the number of instances in total for the specific channel name.

MAXINSTC restricts the number of instances from a specific IP address for that channel name.

IBM Software Group


Limiting client connectionsQueue Manager

SVRCONNMAXINST(4)

MAXINSTC(2)

IBM Software Group


Connection GroupsNew Client Channel attributes

Workload Balance selection of client channel definition in the CCDT

CLNTWGHT

Specifies a weighting to influence which client-connection channel definition is used.

placed in an order of preference based on their weighting. AFFINITY

Specifies whether client applications that connect multiple times using the same queue manager name, use the same client channel PREFERRED - channels selected in the same initial order of

preference NONE - workload balance channel selection

IBM Software Group


Workload Balancing client connections

MQCONN(*planet)

Name CHLTYPE TRPTYPE CONNAME QMNAME

chl1 CLNTCONN TCP ip.mars planet

chl2 CLNTCONN TCP ip.venus planet

chl3 CLNTCONN TCP ip.pluto planet

AFFINITY

PREFERRED

PREFERRED

PREFERRED

CLNTWGHT

4

4

2

40%

40%

20%

mars

venus

pluto

IBM Software Group


Message Properties The MQ V6 JMS client stores some JMS properties in an

MQRFH2 header in the message payload.

This requires the recipient to be aware of the presence of the MQRFH2.

MQ V7 applications can add properties to messages using new MQI calls.

A property is a named piece of data that is not treated as part of the message payload.

The properties are accessed by means of a message handle passed in on the MQPMO and MQGMO.

IBM Software Group


Message Properties A V7 application can choose how to have the properties returned

to the applicaiton :MQGMO_PROPERTIES_IN_HANDLE return the properties in

a message handle MQGMO_PROPERTIES_FORCE_MQRFH2 return the

properties in an MQRFH2.MQGMO_NO_PROPERTIES remove all properties before

giving to the application.MQGMO_PROPERTIES_COMPATIBILITY if a V6 JMS

property is set then all properties are returned in an MQRFH2 otherwise all properties will be removed.

If none of the above are specified then the PROPCTL queue attribute determines how the properties should be returned. Compatibility mode is the default.

IBM Software Group


Message Properties API MQCRTMH - creates a message handle.

MQDLTMH - deletes a message handle.

MQSETMP - sets or modifies the value of a message property.

MQINQMP - inquires the value of a message property.

MQDLTMP - deletes a message property.

MQBUFMH - takes properties in an MQRFH2 and converts them to properties in a message handle.

MQMHBUF - takes a message handle and converts the properties into an MQRFH2.

IBM Software Group


Message Selectors An additional advantage is that message properties can be used as

extra criteria when selecting specific messages.

Prior to MQ V7 natively supported selection by Message ID or Correlation ID.

The JMS implementation of selectors had to browse for messages, compare them to the selection criteria, then get the ones that match.

Applications can now use message selectors to only receive messages meeting specific criteria based on message headers and properties.

IBM Software Group


Message Properties Samples New samples:

amqsstm put a single message with user specified properties

amqsiqm get a single message and display the properties

amqsbcg/CSQ4BCG0/CSQ4BCG1 now has a third parameter to choose how to get the properties

amqsaem sample API exit working with properties

IBM Software Group


New WebSphere MQ API WebSphere MQ V7 extends the MQ API in a number of

ways. Asynchronous Consumption of messages

Asynchronous Put Response

Read-ahead of messages

IBM Software Group


Asynchronous Consumption of Messages

Asynchronous consumer allows the application to register an interest in messages and identify a callback routine which should be invoked when a message arrives.

The application can continue without a need to tie up a thread sitting in an MQGET call.

The application does not need to 'guess' the size of the buffer. The system will pass the application a message already in a buffer.

The application can register an interest in any number of queues.

IBM Software Group


MQCB defines your message consumers

MQCTL - controls whether message consumption is currently operable.

Once MQCTL called for a specific hConn you give up control of that hConn for call-back to use

Errors received if use hconn for any other MQ call except another MQCTL call (i.e. MQOP_STOP)MQRC_HCONN_ASYNC_ACTIVE


IBM Software Group


MQCB ties a function (described in the (MQCBD) to an object handle.

Two types of call-back function you can define.

A message consumer which is tied to an object handle, and receives messages or errors about a queue

An event handler which is tied to the connection handle and receives error notifications about the connection such as MQRC_Q_MGR_QUIESCING.


IBM Software Group


Asynchronous Put Response

Asynchronous Put is a recognition of the fact that a large proportion of the cost of an MQPUT from a client is the line turnaround of the network connection.

When using Asynchronous Put the application sends the message to the server but does not wait for a response.

Once the application has competed it's put sequence it will issue MQCMIT or MQDISC which will flush out any MQPUT calls which have not yet completed.

MQSTAT can be issued at anything to check the status of how many message successfully put or failed.

IBM Software Group


Read-ahead of messagesRead Ahead is a recognition of the fact that a large proportion of the

cost of an MQGET from a client is the line turnaround of the network connection.

Read ahead on a client allow non persistent messages to be sent to a client without the client application having to request the messages.

The server will send as many non-persistent messages matching the criteria (such as MsgId) as it can up to the limit set by the client.

If an application requests read ahead but the messages are not suitable; Read ahead is effectively turned off until a sequence of non-persistent messages are on the queue again.

The message buffer is an 'in memory' queue of messages. If the application ends or the machine crashes these messages will be lost.

IBM Software Group


Read-ahead of messages

Use the new CLOSE option MQCO_QUIESCE to gracefully end an application when messages may be left in the client-side read-ahead buffer.

The MQCLOSE will return with MQRC_READ_AHEAD_MSGS and the application can continue to use the object handle to get the remaining messages.

A subsequent MQGET that reach the end of the messages in the buffer will return with MQRC_HOBJ_QUIESCED_NO_MSGS

The default value for MQCLOSE is MQCO_IMMEDIATE which will throw away any unconsumed messages

IBM Software Group


WebSphere MQ V7.0.1

IBM Software Group


Agenda MQ V7.0.1 Enhancements

Multi-Instances Queue Manager


Enhanced SSL Security

Enhanced .NET support

MQ V7.0.1 Enhancements Log Compression

GROUP Units Of Recovery



IBM Software Group


Multi-instance Queue Managers Provide basic failover support without an HA coordinator

Queue manager data is held in networked storageMQ ensures only one instance of the queue manager is active

Can start multiple instances of a queue manager on different machines (must be same platform)Active instance

owns the queue managers files will accept connections from applications

Standby instance does not own the queue managers files if the active instance fails, performs queue manager restart

and becomes active limited to one standby instance

IBM Software Group


Multi-instance queue managers The IP address is not taken over

Channel config needs all possible addresses CONNAME(host1(port1),host2(port2))

Support for networked storage over modern network file system protocols

For example, NFS v4 (not v3) Tool shipped to validate configuration

New options for crtmqm/strmqm/endmqm to control operations

IBM Software Group


Setting up for multi-instance queue manager

You need to create the queue manager data and logs on networked storage

Use the amqmfsck tool to check out the directories that youre going to use for the dataamqmfsck /shared/qmdata

Checks basic POSIX file locking behaviouramqmfsck w /shared/qmdata

Use on two machines at once to ensure that the locks are handed off correctly when a process ends.

amqmfsck c /shared/qmdata Use on two machines at once to attempt concurrent writes.

You must run successfully run all three tests on both machines to avoid problemsThis diagnoses when the file system doesnt follow the POSIX specification

If this tool fails, a queue manager created using the directory will NOT work correctly.

IBM Software Group


Setting up a multi-instance queue manager

Create the queue manager on machineAcrtmqm md /shared/qmdata ld /shared/qmlog QM1

Define the queue manager on machineB (or edit mqs.ini)addmqinf vName=QM1 vDirectory=QM1 vPrefix=/var/mqmvDataPath=/shared/qmdata/QM1

Start the active instance of the queue manager on machineAstrmqm x QM1WebSphere MQ queue manager QM1 started.

Start the standby instance of the queue manager on machineBstrmqm x QM1WebSphere MQ queue manager QM1 started as a standby instance.

If the queue manager instance on machineA fails, the standby on machineB takes over and becomes the active instance

IBM Software Group


Observing a multi-instance queue manager We have an active instance on machineA and a standby instance on

machineB

On machineA, this is what you see:dspmq x o standbyQMNAME(QM1) STANDBY(Permitted) STATUS(Running) INSTANCE(machineA) MODE(Active) INSTANCE(machineB) MODE(Standby)

On machineB, this is what you see:dspmq x o standbyQMNAME(QM1) STANDBY(Permitted) STATUS(Running as standby) INSTANCE(machineA) MODE(Active) INSTANCE(machineB) MODE(Standby)

If QM1 was also configured on a third machine with no running instances, this is what you see:dspmq x o standbyQMNAME(QM1) STANDBY(Permitted) STATUS(Running elsewhere) INSTANCE(machineA) MODE(Active) INSTANCE(machineB) MODE(Standby)

IBM Software Group


Stopping a multi-instance queue manager To completely stop a multi-instance queue manager, issue a normal endmqm

on the active instance on machine A:endmqm i QM1WebSphere MQ queue manager QM1 ended.

Both instances end

To stop just the standby instance, on machine B:endmqm x QM1WebSphere MQ standby queue manager instance QM1 ended.

To switch over the active to the standby, on machine A:endmqm is QM1WebSphere MQ queue manager QM1 ended, permitting switchover to a standby instance.

Once the active instance has ended, the standby instance will try to become the active instance.

IBM Software Group


Automatic Client Reconnect Manual reconnection requires the client application to recreate a

connection using MQCONN or MQCONNX, and reopen objects after a failure.

With Auto-reconnection, the connection is automatically restored and the handles to open objects are all restored after a failure.

Tries to hide queue manager failures by restoring current state automaticallyFor example, if MQPUT returns error, client reruns

MQCONN/MQOPEN/MQPUT internally

IBM Software Group


Automatic Client Reconnection Uses the list of addresses in CONNAME to find queue manager

MQSERVER=SYSTEM.DEF.SVRCONN/TCP/host1(1414),host2(1414)

Re-opens queues and other qmgr objects, re-establishes subscriptions

Total reconnect timeout is configurable MQReconnectTimeout

The timeout in seconds for retrying a client reconnection. The default value is 1800 seconds (30 minutes).

IBM Software Group


Automatic Client Reconnect Requirements

MQ V7.0.1 server and clientMQRC_ENVIRONMENT_ERROR

Threaded clientMQRC_ENVIRONMENT_ERROR

SHARECNV non-zeroMQRC_ENVIRONMENT_ERROR

IBM Software Group



New MQCONNX optionsMQCNO_RECONNECTMQCNO_RECONNECT_Q_MGRMQCNO_RECONNECT_DISABLED

Options not supportedMQPMO_LOGICAL_ORDERMQGMO_LOGICAL_ORDER

IBM Software Group



DefRecon=NO|YES|QMGR|DISABLED DefRecon attribute provides administrative option to enable or

disable client automatic reconnect,

NO - Unless overridden by MQCONNX, the client is not reconnected automatically.

YES - Unless overridden by MQCONNX, the client reconnects automatically.

QMGR - Unless overridden by MQCONNX, the client reconnects automatically, to the same queue manager.

DISABLED -Reconnection is disabled, even if requested by the client program using the MQCONNX MQI call.

IBM Software Group


Automatic Client Reconnect Should no longer see:MQRC_CONNECTION_BROKEN

MQRC_RECONNECT_FAILEDMQ failed whilst attempting to reconnect your connection

MQRC_RECONNECT_QMID_MISMATCHMQ reconnected your connection, but didn't find the queue

manager it was expecting MQRC_RECONNECT_Q_MGR_REQDMQ reconnected your connection, but due to the type of objects

you have open it requires RECONNECT_Q_MGR to be specified.

IBM Software Group


Automatic Client Reconnect Reconnectable Scenario Communications failureQueue Manager or Listener failureSTOP CONNendmqm s or endmqm r

The following will not cause reconnectSTOP CHANNEL

except if the channel is hung then this may kill socket Any other endmqm

IBM Software Group


Enhanced SSL Security - OCSP SSL and TLS can provide the following to protect customer data:Authentication using digital certificates to check the identity of

the remote entity

Confidentiality using encryption to protect the data sent over the network from snooping

Integrity using digitally signed hashes of data packets to prevent data being modified in transit

Non-repudiation using the uniqueness of the private key to prove that some data originated from a specific sender for audit purposes

Certificate revocation checking is an additional authentication check that can be made against a digital certificate.

IBM Software Group


Enhanced SSL Security - OCSP MQ already has support for CRL certificate revocation checking

using an LDAP server.

To keep up to date with changing SSL standards an alternative method of revocation checking was added.

OCSP is the Online Certificate Status Protocol defined by RFC 2560.

OCSP is a request/response protocol specifically designed for checking certificate revocation status. Typical usage:Request: What is the status of certificate CN=Lauranet, O=IBM

serial #q?Response: The certificate is revoked

OCSP requests and responses are sent over the HTTP protocol. HTTP is the only protocol supported in MQ.

IBM Software Group


Enhanced SSL Security - OCSP

The location of the OCSP responder can be specified as a URL in several different ways, including:The MQAIR structure on a client MQCONNX call.

The Client Channel Definition Table file on a client.

Using AUTHINFO objects named in the queue manager SSLCRLNL namelist.

Embedded in an AuthorityInfoAccess certificate extension.

IBM Software Group


Enhanced SSL Security - OCSP Configure both LDAP CRL and OCSP revocation checking at the

same time.

Sequence of revocation checking depends on the underlying SSL socket library.

GSKit for Windows and UNIX platforms checks in this sequence:1 OCSP responder which has been explicitly configured

2 OCSP responder from an AuthorityInfoAccess certificate extension

3 LDAP CRL server which has been explicitly configured

4 LDAP CRL server from a CrlDistributionPoint cert. extension

IBM Software Group


Enhanced SSL Security - OCSP OCSP revocation checking is not currently supported:

i5/OS z/OS Java and JMS clients

Newer JREs have the ability to configure OCSP on a JRE-wide basis using the ocsp.responderURL security property, but this is not set by the WebSphere MQ Java or JMS code.

IBM Software Group


Enhanced SSL Security - secret key reset

Initial SSL handshake establishes a secret key used to encrypt data. Over time, as more data is encrypted then an attacker can attempt to guess the secret key.

After a certain number of bytes have flowed then the SSL secret key is renegotiated.

Both the client and server-side SSL library must support a compatible version of the secret key reset protocol.

Java clientJava clientQueue Queue

managermanagerSSLSSL

Java/JMSJava/JMS

clientclient

Queue Queue

managermanagerSSLSSLJSSEJSSE SSL librarySSL library

IBM Software Group


Enhanced SSL Security - secret key reset

JSSE V2 changed the way that SSL secret key resets are done.

To allow the MQ Java/JMS clients to be able to perform SSL secret key resets to a queue manager using GSKit.Alternative version known as GSKit 7.5.

MQ can now dynamically load either the existing GSKit 7d or the new GSKit 7.5 SSL library.

IBM Software Group


Enhanced SSL Security - secret key reset To enable JSSE2 secret key reset interoperability, the main steps

are:1 Download and install the GSKit 7.5 runtime packages.

http://www.ibm.com/support/docview.wss?rs=0&uid=swg240228962 Add the AltGSKit=y setting to the SSL stanza of your queue

manager qm.ini (or Windows Registry).3 Issue a REFRESH SECURITY TYPE(SSL) MQSC command to

refresh the SSL configuration and restart SSL channels using GSKit 7.5.

Detailed instructions are provided in a readme file supplied with GSKit 7.5 on IBM Fix Central.

IBM Software Group


Enhanced .NET Support - WCF The Microsoft Windows Communication Foundation (WCF) is a set of new API

introduced in .NET 3.0 which provides a communications and services framework.

WCF primary focus is for service orientated architecturesSimplifies integration by separating the roles of transporting and encoding data

WMQ is integrated as a transport channel

WMQ

Q

Message Encoder

WMQ Transport

Protocols..

WCF Client Application

WCF Channel Stack

WCF Services Layer

Message Encoder

WMQ Transport

Protocols..

WCF ServiceApplication

WCF Channel Stack

WCF Services Layer

IBM Software Group


Enhanced .NET Support - WCF WCF architecture The WebSphere MQ custom channel

for WCF is integrated on top of the IBM Message Service Client for .NET (XMS .NET) API

IBM Software Group


z/OS Log Compression Help eliminate capacity limits due to Log Data bandwidth constraints May reduce the size of your logsDependent on your message contentUseful if you are DASD constrained.

RLE (run-length encoding) of insert log records for private queue messagesWill not compress shared queue log records

SMF 115 records updated to show compression rates achieved Controlled via zPARM option at queue manager level. COMPLOG(NONE) or COMPLOG(RLE) in CSQ6LOGP Can also be viewed/controlled via DISPLAY LOG / SET LOG

IBM Software Group


Group-level Units of Recovery for z/OS Transactional client applications can now be configured to connect

to a z/OS queue-sharing group (QSG) instead of a single queue manager.

Recovery of 2-phase commit transactions, when in-doubt, can be performed on other queue managers in the same QSG.

Requires use of the Extended Transactional Client For example, from WAS

Configure the WAS client connection with the QSG name rather than the QMGR name

To use Group units of recovery on a queue manager within a QSG, enable the GROUPUR queue manager attribute.

IBM Software Group



Queue managers prior to V7.0.1 can only rebuild their own admin structure entries.Created an issue in a disaster recovery situation as every queue

manager in the QSG has to be started.

MQ Version 7.0.1 the first queue manager started can rebuild the admin structure for other members of the queue sharing group as well as its own.

It is no longer necessary to restart each queue manager in the queue sharing group to recover the admin structure.

IBM Software Group



BACKUP CFSTRUCT The name of the Coupling Facility (CF) application structure to be

backed up. An asterisk (*) on its own specifies all recoverable CF

structures.

A trailing asterisk (*) matches all recoverable structure names with the specified stem followed by zero or more characters.

The value (CSQ*) matches all recoverable CF structures with the specified stem (CSQ) followed by zero or more characters.

IBM Software Group


Additional WebSphere Product Resources Discover the latest trends in WebSphere Technology and implementation, participate in

technically-focused briefings, webcasts and podcasts at: http://www.ibm.com/developerworks/websphere/community/

Learn about other upcoming webcasts, conferences and events: http://www.ibm.com/software/websphere/events_1.html

Join the Global WebSphere User Group Community: http://www.websphere.org

Access key product show-me demos and tutorials by visiting IBM Education Assistant: http://www.ibm.com/software/info/education/assistant

View a webcast replay with step-by-step instructions for using the Service Request (SR) tool for submitting problems electronically: http://www.ibm.com/software/websphere/support/d2w.html

Sign up to receive weekly technical My Notifications emails: http://www.ibm.com/software/support/einfo.html

IBM Software Group


Join WebSphere Support Technical Exchange on Facebook!

Stay up-to-update on upcoming webcast sessions

Suggest future topics Suggest program

improvements Network with other product

users And More

Become a fan now! http://www.facebook.com/pages/WebSphere-Support-Technical-Exchange/121293581419

IBM Software Group


Questions and Answers

WebSphere MQ V7 Client Enhancements MQ V7 Client EnhancementsAgendaAgendaAgendaConversation SharingConversation SharingConversation Sharing Limiting client connectionsLimiting client connectionsConnection GroupsWorkload Balancing client connectionsMessage Properties Message PropertiesMessage Properties APIMessage SelectorsMessage Properties Samples New WebSphere MQ APIAsynchronous Consumption of Messages Asynchronous Consumption of MessagesAsynchronous Consumption of MessagesAsynchronous Put ResponseRead-ahead of messagesRead-ahead of messagesSlide 25AgendaMulti-instance Queue ManagersMulti-instance queue managersSetting up for multi-instance queue managerSetting up a multi-instance queue managerObserving a multi-instance queue managerStopping a multi-instance queue managerAutomatic Client ReconnectAutomatic Client ReconnectionAutomatic Client Reconnect RequirementsAutomatic Client Reconnect Automatic Client Reconnect Automatic Client ReconnectAutomatic Client ReconnectEnhanced SSL Security - OCSPEnhanced SSL Security - OCSPEnhanced SSL Security - OCSPEnhanced SSL Security - OCSPEnhanced SSL Security - OCSP Enhanced SSL Security - secret key resetEnhanced SSL Security - secret key resetEnhanced SSL Security - secret key resetEnhanced .NET Support - WCFEnhanced .NET Support - WCF z/OS Log CompressionGroup-level Units of Recovery for z/OSAdmin Structure Recovery Generic Application Structure BackupAdditional WebSphere Product ResourcesJoin WebSphere Support Technical Exchange on Facebook!Slide 56

mq7

Documents

number of client

mq v7 mode1 channel

specific channel

mqi channel

new client enhancements

client applications

agenda mq v7

mq v6 mode1 sharing