Содержащиеся в
Найти другие документыРесурсы поддержки | Загрузить это руководство в формате PDF (1037 КБ)
PrefaceThis Message Queue Developer’s Guide for JMX Clients describes the application programming interface provided in Sun Java System Message Queue 4.0 for programmatically configuring and monitoring Message Queue resources in conformance with the Java Management Extensions (JMX). As in earlier versions of Message Queue, these functions are also available to system administrators by way of the Message Queue Administration Console and command line utilities, as described in the Message Queue Administration Guide. The API described here, new in release 4.0, makes the same administrative functionality available programmatically from within a running client application. Message Queue 4.0 also includes several new broker properties and command-line options to support the new JMX API. These features are described in the Message Queue Release Notes for release 4.0, and will eventually be incorporated into the Message Queue Administration Guide. Who Should Use This BookThis guide is intended for Java application developers wishing to use the Message Queue JMX API to perform Message Queue administrative tasks programmatically from within a client application. Before You Read This BookThis guide assumes that you are already familiar with general Message Queue concepts, administrative operations, and Java client programming, as described in the following manuals:
You should also be familiar with the general principles of the Java Management Extensions, as described in the following publications:
Together, these two publications are referred to hereafter as the JMX Specification. How This Book Is OrganizedThis guide consists of the following chapters:
Related DocumentationIn addition to this guide, Sun provides the additional documentation resources described in the following subsections. Message Queue Documentation SetThe Message Queue documentation set comprises the documents shown in Table P–1, in the order in which you would normally use them. Table P–1 Message Queue Documentation Set
Java Management Extensions (JMX) DocumentationThe Message Queue JMX API conforms to the Java Management Extensions (JMX) standard, described in the Java Management Extensions Instrumentation and Agent Specification and the Java Management Extensions (JMX) Remote API Specification. These documents can be downloaded from the URLs http://jcp.org/aboutJava/communityprocess/final/jsr003 and http://jcp.org/aboutJava/communityprocess/final/jsr160 respectively. For a general conceptual introduction to JMX principles and architecture, see the Java Management Extensions (JMX) Technology Overview at http://java.sun.com/j2se/1.5.0/docs/guide/jmx/overview/JMXoverviewTOC.html and the Java Management Extensions (JMX) Technology Tutorial at http://java.sun.com/j2se/1.5.0/docs/guide/jmx/tutorial/tutorialTOC.html JavaDocMessage Queue API documentation in JavaDoc format is included in your Message Queue installation at the locations shown in Table P–2, depending on your platform. This documentation can be viewed in any HTML browser. Table P–2 JavaDoc Locations
Example Client ApplicationsExample applications providing sample Java client application code are included in your Message Queue installation at the locations shown in Table P–3, depending on your platform. Table P–3 Example Code Locations
Documentation, Support, and TrainingThe Sun Web site provides information about the following additional resources: Typographic Conventions Used in This BookTable P–4 describes the typographic conventions used in this book. Table P–4 Typographic Conventions
Sun Welcomes Your CommentsSun is always interested in improving its documentation and welcomes your comments and suggestions. To share your comments, go to the Sun documentation Web site at and click Send Comments. In the resulting online form, provide the document title and part number along with your comment. (The part number is a seven- or nine-digit number that can be found on the title page of the book or at the top of the document.) |
|||||||||||||||||||||||||||||||||||||||||||||||||