Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Message Queue 3 2005Q1 Technical Overview 

Preface

This book, the Sun Java™ System Message Queue 3 2005Q1 Technical Overview, provides an introduction to the technology, concepts, architecture, capabilities, and features of the Message Queue messaging service.

As such, the Message Queue Technical Overview provides the foundation for other books within the Message Queue documentation set. You should read this book before reading the other books in the Message Queue documentation set.

This preface contains the following sections:


Who Should Use This Book

This guide is meant for administrators, application developers, and other parties who plan to use the Message Queue product or who wish to understand the technology, concepts, architecture, capabilities, and features of the product.

A Message Queue administrator is responsible for setting up and managing a Message Queue messaging system, in particular the Message Queue message server at the heart of this system. This book does not assume any knowledge or understanding of messaging systems.

An application developer is responsible for writing Message Queue client applications that use the Message Queue service to exchange messages with other client applications. This book does not assume any knowledge of the Java Message Service (JMS) specification, which is implemented by the Message Queue service.


Before You Read This Book

There are no prerequisites to this book. You should read this book to gain an understanding of basic Message Queue concepts before reading the Message Queue Developer and Administration Guides.


How This Book Is Organized

This guide is designed to be read from beginning to end; each chapter builds on information contained in earlier chapters. The following table briefly describes the contents of each chapter:

Table 1  Book Contents and Organization

Chapter

Description

Chapter 1, "Conceptual Foundations"

Provides the conceptual background to Message Queue, describing enterprise messaging systems and introducing Java Message Service concepts and terminology

Chapter 2, "Introduction to Message Queue"

Introduces the Message Queue service by discussing its architecture and describing its enterprise-strength features and capabilities

Chapter 3, "Reliable Message Delivery"

Describes how the Message Queue service provides reliable message delivery for messaging applications

Chapter 4, "Message Server"

Discusses the internal structure of the broker, describing the various broker components and their functions. Describes the different approaches to using Message Queue in development and production environments.

Chapter 5, "Broker Clusters"

Discusses the architecture and internal functioning of Message Queue broker clusters

Chapter 6, "Message Queue and J2EE"

Explores the ramifications of implementing JMS support in a J2EE platform environment

Appendix A, "Message Queue Implementation of Optional JMS Functionality"

Describes how the Message Queue product handles JMS optional items

Glossary

Provides information about terms and concepts you might encounter while using Message Queue


Conventions Used in this Book

This section provides information about the conventions used in this document.

Text Conventions

Table 2  Document Conventions 

Format

Description

italics

Italicized text represents a placeholder. Substitute an appropriate clause or value where you see italic text. Italicized text is also used to designate a document title, for emphasis, or for a word or phrase being introduced.

monospace

Monospace text represents example code, commands that you enter on the command line, directory, file, or path names, error message text, class names, method names (including all elements in the signature), package names, reserved words, and URLs.

[]

Square brackets to indicate optional values in a command line syntax statement.

ALL CAPS

Text in all capitals represents file system types (GIF, TXT, HTML and so forth), environment variables (IMQ_HOME), or acronyms (Message Queue, JSP).

Key+Key

Simultaneous keystrokes are joined with a plus sign: Ctrl+A means press both keys simultaneously.

Key-Key

Consecutive keystrokes are joined with a hyphen: Esc-S means press the Esc key, release it, then press the S key.

Directory Variable Conventions

Message Queue makes use of three directory variables; how they are set varies from platform to platform. Table 3 describes these variables and summarizes how they are used on the Solaris™, Windows, and Linux platforms.

Table 3  Message Queue Directory Variables 

Variable

Description

IMQ_HOME

This is generally used in Message Queue documentation to refer to the Message Queue base directory (root installation directory):

  • On Solaris, there is no root Message Queue installation directory. Therefore, IMQ_HOME is not used in Message Queue documentation to refer to file locations on Solaris.
  • On Solaris, for Sun Java System Application Server the root Message Queue installation directory is /imq under the Application Server base directory.
  • On Windows, the root Message Queue installation directory is set by the Message Queue installer (by default, as C:\Program Files\Sun\MessageQueue3).
  • On Windows, for Sun Java System Application Server, the root Message Queue installation directory is /imq under the Application Server base directory.
  • On Linux, there is no root Message Queue installation directory. Therefore, IMQ_HOME is not used in Message Queue documentation to refer to file locations on Linux.

IMQ_VARHOME

