Managing CCM Applications

K2 Management Tool is the set of utilities to manage CCM components and servers effectively and efficiently. The management architecture uses the familiar concept of Managed Objects (as used in JMX and other NMS architectures), contains local management services, supports extensible load-balancing algorithms and also allows dynamic reconfiguration of policies by using scripting managed objects.


K2 Management Architecture

The management of the K2 Component Server is based on the Distributed Management Architecture (DUMA) which is shown in Figure . The K2 Management can create a managed object for any instance of a resource and registers it with the Management Agent. The Management Agent provides a unified access interface to any of these managed objects. Additionally the Management Agent is extensible by accepting managed objects that are actually implemented by a Python script and are used to implement intelligence for handling certain runtime or error conditions locally without the interference of a centralised management tool.

K2 Distributed Management Architecture (DUMA)

The user interface to all the management agents of a cluster can be done using HTTP or IIOP. The following property categories are distinguishable:

  • Performance Management

  • Fault Management

  • Configuration Management (Deployment)

  • Security Management

  • Auditing and Accounting Management (Logging Service)

K2 Management Activities

K2 Management Tool can be used to manage distributed component application from a remote access point. It provides integrated management of distributed clusters, consisting of nodes over LAN. It enables uniform access to manage resources existing in different hierarchy within K2. The key management functionality supported by K2 Management:

  •   Monitoring nodes and CCM Server activities

  •   Start/stop CCM Servers that provides runtime environment to components

  •   Start/stop K2 Daemons on host machine

  •   Configuring load balancing algorithm for service types

  •   Managing application components

  •   Subscribing or unsubscribe from notification for events through e-mail/SMS/pager

  •   Automatics performance management

  •   Improving performance and Quality of Service

Managing CCM Applications

1. Management detail levels for CCM components

There are different hierarchy levels that are possible to display. Each of the instances in each level has properties and actions associated with it depending on the type of the instance.

Network Resource Management

Manage uses of components deployed in cluster and associated information such as average transaction time, transactions committed, transactions rolled back, requests served per second, requests coming per seconds.

2. Monitor resource consumption by CCM servers

K2 Management Tool allows monitoring real time resource consumption of CCM Servers. This allows take appropriate decision while loading and unloading of a component on/from a particular CCM process. It helps in performance management and improving quality of service.

Viewing CCM process summary

The Cluster-summary view displays all the nodes of the selected cluster. These include all hosts, operating systems, processor, performance data, and uptime. It also displays all the components available in the cluster and their related data.


CCM application development lifecycle with K2: overview

The figure K2 easy-to-use tools supporting the complete development process for migrating and managing the CCM environment with K2 Component Server. K2 provides ample tool support involved during each different phase of migration, development, and component maintenance lifecycle.


K2 Management Tool

The key features of management tool are:

K2 Management Tools
1. Cluster Manager To create, update and delete cluster over LAN for scalability and enhanced performance
2. Install and Update Manager To install and update package at multiple sites (remote installation), support dynamic update of packages, view and modify package information.
3. QoS Manager For dynamic setting of QoS based parameters including managing load balancing algorithms. It also supports python based scripting for on-site customization of applications
4. Management Console To manage (remote) various details of component server
5. Server Manager To start and shut down CCM Servers that provide runtime environment to components, supports loading and unloading of component dynamically
6. Managed Objects Browser For nodes, devices and CORBA Components
7. Event and Notification Manager To get event notification through email/pager messages
8. Performance Manager To display performance parameters such as CPU usage, Memory usage and Transaction count per node and service wise
9. Log Manager Distributed logger to log general warning and error messages. Facility to filter and archive log messages

Copyright 2008 iCMG. All rights reserved.
Site Index | Contact Us | Legal & Privacy Policy