HP NonStop WebSphere MQ Series Monitoring

Reflex 80:20 for IBM WebSphere MQ Series, Queue Managers, Queues and Channels -

Reflex allows users to automatically detect all WebSphere MQ components. Once detected, a default object tree can be dynamically created or users can tailor their own using simple, intuitive drag-and-drop-techniques.
 

Reflex 80:20 for IBM WebSphere MQ Series, Managers, Queues and Channels -

All object components are organised by type and subtype for ease of selection. Select any WebSphere MQ type and Subtype to list all detected subordinate components instantly.
 

Reflex 80:20 for IBM WebSphere MQ Series, Queue Managers, Queues & Channels -

All WebSphere MQ channels listed. The monitored icon in the left column indicates that the component is being monitored by Reflex.
 

Reflex for IBM WebSphere MQ Series, Queue Managers, Queues and Channels -

The Queue Manager 'M001.QM.SCB.LIV' has been detected by the Reflex software and is listed and tagged as a monitored WebSphere MQ object.
 

Reflex 80:20 for WebSphere MQ Series, Queue Managers, Queues and Channels -

All WebSphere MQ Queue names currently available. EMS events are generated with a subject token identical to the component name for graphical mapping purposes.
 

Reflex 80:20 for IBM WebSphere MQ, Queue Managers, Queues and Channels -

Once having detected the WebSphere MQ components and refreshed the Reflex NonStop monitoring software, the WebSphere MQ object tree can be accessed from the live Reflex view.
 

Reflex 80:20 for IBM MQ Series, Queue Managers, Queues and Channels -

Opening up the WebSphere MQ object tree reveals all subordinate objects.
 

Reflex for IBM WebSphere MQ Series, Queue Managers, Queues and Channels -

Drilling still further presents the user with each individually detected WebSphere MQ component. Green represents UP, Blue represents VULNERABLE and RED represents CRITICAL.
 

Reflex 80:20 for IBM WebSphere MQ Series, Queue Managers, Queues and Channels:

Left-clicking on each component allows users to obtain detailed information relating to the WebSphere MQ component instantly.
 

Monitoring IBM WebSphere MQ Series, Queue Managers, Queues and Channels -

All information relating to the WebSphere MQ component is presented to the user in a detail text user in a detail text window. This shows the detail for the chosen channel.
 

Reflex 80:20 for WebSphere MQ Series, Queue Managers, Queues and Channels -

Clicking on a WebSphere MQ Queue Name will detail all information relating to that particular Queue name.
 

Reflex for IBM WebSphere MQ Series, Queue Managers, Queues & Channels -

The nerve centre of the Reflex product is known as the Reaction Engine. With this, users can configure an EMS event or EMS event range to invoke one or more reactions from email, SNMP traps, mobile SMS, run a task, alert to an Enterprise Manager or graphically alert to one of the icons seen in the last set of Status Monitor screenshots.
 

IBM WebSphere MQ V5.3 Extended to the HP NonStop Server Platform

At a glance :

WebSphere MQ for HP NonStop Server V5.3 (5.3.1.4) enriches WebSphere MQ. It includes:

• Functional equivalence to other WebSphere MQ V5.3 platforms
  
   
• Availability on the HP NonStop Server S-series and NonStop Integrity Server (32-bit) architectures
  
   
• Full enablement of the Java(TM) Message Service (JMS) application programming interface: embedded classes for Java and JMS support with improved performance and packaging
  
   
• A Publish/Subscribe function, which simplifies the task of getting business messages and transactions to a wide, dynamic, and potentially large audience in a timely manner
  
   
• Scalability and usability improvements over the previous MQSeries® offering
  
   
• Improved MQ workload balancing (through clustering)
  
   
• Improved national language support (for example, code page GB18030 for use in the People's Republic of China)
  
   
• SSL security authentication facilities
  
   
• Four out of five customers who buy inter-application messaging choose WebSphere MQ, according to WinterGreen Research, Inc.1.
   

Overview

WebSphere® MQ for HP NonStop Server V5.3 builds on the success of WebSphere MQ, the market-leading provider of message-oriented-middleware (MOM) software for application connectivity. WebSphere MQ brings enhanced security, better and more flexible management and tuning capability, and added features to enhance cross-platform consistency.

For common security problems, WebSphere MQ provides:

• Symmetric key cryptography to prevent eavesdropping
  
• The hash function to prevent tampering
  
• Digital certificates, asymmetric keys, and certificate revocation lists to prevent impersonation

These security features are implemented using a port of the OpenSSL cryptographic software, provided by IBM with this release.

General MQ operation is significantly enhanced by a process management rules database that enables sophisticated, yet easy-to-use control over the unique multiprocessor architecture of a WebSphere MQ queue manager running on HP NonStop Server.

Most components now run in the Open System Services (OSS) environment of HP NonStop Server, enabling the use of multi-threaded agent processes. This feature can enable a more efficient, scalable implementation for typical mixed workloads.

Reliability and data integrity are enhanced with the introduction of a fault-tolerant Execution Controller process-pair. Components critical to data storage retain their fault-tolerant capabilities, and critical databases remain in the transactional Guardian file system.

The use of OSS, plus other enhancements (including data link libraries), also results in a more consistent set of interfaces to WebSphere MQ on HP NonStop Server, while continuing to support all existing languages and environments. Support for the new Itanium-based HP NonStop Integrity Server is also provided.

Connects applications reliably and affordably

Connects nearly everything to almost anything, reducing IT complexity
Provides IBM's industry-leading messaging middleware at an affordable price
Enables fast and easy installation and deployment: Gets you up and running in minutes and in production within hours, without specialist training

Offers scalability and flexibility for growth

Provides seamless growth for your software as your business needs evolve
Is compatible with WebSphere MQ on many platforms
Takes advantage of a portfolio of product extensions to deliver additional capabilities fast
Speeds solution development and reduces support costs

Simplifies networking interfaces, cuts application development time, and enables design and code reuse
Is supported by more than 3,000 certified professionals
Supports key platforms with the industry's de facto messaging standard

Runs on the HP NonStop Server S-series and NonStop Integrity Server (32-bit) platforms
Extends the WebSphere MQ family

Reflex monitoring IBM WebSphere MQ Series on HP NonStop (ServerNet and Itanium) and Open System Services (OSS)

Reflex provides auto-detection of WebSphere MQ components (Queue Managers, Queues and Channels) on HP NonStop (and OSS) as well as status monitoring and detailed information at a single click.
 

runmqsc (run MQSC commands)

Purpose
Use the runmqsc command to issue MQSC commands to a queue manager. MQSC commands enable you to perform administration tasks, for example defining, altering, or deleting a local queue object. MQSC commands and their syntax are described in the WebSphere MQ Script (MQSC) Command Reference.

Syntax

            .------------------------------.                
            V                              |                
>>-runmqsc----+--------------------------+-+--+----------+-----><
              +- -e ---------------------+    '-QMgrName-'  
              +- -v ---------------------+                  
              '- -w --WaitTime--+------+-'                  
                                '- -x -'                    

Description
You can invoke the runmqsc command in three ways:
Verify command
Verify MQSC commands but do not run them. An output report is generated indicating the success or failure of each command. This mode is available on a local queue manager only.
Run command directly
Send MQSC commands directly to a local queue manager.
Run command indirectly
Run MQSC commands on a remote queue manager. These commands are put on the command queue on a remote queue manager and run in the order in which they were queued. Reports from the commands are returned to the local queue manager.
Indirect mode operation is performed through the default queue manager.

The runmqsc command takes its input from stdin. When the commands are processed, the results and a summary are put into a report that is sent to stdout.

By taking stdin from the keyboard, you can enter MQSC commands interactively.

By redirecting the input from a file, you can run a sequence of frequently-used commands contained in the file. You can also redirect the output report to a file.

Optional parameters
-e
Prevents source text for the MQSC commands from being copied into a report. This is useful when you enter commands interactively.
-v
Verifies the specified commands without performing the actions. This mode is only available locally. The -w and -x flags are ignored if they are specified at the same time.
-w WaitTime
Run the MQSC commands on another queue manager. You must have the required channel and transmission queues set up for this. See Preparing channels and transmission queues for remote administration for more information.
WaitTime
The time, in seconds, that runmqsc waits for replies. Any replies received after this are discarded, but the MQSC commands still run. Specify a time between 1 and 999 999 seconds.
Each command is sent as an Escape PCF to the command queue (SYSTEM.ADMIN.COMMAND.QUEUE) of the target queue manager.

The replies are received on queue SYSTEM.MQSC.REPLY.QUEUE and the outcome is added to the report. This can be defined as either a local queue or a model queue.

Indirect mode operation is performed through the default queue manager.

This flag is ignored if the -v flag is specified.

-x
The target queue manager is running under z/OS®. This flag applies only in indirect mode. The -w flag must also be specified. In indirect mode, the MQSC commands are written in a form suitable for the WebSphere® MQ for z/OS command queue.
QMgrName
The name of the target queue manager on which to run the MQSC commands, by default, the default queue manager.
Return codes
00 MQSC command file processed successfully
10 MQSC command file processed with errors; report contains reasons for failing commands
20 Error; MQSC command file not run

Examples
Enter this command at the command prompt:
runmqscNow you can enter MQSC commands directly at the command prompt. No queue manager name is specified, so the MQSC commands are processed on the default queue manager.
Use one of these commands, as appropriate in your environment, to specify that MQSC commands are to be verified only:
runmqsc -v BANK < "/u/users/commfile.in"
 
runmqsc -v BANK < "c:\users\commfile.in"This command verifies the MQSC commands in file commfile.in. The queue manager name is BANK. The output is displayed in the current window.
These commands run the MQSC command file mqscfile.in against the default queue manager.
runmqsc < "/var/mqm/mqsc/mqscfile.in" > "/var/mqm/mqsc/mqscfile.out"
 
runmqsc < "c:\Program Files\IBM\WebSphere MQ\mqsc\mqscfile.in" >
 "c:\Program Files\IBM\WebSphere MQ\mqsc\mqscfile.out"In this example, the output is directed to file mqscfile.out.

Using Reflex with Websphere MQ 5.3

Note that the information below applies to the following version of Websphere MQ and later:

$ mqver
Name:        WebSphere MQ
Version:     531.4  FP5314
CMVC level:  WMQ-5-3-1-4
BuildType:   IKAP - (Production)

Autodetection of Websphere MQ components

Websphere MQ components are autodetected via the macro, MQAD. MQAD requires access to the mqs.ini file which now resides in OSS.

The following steps can be used to autodetect a Websphere MQ 5.3 environment:

• Copy the mqs.ini file to the Guardian environment.
Note that the mqs.ini file is generally located in the var/mqm folder. Also be aware that OSS can only use physical volumes; it cannot access SMF (virtual) volumes, therefore ensure that the destination volume is a physical disk.

cp /var/mqm/mqs.ini /G/VOL/SVOL/MQSINIC

• The copied file will appear as a code 180 file, e.g.

              CODE              EOF   LAST MODIFIED  OWNER  RWEP   PExt   SExt
MQSINIC        180+            1446 02DEC2008 10:15  90,221 NUNU     28  14000

To be able to use it in the Guardian environment, it should be changed to a filecode 101 file using the CTOEDIT utility. Note that the destination filename should be MQSINI:

            CTOEDIT MQSINIC ,  <reflex_object_subvol>.MQSINI

• Ensure that the mqm.manager user can read and write files in the Reflex object subvolume then logon as mqm.manager and volume to the reflex object subvolume.

  logon mmq.manger
  volume <reflex_object_subvol>.

• Edit the MQAD macro as follows:

Ensure that the mqsc_loc variable is set to the location of the RUNMQSC utility. E.g.

 #SET mqsc_loc  $SYSTEM.ZWMQBIN.RUNMQSC

• Load the macro as follows:

LOAD /KEEP 1/ MQAD

• Execute the macro:

MQAD

This will create Insertion and Deletion commands for the Reflex SQL Database, named MQSQLIN and MQSQLDEL.

• Ensure that the <reflex owner> user has read access to the MQSQLIN and MQSQLDEL files then logon as <reflex.owner> and volume to the reflex object subvolume.

  logon<reflex.owner>
  volume <reflex_object subvolume>

• Load the standard Reflex SQL defines:

  run rsqldefs

• Insert the autodetected components into the Reflex:

  SQLCI /IN MQSQLIN/

Note that the entries are entered into the database as ‘Set-up’ versions and therefore a warmboot is required to make the change ‘live’. Note that a FULL warmboot is required since the autodetect macro does not make use of the Top Level Changes table.

 

Status Agent for Websphere MQ components

The Status Agent for Websphere MQ makes use of the RUNMQSC utility; providing it with a command file and then parsing the resulting output file as follows:

• The MQ Status Agent (MQAG) writes a command to the MQCOMM file.
• The MQCOMM file is then read and processed by the MQ Series utility, RUNMQSC.
• RUNMQSC writes its output to the MQOUT file.
• The contents of the MQOUT file are read and processed by the MQ Status Agent (MQAG).

 

This means that the following security requirements must be adhered to:

• The MQ Status Agent (MQAG) must have write access to MQCOMM
• The RUNMQSC utility must have read access to MQCOMM
• The RUNMQSC utility must have write access to MQOUT
• The MQ Status Agent (MQAG) must have read access to MQOUT

 

 

 

 

 

 

 

 

 

 

In a configuration where Reflex is owned by 90,10 and Websphere MQ is owned by 251,255, a method of providing this security is as follows:

• Secure MQCOMM as NNNN and owned by 90,10
i.e. FUP SECURE MQCOMM, NNNN
      FUP GIVE MQCOMM, 90,10

• Secure MQOUT as NNNN and owned by 251,255
i.e. FUP SECURE MQOUT, NNNN
      FUP GIVE MQOUT, 251,255

• Progid MQAG as 251,255
i.e. Logon SUPER.SUPER
      FUP GIVE MQAG,251,255
      FUP SECURE MQAG , , PROGID
 

The following Reflex Admin File Aliases must also be configured:

 MQCOMM - Location of the command file sent to RUNMQSC
MQOUT - Location of the output file used by RUNMQSC

The following Reflex Admin parameters must also be configured:

 MQSC-CPU  - CPU number to use for the RUNMQSC process
  MQSC-LOCATION - Location of the Guardian RUNMQSC object
  MQSC-PRIORITY - Priority to use for the RUNMQSC process
  MQSC-PROCESS - Processname used for the RUNMQSC process

 MQVOLUME      - MQ’s default volume (MQ 5.1 param)
 MQDEFAULTPREFIX – MQ’s default prefix (MQ 5.1 param)

* Note that the following parameters have been configured but are not currently being used. A beta version of MQAG was coded to try to produce an agent that worked with the initial release of Websphere MQ 5.3 and this version used those fields in the param message that is sent to the TACL process that runs RUNMQSC. Once the updated version of Websphere MQ 5.3 was installed, it was found that the original MQAG program worked.

*  MQNSKOPTPATH - This is the location of the opt folder e.g. /opt/mqm
* MQNSKVARPATH - This is the location of the var folder e.g. /var/mqm
  

If the parameters are not configured, the following default values will be used:

 MQSC-CPU  - 0
  MQSC-LOCATION - $SYSTEM.SYSTEM.RUNMQSC
  MQSC-PRIORITY - 50
  MQSC-PROCESS - $RFMQ

 MQVOLUME      - $SYSTEM
 MQDEFAULTPREFIX – $SYSTEM

 

Important Note:

With the current release of Websphere MQ, when the MQ Status Agent asks for the status of a channel that has not been used via the command “display chstatus ( <channel name>) all” ,  the correct reply is displayed in the GUI e.g.

..MQSC >     2 : display chstatus (SYSTEM.AUTO.RECEIVER) all
..AMQ8420: Channel Status not found.

But the RUNMQSC process abends. This is a bug in the RUNMQSC command which can be recreated from TACL as follows:

$OSS KARL 12> fup copy mqcmdch
display chstatus (SYSTEM.AUTO.RECEIVER) all
1 RECORDS TRANSFERRED

$OSS KARL 11> run $system.zwmqbin.runmqsc /in mqcmdch, out mqresch/
ABENDED: $Z5G2
CPU time: 0:00:00.010
1: Process terminated with warning diagnostics
$OSS KARL 12>fi mq*ch

$OSS.KARL

              CODE              EOF   LAST MODIFIED  OWNER  RWEP   PExt   SExt
MQCMDCH        101             2110 03DEC2008  9:55 251,255 NGNG     14     14
MQRESCH        101              384 03DEC2008  9:57 251,255 NGNG     14     14

$OSS KARL 13> fup copy mqresch
0791003, 5724-A39 (C) Copyright IBM Corp. 1993, 2007  All Rights Reserved.
Starting MQSC for queue manager venus.queue.manager.

MQSC >     1 : display chstatus (SYSTEM.AUTO.RECEIVER) all
AMQ8420: Channel Status not found.
MQSC >One MQSC command read.
No commands have a syntax error.
One valid MQSC command could not be processed.
9 RECORDS TRANSFERRED

N.B. the beta version of MQAG that uses the MQNSKOPTPATH and MQNSKVARPATH params does not resolve this crash.