jmxadmin Enhancements

# Enhancements To Generic JMX CLI

####

#### Author: Lloyd Chambers, Kedar Mhaswade

#### $Id: Enhancements.html,v 1.1.1.1 2005/05/27 22:51:48 dpatil Exp $
$Author: dpatil $
$Date: 2005/05/27 22:51:48 $

## 1. Introduction

This is poor man's bugtraq for the cli-api submodule in admin-cli module. It is for internal tracking purposes. The generic JMX CLI is now used to test the JSR 160 HTTP implementation. The scope in S1AS 8.0.

Related Documents:

- Lloyd's Generic CLI Design Document
  - Provide Links1
  - 2 ...
- All about S1AS HTTP implementation of JSR 160 -
  - Javadoc - http://kedar.red.iplanet.com:8888/jsr160http/
  - TWiki pages - http://appserver.red.iplanet.com/twiki/bin/view/Apollo/JSR160

## 2. Bugs

Id | Type (BUG RFE) | Description | Date Found | State (Found Fixed Integrated Closed) | Date Fixed | Comments | Engineer
001 | RFE | Location of various files is to be documented and finalized. User's home directory? In the same directory as that of jmxadmin.jar | 08/07/2003 | Integrated | 08 Aug 2003 | QA: Where do following go? jmxadmin-aliases.props jmxadmin-env.props Dev: files now reside in user's home directory. | Lloyd
002 | RFE | Add new command: providers: everything to do with existing/new JMXConnectorProviders - --add <class-name> -- remove <class-name> --list | 08/07/2003 | Integrated | 8 Aug 2003 | QA: Very handy to add more providers. Dev: added 'configure' command and its aliases | Lloyd
003 | RFE | New Environmental Commands | 08/07/2003 | Integrated | 08 Aug 2003 | QA: Allow specification of various environment variables, accessed via a new builtin 'setenv' command, to be stored in jmxadmin-env.props. Allow environment variable to specify providers file, commands file Put environment variabls into command environment? Dev: commands are available for providers; no need to set environment variable for those. | Lloyd
004 | RFE | The 'find' command should allow a "current set" to add to or remove from | 08/07/2003 | Integrated | 8 Aug 2003 | QA: INTEGRATED. Each time 'find' is run, update a variable which is the current set ('FIND_CURRENT_SET'); add options to support this (--narrow to find based on the current set, --current to display the current set). | Lloyd
004-1 | RFE | The 'find' command currently can only find based on whatever JMX offers--wildcarding the domain and matching properties with fixed values. | 08 Aug 2003 |  |  | Allow finding by wildcarding property names Allow finding by wildcarding property values Allow the combination of both (?) Dev: |
005 | BUG | Javadoc is not available | 08/07/03 |  |  | QA: A well maintained javadoc is a must for this work. Dev: Yes, will do | Lloyd
006 | BUG | Design documents are not available | 08/07/03 |  |  | QA: How do I know how this was implemented? Dev: maybe...after the JavaDoc |
007 | BUG | Integrate with nightly build and JSR 160 HTTP Connector | 08/07/03 |  |  |  | Kedar
008 | BUG | The inspect command does not work for all the options. | 08/08/03 | Integrated | 08 Aug 2003 | Also fixed bug in 'target' command. |

Summary:

Total: 7

Fixed: 0

Not yet Fixed: 7