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

This shows the general information about the asset, such as the asset's version, last modified date, asset type, owning organization, owning user, a description of the asset, and the number of watchers and consumers.

This shows the list of users, applications, and arbitrary assets that are registered to consume the asset.

This shows additional information about the asset. The profile functions as a high-level container for a set of profiles defined in the asset's type definition. Beginning with CentraSite 9.8, the Advanced Information profile will not be visible in the user interface.

This shows the asset's instance-level permissions. The profile displays the 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 includes only that particular user's permissions for the asset.

This shows the versioning history for the asset and provides links to earlier versions and revisions of the asset. The profile displays 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.

This shows the list of users that are registered to receive notifications when changes are made to the asset.

This shows the update activity associated with the asset. The profile displays 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.

This shows the list of object-specific properties assigned to the asset. An object-specific property includes a key that identifies the name of the property and an optional String value, that 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 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.

This shows the list of consume identifier tokens for a virtual API.

For a list of the supported consumer identifier tokens, see Run-Time Governance with CentraSite.

This profile shows a list of the available access keys for an API. This profile displays the API key string and its expiration date.

This profile shows the OAuth2 client credentials (Client Id, Client Secret, Client Name, Scope, and Refresh Token) for a virtual API.

This shows the list of external documents such as Functional Requirements, Error Messages, Release Notes and so forth that are attached to the asset.

This shows the list of categories that are used to classify the asset. The profile displays controls for adding ad hoc classifiers to the asset.

This shows the list of objects that are related to the asset. The profile displays controls for establishing "ad hoc" relationships between an asset and other registry objects.

This shows the list of links to external documents and files that are attached to the asset. The profile displays controls for attaching documents and files to an asset.

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

This shows the run-time performance metrics captured for the asset. If you are using webMethods Mediator, webMethods Insight, or another run-time monitoring component to log performance metrics for an asset, CentraSite includes those metrics on this profile.

This shows 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.

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

For a Virtual Service, this shows 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, this shows 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.

The profile displays the request routing methods and protocol for authenticating the requests.

Applicable for Virtual Service, Virtual XML Service and Virtual REST Service types. Shows the list of virtual services that are ready for deploying in the webMethods Mediator gateway.

This shows the run-time performance metrics that are available for the asset. If you are using webMethods Mediator, webMethods Insight, or another run-time monitoring component to log performance metrics for an asset, CentraSite includes those metrics on this profile.

This shows the run-time events that are available 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.

This shows the maturity status, grouping, subscription terms , and the access token types for the API. This profile displays the icon shown in API-Portal to represent the API.

This shows the name of the native API associated to the API key. To view details of the native API, click the hyperlinked name.

Displays the ARIS-specific attributes that are of use when CentraSite is integrated with the ARIS products.