Editing Microsoft Message Queuing (section)

==Overview==

MSMQ is a messaging protocol that allows applications running on separate servers/processes to communicate in a failsafe manner. A queue is a temporary storage location from which messages can be sent and received reliably, as and when conditions permit. This enables communication across networks and between computers, running Windows, which may not always be connected. By contrast, [[Internet socket|sockets]] and other network protocols assume that direct connections always exist.

MSMQ has been available to developers on Microsoft platforms since 1997,<ref>[http://www.informationweek.com/673/73iudn2.htm InformationWeek News Connects The Business Technology Community]. Informationweek.com (2014-02-04). Retrieved on 2014-02-22.  {{webarchive |url=https://web.archive.org/web/20080410201921/http://www.informationweek.com/673/73iudn2.htm |date=April 10, 2008 }}</ref> and has commonly been used in enterprise software built with [[Visual Studio]], both in the native pre-[[Microsoft .NET|.NET]] incarnation (version 5 and 6), and in [[Visual Studio .NET]]. Microsoft also has incorporated MSMQ in its messaging technology framework, [[Windows Communication Foundation]] (WCF). Under WCF, MSMQ can be used for providing secure, reliable transport with a unified programming model compatible with other communications standards.

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 queue]]s can be created for looking at messages which timed out or failed for other reasons.

MSMQ supports both durable and non-durable messaging to make a trade off between performance or consistency by writing messages to disk or only in RAM. Non-durable messaging can only be achieved by sending express messages via non-transactional queues.

MSMQ also supports transactions. It permits multiple operations on multiple queues, with all of the operations wrapped in a single transaction, thus ensuring that either all or none of the operations will take effect. Microsoft [[Distributed Transaction Coordinator]] (MSDTC) supports transactional access to MSMQ and other resources to achieve transactional exact once processing.

The following ports are used for Microsoft Message Queuing operations:
* TCP: 1801
* RPC: 135, 2101*, 2103*, 2105*
* UDP: 3527, 1801
* * These port numbers may be incremented by 11 if the initial choice of RPC port is being used when Message Queuing initializes. Port 135 is queried to discover the 2xxx ports.<ref>[http://support.microsoft.com/kb/178517 TCP ports, UDP ports, and RPC ports that are used by Message Queuing]. Support.microsoft.com (2011-09-28). Retrieved on 2014-02-22.</ref>