Grouping Applications into Partitions

When deciding how to group applications into partitions, administrators need to be aware of certain rules and restrictions, including the following:

• An application can be installed into one or more partitions.
• Only one instance of a given component can exist in an application.

Public and Private Components

Other restrictions exist when deciding how to group COM+ applications. These restrictions pertain to public versus private components within an application. Application components can generally be either public or private. However, when grouping applications into partitions, administrators should be aware of some restrictions around public and private components. The following table lists these restrictions.

If an application is:	Then components in a partition can be:
A server application	Public and private.
A library application	Public only. Otherwise, the callers application could have the same components, which would create ambiguity.
In the global partition	Public only. This ensures backward compatibility.

Application IDs

Every COM+ application installed on a computer has a unique application ID. However, application names need only be unique within a single partition and not on the entire computer.

The following table shows what happens to the application ID when an application is imported into a partition or exported from a partition.

If an application is:	Then the application ID:
Imported to the global partition	Remains the same
Imported to a partition other than the global partition	Is changed
Exported	Is included in the exported file

Related topics

Collecting Partition Metrics

Configuring the Partition Cache

Managing Local Partitions

Managing Partitions Within Active Directory

Setting Administrative Rights for a Partition