Service Discovery with Connected Services Framework
The service catalog should be discoverable through all the common discovery mechanisms, such as UDDI, WS-Discovery, WS-Inspection, DISCO, and so forth. A Really Simple Syndication (RSS) feed can also be provided for convenience.
Service Catalog also provides authorization capability. This ensures the ability to read and access services within Service Catalog can be secured. For example, an operator can enable access to core network services for its internal developers but can disable access for all external developers. Another example is when the operator wants to distinguish different levels of developers based on the amount they pay to access the platform (such as Developer Gold, Developer Platinum or Developer Iron).
The CSF Service Catalog component provides a WSE interface to UDDI 2.0.
UDDI is important to SOA solutions because it stores service description information in a central location and it allows information to be retrieved in a standard way.
The Service Catalog component is primarily used for providing Uniform Resource Identifiers (URIs) given service universally unique identifiers (UUIDs). In other words, the physical URI of a specific service should always be stored in the Service Catalog, and it should be read from the Service Catalog component before calling the service. In this way, if the service URI must be changed, it has to be changed only in a single location.
The Service Catalog component consists of one endpoint, ServiceCatalog. The ServiceCatalogClient can be used to send requests to the Service Catalog endpoint.