Ekinlikler
19 Kas 23 - 21 Kas 23
Ottenere il vantaggio competitivo necessario con potenti soluzioni di intelligenza artificiale e cloud partecipando a Microsoft Ignite online.
Iscriviti subitoCOM+ Queued Components and Partitions
The COM+ queued components service fully supports the concept of partitions. That is, when a queued component within a partition is executed, the message is queued and the component is eventually executed within the component's partition.
Traditionally, the queued components service uses the application name as the queue name. This means that in a non-partitions scenario, where only one instance of an application name exists on a computer, each application name has its own message queue.
In the case of partitions, however, where multiple instances of the same application name can exist on a computer, the queued components service uses the same queue for any queued components that share the same application name.
The same rules for how the partition ID is used to activate a non-queued component applies to a queued component, as follows:
- If a moniker is used to activate the queued component and a partition ID is included, this partition ID is used to locate the partition. This partition ID takes precedence over any partition ID that might exist in the context for the component being activated.
- If no moniker is being used to activate the component, the partition ID that is in the object's context is used.
- If no partition ID exists in the object's context, the default user-to-partition mapping within Active Directory is used.
Not
If a server computer is disconnected from the network and if the user-to-partition set mapping is changed while the server is disconnected, the partition cache might contain outdated user-to-partition set mapping. This could result in an activation error if user-to-partition set mapping is the mechanism used to activate a component.
COM+ events are fully integrated into partitions. This means that a subscriber can subscribe to a publisher whose application resides within a partition. To allow this subscription, the subscriber class collection includes two partition-related properties—an event class partition ID and an event class application ID.