Export (0) Print
Expand All

CCF Server Components

Internet Security and Acceleration Server 2000

The CCF server components provide the back-end functionality. These include the CCF Core Services, Distributed Connectivity Services (DCS), Configuration Server, and the CCF databases.


The CCF Core Services perform logging and reporting, configuration, session management, ESSO credential storing, and other functions. The services support horizontal scale-out, as well as clustered and load-balanced deployment. CCF Core Services include the following:

  • Agent activity logging – Logging produces a record of an agent’s transactions, and can be aggregated to produce custom reports.
  • Enterprise Single Sign-On (ESSO) – CCF Core Services uses ESSO and the Windows Active Directory® service to integrate authentication and authorization for agent roles and applications. ESSO allows you to map a Windows user ID to non-Windows user credentials.
  • Sessions management – CCF Core Services can start an application automatically (for example, to support a workflow). In addition, if a step in a workflow process needs to be continued by another agent or at a later time, the core services can save the session context—including the state of the supporting applications and information—and transfer it automatically to the agent, restore it, or transfer it to another communication channel.
  • Application configuration storage – All configuration information is stored on a core server. If an agent’s workstation fails, the agent’s applications and operating state can be restored when the agent logs back on from another workstation.

For more information about CCF Core Services, see the CCF 2009 SP1 Deployment Guide.


Distributed Connectivity Services (DCS) is an application infrastructure that provides an end-to-end development model and reference architecture. DCS provides service management capabilities such as transparent service location, dynamic client, context-driven business process selection, scalable hosting of workflows and service configuration, and a standards-based security token service. DCS is built on Microsoft .NET 3.0, Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF). DCS is a collection of reusable application blocks packaged in a software factory.

DCS includes the following components:

  • Discovery Service Application Block – Allows client applications to discover at run time the service endpoints based on service type. DCS utilizes a Microsoft SQL Server® based repository store and a WCF–based service discovery method (WS-Discovery).
  • Central Policy Store Application Block – This block provides centralized configuration of service policies. Policies are consumed by the client application through metadata exchange.
  • DCS Application Server – The DCS application server is hosted inside Microsoft Internet Information Server (IIS).It has two primary components:
    • A task factory that supports DCS business logic selection based on context.
    • The Workflow Host Application Block, which executes Windows Workflow-based business Logic.
  • Security Token Service Application Block – This block implements the WS-Trust based authority service that issues SAML based tokens.

DCS uses the following patterns:

  • DCS Dynamic Messaging Patterns – DCS provides unique messaging patterns so that distributed services in an enterprise can communicate with each other. These patterns include messaging that allows client applications to discover the service location, and communication policies at run time, transportation of context data, authentication, and authorization. DCS Messaging Patterns use WCF and WS standards to provide interoperability and extensibility.
  • Dynamic Service Policy Patterns – DCS supports central storage and management of service policies. When the DCS based service starts, it contacts the central policy service, retrieves the relevant policies and configures its WSDL and receive pipeline according to the policies.

The CCF Configuration Server allows you to create .NET configuration files dynamically. To do this, the configuration server uses hierarchical sets of assertions about an application’s context. For example, assertions could be related to user roles, business environments, or geographical locations. CCF provides the ConfigurationUpdater client API that allows interaction with the Configuration Server.

For more information about the Configuration Server, see the CCF 2009 SP1 Deployment Guide.


Show:
© 2015 Microsoft