Page tree
Skip to end of metadata
Go to start of metadata
The full text of this page is only available to our customers.

Please login or sign up. You may also need to provide your support ID if you have not already done so.

Product Name
Message Queuing
Publisher Page
Event-Driven Middleware
TKU 2019-Jul-1
More Information
Publisher Link

Product Description

Microsoft Message Queuing (MSMQ) is a component of the Windows operating system that allows cooperating applications to send and receive messages to each other, even if the intended recipient application is not running or the computer on which the sender or recipient application is running is disconnected from the network. Messages are stored and forwarded by MSMQ until they reach the destination queue. Later, when a recipient application runs, it can retrieve the messages from the queue. MSMQ de-couples sender and recipient applications so they do not need to run at the same time. Message Queuing provides built-in enhanced security, transaction support, and other features.

MSMQ is responsible for reliably delivering messages between applications inside and outside the enterprise. MSMQ ensures reliable delivery by placing messages that fail to reach their intended destination in a queue and then resending them once the destination is reachable. It also supports security and priority based messaging. Dead letter queues can be created for looking at messages which timed out or failed for other reasons.

MSMQ is useful when custom applications need to communicate reliably across potentially unreliable or occasionally connected networks. MSMQ is also useful as a persistent storage mechanism for a list of items. For example, a server-based application could use MSMQ to store queued orders that would be submitted as a batch to an order-processing system at the end of the day.

Known Versions

  • 1.0
  • 2.0
  • 3.0
  • 4.0
  • 5.0
  • 6.0
  • 6.3

Software Pattern Summary

Product ComponentOS TypeVersioningPattern Depth
MSMQWindowsOS, WMI QueryInstance-based

Platforms Supported by the Pattern

Microsoft Message Queuing is a Windows service, so the pattern discovers Microsoft Message Queuing on Windows only.


Software Instance Triggers

PatternTrigger NodeAttributeConditionArgument


Version information for the product is currently collected using the following methods:

  • OS Versioning
  • WMI Query Versioning

Storage locations

The patterns query the following registry keys for the storage location: 

  • For message queue, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\StoreJournalPath
  • For message logger, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\StoreLogPath
  • For transaction logger, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\StoreXactLogPath

OS Versioning

The pattern tries to use an OS version attribute from related Host node as Microsoft Message Queuing version.

WMI Query Versioning

The pattern supports WMI query versioning.

On Windows the CIM_DataFile class in the root\CIMV2 namespace contains properties of the files present on the host. The version of the executable process (if the process list contains absolute paths) can be obtained by running the following WMI query:

  • SELECT Version FROM cim_datafile where name=<process command line>

If the output is retrieved it is assigned to the 'version' attribute of the Software Instance.

Application Model Produced by Software Pattern

Product Architecture

Only one Microsoft Message Queuing can run on a host.

Software Pattern Model

Pattern Trigger

The MSMQ pattern triggers on the mqsvc.exe process (MSMQ service).

SI Depth

The MSMQ pattern creates an instance-based Software Instance, its key being based on si type and host key.

List of queues is retrieved either from the filenames in the lqs subdirectory in the message file location, or from the output of the following WMI query:

  • Select Name FROM Win32_PerfRawData_MSMQ_MSMQQueue

Software Instance Modeling

Software Instance details of Microsoft Message Queuing Service generated with this pattern:

Subject Matter Expertise

Subject Matter Expert input will be welcome on any other potential approaches not discussed to improving product versioning coverage and depth of Microsoft Messaging Queuing.


This pattern was tested against a live instance of the Microsoft Messaging Queuing.

Information Sources

Open Issues

There are no known open issues with this pattern.

15 Oct 2014

The full text of this page is only available to our customers.

Please login or sign up. You may also need to provide your support ID if you have not already done so.