iplanet message queue for java installation guide, version 2 · 2011-02-09 · programming...

Installation GuideiPlanet™ Message Queue for Java™

Version 2.0

August 24, 2001

Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corporation. All rights reserved.

Sun, Sun Microsystems, the Sun logo, Java, Solaris, iPlanet, and the iPlanet logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Netscape and the Netscape N logo are registered trademarks of Netscape Communications Corporation in the U.S. and other countries. Other Netscape logos, product names, and service names are also trademarks of Netscape Communications Corporation, which may be registered in other countries.

Federal Acquisitions: Commercial Software—Government Users Subject to Standard License Terms and Conditions

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation. No part of the product or this document may be reproduced in any form by any means without prior written authorization of the Sun-Netscape Alliance and its licensors, if any.

THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

______________________________________________________________________________________________________

Copyright © 2001 Sun Microsystems, Inc. Pour certaines parties préexistantes, Copyright © 2001 Netscape Communication Corp. Tous droits réservés.

Sun, Sun Microsystems, et le logo Sun, Java, Solaris, iPlanet, et le logo iPlanet sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et d’autre pays. Netscape et le logo Netscape N sont des marques déposées de Netscape Communications Corporation aux Etats-Unis et d’autre pays. Les autres logos, les noms de produit, et les noms de service de Netscape sont des marques déposées de Netscape Communications Corporation dans certains autres pays.

Le produit décrit dans ce document est distribué selon des conditions de licence qui en restreignent l'utilisation, la copie, la distribution et la décompilation. Aucune partie de ce produit ni de ce document ne peut être reproduite sous quelque forme ou par quelque moyen que ce soit sans l’autorisation écrite préalable de l’Alliance Sun-Netscape et, le cas échéant, de ses bailleurs de licence.

CETTE DOCUMENTATION EST FOURNIE “EN L'ÉTAT”, ET TOUTES CONDITIONS EXPRESSES OU IMPLICITES, TOUTES REPRÉSENTATIONS ET TOUTES GARANTIES, Y COMPRIS TOUTE GARANTIE IMPLICITE D'APTITUDE À LA VENTE, OU À UN BUT PARTICULIER OU DE NON CONTREFAÇON SONT EXCLUES, EXCEPTÉ DANS LA MESURE OÙ DE TELLES EXCLUSIONS SERAIENT CONTRAIRES À LA LOI.

3

Contents

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

List of Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Audience for This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Organization of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Environment Variable Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Other Documentation Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12The iMQ Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Example Client Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13iMQ Product Editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Supported Platforms and Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14iMQ Software Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Installing from Web and CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Upgrading from a Beta Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installed Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Where To Go Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2 Solaris Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Installing iMQ on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Installing from the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Installing from CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Upgrading Editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Where To Go Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Uninstalling iMQ on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4 iPlanet Message Queue for Java • Installation Guide • August 24, 2001

Chapter 3 Linux Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Installing iMQ on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Installing from the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installing from CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Upgrading Editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Where To Go Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Uninstalling iMQ on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 4 Windows Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installing iMQ on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Installation Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Troubleshooting Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Upgrading Editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Where To Go Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Uninstalling iMQ on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5

List of Tables

Table 1 Book Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 2 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Table 3 iMQ Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 4 iMQ Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 1-1 iMQ 2.0 Product Support Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 1-2 iMQ Software Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Table 1-3 Installed Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Table 2-1 Hardware and Software Requirements for Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Table 3-1 Hardware and Software Requirements for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table 4-1 Hardware and Software Requirements for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table 4-2 Windows Installation Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

7

List of Procedures

To install iMQ on Solaris from the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

To install iMQ on Solaris from CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

To upgrade to Enterprise edition on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

To remove iMQ on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

To install iMQ on Linux from the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

To install iMQ on Linux from CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

To upgrade to Enterprise edition on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

To remove iMQ on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

To install iMQ on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

To troubleshoot installation problems on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

To upgrade to Enterprise edition on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

To remove iMQ on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

9

Preface

This book explains how to install iPlanet Message Queue for Java (iMQ) 2.0, and this preface contains the following sections:

• Audience for This Guide

• Organization of This Guide

• Conventions

• Other Documentation Resources

Audience for This GuideThe audience for this guide is iMQ developers and administrators.

Organization of This GuideAll users should read the introduction and then the appropriate platform-specific chapter. The following table briefly describes the contents of each chapter:

Table 1 Book Contents

Chapter Description

Chapter 1, “Introduction”

Explains the iMQ editions, supported platforms and products, the iMQ software modules, and the installed directory structure.

Chapter 2, “Solaris Installation”

Explains the hardware and software requirements, defaults, and installation procedure for Solaris, as well as how to uninstall the product on this platform.

Conventions


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

Text Conventions

Chapter 3, “Linux Installation”

Explains the hardware and software requirements, defaults, and installation procedure for Linux, as well as how to uninstall the product on this platform.

Chapter 4, “Windows Installation”

