The goal of CSF is to achieve rapid integration – with the minimum amount of custom coding – between Web services, and to reduce (or eliminate) dependencies between Web services.
Connected Services Framework provides a platform for developing, aggregating and using Web services by abstracting collaboration essentials, such as identity, service discovery, and profile management. It also provides collaboration context management, which is based on intelligent routing criteria.
A typical Web service aggregation uses the CSF collaboration context – the Session – to route messages (based on routing logic that can be altered at run time) to the participants (participating Web services) in order to facilitate a business scenario.
The interaction between the Web services and CSF is similar to that of computers connected to a hub in a star schema. In CSF, the Session is the hub and the Web services (the participants) are the computers.
The Session component is an intermediary Web service that provides service isolation, logical message routing, seamless identity mapping, seamless security scheme usage, and message interception services to composite Web service applications. It acts as the abstraction layer of each service rather than an abstraction of a platform service. Ideally, all the Web services in a composite application send messages to each other through the Session component so that each Web service need only work directly with the Connected Services Framework. The isolation that the Session component provides
by being the “middleman” allows each Web service to become independent of the other services. Using the CSF Session component for all message traffic in a composite Web service application increases
the modularity of the application components and decreases their “coupling.”
The CSF Session component acts as a router or communications agent between all the Web service participants, as shown in the preceding illustration. It routes messages between all the participants based on the routing criteria specified in the manifest file or a custom route provided at run time. Each Web service sends messages to the Session (the runtime collaboration context), which then
forwards the messages to the appropriate participant Web services.
CSF Session component provides interception capability so that message structures can be transformed at run time and it provides logical routing capability, which allows the same message to one (or more than one or no) Web service conditionally
“Identity Management is the process and technology used to manage digital identities as well as
the policies that govern how the identities can be used to access IT resources”
Within Connected Services Framework, the Profile Manager component is a Web Services Enhancements (WSE) 2.0 Web service that provides:
- WSE interface to Active Directory
- BizTalk orchestration for propagating attributes across VAS systems
- User-Service Mapping table
The Service Catalog component is a Universal Description, Discovery, and Integration (UDDI) database that contains a list of all the services available within the CSF environment.
The Service Catalog may also contain information about the required policy for using the service. No commercial definitions should be stored within this catalog. The CSF Service Catalog is a technical catalog only.
[from CSF documentation]
more on [lavbox Connected Services Framework]