COM+ Partitioning
Under Windows XP, COM+ 1.5 introduces support for COM+ partitions, including multiple versions of COM+ applications to be installed and configured on the same computer. This characteristic can save you the cost and time-consuming energy of using numerous servers to handle several versions of an application. Consequently, on a single computer each partition has the functionality of a virtual server.
When you install an application into each partition, you will be generating partition sets which, map users to the logical servers. Developers can use COM+ to programmatically generate and configure COM+ partitions. Each generation and configuration task which a developer should do using the Component Services or Active Directory Users and Computers administrative tools should also be done by using COM+ collections, objects, and interfaces or through the Active Directory System Interface (ADSI).
Application Partitioning and Aliasing Components
In an enterprise class environment COM+1.5 provides you and enhanced handling,
administrating and purification of an application using application-partitioning
service. Each application partition service is built from a set of COM+ 1.5
applications. Partitions support an effective method by offering to every client
to use a group of applications and components that are already exist in client’s
computer.
Before the XP and COM+1.5, a component used to belong only to one COM+ application
on a given computer. The problem with that was, when you needed to install the
same component including the same CLSID in multiple applications you needed
multiple computers. With partitions future you are able to install a component
to various applications by using different partitions. That means, a single
computer can include several partitions. Therefore, every partition can handle
its own set of applications and components.
Again, it was not possible to apply more than one set of configuration to the same component more than once before COM+1.5. The new version has futures that allow you to use a new alias to an existing configured component and therefore you can use a new CLSID with this alias. As a result you will be able to apply a set of configuration to your old component like a new component. Aliasing a component is very important future that XP and Com+1.5 bring us. Therefore, you can design and develop a piece of your enterprise application and then, if you need you can also assign various sets of configuration parameters by using aliasing method to it. Moreover, with this method client can decide which configuration setting and component or application will be instantiated by generating a part of CLSID. Once you use alias method to a component the original and the clone are considered different components by the COM+ services and you can configure them differently. COM+ services consider the original and the duplicate one as different components when we use alias method to the component and after all we can configure them differently. Please note, this is very important: Partitions are generally configured in active directory therefore, you should assign each client to partitions in active directory.
Comments