Chapter 4 Windows Installation
This chapter explains the following topics as they apply to a Windows installation of Sun Java System Message Queue 3.7 UR1:
Hardware and Software Requirements
At a minimum, your Windows system should satisfy the requirements indicated in the following table.
Table 4–1 Hardware and Software Requirements (Windows)|
Component |
Requirements |
|---|---|
|
Operating system |
Windows XP Professional SP2 Windows 2000 all editions, SP4 or higher Wondows Server 2003, Enterprise Edition |
|
CPU |
Intel Pentium 3 |
|
RAM |
256 MB |
|
Disk space |
The installation file containing the product is approximately 7 MB. The installed product requires approximately 13 MB. 125 MB are needed if a new Java runtime must be installed. Message Queue, however, may need more space if the broker stores persistent messages locally. |
|
Java 2 Platform, Standard Edition (J2SE) |
See Supported Platforms and Components for the supported versions of the Java Runtime Environment (JRE) and Java Software Development Kit (JDK) that are supported on Linux. The Message Queue software distribution includes the required JRE version at the time of release. |
Message Queue also depends upon other technologies, as shown in Supported Platforms and Components.
Installing Message Queue on Windows
The Sun Java System Message Queue product can be downloaded from the Sun Java System Web site. Message Queue also depends upon components that you must install to be able to develop and run Message Queue clients. See Table 1–1 and Table 1–2 for more information.
The following instructions explain how to install the Message Queue product.
Upgrading from Previous Versions
To upgrade from prior Message Queue versions, it is recommended that you first uninstall Message Queue software as described in the Message Queue Installation Guide of the appropriate version, before installing Sun Java System Message Queue 3.7 UR1.
If you want to preserve data from a previous version of Message Queue when you migrate from an older version, refer to Migration Issues prior to uninstalling Message Queue.
If you are installing Message Queue after a previous uninstall, check that any references to the previous Message Queue installation have been removed from the system’s PATH environment variable.
Installed Directory Structure
Table 4–2 shows the installed directory structure for Message Queue 3.7 UR1 on the Windows platform. Paths shown are relative to the Message Queue base directory (root installation directory), represented by the IMQ_HOME directory variable.
Note –
File locations for Message Queue bundled with Sun Java System Application Server may differ from those shown in the table.
Table 4–2 Installed Directory Structure (Windows)
|
Windows |
Contents |
|---|---|
|
IMQ_HOME\README.txt |
README text file |
|
IMQ_HOME\bin |
Executable files for the following administration tools:
All executable files have the filename extension .exe. This directory also includes other executables (imqbrokersvc). |
|
IMQ_HOME\lib |
Support files for Message Queue Java client runtime.
Support files for Message Queue tools and processes Libraries to support C client applications Note – See Supported Platforms and Components for the versions of Netscape Portable Runtime (NSPR) and Network Security Service (NSS) needed to support the C API. |
|
IMQ_HOME\lib\props |
Broker's default configuration files |
|
IMQ_HOME\lib\ext |
Files needed for JDBC-based persistence |
|
IMQ_HOME\lib\help |
Message Queue help files |
|
IMQ_HOME\lib\images |
Admin GUI image files |
|
IMQ_HOME\var |
Message Queue working storage |
|
IMQ_HOME\var\instances |
Configuration properties, file-based persistent data stores, log files, flat-file user repositories, and access control properties files for individual broker instances |
|
IMQ_HOME\javadoc |
Message Queue and JMS API documentation in JavaDoc format |
|
IMQ_HOME\demo |
Example Java client applications |
|
IMQ_HOME\demo\C |
Example C client applications |
|
IMQ_HOME\include |
Header files to support C client applications |
|
IMQ_HOME\etc |
License files and instance template files |
Installing Message Queue
Follow these steps to install Message Queue 3.7 UR1 on Windows.
To Install Message Queue on Windows
-
Unzip the bundle mq_37–ent-win.zip.
-
Edit the file $TOP/mq/etc/imqenv.conf to set the IMQ_DEFAULT_JAVAHOME variable to specify a JDK 1.5.0 runtime. For example:
set IMQ_DEFAULT_JAVAHOME=c:\Program Files\Java\jre1.5.0_09
-
Change directories to $TOP/mq/bin.
-
Start the broker using the following command.
./imqbrokerd -tty
Running Sample Applications
After installing Message Queue, you can compile and run example applications located in the c:\Sun\MessageQueue\demo directory. See the Message Queue Developer's Guide for Java Clients or the Sun Java System Message Queue 3.7 UR1 Developer’s Guide for C Clients for additional instructions.
To run JMS client applications, include the following jar files in your classpath.
|
$TOP/mq/lib/jms.jar |
|
$TOP/mq/lib/imq.jar |
Troubleshooting Installation Problems
If the Message Queue installation program does not complete successfully on your Windows platform, use the following procedure to correct the problem.
To Troubleshoot Installation Problems on Windows
-
Clear any temporary directories (for example, temp or tmp).
-
Clear any temporary directories (for example, temp or tmp).
-
In the Services control panel, temporarily stop any non-Windows network-related services (for example, a Solstice NFS Server service).
-
Delete the MessageQueue directory and all its contents.
-
In your Systems control panel, remove all references to MessageQueue from your environment settings.
Example: IMQHOME and PATH environment variables.
-
Restart your Windows operating system.
-
Reinstall Message Queue in the same directory location as the initial failed installation.
-
Reset any services in the Services (Control Panel) that you stopped in Troubleshooting Installation Problems.
Uninstalling Message Queue on Windows
The following instructions explain how to uninstall Message Queue on Windows.
To Remove Message Queue on Windows
-
Stop any running client applications.
-
Stop any running brokers. (You will be prompted for the admin user name and password.)
imqcmd shutdown bkr [-b hostName:port]
If you had installed the broker as a Windows service, you can stop it as follows:
-
Unless you want to retain dynamic data, the Message Queue flat file user repository, and the Message Queue access control properties file associated with each broker instance, remove this data using the following command.
imqbrokerd -name instanceName -remove instance
-
Delete the folder containing the Message Queue 3.7 UR1 files.
This is the same folder into which you decompressed the mq3_7-ent-win.zip file when installing Message Queue 3.7 UR1.
Where To Go Next
Read the README and Message Queue Release Notes files.
-
The README includes information on where to find documentation, news and updates, and how to send feedback.
-
The Message Queue Release Notes contain information on code and documentation changes, open bugs, and important technical notes. This document is available on the Sun Java System documentation Web site.
For an overview of Sun Java System Message Queue concepts, see the Message Queue Technical Overview.
For a brief introduction to writing and compiling a client application, see the Message Queue Developer's Guide for Java Clients or the Message Queue Developer's Guide for C Clients.
For details on configuring brokers and managing a Message Queue messaging system, see the Message Queue Administration Guide.
For class and member information used when writing a client application, browse the API documentation in the IMQ_HOME\javadoc directory.
To uninstall the product, see the following section.
- © 2010, Oracle Corporation and/or its affiliates