| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server Message Queue 4.5 Developer's Guide for Java Clients |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle GlassFish Server Message Queue 4.5 Developer's Guide for Java Clients |
3. Message Queue Clients: Design and Features
4. Using the Metrics Monitoring API
6. Embedding a Message Queue Broker in a Java Client
This book provides information about concepts and procedures for developing Java messaging applications (Java clients) that work with Oracle GlassFish Server Message Queue.
This preface consists of the following sections:
This guide is meant principally for developers of Java applications that use Oracle GlassFish Server Message Queue.
These applications use the Java Message Service (JMS) Application Programming Interface (API), and possibly the SOAP with Attachments API for Java (SAAJ), to create, send, receive, and read messages. As such, these applications are JMS clients and/or SOAP client applications, respectively. The JMS and SAAJ specifications are open standards.
This book assumes that you are familiar with the JMS APIs and with JMS programming guidelines. Its purpose is to help you optimize your JMS client applications by making best use of the features and flexibility of a Message Queue messaging system.
This book assumes no familiarity, however, with SAAJ. This material is described in Chapter 5, Working with SOAP Messages and assumes only basic knowledge of XML.
You must read the Oracle GlassFish Server Message Queue 4.5 Technical Overview to become familiar with the Message Queue implementation of the Java Message Specification, with the components of the Message Queue service, and with the basic process of developing, deploying, and administering a Message Queue application.
This guide is designed to be read from beginning to end. The following table briefly describes the contents of each chapter.
Table P-1 Book Contents
|
This section describes the following conventions used in Message Queue documentation:
The following table describes the typographic conventions that are used in this book.
Table P-2 Typographic Conventions
|
The following table explains symbols that might be used in this book.
Table P-3 Symbol Conventions
|
The following table shows the conventions used in Message Queue documentation for the default UNIX system prompt and superuser prompt for the C shell, Bourne shell, Korn shell, and for the Windows operating system.
Table P-4 Shell Prompt Conventions
|
Message Queue documentation makes use of three directory variables; two of which represent environment variables needed by Message Queue. (How you set the environment variables varies from platform to platform.)
The following table describes the directory variables that might be found in this book and how they are used. Some of these variables refer to the directory mqInstallHome, which is the directory where Message Queue is installed to when using the installer or unzipped to when using a zip-based distribution.
Note - In this book, directory variables are shown without platform-specific environment variable notation or syntax (such as $IMQ_HOME on UNIX). Non-platform-specific path names use UNIX directory separator (/) notation.
Table P-5 Directory Variable Conventions
|
The information resources listed in this section provide further information about Message Queue in addition to that contained in this manual. The section covers the following resources:
The documents that constitute the Message Queue documentation set are listed in the following table in the order in which you might normally use them. These documents are available through the Oracle GlassFish Server Server documentation web site at
Table P-6 Message Queue Documentation Set
|
The Message Queue message service conforms to the Java Message Service (JMS) application programming interface, described in the Java Message Service Specification. This document can be found at the URL
JMS and Message Queue API documentation in JavaDoc format is included in Message Queue installations at IMQ_HOME/javadoc/index.html. This documentation can be viewed in any HTML browser. It includes standard JMS API documentation as well as Message Queue–specific APIs.
Message Queue provides a number of example client applications to assist developers.
Example Java client applications are included in Message Queue installations at IMQ_HOME/examples. See the README files located in this directory and its subdirectories for descriptive information about the example applications.
Example C client applications are included in Message Queue installations at IMQ_HOME/examples/C. See the README files located in this directory and its subdirectories for descriptive information about the example applications.
Example Java Management Extensions (JMX) client applications are included in Message Queue installations at IMQ_HOME/examples/jmx. See the README files located in this directory and its subdirectories for descriptive information about the example applications.
Online help is available for the Message Queue command line utilities; for details, see Chapter 16, Command Line Reference, in Oracle GlassFish Server Message Queue 4.5 Administration Guide for details. The Message Queue graphical user interface (GUI) administration tool, the Administration Console, also includes a context-sensitive help facility; see the section “Administration Console Online Help” in Chapter 2, Quick-Start Tutorial, in Oracle GlassFish Server Message Queue 4.5 Administration Guide.
The Oracle web site provides information about the following additional resources:
Where relevant, this manual refers to third-party URLs that provide additional, related information.
Note - Oracle is not responsible for the availability of third-party Web sites mentioned in this manual. Oracle does not endorse and is not responsible or liable for any content, advertising, products, or other materials available on or through such sites or resources. Oracle will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any such content, goods, or services available on or through such sites or resources.
|