| Distributed Application Management |
|
| Continuous monitoring of all application components so that any critical failure can be highlighted immediately |
|
| Model based management so that the reason for application failure can be easily detected |
|
| Automatic fault recovery so that application problems can be corrected even when an operator is not present |
|
| Application level performance monitoring so that performance bottle-necks can be easily found and rectified |
|
| Object Level Management | |
| Full support for objects and their containers so that users can be modeled and managed correctly |
|
| Objects support all relationships so that users can define scalable and fault tolerant solutions at the object level |
|
| Supports internal management of specific object types for the centralization of management functionality |
|
| Visually analyze management data |
|
| CORBA Management | |
| Object-level browser for easy drag & drop management of CORBA objects |
|
| Supports naming service to allow objects to be located easily |
|
| Supports interface repository to allow automatically started object to still be manageable |
|
| Supports management interface to allow developers to specify management needs for individual objects |
|
| Supports performance metrics for the collection and graphing of important performance information |
|
| EJB Management | |
| Supports EJB containers and all bean types for complete management of the EJB environment |
|
| Supports EJB start and stop for active management and load balancing support |
|
| Supports predefined statistics for easy performance tuning |
|
| Wizards and auto-discovery for easy application model construction |
|
| Application Server Management | |
| Supports EJB Containers, Web Servers and all other services for complete management support |
|
| Supports start and stop for active management and load balancing support |
|
| Supports Wizard for easy application model construction |
|
| Entera Management for the easy management of Entera DCE-RPC based servers | |
| Supports creation of DAP files for easy process configuration and startup |
|
| Supports user defined ping to allow users to customize Entera servers to provide accurate monitoring information |
|
| Process Management for the easy management of any process on the system | |
| NT Service Management for the easy management of any NT Service |
|
| Define process environment for full control over process start and stop operations |
|
| Modeling for the ability to manage distributed applications | |
| Uses Rules-based modeling techniques to allow changes in policy to be made |
|
| Uses Desired state modeling techniques to ensure accurate depiction of the current state of an application |
|
| Centralized model repository for easy access by all operators |
|
| Status propagation hierarchy to show the true status of the application |
|
| Object relationship modeling for the ability to accurately define distributed applications | |
| Group relationships for ability to define and manage scalable applications |
|
| Dependency relationships so that operators can understand fault relationships |
|
| Separate start/stop/fail dependencies so that AppCenter can start and stop application components in the correct sequence |
|
| Fault Tolerant relationships for ability to automatically start defined backup services without operator intervention |
|
| Containment relationships for correct handling of contained objects, such as Corba objects and EJBs |
|
| Host relationships for the correct modeling of deployment information and to allow active management |
|
| Inter-application relationships for the ability to model components that are associated with more than one application |
|
| Timer-based relationships to allow applications to scale up to meet peak demands at specific times of the day or week |
|
| Generic properties on objects allow users to reduce management overhead | |
| Property Inheritance for the ease of configuring severs in a model |
|
| Scalability relationships to allow AppCenter to always have the correct number of objects running |
|
| Define environment variables to ease configuration of processes and servers |
|
| Define log files to ease the debugging of failed objects |
|
| Supports user defined states to aid in the correct visualization of the current state of any object |
|
| Event / Action Mechanism | |
| Wizards for easy application model construction |
|
| Hierarchical filter mechanism for the easy and accurate filtering of incoming events |
|
| Execute any command as action to allow users to tailor the required action as needed (for example, send email or page someone) |
|
| Execute action on any host to allow events to trigger specific management responses to solve the problem |
|
| Define actions at configuration level to allow for the creation of actions that occur for any object in the configuration |
|
| Active Management | |
| Supports Before and After commands to allow users to correctly startup objects and cleanup if they fail |
|
| Supports Start operation to allow users to easily start an entire distributed application with one click |
|
| Supports Stop operation to allow users to stop an entire application or parts of it, quickly and easily |
|
| Supports Ping operation for the correct monitoring of each component in the application |
|
| Create INI files to ensure the correct configuration of components before startup |
|
| Agent level restart to provide basic fail-safe mechanism for failed objects |
|
| Manual ping to provide operator check of current objects status |
|
| Supports startup latency to ensure that an object is fully operational before being used by other components |
|
| Intelligent agents to ensure a robust and reliable architecture that limits the use of network bandwidth for management traffic |
|
| Application Mobility | |
| Virtual Hosts to allow applications to be moved from one AppCenter domain to another easily |
|
| Templates to allow components of an application to be reconfigured quickly |
|
| Multi-level property inheritance to allow new objects with similar characteristics to be created quickly |
|
| Performance Monitoring to provide important performance related data about the running of a distributed application | |
| System metrics for out-of-the-box monitoring |
|
| User defined metrics to allow users to define important object specific metrics to monitor |
|
| Thresholding to allow automated and manual actions to be performed when certain critical metrics go out of normal range | |
| Multiple metrics in a single threshold so that user can create more realistic and useful thresholds |
|
| Visually create and manipulate thresholds |
|
| History to provide users with historical details of peak load periods and track important performance metrics during that period | |
| Supports text format for historical data so that users can import results into spreadsheets or databases for further research |
|
| Visually create and manipulate histories |
|
| Load Balancing | |
| Supports the starting and stopping of server processes based on load so that users can ensure that the right number of servers are running to handle the current user load. |
|
| Supports user defined load definition so that users can accurately describe the characteristics under which load balancing will occur |
|
| Fault Tolerant Architecture | |
| Semi-automated fail-over of management core services for easy recovery of the management environment from hardware failures |
|
| Redundant broker architecture so there is no single point of failure in management environment |
|
| Scalable Architecture | |
| Supports multiple AppCenter domains so that large applications can be managed effectively |
|
| Supports intelligent agents and event driven notification so that network traffic is minimized and larger numbers of hosts can form part of a single domain |
|
| Integration with other Management Platforms | |
| Supports sending SNMP traps for easy and quick integration with other leading management platforms |
|
| Supports user definable MIB for ability to tailor management integration needs to suit the individual site |
|
| Supports emerging standards to ensure compatibility with other environments | |
| Supports JMX to ensure compatibility with Java management standards |
|
| Support WEBM/CIM to ensure compatibility with other management platforms and new web-based management standards |
|
| APIs to support user configuration of the management environment | |
| Generic driver for management of any object |
|
| Management API for building other management apps |
|
| Performance API for adding user defined statistics |
|
| Management API for “deep” management of objects |
|
| Easy and Quick installation and configuration | |
| Repository upgrade for quick and painless upgrade of existing repository information |
|
| Self configuring agents for a more reliable, robust environment |
|
| Java Management Console | |
| Application centered view to allow operators to focus on what is important - the applications |
|
| Operator login and security to allow different views and different levels of control to be granted to different types of operators |
|
| Supports mass edit for the easy updating of a large number of objects at the same time |
|
| Supports XML import/export for the easy movement of configurations from one AppCenter repository to another |
|
| Context-based help for instant access to help information |
|
| Visual Management Environment | |
| Drag & Drop interface for easy construction of management models |
|
| Tree-structured layout for easy access to managed objects |
|
| Performance graphs for the graphing of real-time or historical performance metrics |
|
| View log files for the easy debugging of failed servers |
|
| Wizard support for easy, guided creation of managed objects |
|
| Multi-window support to allow maximum flexibility to the operators. |
|
| Multiple relationship views for the simple representation of complex information |
|
| Customizable Management Console | |
| Single icon view for operators who need only simple output |
|
| Multi-application view for operators who need to be in control of multiple applications at the same time. |
|
| Cockpit for the building of user defined views of the management world |
|
| Customize pull-down menus for easy addition of site specific management commands |
|
| Customize popup menus for easy addition of object specific management commands |
|
| Platform Availability | |
| Microsoft Windows |
|
| Sun Solaris |
|
| IBM AIX |
|
| HP-UX |
|