The Java Dynamic ManagementTM Kit provides a set of Java classes and tools for developing management solutions. This product conforms to the specification of the Java Management extensions (JMX) which define a three-level architecture: resource instrumentation, dynamic agents and remote management applications. Such an architecture is applicable to network management, remote system maintenance, application maintenance and service provisioning.
The Getting Started with the Java Dynamic Management Kit 4.0 Guide presents the architecture of the Java Dynamic Management Kit, introducing the key concepts of the product and the development process.
This book is aimed at anyone seeking an introduction to the concepts and components of the Java Dynamic Management Kit.
Familiarity with Java programming and the JavaBeansTM component model is assumed.
This book is not intended to be an exhaustive reference: management tutorials intended to demonstrate each of the management levels and how they interact are covered in Java Dynamic Management Kit 4.0 Tutorials, and the complete Javadoc API definitions are provided in the product documentation package.
In order to build and run the sample programs in these tutorials, or use the tool commands, you must have a complete installation of the Java Dynamic Management on your machine. Please refer to the Java Dynamic Management Kit 4.0 Installation Guide and Release Notes document for instructions on how to install the product components and configure your environment.
After familiarizing yourself with the concepts of the Java Dynamic Management Kit, you should familiarize yourself with the tools provided with the Java Dynamic Management Kit and learn how to instrument new or existing resources for management. The following books are part of the product documentation set:
Java Dynamic Management Kit 4.0 Tools Reference
Java Dynamic Management Kit 4.0 Tutorials
These books are available on-line after you have installed the documentation package of the Java Dynamic Management. The on-line documentation also includes the Javadoc API for the Java packages and classes, including those of the Java Management extensions. Using any web browser, open the home-page corresponding to your platform:
Operating Environment |
Home-Page Location |
---|---|
Solaris |
installDir/SUNWjdmk/jdmk4.0/JDKversion/index.html |
Windows NT |
installDir\SUNWjdmk\jdmk4.0\JDKversion\index.html |
In these file names, installDir refers to the base directory of your Java Dynamic Management installation. The JDKversion is that of the Java Development Kit which you use and which you selected during installation; it can be either 1.1 or 1.2. This convention is used throughout this book whenever referring to files or directories which are part of the installation. In a default installation procedure, installDir is:
/opt on the Solaris platform
C:\Program Files on the Windows NT platform
This book explains the key concepts of the Java Dynamic Management Kit, introduces the main components of the product, provides an overview of the development process and outlines the tools you need to use the Java Dynamic Management Kit. It is divided into the following sections:
The Java Dynamic Management Kit relies on the management architecture of the Java Management extensions. The three specifications documents are provided in the product documentation package:
"Java Management Extensions Instrumentation and Agent Specification" (jmx_instr_agent.pdf)
"Java Management Extensions SNMP Manager API" (jmx_snmp_api.pdf)
Fatbrain.com, an Internet professional bookstore, stocks select product documentation from Sun Microsystems, Inc.
For a list of documents and how to order them, visit the Sun Documentation Center on Fatbrain.com at http://www1.fatbrain.com/documentation/sun.
The docs.sun.comSM Web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. The URL is http://www.oracle.com/technetwork/indexes/documentation/index.html.
The following table describes the typographic changes used in this book.
Table P-1 Typographic Conventions
Typeface or Symbol |
Meaning |
Example |
---|---|---|
AaBbCc123 |
Book titles, new words or terms, or words to be emphasized |
Read Chapter 6 in User's Guide. These are called class options. You must be root to do this. |
AaBbCc123 | Class or object names, methods, parameters or any other element of the Java programming language | Instantiate the MyBean class. |
AaBbCc123 | The names of commands, files, and directories; on-screen computer output |
Edit your .login file. Use ls -a to list all files. machine_name% you have mail. |
AaBbCc123 | What you type, contrasted with on-screen computer output | machine_name% su Password: |
AaBbCc123 | Command-line placeholder: replace with a real name or value |
To delete a file, type rm filename. |
The following table shows the default system prompts for the different platforms and shells.
Table P-2 Shell Prompts
Shell |
Prompt |
---|---|
C shell prompt | machine_name% |
C shell superuser prompt | machine_name# |
Bourne shell and Korn shell prompt | $ |
Bourne shell and Korn shell superuser prompt | # |
Windows NT system prompt | C:\ |
Unless otherwise noted, the command examples in this book use the Korn shell prompt.