Part #2 Structure
Part #3 Code
MessageQueuing (3)MessageTypes:
Normal
Which is either a typical message sent from an application to a queue, or a response message returned to the sending application.
Acknowledgement
Which Message Queuing generates whenever the sending application requests one. For example, Message Queuing can generate positive or negative messages to indicate that the original message arrived or was read. Message Queuing returns the appropriate acknowledgment message to the administration queue specified by the sending application.
Report
Which Message Queuing generates whenever a report queue is defined at the source Queue Manager. When tracing is enabled, Message Queuing sends a report message to the Message Queuing report queue each time the original message enters or leaves a Message Queuing server.
MessageQueuing (4)QueueTypes:
Outgoing
Used to temporarily store messages before they are sent to its destination.
Public
Published in the Active Directory. Applications on different servers throughout the network can find and use public queues via Active Directory.
Private
These queues are local to a server and are not available to other machines (thus, these queues are not published in Active Directory).
System
Contains journal messages (sent from the system), dead messages, and transactional dead-letter messages. Dead messages are undeliverable.
MessageQueuing (18)Features:
Subqueues
New in Message Queuing 4.0, subqueues are implicitly created local queues that are logical partitions of a physical queue. Applications can use subqueues to group messages. The subqueues feature enables you to logically group messages in a queue without creating another physical queue.
Move messages
New in Message Queuing 4.0, move message functionality allows you to move messages. You can move messages between subqueues of the same main queue, or from a main queue to its subqueue. You cannot move messages from a main queue to a subqueue of a different main queue or between two main queues or between two subqueues of different main queues. The message is moved as is, from the source queue to the target queue. The properties of the message remain unchanged, except for the current move count.
Transactional remote receive
New in Message Queuing 4.0, transactional remote receive is a transactional receive of a message from a remote queue. Transactional remote receive capability may simplify or enable certain message processing scenarios. For example, when work orders from a remote central queue need to be processed across a farm of application servers, a transactional remote receive will enable the message processing to be load-balanced across the server farm.
Delivering messages over HTTP transport
SRMP (SOAP Reliable Messaging Protocol), an XML-based messaging protocol, can be used for delivering high Quality of Service (QoS) messages. The direct, public, and private format names of administration and response queues can be included in messages sent over HTTP transport. Similarly, the names of administration and response queues in HTTP format can be included in messages sent over ordinary (non-HTTP) transport.
SRMP (SOAP Reliable Messaging Protocol), an XML-based messaging protocol, can be used for delivering high Quality of Service (QoS) messages. The direct, public, and private format names of administration and response queues can be included in messages sent over HTTP transport. Similarly, the names of administration and response queues in HTTP format can be included in messages sent over ordinary (non-HTTP) transport.
Triggers
Triggers provides a mechanism that associates the arrival of each incoming message at a queue with a response that depends on the contents of the message and may invoke either a COM component or a stand-alone executable program. Business rules can be defined and invoked in response to such messages without any additional programming.
Triggers provides a mechanism that associates the arrival of each incoming message at a queue with a response that depends on the contents of the message and may invoke either a COM component or a stand-alone executable program. Business rules can be defined and invoked in response to such messages without any additional programming.
Sending messages to multiple destinations
MSMQ clients are able to send the same message to multiple recipient queues. Lists of destination queues can be specified explicitly by means of distribution group objects (distribution lists) in Active Directory Domain Services as well as in the form of multiple-element format names. Support for ensuring that messages sent to distribution lists and multiple-element format names will reach queues on downlevel computers is provided. In addition, message delivery to IP multicast destinations using the PGM protocol is supported.
MSMQ clients are able to send the same message to multiple recipient queues. Lists of destination queues can be specified explicitly by means of distribution group objects (distribution lists) in Active Directory Domain Services as well as in the form of multiple-element format names. Support for ensuring that messages sent to distribution lists and multiple-element format names will reach queues on downlevel computers is provided. In addition, message delivery to IP multicast destinations using the PGM protocol is supported.
Message lookup
Message Queuing 4.0 provides a way to peek at or retrieve a specific message without using cursors to navigate through the queue until the message sought is located. This functionality is based on a 64-bit lookup identifier that is assigned to each message when it is placed in a destination queue.
Message Queuing 4.0 provides a way to peek at or retrieve a specific message without using cursors to navigate through the queue until the message sought is located. This functionality is based on a 64-bit lookup identifier that is assigned to each message when it is placed in a destination queue.
Directory Service Integration
Message Queuing 4.0 provides functionality to integrate with Active Directory Domain Services to store all configuration, security, and status information. Message Queuing clients use the Lightweight Directory Access Protocol (LDAP) to access domain controllers and global catalog servers for Message Queuing-specific information in Active Directory Domain Services directly without assistance from a Message Queuing server on a domain controller.
Message Queuing 4.0 provides functionality to integrate with Active Directory Domain Services to store all configuration, security, and status information. Message Queuing clients use the Lightweight Directory Access Protocol (LDAP) to access domain controllers and global catalog servers for Message Queuing-specific information in Active Directory Domain Services directly without assistance from a Message Queuing server on a domain controller.
Workgroup support
Message Queuing can be installed in workgroup mode on computers belonging to a Windows Vista®, Windows Server® 2008 or Windows Server 2003 workgroup, rather than to a domain. In addition, a computer on which Message Queuing is installed in a workgroup can later join a domain, and then separate from the domain.
Message Queuing can be installed in workgroup mode on computers belonging to a Windows Vista®, Windows Server® 2008 or Windows Server 2003 workgroup, rather than to a domain. In addition, a computer on which Message Queuing is installed in a workgroup can later join a domain, and then separate from the domain.
Active/active cluster support
Message Queuing 4.0 fully supports the active/active paradigm in a server cluster, which means that Message Queuing can run on all nodes in a server cluster simultaneously. Message Queuing triggers are also integrated with active/active cluster support.
Message Queuing 4.0 fully supports the active/active paradigm in a server cluster, which means that Message Queuing can run on all nodes in a server cluster simultaneously. Message Queuing triggers are also integrated with active/active cluster support.
Windows CE support
A special version of a Message Queuing client is preinstalled on handheld and palm-sized computers running the Windows CE 3.0 (or later) operating system. Windows CE supports the Message Queuing SRMP protocol, for HTTP messaging.
A special version of a Message Queuing client is preinstalled on handheld and palm-sized computers running the Windows CE 3.0 (or later) operating system. Windows CE supports the Message Queuing SRMP protocol, for HTTP messaging.
Message backup and restore
Message storage files, log files, transaction log files, and registry settings can be backed up and restored in case of computer failure.
Message storage files, log files, transaction log files, and registry settings can be backed up and restored in case of computer failure.
Message prioritization
Message prioritization allows urgent or important messages to be sent before less important messages, so you can guarantee adequate response time for critical applications at the expense of less important applications.
Message prioritization allows urgent or important messages to be sent before less important messages, so you can guarantee adequate response time for critical applications at the expense of less important applications.
Guaranteed message delivery
Messages can be stored on a disk-based queue, and then later forwarded to provide guaranteed delivery.
Messages can be stored on a disk-based queue, and then later forwarded to provide guaranteed delivery.
Sending messages within transactions
Using transactional capabilities, you can couple several related actions in a single transaction, ensure messages are delivered in order, ensure messages are delivered only once, and confirm that messages were successfully retrieved from the destination queue.
Using transactional capabilities, you can couple several related actions in a single transaction, ensure messages are delivered in order, ensure messages are delivered only once, and confirm that messages were successfully retrieved from the destination queue.
Dynamic queue creation
You can create queues or change queue properties on the fly without affecting messaging applications.
You can create queues or change queue properties on the fly without affecting messaging applications.
Message routing
Message Queuing provides message routing based on the physical topology of the network, session concentration needs, and transport connectivity. Session concentration facilitates the efficient usage of slow communication links.
Message Queuing provides message routing based on the physical topology of the network, session concentration needs, and transport connectivity. Session concentration facilitates the efficient usage of slow communication links.
Cross-platform integration
Message Queuing can be used across a wide variety of hardware platforms using connectivity products provided by other vendors.
The content of this series was found merged and customised from the following sites:
http://support.microsoft.com/kb/178517
http://support.microsoft.com/kb/815811
http://technet.microsoft.com/en-us/library/cc730994
http://www.primaryobjects.com/CMS/Article77.aspx
http://en.wikipedia.org/wiki/Microsoft_Message_Queuing
http://www.c-sharpcorner.com/UploadFile/rajkpt/101262007012217AM/1.aspx
http://www.techrepublic.com/article/using-message-queue-services-in-net/6136686
http://technet.microsoft.com/en-us/library/154e24ed-e149-4a2b-85cc-0dbae721cf48
http://msdn.microsoft.com/en-us/library/system.messaging.message.messagetype.aspx
Message Queuing can be used across a wide variety of hardware platforms using connectivity products provided by other vendors.
The content of this series was found merged and customised from the following sites:
http://support.microsoft.com/kb/178517
http://support.microsoft.com/kb/815811
http://technet.microsoft.com/en-us/library/cc730994
http://www.primaryobjects.com/CMS/Article77.aspx
http://en.wikipedia.org/wiki/Microsoft_Message_Queuing
http://www.c-sharpcorner.com/UploadFile/rajkpt/101262007012217AM/1.aspx
http://www.techrepublic.com/article/using-message-queue-services-in-net/6136686
http://technet.microsoft.com/en-us/library/154e24ed-e149-4a2b-85cc-0dbae721cf48
http://msdn.microsoft.com/en-us/library/system.messaging.message.messagetype.aspx
No comments:
Post a Comment