Share via

Internet deployment considerations

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Internet deployment considerations

Message Queuing 3.0 has increased support for Internet messaging and includes the following features:

  • HTTP as an optional transport protocol

  • An XML-based SOAP extension that defines a reliable end-to-end messaging protocol

  • Support for load-balancing, Web farms, and firewalls

If your network will be sending or receiving messages through the Internet, consider the following:

  • Network load balancing. For increased scalability and availability, Message Queuing integrates with common network load-balancing mechanisms, namely, Network Load Balancing (NLB), NAT, and DNS round-robin. For more information, see Message Queuing in Network Load Balancing clusters.

  • Messaging through perimeter networks. Most organizations connect to the Internet using a proxy server and a perimeter network protected by firewalls. Incoming messages pass through the firewall, and outgoing messages are sent through a proxy server. The proxy server is a mediator between the organization's intranet and the Internet world. It provides caching and decoupling. Message Queuing uses an HTTP proxy to connect to Web addresses for delivering HTTP messages. Message Queuing thus needs to know the name of the proxy server and the applicable port to which it will connect. At the same time, there may be a list of target names for which the proxy connection is bypassed; that is, Web addresses that do not need to be accessed through the proxy server. An attempt is made to establish a direct connection with such targets. All of the information regarding proxy servers is stored in registry keys. For more information, see Configuring firewalls for Message Queuing and Configuring Message Queuing with a proxy server.

  • Deploying Message Queuing in hardened MSMQ mode. This new feature enhances the security of Message Queuing computers running on the Internet. Hardened MSMQ mode is intended to support scenarios that employ only HTTP (SRMP) messages. For more information, see Message Queuing in hardened MSMQ mode.

For information on Internet messaging, see Internet Messaging.