MSMQ Glossary: S
Security information that can be cached in a structure on the source computer and used by Message Queuing to attach a certificate to a message or to impersonate a user.
A security context structure is used primarily when a large number of authenticated messages are sent using the same certificate. When sending a large number of authenticated messages, the sending application can request Message Queuing to cache the certificate, the corresponding private key, the user's SID, and other security information in a security context structure, which is then used by the Message Queuing runtime to attach the same certificate to each message.
The security context information is stored locally and is not sent with the message.
The SECURITY_DESCRIPTOR structure and associated security information for a securable object, for example, a queue.
Security information can include the security identifiers (SIDs) of the owner and primary group, a discretionary access control list (DACL), and a system access control list (SACL).
For a complete description of security descriptors, see the Platform SDK.
security identifier (SID)
A unique value of variable length used to identify a user, a group of users, or a logon session. The SID is assigned when the user logs on and becomes part of the access token for any process started by the user.
An access mode that allows messages to be sent to the queue. Used when the sending application opens a queue to send messages.
The access mode of a queue is set when the queue is opened and cannot be changed while the queue is open.
A queue setting that specifies who can use the queue when it is opened with peek or receive access (share mode does not apply to queues opened with send access). The queue can be restricted to exclusive access or completely unrestricted access.
The share mode of a queue is set when the queue is opened.
See security identifier.
The SID contains a 48-bit identifier authority value, a revision level, and any number of subauthority values. For a complete description of SIDs, see the Platform SDK.
A single-message transaction is an implicitly invoked Message Queuing internal transaction that includes a single operation performed on a single message. A single-message transaction can be used to request guaranteed exactly-once delivery (EOD) of a single message sent to a transactional queue.
A threading model in which apartments consist of exactly one thread. As a result, all COM objects in a single-threaded apartment (STA) receive method calls only through the thread in which they were created. All method calls to a COM object in a single-threaded apartment are processed synchronously.
The ability to track messages that were sent. Applications can request positive source journaling (the message was successfully sent from the computer), negative source journaling (the message could not be delivered), or both.
When source journaling is requested, returned messages are sent to the computer journal queue (for positive source journaling) or one of two dead-letter queues (negative source journaling).
XML or non-XML (binary) documents attached to an SRMP message. An SRMP message can contain any number of SOAP attachments.
See also SRMP.
The top element of the XML document that represents an SRMP message. The SOAP envelope includes a SOAP header and a SOAP body. The SOAP header contains all of the message properties encoded in SOAP and SRMP elements, and may contain additional XML-formatted information inserted by the sending application. The SOAP body does not contain any Message Queuing-generated information, but may contain other XML-formatted information inserted by the sending application.
See also SRMP.
The SOAP Reliable Messaging Protocol, a published specification defining an open general-purpose extension of WS-Routing that adds reliability to the Web Services Routing Protocol (WS-Routing) and to SOAP. Message Queuing uses this protocol to format the packets in messages sent over HTTP/HTTPS or to a multicast address.
See also HTTP message and multicast address.
A Message Queuing server that performs all standard Message Queuing functions for a dependent client. These functions include creating queues, sending messages, storing messages in queues, and receiving messages.
See also dependent client.
A keyword indicating that the queue is a computer system queue. These queues include the computer's computer journal queue, nontransactional dead-letter queue, and transactional dead-letter queue.
The SYSTEM$ keyword is only used in direct format names.
See also computer system queue.
A queues created by Message Queuing or indirectly by the Message Queuing administrator. System queues include queue journals, dead-letter queues, and report queues.