- New technology Agent Controller for Linux (IA32).
- Profiling tool improvements:
- Improved analysis views for analyzing execution statistics.
- Java Profiler Technology Preview improvements.
- Improved usability of Probekit.
- Test tool improvements:
- Improved JUnit
integration between TPTP and JDT.
- Automanted GUI Recorder (AGR) data mining support.
- New Generic API recorder technology
Note :All technology preview functions are available as a separate plugin download from the TPTP 4.3 download page. To be able to use a technology preview function make sure you download these plugins and any other required plugins, as recommended on the Technical Preview section.
- New Log Analyzer RCP application.
- New Symptom Database RCP application.
- Support for importing symptom catalogs from zip files.
- External APIs for common back-end Log Analyzer UI functionality.
- Generic Log Adapter improvements:
- Sensor/extractor filtering capability for Generic Log Adapter log parsers.
- Improved usability of
Log Adapter package.
- Managent Agent
Explorer technology preview moved to GA.
- New technology Agent
Controller for Linux (IA32).
Support existing Agent Controller clients and agents on the Linux IA32 platform using the new Agent Controller technology through compatibility layers.
- Improved usability of
Probe authors no longer have to use reflection to resolve external classes in their Probes. External classes will be resolved as long as they're included in the CLASSPATH. See image.
Profiling and tracing :
- Improved analysis views
for analyzing execution statistics.
- Java Profiler
Technology Preview improvements.
TPTP profiler based on JVMTI (JSR-163) is a full featured Java profiler supporting CPU Profiling, Heap Analysis and Thread Analysis of Java applications. See image.
- Improved JUnit
integration between TPTP and JDT.
TPTP now recognizes and executes any JUnit test class in the workspace, without requiring them to be imported as TPTP JUnit test suites first. A Java developer can switch to the tester role just by switching perspective: JUnit tests can be executed as TPTP tests. Navigation from the TPTP Test Perspective's views to the Java Perspective's view has been improved and is available on all items in the Test Navigator as well as in the JUnit Test editor. Code synchronization between TPTP models and JUnit code has been improved with code preview before applying changes. See image.
- Disabling the
invocation of a test case without having to remove the invocation from
a TPTP test suite.
Users are now able to disable the invocation of a test case without the need to remove that invocation from a TPTP test suite. See image.
- Providing the ability
to specify JVM arguments and a custom workspace location for a TPTP
test suite. See image.
- Integrated directory
and file browser with New Property dialog.
The General Properties for both artifacts and locations now provide a directory/file selector from the New Property dialog. A "Select file..." combo item has been added to the list for the classpath category. When choosing this item, a dialog allows the user to select a file that will be the property value. And a "select directory..." combo item has been added for both classpath and root directory categories. See image.
folder and project creation within test suite wizards.
Users are now able to create a new folder and/or project in the test suite wizards for saving the generated test suite. See image.
- Object mines for Automated GUI
Recorder (AGR) test suites.
An object mine keeps track of a single object (referenced by ID) irregardless of the number of times it occurs in the test cases owned by an Automated GUI Recorder (AGR) test suite. Users are now able to create object mines for use in AGR test suites, include external object mines (i.e. object mines owned by other test suites) in AGR test suites and contribute newly detected objects during recording to an external object mine. See image.
- Generic Java API
recorder to capture API invocation for TPTP JUnit test suite generation.
The API Recorder allows users to record API invocations of local/remote Java applications based on user-defined filters (package/class/method/signature). Recordings may be converted into TPTP JUnit test suites for unit and regression testing of the recorded Java application.
Monitoring Project :
- New Log Analyzer and Symptom
Database RCP applications.
TPTP now provides two standalone RCP applications, one for analyzing log files and one for creating and modifying symptom databases. These applications provide the same log analysis and symptom database editing functionality as is available in the full TPTP package but in a much smaller footprint for users that do not require all of the TPTP components.
- Support for importing
symptom catalogs from zip files.
Symptom catalogs stored in zip files can be imported either from ftp or http/https URLs or from a local disk. The following limitation applies: zips can only contain either a single Websphere version 4 or version 5 proprietary format catalog or multiple Symptom 2.0 catalogs.
- External APIs for
common back-end Log Analyzer UI functionality.
A set of common service base level apis are provided to import/export log files, analyze log files and correlate log files. The intention is to make it easier to develop non-eclipse tooling on top of these services.
- Generic Log Adapter
Parsing a whole log file may take a long time depending on the size of the file. If it is known that only a certain group of records is required to be analyzed, it would be useful to only parse those records of interest. Filtering support was added to Generic Log Adapter run-time in TPTP 4.2 to allow filtering of log records as they are read and extracted in the Sensor and Extractor components instead of after they are parsed into Common Base Events. For 4.3, filter implementations are added for each of the log parsers included in TPTP for filtering by severity and time. The filter is specified with XPATH expressions based on the CommonBaseEvent severity and creationTime properties.
The Stand-alone Generic Log Adapter package of TPTP can be used to parse log files from a command line using execution scripts or can be incorporated into an application and called programatically. To facilitate its use programatically, a new method has been added to the Adapter class to get the adapter configuration so that it can be modified before it is executed. This makes it easy to change the log file to be parsed and adjust the destination properties for the resulting CommonBaseEvents without having to change the adapter configuration file. Support was also added for disabling components in an adapter configuration Context. This allows, for instance, adapter configuration files to contain multiple Outputter component configurations that can be enabled or disabed as required before execution. Some of the adapter files included in the stand-alone package include multiple outputters.
- Managed Agent Explorer.
The Managed Agent Explorer view used for managing resources was introduced in TPTP 4.2 as a technology preview. It has been improved with
additional function such as notification support and is included as a full TPTP component in 4.3. It includes support for managing JMX instrumented Java applications. Support for managing resources via Web Services Distributed Managment (WSDM) is available as a technology preview.
to Manage Toolkit
In TPTP 4.2, tooling was introduced as a technology preview to instrument Java applications with JMX, Application Response Measurement (ARM) and Common Base Event code to make them more managable, by enabling the collection of performance and logging data. In 4.3, this support is improved. Also in 4.3, a technology preview of tooling to help build WSDM enabled resources that can be managed with Managed Agent Explorer. Download the tool from here.
Copyright © 2006 IBM Corporation. All rights reserved. This document and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which is available at http://www.eclipse.org/legal/epl-v10.html