Explains the hardware and software requirements, defaults, and installation procedure for Windows (98, NT, 2000), as well as how to uninstall the product on this platform.

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 (JMQ_HOME), or acronyms (iMQ, 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.

Table 1 Book Contents (Continued)

Chapter Description

Conventions

Preface 11

Environment Variable ConventionsiMQ makes use of two environment variables.

In this guide, JMQ_HOME and JMQ_VARHOME are shown without platform-specific environment variable notation or syntax (for example, $JMQ_HOME on UNIX). However, all path names use UNIX file separator notation (/).

Table 3 iMQ Environment Variables

Environment Variable Description

JMQ_HOME This is the root iMQ installation directory in which all installed files are placed. On Windows, the installer sets JMQ_HOME to the iMQ installation directory. On Solaris and Linux, JMQ_HOME is manually set to /opt/SUNWjmq.

JMQ_VARHOME This is a directory in which all transient or dynamically-created configuration and data files are stored. On Windows JMQ_VARHOME is set to JMQ_HOME\var. On Solaris and Linux, JMQ_VARHOME is manually set to /var/opt/SUNWjmq.

Other Documentation Resources


Other Documentation ResourcesIn addition to this guide, iMQ provides additional documentation resources.

The iMQ Documentation SetThe following documents are included with the iMQ product, listed in Table 4 in the order in which you would normally use them:

Example Client ApplicationsA number of example applications that provide sample client application code are included in the following location:

JMQ_HOME/examples/jms

See the README file located in that directory.

Table 4 iMQ Documentation Set

Document Audience Description

iMQ Installation Guide Developers and administrators

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

iMQ Release Notes Developers and administrators

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

iMQ Migration Guide Developers and administrators

Explains differences between JMQ 1.1 and iMQ 2.0 and how to perform necessary conversions.

iMQ Developer’s Guide Developers Provides a quick-start tutorial and programming information relevant to the iMQ implementation of JMS.

iMQ Administrator’s Guide Administrators, also recommended for developers

Provides background and information needed to perform administrative tasks using iMQ administration tools.

13

Chapter 1

Introduction

This chapter provides an overall introduction to installing the iMQ product. The topics covered are:

• “iMQ Product Editions”

• “Supported Platforms and Products”

• “iMQ Software Modules”

• “Installing from Web and CD-ROM”

• “Upgrading from a Beta Version”

• “Installed Directory Structure”

• “Where To Go Next”

iMQ Product EditionsThe iPlanet Message Queue for Java product is available in three editions—trial, developer, and enterprise—each corresponding to a different licensed capacity, as described below.

Trial Edition This edition is for product evaluation purposes. It has a 90-day maximum duration license (expiration is enforced by the software). The license places no limit on the number of broker components implementing an iMQ Message Service nor on the number of client connections supported by each broker. You cannot use the Trial edition for deploying and running messaging applications in a production environment.

Supported Platforms and Products


Developer Edition This edition is for client application development purposes. It has an unlimited duration license. The license limits the number of brokers implementing an iMQ Message Service to three, and the number of client connections supported by each broker to five. The Developer edition also includes the Trial edition license; once you have developed and debugged a messaging application, you can use the Trial edition license to perform unlimited-connection load testing for a maximum 90-day period. You cannot use the Developer edition for deploying and running messaging applications in a production environment.

Enterprise Edition This edition is for deploying and running messaging applications in a production environment. You can also use the Enterprise edition for developing, debugging, and load testing messaging applications. It has an unlimited duration license. The license places no limit on the number of brokers implementing an iMQ Message Service nor on the number of client connections supported by each broker. However, the license limits the Message Service to one host and one CPU; An additional license is needed for each broker running on an additional host or CPU.

If you are upgrading from one edition to another, see the platform-specific instructions in subsequent chapters.

Supported Platforms and ProductsiMQ 2.0 is supported on Solaris, Linux, and Windows operating systems and platforms. It also requires the support of other technologies, as indicated in the following table. Other versions or vendor implementations can also be used but they are untested by iPlanet and therefore not supported.

Table 1-1 iMQ 2.0 Product Support Matrix

Platform/Product Supported Version

Java Development Kit (Sun Microsystems production versions only)

The iMQ broker and iMQ administration tools are supported on the 1.3.0_02 JDK/JRE only. The 1.3.0_02 JRE is bundled with iMQ 2.0.

iMQ client applications are supported as follows:

• Java 2 SDK, Standard Edition, version 1.3.0_02 (Solaris, Windows and Linux)1

• Java 2 SDK, Standard Edition, version 1.2.2_08 (Solaris) and 1.2.2_008 (Windows)2

• JDK 1.1.8_07 (Solaris) and JDK 1.1.8_007 (Windows)3

iMQ Software Modules

Chapter 1 Introduction 15

iMQ Software ModulesThe following table identifies the full set of software modules included with the iMQ product.

LDAP Directory Server (user repository and administered object support)

iPlanet Directory Server (Netscape Directory Server) version 4.12

Web Server (HTTP support)

• iPlanet Web Server, Enterprise Edition 4.1

• iPlanet Web Server, FastTrack Edition 4.1

Database (plugged-in persistence support)

Cloudscape (version 3.0)

Oracle 8i, version 8.1.7

JNDI (administered object support)

• JNDI version 1.2.1

• LDAP Service Provider version 1.2.2

• File System Service Provider version 1.2 Beta 3

Note: The File System Service Provider is supported for development and testing, but not for deployment in a production environment.

1. Download this JDK from: http://java.sun.com/products/jdk/1.3/index.html



Table 1-2 iMQ Software Modules

Module Contents

Broker The server-side software used to route and deliver messages. This module requires the Java runtime module.

Client runtime The client-side software needed to support client applications.

Administration tools The command-line utilities and GUI tools used to administer an iMQ messaging system. This module requires the client runtime and Java runtime modules.

Table 1-1 iMQ 2.0 Product Support Matrix (Continued)

Platform/Product Supported Version

Installing from Web and CD-ROM


Installing from Web and CD-ROMYou have the option of either downloading the iMQ 2.0 product from the iPlanet website or installing it from CD-ROM. For detailed instructions, see the platform-specific instructions in subsequent chapters.

Upgrading from a Beta VersionBecause iMQ 2.0 is not compatible with the Beta version, you should uninstall the Beta version (using procedures in the Beta documentation) before installing iMQ 2.0.

The uninstall operation, however, does not remove the Beta version’s JMQ_VARHOME directory. This directory (by default /var/opt/SUNWjmq on Solaris and Linux operating systems, and c:\Program files\JavaMessageQueue2.0\var on Windows systems) contains transient and security-related files. You should delete the Beta JMQ_VARHOME directory before installing iMQ 2.0.

Documentation Documentation needed by both client application developers and administrators: iMQ Installation Guide, iMQ Release Notes, iMQ Migration Guide, and iMQ Administrator’s Guide, as well as documentation only for developers: iMQ Developer’s Guide, API JavaDoc, and the JMS specification.

Example applications Example client applications.

Java runtime Version 1.3 Java Runtime Environment (JRE).

License The software needed to enable the licensed capacity of an iMQ messaging system.

Table 1-2 iMQ Software Modules (Continued)

Module Contents

Installed Directory Structure


Installed Directory Structure The install image below reflects a full Solaris installation (all packages) or a full (“Typical”) Windows installation. This image might vary if you perform a partial installation.

NOTE On Windows, the COPYRIGHT, LICENSE, and README files have a .txt filename extension.

Table 1-3 Installed Directory Structure

File/directory Contents

COPYRIGHT Copyright text file

LICENSE License text file

README README text file

bin directory Contains the executables for the broker (jmqbroker) and the following iMQ administration tools:

• iMQ Admin Console (jmqadmin)

• iMQ Command (jmqcmd)

• iMQ Object Manager (jmqobjmgr)

• iMQ User Manager (jmqusermgr)

• iMQ Database Manager (jmqdbmgr)

• iMQ Key Tool (jmqkeytool)

On Windows, the files named above have a .bat filename extension. This directory also includes the utility to install and uninstall the broker as a Windows Service (jmqsvcadmin) as well other executables (jmqbrokersvc).

Installed Directory Structure


doc directory User information (for developing, deploying, and administering iMQ applications) as well as developer reference information (JMS Specification and APIs).

The /doc/en/ (English) subdirectory contains the following files:

/setup subdirectory contains

• install.pdf (iMQ Installation Guide)

• relnotes.html (iMQ Release Notes)

/userguides subdirectory contains

• admin.pdf (iMQ Administrator’s Guide)

• developer.pdf (iMQ Developer’s Guide)

• migration.pdf (iMQ Migration Guide)

/apidoc subdirectory contains the iMQ and JMS API documentation distributed as Javadoc (html).

/jmsspec subdirectory contains the JMS API Specification.

etc directory (Solaris and Linux only)

A script that can be used for automatic startup.

examples directory Source code for and instructions on how to run client example applications.

lib directory The .jar files used to build and run iMQ client applications.

jre directory The JRE 1.3 files.

props directory The broker’s default configuration file.

var directory Working storage directory for iMQ. On Solaris and Linux, the var directory is /var/opt/SUNWjmq/. On Windows, the var directory is the var subdirectory of the installation directory.

var.init directory The files used to initially populate the var directory.

Table 1-3 Installed Directory Structure (Continued)

File/directory Contents

Where To Go Next


Where To Go NextWhen you are ready to install iMQ on a specific platform, see the appropriate chapter for your platform (Solaris, Linux, or Windows). Each chapter contains hardware and software requirements, installation procedures, and other relevant instructions, such as how to upgrade editions and how to proceed after installation.

Where To Go Next


21

Chapter 2

Solaris Installation

This chapter explains the following topics as they apply to a Solaris installation:

• “Hardware and Software Requirements”

• “Installing iMQ on Solaris”

• “Upgrading Editions”


• “Uninstalling iMQ on Solaris”

Hardware and Software Requirements


Hardware and Software RequirementsAt a minimum, your Solaris™ development system (SPARC™ Platform Edition) should satisfy the requirements indicated in the following table.

Installing iMQ on SolarisThe iPlanet Message Queue product can be downloaded from the iPlanet website or installed from the product CD-ROM. See the appropriate section below for details.

Table 2-1 Hardware and Software Requirements for Solaris

Component Requirements

Operating system • Solaris 2.6 (SunOS™ 5.6)

• Solaris 7 (SunOS 5.7, SPARC platforms)

• Solaris 8 (SunOS 5.8, SPARC platforms)

Note: To ensure proper operation of iMQ, you should install all required Solaris Patches for Java 2. For the latest information about the patches and to download the recommended and required patches, see:

http://java.sun.com/j2se/1.3/install-solaris-patches.html

(The iMQ software distribution CD includes the solaris/jdk-patches available at the time of release.)

CPU Sun Ultra™ 1 (or compatible) workstation that is TCP/IP networked

RAM 64 Mbytes

Hard drive space The compressed installation file is approximately 28 Mbytes. The temporary working directory used for extracting the installation files requires an additional 90 Mbytes.

The installed product requires approximately 49 Mbytes of hard drive space. iMQ, however, may need more space if the broker stores persistent messages locally.

Installing iMQ on Solaris

Chapter 2 Solaris Installation 23

Installing from the WebThe following instructions explain how to download and install the iMQ product on Solaris from the iPlanet website.

➤ To install iMQ on Solaris from the Web

1. Download the iMQ product from the website into an empty, temporary working directory.

2. Run the command script:

sh imq2_0-edition-solsparc.sh

where edition takes one of the following values: try, dev, or ent, depending on whether you are installing the Trial, Developer, or Enterprise edition, respectively.

The command displays the first page of the license for the product.

3. Read the product license. Installation and use of the product is subject to acceptance of the license agreement.

4. To display the entire license, one page at a time, repeatedly press the space bar. When you reach the end of the license, the program prompts you to accept the license.

❍ If you choose not to accept the license agreement, type no or n and the installation terminates.

❍ If you choose to accept the license agreement, type yes or y and the installation continues. The following files are extracted:

◗ README

◗ install.pdf (iMQ Installation Guide)

◗ relnotes.html (iMQ Release Notes)

◗ imq2_0-edition-solsparc.tar.Z

◗ COPYRIGHT

◗ LICENSE (a copy of the license agreement)

◗ imq2_0-api.tar.Z (a package that can be used by client application developers and which includes the components of iMQ that can be redistributed with client application code)

5. Uncompress the file archive:

uncompress imq2_0-edition-solsparc.tar.Z



6. Extract the archived files:

tar xvfp imq2_0-edition-solsparc.tar

A new directory, imq2_0-pkgs, is created.

7. Change directories:

cd imq2_0-pkgs

8. Become root:

su root

9. Run the pkgadd command to install the packages:

pkgadd -d ./

The pkgadd utility lists the names of all packages in the directory available for installation. When prompted, indicate you want to install all packages by typing:

all

By default, the iMQ product is installed into /opt/SUNWjmq/ with a few files placed in the /var/opt/SUNWjmq/ directory. If you need to install iMQ into a different directory, you can use the -R option of the pkgadd command, however in that case you will have to make the modifications noted at the end of this procedure.

10. Choose to install the broker for automatic or manual startup.

When installing the SUNWjqrtr package, the install script will ask if you want the broker (see Table 1-2 on page 15) to start automatically on system reboot. (If the broker is started automatically, it is not affected by any user logging on or logging off.)

❍ To install the broker to start automatically, type y.

❍ To install the broker to start manually, type n.

You can later decide to have the broker start automatically. Simply read and follow the instructions provided in the installed /opt/SUNWjmq/etc/jmq file.

11. When the pkgadd prompt returns, type q to quit.

12. Exit the root shell.

NOTE To avoid possible problems, do not use the GNU tar utility when installing iMQ.



13. Back up the imq2_0-edition-solsparc.sh file from your temporary working directory.

This is your logical media. Treat this file as you would any other installation media. Place a copy in a safe location in case you encounter a situation (such as a system failure) that requires reinstallation of the product.

14. Clean up all remaining files in your temporary working directory.

15. Reboot your machine if necessary.

If you installed the broker to start automatically, you can start the broker in one of two ways. Either reboot your machine, or type the following command:

/etc/init.d/jmq start

Installing from CD-ROMThe following instructions explain how to install the iMQ product on Solaris from CD-ROM.

NOTE If you chose in Step 9 to install iMQ in a root_path directory different from the default (using the -R option of pkgadd), you might need to make a few modifications, as described below:

If you are mounting root_path remotely as “/” to be used by a diskless client, you do not need to make any modifications in the default installation.

If you are running iMQ software locally, however, the installer placed iMQ files in the root_path/opt/SUNWjmq/ and root_path/var/opt/SUNWjmq/ directories. You need to set the iMQ environment variables accordingly (see “Environment Variable Conventions” on page 11):

setenv JMQ_HOME root_path/opt/SUNWjmqsetenv JMQ_VARHOME root_path/var/opt/SUNWjmq

Also, if you chose in Step 10 to install the broker for automatic startup, you need to make these same modifications in the iMQ environment variable settings in the iMQ startup scripts: root_path/etc/init.d/jmq and root_path/etc/rc*.d/*jmq (and copy these files to their respective /etc directories to enable automatic startup of the broker).

NOTE A compressed installation file (tar.Z) is provided on the CD if you do not want to install iMQ directly from the packages on the CD.



➤ To install iMQ on Solaris from CD-ROM

1. Log in as root or change to superuser.

For example, type the following at a command prompt:

su

Then type your superuser password.

2. Insert the iMQ CD into your CD-ROM drive.

If the Volume Manager™ software is running on your machine, the CD-ROM is automatically mounted to the /cdrom/iplanetmessagequeue2_0 directory.

If the Volume Manager is not running on your machine:

❍ Create a directory called /cdrom/iplanetmessagequeue2_0 by typing:

mkdir -p /cdrom/iplanetmessagequeue2_0

❍ Mount the CD-ROM manually:

mount -rF hsfs cdrom-device /cdrom/iplanetmessagequeue2_0

An example of cdrom-device is /dev/dsk/c0t0d0s0.

Open and read (using your preferred text editor) the LICENSE file located in the solaris/ directory of the CD.

❍ If you choose NOT to accept the license agreement, discontinue installation and contact the place where you purchased the product to determine the return policy.

❍ If you choose to accept the agreement, continue with the installation steps below.

3. Change to the directory on the CD containing the installation packages. For example, type:

cd /cdrom/iplanetmessagequeue2_0/solaris/imq2_0-pkgs

The contents of this directory vary depending on the product edition.

NOTE Volume Manager is a tool provided on Solaris that allows you to perform administrative tasks, such as mounting CD-ROMs, more easily. Volume Manager mounts a CD-ROM as /cdrom/name_of_media, where name_of_media is determined from the CD-ROM itself.



4. Run the pkgadd command to install the packages:

pkgadd -d ./

The pkgadd utility lists the names of all packages in the directory available for installation. When prompted, indicate you want to install all packages by typing:

all

By default, the iMQ product is installed into /opt/SUNWjmq/ with a few files placed in the /var/opt/SUNWjmq/ directory. If you need to install iMQ into a different directory, you can use the -R option of the pkgadd command, however in that case you will have to make the modifications noted at the end of this procedure.

5. Choose to install the broker for automatic or manual startup.

When installing the SUNWjqrtr package, the install script will ask if you want the broker (see Table 1-2 on page 15) to start automatically on system reboot. (If the broker is started automatically, it is not affected by any user logging on or logging off.)

❍ To install the broker to start automatically, type y.

❍ To install the broker to start manually, type n.

You can later decide to have the broker start automatically. Simply read and follow the instructions provided in the installed /opt/SUNWjmq/etc/jmq file.

6. When the pkgadd prompt returns, type q to quit.

7. Exit the root shell.

8. Reboot your machine if necessary.

If you installed the broker to start automatically, you can start the broker in one of two ways. Either reboot your machine or type the following command:

/etc/init.d/jmq start

Upgrading Editions


Upgrading EditionsiPlanet Message Queue comes in three editions, as explained in “iMQ Product Editions” on page 13.

To upgrade from the Developer edition to the Enterprise edition, you need to install the Enterprise edition license. This installation does not overwrite the iMQ modules already installed and does not modify the configuration of your iMQ messaging system.

To install the Enterprise edition license you need only the SUNWjqent package contained in the Enterprise edition. The SUNWjqent package is placed automatically in the imq2_0-pkgs directory (Web installation) or in the solaris/imq2_0-pkgs directory (CD-ROM installation) as a result of running the installation command script, uncompressing the file archive, and extracting the archived files.

NOTE If you chose in Step 4 to install iMQ in a root_path directory different from the default (using the -R option of pkgadd), you might need to make a few modifications, as described below:

If you are mounting root_path remotely as “/” to be used by a diskless client, you do not need to make any modifications in the default installation.

If you are running iMQ software locally, however, the installer placed iMQ files in the root_path/opt/SUNWjmq/ and root_path/var/opt/SUNWjmq/ directories. You need to set the iMQ environment variables accordingly (see “Environment Variable Conventions” on page 11):

setenv JMQ_HOME root_path/opt/SUNWjmqsetenv JMQ_VARHOME root_path/var/opt/SUNWjmq

Also, if you chose in Step 5 to install the broker for automatic startup, you need to make these same modifications in the iMQ environment variable settings in the iMQ startup scripts: root_path/etc/init.d/jmq and root_path/etc/rc*.d/*jmq (and copy these files to their respective /etc directories to enable automatic startup of the broker).

Where To Go Next


➤ To upgrade to Enterprise edition on Solaris

1. Stop any running brokers.

2. Follow the installation procedure in “Installing from the Web” on page 23, Step 1 through Step 7 or in “Installing from CD-ROM” on page 25, Step 1 through Step 3.

3. When the installation is finished, add the SUNWjqent package:

pkgadd -d . SUNWjqent

4. verify that the Enterprise edition license is available by running

jmqbroker -license

Where To Go NextRead the README and Release Notes (relnotes.html) files.

• The README includes information on where to find documentation, news and updates, and how to send feedback.

• The Release Notes might include last-minute information that was not available when the other documentation was sent to production. In addition, the Release Notes always contain information on code and documentation changes, open bugs, and important technical notes.

For an overview of iPlanet Message Queue for Java concepts, a brief introduction to writing and compiling a client application, see the iMQ Developer’s Guide.

For details on configuring brokers and managing an iMQ messaging system, see the iMQ Administrator’s Guide.

For class and member information used when writing a client application, browse the API documentation in the doc/en/apidoc/ directory of the installation.

To uninstall the product, see the following section.

Uninstalling iMQ on Solaris


Uninstalling iMQ on SolarisThe following instructions explain how to uninstall iMQ.

➤ To remove iMQ on Solaris

1. Stop the broker and any running client applications.

2. Determine which iMQ packages are installed.

To see a list of iMQ packages installed on your system using pkgadd, type:

pkginfo | grep SUNWjq

3. Become root by typing:

su

When prompted, type your root password.

4. Remove the iMQ packages that were installed with pkgadd.

Issue the following command:

pkgrm <packagename>

where <packagename> is a package name from the previous list.

To remove multiple packages, separate the package names by a space.

5. When prompted, confirm your removal request by typing y.

6. Perform any additional cleanup desired.

The pkgrm utility does not remove any files or directories created by the user after installation. For example, it does not remove broker configuration or persistence files in JMQ_VARHOME. If you want to remove such files or directories, use the standard Solaris commands for file and directory removal.

NOTE If you installed iMQ using the -R option of pkgadd, you must use that option as well with the pkginfo and pkgrm commands.

31

Chapter 3

Linux Installation

This chapter explains the following topics as they apply to a Linux installation:


• “Installing iMQ on Linux”

• “Upgrading Editions”


• “Uninstalling iMQ on Linux”

Hardware and Software RequirementsAt a minimum, your Linux development system should satisfy the requirements indicated in the following table.

Table 3-1 Hardware and Software Requirements for Linux


Operating system Red Hat Linux 6.2 (or compatible)

CPU Intel Pentium 166 MHz (or compatible) PC that is TCP/IP networked

RAM 64 Mbytes

Hard drive space The GNUZIP tar file containing the product is approximately 18 Mbytes.

The installed product requires approximately 49 Mbytes of hard drive space. iMQ, however, may need more space if the broker stores persistent messages locally.

Installing iMQ on Linux


Installing iMQ on LinuxThe iPlanet Message Queue for Java product can be downloaded from the iPlanet website or installed from the product CD-ROM. See the appropriate section below for instructions.

Installing from the WebThe following instructions explain how to download and install the iMQ product on Linux from the iPlanet website.

➤ To install iMQ on Linux from the Web

1. Accept the license agreement

2. Download the iMQ product from the website into an empty, temporary download directory, temp_directory.

The download tar file is: imq2_0-edition-linx86.tar.gz


3. Uncompress the downloaded file.

gunzip imq2_0-edition-linx86.tar.gz

This creates a single tar file, imq2_0-edition-linx86.tar

4. Become root on your system:

su root

5. Change to the /opt directory.

cd /opt

This is the recommended installation directory. If you install iMQ into a root_path directory different from /opt, you will have to make the corresponding modifications to the steps that follow, as well as the modifications noted at the end of this procedure.

6. Untar the archive:

tar xvfp temp_directory/imq2_0-edition-linx86.tar

The /opt/SUNWjmq directory and its contents are created.

Installing iMQ on Linux

Chapter 3 Linux Installation 33

7. Create the directory /var/opt/SUNWjmq:

mkdir -p /var/opt/SUNWjmq

This directory is used by the broker to store configurations, security information, and persistent messages.

8. Copy the contents of /opt/SUNWjmq/var.init to /var/opt/SUNWjmq:

cp -r /opt/SUNWjmq/var.init /* /var/opt/SUNWjmq

9. If you plan to use the broker (see Table 1-2 on page 15) as a user other than root, change permissions to allow reading and writing to the /var/opt/SUNWjmq directory:

chmod 777 /var/opt/SUNWjmq

10. Back up the imq2_0-edition-linx86.tar.gz file from your temporary working directory.

This is your logical media. Treat this file as you would any other installation media. Place a copy in a safe location in case you encounter a situation (such as a system failure) that requires reinstallation of the product.

Installing from CD-ROMThe following instructions explain how to install the iMQ product on Linux from CD-ROM.

➤ To install iMQ on Linux from CD-ROM

1. Log in as root or change to superuser.

For example, type the following at a command prompt:

su

Then type your superuser password.

NOTE If you chose in Step 5 to install iMQ in a root_path directory different from the default, you need to make the modifications described below:

If you installed iMQ files in the root_path/SUNWjmq/ and root_path/var/SUNWjmq/ directories. You need to set the iMQ environment variables accordingly (see “Environment Variable Conventions” on page 11):

setenv JMQ_HOME=root_path/SUNWjmqsetenv JMQ_VARHOME=root_path/var/SUNWjmq

Upgrading Editions


2. Insert the iPlanet Message Queue for Java CD into your CD-ROM drive and mount it.

mount /mnt /cdrom

This command may vary depending on the version of Linux being used. Check the mount man page on the system.

3. Change to the directory on the CD containing the installation tar file:

cd /cdrom/iplanetmessagequeue2_0/linux

The contents of this directory vary depending on the iMQ product edition.

4. Copy the iMQ tar file from the CD directory into an empty, temporary working directory, temp_directory.

The tar file is: imq2_0-edition-linx86.tar.gz


5. Continue with Step 3 under “Installing from the Web” on page 32.


To upgrade from the Developer edition to the Enterprise edition, you need to install the Enterprise edition license. This upgrade does not overwrite the iMQ modules already installed and does not modify the configuration of your iMQ messaging system.

To install the Enterprise edition license you need only extract the license file contained in the Enterprise edition and place it in your iMQ installation directory.

➤ To upgrade to Enterprise edition on Linux


2. Follow the installation procedure in “Installing from the Web” on page 32, Step 1 through Step 4 or in “Installing from CD-ROM” on page 33, Step 1 through Step 4.

Where To Go Next

Chapter 3 Linux Installation 35

3. Change to the root_path directory (where iMQ is installed).

For example, change to /opt if iMQ is installed in /opt/SUNWjmq.

4. Extract the iMQ license file:

tar xvf download_directory/imq2_0-ent-linx86.tar SUNWjmq/lib/lic/jmqbrokerunl.lic

This installs the license into the appropriate iMQ directory.

5. Verify that the Enterprise edition license is available by running

jmqbroker -license

Where To Go NextRead the README and Release Notes (relnotes.html) files.


• The Release Notes might include last-minute information that was not available when the other documentation was sent to production. In addition, the Release Notes always contain information on code and documentation changes, open bugs, and important technical notes.





Uninstalling iMQ on Linux


Uninstalling iMQ on LinuxThe following instructions explain how to uninstall iMQ on Linux.

➤ To remove iMQ on Linux

1. Stop any running client applications.

2. Stop the broker.

3. Become root:

su root

4. Remove the iMQ product.

Issue the /bin/rm command. For example, if the product is installed in /opt/SUNWjmq and /var/opt/SUNWjmq you could type:

rm -rf /opt/SUNWjmq

rm -rf /var/opt/SUNWjmq

37

Chapter 4

Windows Installation

This chapter explains the following topics as they apply to a Windows installation:


• “Installing iMQ on Windows”

• “Installation Defaults”

• “Troubleshooting Installation Problems”


• “Uninstalling iMQ on Windows”

Hardware and Software RequirementsAt a minimum, your Windows development system should satisfy the requirements indicated in the following table.

Table 4-1 Hardware and Software Requirements for Windows


Operating system Windows NT 4.0 Service Pack 5 and 6, Windows 2000, Windows 98 (client only), or Windows ME (client only)

CPU Intel Pentium 166 MHz (or compatible) workstation that is TCP/IP networked

RAM 64 Mbytes

Installing iMQ on Windows


Installing iMQ on WindowsThe iPlanet Message Queue for Java product can be downloaded from the iPlanet website or installed from the product CD-ROM.

The following instructions explain how to install the iMQ product either by downloading from the iPlanet website or using the CD-ROM.

➤ To install iMQ on Windows

1. Quit any other programs you are running.

2. Download the distribution into an empty, temporary working directory.

If you are installing from CD-ROM, insert the CD into the CD-ROM drive.

3. In the Windows Explorer, double-click the imq2_0-edition-win.exe file.

The installation file is extracted and setup is launched. If you are installing from CD-ROM, the setup program is started automatically.

4. Read the license agreement. Installation and use of the product is subject to acceptance of the license agreement.

Hard drive space The self-extracting installation file is approximately 15 Mbytes.

The temporary directory used for extracting the installation files requires an additional 26 Mbytes.

The installed product requires approximately 30 Mbytes. iMQ, however, may need more space if the broker stores persistent messages locally.

NOTE If you are installing iMQ after a previous uninstall, remove any references to the previous iMQ installation from the system’s PATH environment variable (Windows NT or 2000) or the autoexec.bat file (Windows 98 or ME) before reinstalling.

Table 4-1 Hardware and Software Requirements for Windows (Continued)


Installing iMQ on Windows

Chapter 4 Windows Installation 39

5. Follow the setup program’s instruction to select installation options.

a. Select the type of installation.

◗ Compact Includes only the files necessary to run the iMQ broker, administration, and client applications. No documentation or example client applications are installed.

◗ Custom Lets you specify which iMQ modules you want to install. Your options include the broker, client runtime, administration tools, documentation, example client applications, and Java runtime.

◗ Typical Installs all files, including broker, client runtime, administration tools, documentation, example client applications, and Java runtime.

◗ Capacity License Installs only the files necessary to enable the licensed capacity of an iMQ messaging system. This option does not overwrite the iMQ files already installed, and does not modify the configuration of your messaging system.

b. Select a location for the installation.

c. Select or create a folder for the Windows Start > Programs menu.

d. On NT and Windows 2000 operating systems, choose whether or not to install the iMQ broker as a Windows service. If you choose to install the broker as a Windows service, the broker will be started automatically at system startup and run in the background. This option is only available on Windows NT or 2000 systems and requires Windows Administrator Group privileges.

If you choose not to install the broker as a Windows service now but later change your mind, you can use the jmqsvcadmin utility to do so. See the iMQ Administrator’s Guide for information on using the jmqsvcadmin utility.

6. Restart your computer if prompted to do so.

Restarting the Windows operating system allows the System’s PATH environment variable to be updated and for services that rely on the PATH variable to pick up the new value.

7. Verify installation by choosing Start > Programs > iPlanet Message Queue 2.0 > iMQ Broker to run the iMQ broker.

You can also compile and run example applications located in the c:\Program Files\iPlanetMessageQueue2.0\examples\jms directory. See the iMQ Developer’s Guide.

Installation Defaults


Installation DefaultsThe following table indicates the installation defaults for Windows.

Troubleshooting Installation ProblemsIf the iPlanet Message Queue for Java installation program does not complete successfully on your Windows platform (for example, if it stops responding at some stage), try the following remedies. These remedies apply regardless of whether you installed the product from CD-ROM or downloaded it from the Web.

➤ To troubleshoot installation problems on Windows

1. Use the Windows Task Manager to end the iMQ installation program.

2. Clear any temporary directories (for example, temp or tmp).

3. Start the iMQ installation again, being certain to install to the same directory as the initial installation attempt.

If your Windows installation of the iMQ product is still not successful, try this more comprehensive procedure:

1. Use the Windows Task Manager to end the iMQ installation program.

2. Clear any temporary directories (for example, temp or tmp).

3. In the Services control panel, temporarily stop any non-Windows network-related services (for example, a Solstice NFS Server service).

Table 4-2 Windows Installation Defaults

Installation directory The product is installed into:

C:\Program Files\iPlanetMessageQueue2.0\

Environment Variables JMQ_HOME: The installer automatically sets the JMQ_HOME environment variable to the installation directory.

JMQ_VARHOME: The installer automatically sets the JMQ_VARHOME environment variable to JMQ_HOME\var.

PATH: The installer automatically sets PATH to %PATH%;%JMQ_HOME%\bin. This enables you to run utilities, such as jmqcmd, without specifying the entire path.

Upgrading Editions


4. Delete the iPlanet Message Queue for Java 2.0 directory and all its contents.

5. In your Systems control panel, remove all references to iMQ 2.0 from your environment settings.

6. Restart your Windows operating system.

7. Reinstall iMQ to the same location as the initial failed installation.

8. Reset any services in the Services (Control Panel) that you stopped in Step 3.


You can upgrade from the Developer edition to the Enterprise edition by installing the Enterprise edition. The Enterprise edition is available from the iPlanet website.

➤ To upgrade to Enterprise edition on Windows


2. Follow the installation procedure explained in “Installing iMQ on Windows.” Choose the option Capacity License when it appears on your screen.

This setup does not overwrite the iMQ modules installed, and does not modify the configuration of your iMQ messaging system.

Where To Go NextRead the README.txt file and the iMQ Release Notes (relnotes.html).


• The iMQ Release Notes might include last-minute information that was not available when the other documentation was sent to production. In addition, the Release Notes always contain information on code and documentation changes, open bugs, and important technical notes.


Uninstalling iMQ on Windows





Uninstalling iMQ on WindowsThe following instructions explain how to uninstall iMQ on Windows.

➤ To remove iMQ on Windows

1. Stop any running client applications.

2. Stop the broker.

If you installed the broker as Windows service, you can stop it as follows:

❍ From the Windows Start menu, choose Settings, then Control Panel.

❍ Double-click the Services icon.

❍ In the Services panel, select the JMQ Broker entry then click Stop.

❍ Close the Services panel.

3. Remove the iPlanet Message Queue for Java product.

❍ From the Windows Start menu, choose Programs.

❍ From the iPlanet Message Queue for Java 2.0 program group, choose Uninstall.

❍ After Uninstall completes, remove any leftover files.

The Windows Uninstall utility does not remove any files or directories installed into the product directory that were later modified. It also does not remove any files or directories created by the user as a result of product operations.

If you want to remove such files or directories, you can do so using the standard Windows methods of file and directory removal. For example, from the command line you could type:

DRIVE:\>cd path-to-installed-iPlanetMessageQueue

DRIVE:\>rmdir iPlanetMessageQueue2.0 /s /q



4. Manually remove iMQ references from your environment.

❍ From the Windows Start menu, choose Settings.

❍ In the Control Panel, double-click the System icon.

❍ On the Environment page, select the PATH environment variable and remove the iPlanetMessageQueue2.0 reference from the value.

❍ Click Set then OK.

❍ If you installed on Windows 98 or ME, open your Windows autoexec.bat file and remove the two lines that reference the iPlanet Message Queue for Java 2.0 installation. The lines to be removed will be similar to the following:

SET JMQ_HOME=C:\Program Files\iPlanetMessageQueue2.0

SET PATH=%PATH%;"C:\Program Files\iPlanetMessageQueue2.0\bin"

iplanet message queue for java installation guide, version 2 · 2011-02-09 · programming...

Documents