Preface
This book, the Message Queue Technical Overview, provides an introduction to the technology, concepts, architecture, capabilities, and features of the Message Queue messaging service.
As such, this book provides the foundation for other books within the Message Queue documentation set, and should be read first.
This preface consists of the following sections:
Who Should Use This Book
This guide is meant for application developers, administrators, 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. In the context of Message Queue:
-
An application developer is responsible for writing Message Queue client applications that use the Message Queue service to exchange messages with other client applications.
-
An administrator is responsible for setting up and managing a Message Queue messaging service.
This book does not assume any knowledge of messaging systems or 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 and technology 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 P–1 Book Contents|
Chapter |
Description |
|---|---|
|
Introduces messaging middleware technology, discusses the JMS standard, and describes the Message Queue service implementation of that standard. |
|
|
Describes the JMS programming model and how you can use the Message Queue client runtime to create JMS clients. Describes runtime support for C++ clients and for the transport of SOAP messages. |
|
|
Discusses administrative tasks and tools and describes broker services used to configure connections, routing, persistence, security, and monitoring. |
|
|
Discusses the architecture and use of Message Queue broker clusters. |
|
|
Explores the ramifications of implementing JMS support in a Java EE platform environment. |
|
|
Appendix A, Message Queue Implementation of Optional JMS Functionality |
Describes how the Message Queue product handles JMS optional items. |
|
Lists Message Queue features, summarizes steps needed to implement these, and provides reference for further information. |
|
|
Provides information about terms and concepts you might encounter while using Message Queue. |
Documentation Conventions
This section describes the following conventions used in Message Queue documentation:
Typographic Conventions
The following table describes the typographic conventions that are used in this book.
Table P–2 Typographic Conventions|
Typeface |
Meaning |
Example |
|---|---|---|
|
AaBbCc123 |
The names of commands, files, and directories, and onscreen computer output |
Edit your .login file. Use ls -a to list all files. machine_name% you have mail. |
|
AaBbCc123 |
What you type, contrasted with onscreen computer output |
machine_name% su Password: |
|
aabbcc123 |
Placeholder: replace with a real name or value |
The command to remove a file is rm filename. |
|
AaBbCc123 |
Book titles, new terms, and terms to be emphasized |
Read Chapter 6 in the User's Guide. A cache is a copy that is stored locally. Do not save the file. Note: Some emphasized items appear bold online. |
Symbol Conventions
The following table explains symbols that might be used in this book.
Table P–3 Symbol Conventions|
Symbol |
Description |
Example |
Meaning |
|---|---|---|---|
|
[ ] |
Contains optional arguments and command options. |
ls [-l] |
The -l option is not required. |
|
{ | } |
Contains a set of choices for a required command option. |
-d {y|n} |
The -d option requires that you use either the y argument or the n argument. |
|
${ } |
Indicates a variable reference. |
${com.sun.javaRoot} |
References the value of the com.sun.javaRoot variable. |
|
- |
Joins simultaneous multiple keystrokes. |
Control-A |
Press the Control key while you press the A key. |
|
+ |
Joins consecutive multiple keystrokes. |
Ctrl+A+N |
Press the Control key, release it, and then press the subsequent keys. |
|
-> |
Indicates menu item selection in a graphical user interface. |
File -> New -> Templates |
From the File menu, choose New. From the New submenu, choose Templates. |
Shell Prompt 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|
Shell |
Prompt |
|---|---|
|
C shell on UNIX, Linux, or AIX |
machine-name% |
|
C shell superuser on UNIX, Linux, or AIX |
machine-name# |
|
Bourne shell and Korn shell on UNIX, Linux, or AIX |
$ |
|
Bourne shell and Korn shell superuser on UNIX, Linux, or AIX |
# |
|
Windows command line |
C:\> |
Directory Variable 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. When installed from the IPS (pkg(5)) image distribution, Message Queue is installed in a directory referred to as mqInstallHome, and some of the directory variables in Table P–5 reference this mqInstallHome directory.
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
Related Documentation
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:
Message Queue Documentation Set
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 GlassFishTM Server documentation web site at
Table P–6 Message Queue Documentation Set|
Document |
Audience |
Description |
|---|---|---|
|
Developers and administrators |
Describes Message Queue concepts, features, and components. |
|
|
Developers and administrators |
Includes descriptions of new features, limitations, and known bugs, as well as technical notes. |
|
|
Administrators, also recommended for developers |
Provides background and information needed to perform administration tasks using Message Queue administration tools. |
|
|
Oracle GlassFish Message Queue 4.4.2 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 or SOAP/JAXM APIs. |
|
Oracle GlassFish Message Queue 4.4.2 Developer’s Guide for C Clients |
Developers |
Provides programming and reference documentation for developers of C client programs using the Message Queue C implementation of the JMS API (C-API). |
|
Oracle GlassFish Message Queue 4.4.2 Developer’s Guide for JMX Clients |
Administrators |
Provides programming and reference documentation for developers of JMX client programs using the Message Queue JMX API. |
Java Message Service (JMS) Specification
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
JavaDoc
JMS and Message Queue API documentation in JavaDoc format is included in your Message Queue installation at the locations shown in Table P–7, depending on your installation method. This documentation can be viewed in any HTML browser. It includes standard JMS API documentation as well as Message Queue–specific APIs.
Table P–7 JavaDoc Locations
Example Client Applications
Message Queue provides a number of example client applications to assist developers.
Example Java Client Applications
Example Java client applications are located in the following directories, depending on installation method. See the README files located in these directories and their subdirectories for descriptive information about the example applications.
|
Installation Method |
Location |
|---|---|
|
IPS image |
IMQ_HOME/examples [IMQ_HOME is the Message Queue home directory.] |
|
Solaris SVR4 packages |
/usr/demo/imq |
|
Linux RPM packages |
/opt/sun/mq/examples |
Example C Client Programs
Example C client applications are located in the following directories, depending on installation method. See the README files located in these directories and their subdirectories for descriptive information about the example applications.
|
Installation Method |
Location |
|---|---|
|
IPS image |
IMQ_HOME/examples/C [IMQ_HOME is the Message Queue home directory.] |
|
Solaris SVR4 packages |
/opt/SUNWimq/demo/C |
|
Linux RPM packages |
/opt/sun/mq/examples/C |
Example JMX Client Programs
Example Java Management Extensions (JMX) client applications are located in the following directories, depending on installation method. See the README files located in these directories and their subdirectories for descriptive information about the example applications.
Online Help
Online help is available for the Message Queue command line utilities; for details, see Chapter 16, Command Line Reference 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.
Documentation, Support, and Training
The Oracle web site provides information about the following additional resources:
Searching Oracle Product Documentation
Besides searching Oracle product documentation from the docs.sun.com web site, you can use a search engine by typing the following syntax in the search field:
search-term site:docs.sun.com |
For example, to search for “broker,” type the following:
broker site:docs.sun.com |
To include other Oracle web sites in your search (for example, java.sun.com and developers.sun.com), use “sun.com” in place of “docs.sun.com” in the search field.
Third-Party Web Site References
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.
- © 2010, Oracle Corporation and/or its affiliates