The Catalog
In CentraSite, the term catalog refers collectively to the sub-set of the objects in the registry that are assets. Generally speaking, an asset is an object that represents an artifact in your SOA environment, such as a Web service, an XML schema, or a BPEL process.
When initially installed, the CentraSite catalog supports the following types of assets:
Services
Virtual Services
REST Services
Virtual REST Services
OData Services
Virtual OData Services
XML Schemas
BPEL Processes
Application
Application Servers
It also includes support for the types of assets that are published and consumed by products in the webMethods product suite (for example, assets such as CAF Task Types, TN Document Types, and so forth).
However, CentraSite's catalog is completely extensible and can be configured to hold any type of artifact that your organization cares to model. For example, you might want to customize your catalog to include metadata for artifacts such as Java libraries, portlets, and XSLT documents.
Any custom object type that you add to CentraSite is, by default, treated as an asset that is part of the catalog. For information about configuring CentraSite to store metadata for custom asset types, see the CentraSite Administrator’s Guide.
Note: | The terms object and asset have very specific meanings within CentraSite. An object is any data object that CentraSite maintains in its registry. An asset is an object that is treated as a member of the catalog as described above. Therefore, all assets are objects, but not all objects are assets. |
