Cross-Enterprise Support


Updated: July 19, 2016

Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista

Message Queuing provides support for applications that must communicate across two Microsoft® Windows® 2000 or Windows Server 2003 enterprises. In this situation, your application must be able to send and retrieve messages without using the directory service.

The following illustrations shows the possible connections between a computer operating in the enterprise A and the other computers operating in environment B.

<No Change>

From an application architecture perspective, your cross-enterprise application must take into account the following limitations:

  • Queues in the other enterprise can be referenced only by using direct format names. For example, when opening a queue you must specify the queue using a direct format name.

  • You cannot make any function or method call that requires access to the directory service on the other enterprise. You can access the directory service only on your own enterprise.

  • When requesting message authentication, you must provide an external certificate. Internal certificates cannot be used.

  • To send encrypted messages, your application must obtain the public key of the receiving computer and encrypt the message itself. (The destination queue manager will still decrypt the message for you.)

  • When you send messages within a transaction, the IP address of the sending computer must remain constant. Message Queuing uses the IP address to return a confirmation notice when the message has been retrieved from the target queue.