The Connected Services Framework Components

Connected Services Framework
The Connected Services Framework Components

Developing reliable, secure, scalable, and SOA-compliant composite Web services applications is rapidly becoming a business requirement for many companies. The vision behind the Connected Services Framework is to meet these needs with a flexible architecture that enables composite Web service applications to be developed rapidly, and to be changed quickly.

Companies with large numbers of value-added services (VAS) systems will greatly benefit from the Connected Services Framework, since they will only need to integrate their services with the Connected Services Framework.

The goal of the Connected Services Framework is to achieve rapid integration between Web services with the minimum amount of custom coding, and to reduce (or eliminate) inter-Web service dependencies. By reducing the "coupling" between Web services, applications composed of Web services can be quickly developed, deployed, and revised. Removing the dependencies between Web services is a key Service-Oriented Architecture (SOA) concept. By using the Connected Services Framework, applications can realize the full potential of Web services.

Using the Connected Services Framework Components

The Connected Services Framework components are WSE Web services that can be used as participants by the Connected Services Framework Session component, depending on the business scenario.

Why Should All Web Service Calls Go Through the Connected Services Framework Session Component?

The Connected Services Framework Session component:

  • Seamlessly handles the different identities used by Web services
  • Seamlessly handles different security schemes (UsernameToken, Kerberos certificates) used by Web services
  • Provides interception capability so that message structures can be transformed at runtime
  • Provides logical routing capability, allowing the same message to one (or more than one, or no) Web services conditionally

The Session component should greatly reduce the cost of adding, integrating, deploying, and upgrading the Web services used in an application.  

KEY CONCEPT: In order to achieve service isolation, and therefore reinforce modularity of application components, ALL calls between applications and services should be routed through the Connected Services Framework Session component. The other Connected Services Framework components—Service Catalog, Identity Manager, and Profile Manager—can be called directly by an application.

Standard Business Event Applications

A Standard Business Event (SBE) application is an application that sits between the Connected Services Framework and business applications. This type of interface application is common in many large-scale enterprise applications. Large companies that have many business applications may benefit from using SBE applications as an interface to the Connected Services Framework. This approach may increase flexibility and reuse. It also may be a practical way of integrating legacy business applications with the Connected Services Framework's components which are WSE Web services.

The Connected Services Framework Component Web Services

Each of the Connected Services Framework components is a .NET assembly—that is, a .dll file that is configured to run as one or more .ashx Web services. Some of the Connected Services Framework Components expose multiple Web services. Methods that are logically related are grouped together as a distinct Web service. Within a component, some Web services will require different permissions than other Web services belonging to the same component, which gives the more granular security settings. For example, the Session component requires different permissions to use the SessionManager and the Session Web services.

The diagram below shows the 14 Web services for the Connected Services Framework components: