Your guide to finding IBM autonomic computing toolkit components
IBM autonomic computing tools include
- Autonomic Computing Toolkit: Integrated Solutions Console technology.
- Autonomic Computing Toolkit: Solution installation and deployment technologies.
- Build to Manage Toolkit for Problem Determination: Log Discovery Service.
- Build to Manage Toolkit for Problem Determination: Log and Trace Analyzer.
- Build to Manage Toolkit for Problem Determination: Generic Log Adapter.
- Build to Manage Toolkit for Problem Determination: Remote Agent Controller.
Integrated Solutions Console
No matter how automated the system becomes, at some point humans must interact with the system -- the Integrated Solutions Console technology is the common console technology for systems administration. It provides the main platform on which IBM and non-IBM products can build administrative user interfaces as individual plug-ins to a common console framework. Standardizing product administration functions to run on the Integrated Solutions Console platform gives them a more common look and feel and a more consistent behavior, thereby reducing the learning curve and adoption as new management components are introduced. Administrators can interact with multiple IBM and non-IBM products from a single browser-based console. The following components are available with the ISC:
|Scenario||Solution Installation and Deployment Samples Scenario|
|Runtime components||Integrated Solutions Console (standard)|
|Runtime components||Integrated Solutions Console (custom)|
|Tools*||Integrated Solutions Console Toolkit|
*Requires Rational Application Developer 22.214.171.124.
The ISC is based on WebSphere Portal, so administrative functions are handled through portlets (using the JSR-168 standard) or components, within a single system. When an administrator adds new software, its administrative functions and help files are added to the common administrative system. The ISC Toolkit is the development environment for creating Integrated Solutions Console plug-ins and is included in the ISC component. It includes the Integrated Solutions Console Developer Info Center, Sample Integrated Solutions Console Components, and an Integrated Solutions Console tooling plug-in for Rational Application Developer and Rational Software Architect. This plug-in prereqs the IBM WebSphere Portal Toolkit.
Solution installation and deployment
Solution installation and deployment technologies enable software solutions to be deployed and supported with reduced human interaction:
- A common infrastructure ensures a simpler deployment experience.
- Common packaging minimizes the number of software instances installed within an enterprise.
- Common deployment descriptors describe the installation capabilities and dependency requirements for a given software package.
- Common tools reduce the cost and complexity of building, deploying, and maintaining software solutions.
- Common dependency-checking technologies address the major configuration and change management concerns that customers experience.
The Solution installation and deployment architecture is demonstrated using a set of scenarios targeting the self-configuring aspect of self-managing autonomic technology:
|Solution Installation and Deployment Samples|
|Solution Installation and Deployment using FNPIM|
|Solution Installation and Deployment using InstallAnywhere|
The Samples scenario is a teaching tool, introducing the core components that make up the Solution installation and deployment architecture and then relating them together to illustrate the benefits of the architecture. It also identifies how installation behavior is defined and carried out and allows the user to verify each step of the installation by viewing the repository of installed components. All the samples are managed and controlled using an Integrated Solutions Console component plug-in.
Build to Manage Toolkit for Problem Determination
So where did things that used to be in the Autonomic Computing Toolkit go? Things like the Log and Trace Analyzer, the Generic Log Adapter, and the Remote Agent Controller? They have been moved to a new toolkit, the Build to Manage Toolkit for Problem Determination R1.01. The IBM Build to Manage Toolkit for Problem Determination is a set of tools, documentation, and tutorial videos that help developers build problem manageability features into their applications.
What is the difference between the Autonomic Computing Toolkit on developerWorks and this new IBM Build to Manage Toolkit for Problem Determination? The IBM Build to Manage Toolkit for Problem Determination is the new home for the set of problem determination and root-cause analysis tools and technologies previously available on IBM developerWorks in the Autonomic Computing Toolkit. As a member of the family of IBM Build to Manage toolkits, this toolkit will be tied more closely to other members of the family, such as the Build to Manage Toolkit for Java Instrumentation.
The latest release includes new tools that make it easy to capture information about problem symptoms and recommended solutions. A new problem correlation technology allows for identification of complex problem signatures. In addition, this release supports V1.1 of the Web Services Distributed Management (WSDM) Event Format (WEF) standard for event formats, recently ratified by the OASIS standards body.
So why are these new symptom tools important? As it turns out, many problems occuring in an IT environment have known solutions. Today, problem analysts use mostly manual methods to search problem knowledge databases. The tools made available in this toolkit make it easy for application developers, testers, and support personnel to capture knowledge about problems and their solutions, and publish them in a "symptom catalog." These catalogs are then automatically accessed by problem management products during deployment and operations, thus saving significant time and effort in determining effective resolutions to problems.
What are problem signatures? Problem signatures can be as simple as one error logged by a single product or as complex as a sequence of errors logged by a number of interacting products. This toolkit includes tools that make it easy to define rules that identify both simple and complex problem signatures. During problem analysis, these rules can be applied against product log files to quickly diagnose problems. When used together with the symptom tools explained above, a powerful root-cause analysis and problem resolution solution is achieved.
Log Discovery Service
Log Discovery Service is a standalone tool that consolidates the location of log files residing on one or more systems by capturing the location information into a central repository using an IBM Cloudscape database. It provides a command-line interface so that you can access this information from the central repository and the interface allows you to register, update, and retrieve the location information of log files which can then be used to import log files into the Log and Trace Analyzer. The current version is 4.2.1 for Windows.
Log and Trace Analyzer
The symptom catalogs you develop for your application are consumed by problem-analysis tools such as the IBM Log and Trace Analyzer. The Log and Trace Analyzer is available in three versions -- an Eclipse plug-in version, a portal-based version, and a Java desktop version:
|Log and Trace Analyzer for Eclipse 4.2.1|
|Log and Trace Analyzer for Portal 4.2.1|
|Log and Trace Analyzer for Java Desktop 4.2.1|
Generic Log Adapter and Rule Sets
To take advantage of the problem determination capabilities provided by such self-management components as the Log and Trace Analyzer, log events need to be presented to these tools in the Common Base Event format, IBM's initial implementation of the Web Services Distributed Management (WSDM) Event Format (WEF) standards. The Generic Log Adapter and Rule Sets includes a set of parser rules for many IBM and other popular vendor applications. These parser rules are used in conjunction with the GLA runtime to convert log events to the Common Base Event format. To build your own parser rules that convert your application's existing log format, an Eclipse plug-in parser rule editor is available in the Log and Trace Analyzer for Eclipse package:
|Generic Log Adapter Runtime and Rule Sets 4.2.1|
The big package
You can get the Log and Trace Analyzer, the Generic Log Adapter, and Eclipse in a single installation package that contains all prerequisites. Current version is 4.2.1 for Linux and for Windows.
Remote Agent Controller
The Remote Agent Controller is used to import log files remotely from any platform that the agent controller supports. The agent controller makes it convenient to analyze a log file from a remote machine without having to transfer a copy of the file to a local machine. For example, by installing the agent controller on an IBM Systems machine, you can use the Log and Trace Analyzer tool running on a Windows or Linux desktop machine to analyze log files that are continuously updated by applications running on the server:
|Remote Agent Controller 7.0.1|