The Concept of Registering a Consumer for an Asset
Consumer registration in CentraSite has two major elements: it has an asset, which denotes the asset to be consumed; and it has a consumer asset, which denotes the asset consuming the asset. In the CentraSite Business user interface, an asset that is consumed by another asset is represented by the Consumed Assets attribute, and the consuming asset is represented by the Consumers attribute in the details page of an asset.
CentraSite users with View permissions for assets can provide a consumer from any of the following four categories:
A registered user of CentraSite -
CentraSite users can register themselves as consumers of the specified assets. That is, users access the asset's metadata (that is, view additional profiles) and/or receive notifications when changes occur to an asset that they consume.
A registered group of users -
CentraSite users can register a specific set of users who are represented by a group as consumers of the specified assets.
A consumer who is identified by an asset instance of Application type -
CentraSite users can register Application assets as consumers of the specified assets. The Application assets contain precise characteristics by which Mediator can identify messages from these specified Application assets at run time.
A consumer who is identified by an arbitrary asset instance of the consuming type -
CentraSite users can register arbitrary assets as consumers of the specified assets. These are asset instances whose types are defined to be as the consumers of the specified assets in their type definition.
In general, an asset type definition specifies a default set of consuming types, for example, Users, Groups, and Applications, whose instances are allowed to consume instances of the specified type. An administrator can optionally modify this type definition and remove the default consumption type to disable the consumer registration for all assets of the default type removed from the type definition. For example, an administrator might want to remove the default Application type in the BPEL type definition to disable the Application assets from consuming any asset of the type BPEL.