This is the /var directory in which Message Queue temporary or dynamically-created configuration and data files are stored. It can be set as an environment variable to point to any directory.

  • On Solaris, IMQ_VARHOME defaults to the /var/imq directory.
  • On Solaris, for Sun Java System Application Server, Evaluation Edition, IMQ_VARHOME defaults to the IMQ_HOME/var directory.
  • On Windows IMQ_VARHOME defaults to the IMQ_HOME\var directory.
  • On Windows, for Sun Java System Application Server, IMQ_VARHOME defaults to the IMQ_HOME\var directory.
  • On Linux, IMQ_VARHOME defaults to the /var/opt/imq directory

IMQ_JAVAHOME

This is an environment variable that points to the location of the Java™ runtime (JRE) required by Message Queue executables:

  • On Solaris, IMQ_JAVAHOME looks for the java runtime in the following order, but a user can optionally set the value to wherever the required JRE resides.
    Solaris 8 or 9:
      /usr/jdk/entsys-j2se
      /usr/jdk/jdk1.5.
    *
      /usr/jdk/j2sdk1.5.*
      /usr/j2se
    Solaris 10:
      /usr/jdk/entsys-j2se
      /usr/java
      /usr/j2se
  • On Linux, Message Queue first looks for the java runtime in the following order, but a user can optionally set the value of IMQ_JAVAHOME to wherever the required JRE resides.
      /usr/jdk/entsys-j2se
      /usr/java/jre1.5.
    *
      /usr/java/jdk1.5.*
      /usr/java/jre1.4.2*
      /usr/java/j2sdk1.4.2
    *
  • On Windows, IMQ_JAVAHOME defaults to IMQ_HOME\jre, but a user can optionally set the value to wherever the required JRE resides.

In this guide, IMQ_HOME, IMQ_VARHOME, and IMQ_JAVAHOME are shown without platform-specific environment variable notation or syntax (for example, $IMQ_HOME on UNIX�). Path names generally use UNIX directory separator notation (/).


Related Documentation

In addition to this guide, Message Queue provides additional documentation resources.

The Message Queue Documentation Set

The documents that comprise the Message Queue documentation set are listed in Table 4 in the order in which you would normally use them.

Table 4  Message Queue Documentation Set 

Document

Audience

Description

Message Queue Installation Guide

Developers and administrators

Explains how to install Message Queue software on Solaris, Linux, and Windows platforms.

Message Queue Release Notes

Developers and administrators

Includes descriptions of new features, limitations, and known bugs, as well as technical notes.

Message Queue Administration Guide

Administrators, also recommended for developers

Provides background and information needed to perform administration tasks using Message Queue administration tools.

Message Queue Developer’s Guide for Java Clients

Developers

Provides a quick-start tutorial and programming information for developers of Java client programs using the Message Queue implementation of the JMS and SOAP/JAXM specifications.

Message Queue Developer’s Guide for C Clients

Developers

Provides programming and reference documentation for developers of C client programs using the C interface (C-API) to the Message Queue message service.

Online Help

Message Queue includes command line utilities for performing Message Queue message service administration tasks. To access the online help for these utilities, see the Message Queue Administration Guide.

Message Queue also includes a graphical user interface (GUI) administration tool, the Administration Console (imqadmin). Context sensitive online help is included in the Administration Console.

JavaDoc

Message Queue Java client API (including the JMS API) documentation in JavaDoc format, is provided at the following location:

Platform

Location

Solaris

/usr/share/javadoc/imq/index.html

Linux

/opt/sun/mq/javadoc/index.html/

Windows

IMQ_HOME/javadoc/index.html

This documentation can be viewed in any HTML browser such as Netscape or Internet Explorer. It includes standard JMS API documentation as well as Message Queue-specific APIs for Message Queue administered objects (see Chapter 3 of the Message Queue Developer’s Guide for Java Clients), which are of value to developers of messaging applications.

Example Client Applications

A number of example applications that provide sample client application code are included in a directory that depends upon the operating system (see the Message Queue Administration Guide).

See the README file located in that directory and in each of its subdirectories.

The Java Message Service (JMS) Specification

The JMS specification can be found at the following location:

The specification includes sample client code.


Related Third-Party Web Site References

Third-party URLs are referenced in this document and provide additional, related information.


Note

Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.



Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions.

To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document.



Previous      Contents      Index      Next     


Part No: 819-0069-10.   Copyright 2005 Sun Microsystems, Inc. All rights reserved.