This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for

MSMQ defines and implements an XML-based SOAP extension. The SOAP Reliable Messaging Protocol (SRMP) enables message exchange and provides support for several qualities of services and kinds of message notifications. SRMP supports the following functionality:

  • Express messages

  • End-to-end reliable messages

  • End-to-end authentication

  • Notifications of message delivery

From a programming point of view, every message sent through HTTP is formatted as a SOAP-based message. For example commands to enable protocols, see Using the MSMQAdm Utility.

New properties, specific to SOAP, are available to developers for controlling SOAP formatting at a fine level. For instance, it is possible for a message sender to insert non-MSMQ headers into the SOAP envelope and have them retrieved and processed by the message receiver.

SRMP and the Web Server

SRMP accepts incoming requests through HTTP using the Web server on the device. The ISAPI extension called SrmpIsapi.dll handles the initial request and passes the request to MSMQ.

Accepting SRMP requests requires a web server.

If SRMP is included in the OS design, by default the Web server is configured to map all requests to the virtual root /MSMQ to SrmpIsapi.dll.

The following registry value activates this setting:

Copy Code

For more information about this setting, see Setting Virtual Paths.

See Also