Understanding CCS

CCS is installed quickly and easily as part of your CA product so you do not have to worry about additional installations or difficult deployments. CCS also provides significant resource savings, because only those components that are actually required get installed. The desired components are selected from a menu of items in visualization, management, and infrastructure services. CCS offers great flexibility in the selection of suitable components, as indicated by the following partial list of components in the CCS bundle.

CCS Component	Function
Event Management	Management
Common Enterprise Tools	Infrastructure
WorldView 2D Map Interface	Visualization
WorldView 3D Map Interface	Visualization
WorldView Common Services	Infrastructure
Common Communications	Infrastructure
Report Explorer	Visualization
Agent Technology Common Services	Infrastructure
Management Command Center	Visualization
Agent Technology Distributed State Machine	Management
Event Wireless Management	Management
ManagedPC Components	Management

CCS includes runtime modules and provides a Software Development Kit (SDK) for third parties to integrate the runtimes with your CA product and to facilitate the rapid incorporation of specific CA technologies.

Runtime Component-A set of programs and modules that complements the Software Development Kit and is used to provide runtime functionality. The runtime modules are chargeable.
SDK- A component that provides the APIs and utilities required to develop solutions that integrate with your CA product. The SDK offers the opportunity to integrate custom applications with CA architecture, including WorldView, Agent Technology, and Enterprise Management. The SDK provides an extensive set of APIs that lets you manipulate classes and objects in the Common Object Repository, create agents to instrument custom resources, and much more.
Tip: For more information about the Software Development Kit, see the CA SDK Developer Guide. Each CA solution has the runtime modules it requires embedded in the product.

Any third‑party product that is enhanced with the Software Development Kit can communicate and integrate with any of the CA solutions containing the specific common services (such as Event Management) for which an integration has been performed.

Two typical scenarios when a vendor or third-party can use CCS are as follows:

Integration-Integrate an existing third-party product so that it can communicate with your CA solution.
OEM-Develop a third-party product in which the partner provides added value by embedding CA technology in the product. The embedded technology could be a complete CA solution (such as CA NSM) or a CCS runtime component (such as Event Management).

Note: Not all CCS components are available on every platform. Virus Scan, for example, is available only on Windows.

Tell Technical Publications how we can improve this information