Enhance the xsadmin of WebSphere EXtreme Scale

Introduction

IBM WebSphere EXtreme Scale can be deployed in two different ways:

Install to an existing WebSphere application Server network deployment instance by extending the WebSphere configuration file.

Install to a j2se™ environment that does not have a WebSphere application Server.

In the first scenario, system monitoring and server management tasks are performed by the management components of the WebSphere application server, but in an isolated environment and in a WebSphere-managed environment, the internal view of the grid is only visible through the Xsadmin application.

The Xsadmin application is not part of the WebSphere eXtreme Scale V6.1.0.3 Product code, but is provided as a sample application. Almost all of the functionality provided by Xsadmin can be accomplished by interacting with Jmx™mbean instances contained in the EXtreme Scale process.

Without any configuration, you can use Xsadmin to view the placement of the current grid unit (primary unit and copy) in the configured container, see which containers are available, and see which host the container is running on. Through this article, you will be able to:

Overwrites the command-line parameter code to support a more logical flow of required and non-essential parameters.

Exposes the-l parameter for easy browsing of available grid instances and associated mapping sets.

Add and Expose-? parameter to supplement the existing help parameter –h.

Add the-catserv parameter to display information about the Environment directory server.

Add the-CG parameter to display only information about the current core group Run-time state and the quota state and heartbeat interval settings.

Before you start making changes to Xsadmin, it's helpful to know what's already included.

Xsadmin Sample Application

This article assumes that you will use the IBM Rational®software Development platform (specifically, IBM Rational application Developer V7.0.0.7) to update the sample application. Because the Xsadmin application is a sample Java application, you can use any IDE of your choice. However, you must be able to include Objectgrid.jar files in the WebSphere eXtreme Scale V6.1.0.3, which includes the necessary compile-time classes that need to be placed in the build path to properly compile and test the application. For more information about how to insert the Objectgrid.jar file into your application's build path, see the documentation for your development environment.

The Xsadmin application consists of a single package, that is, com.ibm.websphere.samples.objectgrid.admin. There are two class files in this package, Jmxproxy and Ogadmin. Our focus will be on the Ogadmin class; We will refer to and use the Jmxproxy class, but for this article, you will not be working with source code.

The Ogadmin class contains multiple internal classes:

Options

Cmdlineparser