Middleware News

Example1 :To start the http process on a First message put in the Queue NOTE : The method to stop/start http as mqm is not covered in this tutorial . Http Process is just used for example .. you can use any process as per your requirement ( Ensure that mqm user should be able to stop/start those processes) ——-  Start QMgr bash-3.2$ strmqm QMC01                      bash-3.2$ runmqsc QMC01 ——- Create Initiation Queue DEFINE QL(TRIGGER.INITIATION.QUEUE) like SYSTEM.DEFAULT.INITIATION.QUEUE ——- Create Local Queue with Triggering Options with  TRIGTYPE(FIRST) DEFINE QLOCAL(TRIGGER.Q) TRIGGER TRIGDPTH(1) TRIGTYPE(FIRST) INITQ(TRIGGER.INITIATION.QUEUE) PROCESS(TRIG.PROCESS) ——- Create Process with APPLICID (  /etc/init.d/httpd start ) It can be any process as per env  DEFINE PROCESS (‘TRIG.PROCESS’) APPLTYPE(UNIX) APPLICID (‘/etc/init.d/httpd start’)   ——- Display QueueDepth before testing to ensure there are no messages in the QUEUE bash-3.2$ echo “DISPLAY QL(TRIGG

New runmqsc features added in MQ 8.0: non-Administrators, client connection, CCDT, authentication The purpose of this techdoc is to provide examples of the new features added to the "runmqsc" command in IBM MQ 8.0. You use runmqsc to issue MQSC commands to a queue manager. New runmqsc features in MQ V8.0 support customizable prompt, "quit", access by non-Administrators, client connection, CCDT, and authentication The chapters are: Chapter 1: Quick summary of commands Chapter 2: Usability: customizable prompt, using 'quit' or 'exit' as synonym for 'end' Chapter 3: Non-administrators (not in the group 'mqm') can now use runmqsc Chapter 4: Flag -u to allow authentication Chapter 5: Flag -c to allow remote access through a client connection Chapter 6: Flag -n to allow the modification of a local CCDT file New runmqsc features added in MQ V8.pdf

You have noticed that the IBM MQ product now takes a stance to have security features turned on by default. many of you will have undoubtedly tripped over CHLAUTH rules blocking you because you asserted a privileged user ID over a client connection, or more recently when playing with V8, you may have also tripped over CONNAUTH rules mandating you provided a user ID and password because you asserted a privileged user ID over a client connection. You'll have no doubt learned that to just turn off CHLAUTH and CONNAUTH completely, you can issue the following commands:- ALTER QMGR CHLAUTH(DISABLED) CONNAUTH(' ') REFRESH SECURITY TYPE(CONNAUTH) Plus, adding the user ID that is already defined on the queue manager system and in the privileged mqm group to your server-connection channel's MCAUSER field. ALTER CHAN NEL( 'SYS TEM. DEF. SVRC ONN) CHLTYPE(SVRCONN) MCAUSER('morag1') However, as you do so, you wish that you

Building highly available architectures with WAS and MQ from Matthew White

The MQ Appliance adds a new simpler way to start collecting this trace information. It also gives you new ways to narrow down what you actually trace. Application activity trace has been available on the distributed MQ platforms since version 7.1 and is a mechanism that allows you to track exactly what an application is doing when it comes to its MQ operations. So it'll show you how they connect, what queues or topics they open and then the messages they put and get. An excellent way to diagnose a wide variety of problems. If you're already familiar with activity trace you'll know that you can enable it in a number of ways and once it's collecting trace it'll write all the trace data as a series of messages to the SYST EM.A DMIN .TRA CE.A CTIV ITY. QUEU E of the queue manager. There are multiple ways to enable activity trace, it's either through turning trace on for all applications by using the queue manager attribute ACTVTRC, or through w

IBM has provided customers with a Software Product Compatibility Reports (SPCR) tool where you can locate and find complete lists of supported operating systems, system requirements, prerequisites, and optional supported software for WebSphere MQ 8.0.   RHEL Compatible OS . Defect support is available for Linux environments that are fully compatible - both source and binary - with Red Hat Enterprise Linux V6. Unless stated otherwise, WebSphere MQ has not been specifically tested in such compatible environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the linux environment itself. If issues arise that are related to the compatible linux environment, the user may need to contact the linux environment vendor for support, or the issue may need to be recreated inside an environment tested by IBM in order to receive WebSphere MQ support. Virtualization . Defect support is av

Virtualization Environments   Defect support is available for Virtualization environments where they relate to releases of the operating system supported by IBM MQ. For IBM MQ for Linux on zSeries, this applies regardless of whether Linux is running natively in a LPAR or within a z/VM. Unless stated otherwise, IBM MQ has not been specifically tested in Virtualization environments. IBM MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the Virtualization environment itself. If issues arise that are related to the Virtualization environment, the user may need to contact the Virtualization environment vendor for support, or the issue may need to be recreated outside of the Virtualization environment in order to receive IBM MQ support. This statement also applies to shared root configurations, such as AIX LPARs and Solaris Zones. IBM MQ has not been adapted to exploit shared root Virtualizat

The WebSphere MQ technote Testing and support statement for WebSphere MQ multi-instance queue managers documents the requirements on a shared file system for it to be supported by WebSphere MQ multi-instance queue managers. It also documents the shared file systems that IBM has already tested with. This technote follows on by describing how to focus testing of a file system that was not listed in the previous technote, to give best confidence that the system will keep integrity and work successfully. WebSphere MQ V7.0.1 introduces multi-instance queue managers. For this you will need a shared file system on networked storage, such as a NAS, or a cluster file system such as IBM's General Parallel File System (GPFS). Shared file systems must provide data write integrity, guaranteed exclusive access to files, and release locks on failure to work reliably with WebSphere MQ. Further details are described in the technote Testing and support statement for WebSphere MQ