Available only for Service, XML Schema, Application Server, BPEL Process, Interface and Operation asset types. Provides basic information about the asset. For a service asset, this profile includes a list of the operations and bindings that the service provides. For a BPEL Process, Interface, or Operation asset, the profile shows basic information such as the asset owner, but includes no type-specific attributes.

Displays the list of users and applications that are registered to consume the asset. This profile also contains controls for registering an application, a user, or a group as a consumer of the asset.

Displays the list of users who are registered to receive notifications when changes are made to the asset.

Displays the list of categories by which an asset is classified. This profile also contains controls for adding ad hoc classifiers to an asset.

Displays the list of objects to which the asset is related. This profile also contains controls for establishing "ad hoc" relationships between an asset and other objects in the registry.

Displays the asset's instance-level permissions. This profile also contains controls for modifying the asset's instance-level permissions.

To view all of the instance-level permissions for an asset, a user must have Modify or Full permissions on the asset. To edit the instance-level permissions for an asset, a user must have Full permissions on the asset. If a user has only View permission on an asset, the Permissions profile shows only that particular user's permissions for the asset.

Displays the versioning history for an asset and provides links to earlier versions and revisions of the asset. This profile also contains the controls for generating a new version of the asset, purging older versions of the asset and reverting to a previous version of an asset.

Displays the list of links to external documents and files that are attached to the asset. This profile also contains controls for attaching documents and files to an asset.

Displays the list of object-specific properties that have been assigned to an asset. An object-specific property consists of a key, which identifies the name of the property, and an optional String value, which contains the data associated with the property. (A property's value can be null.)

Object-specific properties are used to hold information about an instance of an asset when there is no predefined attribute to hold that data. Typically, they are used in one-off situations to attach ad-hoc data to an instance of an asset. For example, if you were managing a certification effort, you might use an object-specific property to identify the set of assets that required certification.

Displays the update activity associated with an asset. This profile lists each change that has been made to an asset (including changes in an asset's lifecycle state) and identifies the user that made the change.

Available for only Package and IS Package types. Displays the list of objects to which the asset is related. This profile also contains controls for establishing "ad hoc" relationships between an asset and other objects (for example, assets, users or organizations) in the registry.

Displays the run-time performance metrics associated with an asset. If you are using webMethods Mediator, webMethods Insight, or another run-time monitoring component to log performance metrics for an asset, CentraSite displays those metrics on this profile.

Displays the run-time events associated with an asset. If you are using webMethods Mediator, webMethods Insight, or another run-time monitoring component to log run-time events for an asset, CentraSite displays those events on this profile.

Displays the list of design/change-time policies and run-time policies that are applicable to an asset (that is, it displays all the policies whose scope encompasses the displayed asset).

For a Virtual Service, displays the protocol (HTTP, HTTPS or JMS) and SOAP format (1.1 or 1.2) of the requests that the service will accept.

For a Virtual REST Service or Virtual XML Service, displays the protocol (HTTP or HTTPS) of the requests that the service will accept. Also, you specify the HTTP methods (GET, POST, PUT, DELETE or Use Context Variable) that are supported by the native service.

This profile also contains the request routing methods and protocol for authenticating the requests.

Available for Virtual Service, Virtual XML Service and Virtual REST Service types. Displays the list of virtualized services that are ready for deploying in the webMethods Mediator target.