This document describes how to install Sun Java System Messaging Server 6.3 64–bit Edition. In future releases, this installer will include other Communications Suite components.
In addition to being able to install Messaging Server 64–bit edition, this installer also allows you install the 32–bit version.
This technical note contains the following sections:
Version |
Date |
Description of Changes |
---|---|---|
1 |
July 2007 |
Initial release of this technical note. |
The Sun Java System Messaging Server 6.3 64–bit Installer is a different installer from its previous version, the Communications Suite 5 Installer (which includes Sun Java System Messaging Server 6.3). See the following table of changes:
Table 1 Differences Between Messaging Server 6.3 64–bit Installer and Communications Suite 5 Installer (which includes Messaging Server 6.3)
Sun Java System Messaging Server 6.3 64–bit Installer |
Communications Suite 5 Installer |
Installs Messaging Server Installs required Shared Components and Operating System patches for Messaging Server Installs Veritas Cluster Agent, but not Sun Cluster Agent or Sun Cluster software (You can get Sun Cluster from the Communications Suite 5 Installer). |
Installs Java Enterprise System components (such as Directory Server, Sun Cluster) Installs Communications Suite: Messaging Server, Calendar Server, Delegated Administrator, Communications Express as well as Sun Cluster Agent or Veritas Cluster Agent |
Text-based Installer |
GUI-based installer and text-based installer |
No product registry; uses package database to determine whether a package is installed or partially installed. |
Uses Product Registry |
Installs 32–bit and 64–bit editions |
Installs 32–bit edition. |
The following feature is not available in this release:
Upgrade: In this release, there is no automatic upgrade utility to go from Communications Suite 5 (Sun Java System Messaging Server 6.3) to Sun Java System Messaging Server 6.3 64–bit Edition. However, you are able to manually upgrade to this version of Messaging Server by choosing from three upgrade processes. See: Upgrading Messaging Server.
This section covers the following pre-installation topics:
Before you install components, use the steps in this section to make sure the system on which you are installing is ready.
The performance of your messaging server depends on many factors, including CPU power, available memory, disk space, file system performance, usage patterns, network bandwidth, and so on. For example, throughput is directly related to file system performance. If you have questions about sizing and performance, contact your Sun Java System representative.
Make sure you are the root user for the system.
Have at least 2.2 GB free disk space for the unzipped image.
Have the image already unzipped.
Make sure that the /etc/resolv.conf file has name server entries with the IP addresses of valid name servers. For example:
domain comms.beta.com nameserver 192.168.100.22 nameserver 192.168.100.23 nameserver 192.168.100.24 nameserver 192.168.100.25
Make sure that the /etc/hosts file has an entry for the fully qualified host name of the server. This fully qualified host name should be listed before the non fully qualified host name. For example:
10.1.82.52 wireless.comms.beta.com wireless loghost
Make sure that the /etc/nsswitch.conf file is configured to use files first to resolve host names. The hosts line in the nsswitch.conf file should list files first in its entry:
hosts: files dns nis [NOTFOUND=return]
Or, if NIS is not used:
hosts: files dns
On Solaris 10 platforms, you not only have to add the Fully Qualified Domain Name (FQDN) to the /etc/hosts file, but also to the /etc/inet/ipnodes file.
Otherwise, you'll get an error indicating that your host name is not a fully qualified domain name (FQDN).
The following file systems are recommended for message stores:
LUFS (Logging UFS).
VxFS (Veritas File System). Veritas File System provides good system performance if configured properly. If you use VxVM, the Veritas Volume Manager, you need to carefully watch that the volumes and the log file for the volumes are set to be regularly striped.
HAStoragePlus File System for Sun Cluster installations. The HAStoragePlus File System provides better performance than the default Sun Cluster Global File System.
NFS (Network File System).
You can use NFS on MTA relay machines for LMTP, for autoreply histories, and for message defragmentation. (See the Sun Java System Messaging Server 6.3 Administration Guide). In addition, NFS can be supported on BSD-style mailboxes (/var/mail/ ) as well as for the Message Store. The following versions of NFS have been certified for use with Messaging Server: Sun StorEdge 5310 NAS Appliance.
The 64–bit release supports the following platforms:
64–bit version Solaris 9 Operating System Update 2 (SPARC® Platform Editions) with required patches
64–bit Solaris 10 Operating System SPARC and 64–bit x86 Platform Editions including Zones Support
Any required 64–bit Hardware. See Solaris 64–bit documentation.
The following platforms are not supported:
The 64–bit version of the installer is not supported on Linux
Messaging Server is no longer supported on HP-UX and Windows
The 32–bit release supports the following platforms:
Solaris 9 Operating System Update 2 (SPARC and x86 Platform Editions) with required patches
Solaris 10 Operating System (SPARC and x86 Platform Editions) including Zones Support
Red Hat Enterprise Linux Advanced Server, versions 3 (all updates) and 4 (all updates).
Red Hat Enterprise Linux Enterprise Server, versions 3 (all updates) and 4 (all updates)
For the most current list of required patches for Sun Java System Messaging Server go to http://sunsolve.sun.com and select either “Patches” or “Patch Portal”. As operating system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.
The installer checks for required platform patches. You must install all required patches or the installation process will not continue.
At the time of general release, the following Messaging Server 6.3 32–bit upgrade patches are available:
Solaris Platform |
Patch Number (English) |
---|---|
SPARC |
120228–21 |
x86 |
120229–21 |
The following Messaging Server 6.3 product packages are part of this release:
English |
Localized Version |
---|---|
32–bit: SUNWmessaging-server |
32–bit: SUNWmessaging-server-l10n |
64–bit: SUNWmessaging-server-64 |
64–bit: SUNWmessaging-server-l10n–64 |
The following topics are described in this section:
You can get the Sun Java System Messaging Server 6.3 64–bit Edition software as a Web download.
You can download a compressed archive of all installation files from the Sun Download Center at http://www.sun.com/downloads. The Messaging Server installation files are available in zip images: one for SPARC and one for x86 platforms.
The commpkg command enables you to run the Messaging Server 6.3 64–bit Edition installer. This command lays down the Messaging Server installation bits on your machine, but it does not configure Messaging Server. To configure Messaging Server after installation, see Chapter 1, Post-install Tasks and Layout, in Sun Java System Messaging Server 6.3 Administration Guide in the Sun Java System Messaging Server 6.3 Administration Guide.
commpkg [general options] verb [verb-specific options] |
The general options for this command are:
Option |
Description |
---|---|
-? or —help |
Displays Help |
-V or —version |
Displays Version of Messaging Server |
The verb is one of the following:
Verb |
Description |
---|---|
install |
Performs Messaging Server installation |
uninstall |
Performs Messaging Server uninstallation |
Automatic Upgrade is not available at this time. You can perform a manual upgrade by following the procedures in Upgrading Messaging Server.
The verb-specific options can be one or more of the following:
verb-specific options |
Description |
---|---|
—excludeOS |
Do not apply Operating System patches during product installation |
—excludeSC |
Do not install, upgrade, or patch any Shared Components |
—acceptLicense |
Accept the license conditions in the LICENSE.txt file |
—altroot |
Specify an alternate root directory during a multi-host installation. The INSTALLROOT (the top level installation directory for all products and shared components) will be the alternate root. |
—distro path |
Specify the path to packages/patches for the products Default: Location of commpkg script |
—installroot path |
Specify the path of INSTALLROOT, the top level installation directory for Messaging Server. . Note – The subdirectories for individual Communications Suite products (which will be a part of this installer at later releases) will be under the INSTALLROOT. |
—silent INPUTFILE |
Run silent installation, taking the inputs from the INPUTFILE and the command line arguments. The command line arguments override entries in the INPUTFILE. Installation proceeds without interactive prompts. Use —dryrun to test silent installation. |
—dry-run or -n |
Does not install Messaging Server. Performs checks. |
—upgradeSC [y|n] |
Indicate whether or not to upgrade shared components as required. Warning: Upgrading Shared Components is irreversible. However, if you do not upgrade required shared components, products might not work as designed. Note: If the [y|n] is not specified, you will be prompted for each shared component that needs to be upgraded. Default: n The —excludeSC flag has precedence over this flag. |
—auditDistro |
Audit the installation distribution to verify that the required patches and packages are present and that the packages have the correct versions. |
—pkgOverwrite |
Overwrite the existing installation package. You might use this option when you are installing a shared component in a global zone where either the shared component does not exist in a global zone, or the shared component exists in the whole root zone. The default is not to override the existing package. In general, shared components should be managed in the global zone. |
Log on as root to become a superuser.
Start the text-based installer. Use the commpkg usage as described in commpkg usage. When commpkg is invoked, a log file will record the installation parameters.)
# ./commpkg install -- LOGFILE: /tmp/CommsInstaller_20070501132825.log |
Accept the License Agreement. If you have already read the agreement in its entirety, you have the option of skipping the agreement and accepting the terms. To accept the terms of the agreement without viewing the entire license agreement, hit Enter to continue, then enter n to skip reading the agreement, and enter yes to accept the terms.
Specify Installation Location where server files will be installed (also known as the INSTALLROOT) or accept the default location.
The default INSTALLROOT has changed from /opt/SUNWmsgsvr to /opt/sun/comms/messaging (for 32–bit installations) and /opt/sun/comms/messaging64 (for 64–bit installations)
After specifying the INSTALLROOT, notices for Operating System and Shared Components patches may appear if previous versions of patches are installed on the machine.
Select Products to Install
In this release, there are four products: Messaging Server 6.3, Messaging Server 6.3 (Localized Version), Messaging Server 6.3 64–bit, and Messaging Server 6.3 64–bit (Localized Version).
Generate List of Items to Install
In this step, the installer lists all the products as well as shared components that will be installed or upgraded. If items need to be upgraded, the installer will give you the choice to upgrade.
Remember, upgrading shared components is an irreversible process. However, if you do not install the correct version of the shared components, the product may not work as designed. So, proceed carefully when installing and upgrading shared components and products.
Once you determine what you are going to install and upgrade, the installer will create a summary.
Ready to Install
Once you specify the components you're installing and upgrading, the installer is ready to install Messaging Server files into INSTALLROOT.
If everything installs properly, you will see All tasks PASSED in the summary panel.
Log Files
Once installation has completed, time-stamped log files are created like in the following example:
To undo your installation, go to your undoCommsInstall script like the following example:/var/opt/CommsInstaller/logs/undoCommsInstall_20070501135358
To run silent installation for multiple installations, use the silent installation file like in the following example:/var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358
The installer creates a log file of the installation process in the following location. For example:/var/opt/CommsInstaller/logs/CommsInstaller_20070501135358.log
Undo Installation
If you want to remove the installation that you just ran, you can undo your installation by running the undoCommsInstall script like the following example:/var/opt/CommsInstaller/logs/undoCommsInstall_20070501135358.
Undo reverses the specific steps taken during installation. It will also undo Shared Component installations. If, however, you want to pick and choose specific components to uninstall, use the commpkg uninstall command: Uninstalling Messaging Server. The uninstaller does not uninstall shared components.
Directory Layout
In the INSTALLROOT (default: /opt/sun/comms), you may see the following directories:
CommsInstaller, where a copy of the Installer resides.
The log files listed in the previous step are located in the /var/opt/CommsInstaller/log directory. If you install Messaging Server in an alternate root, the logfiles are located in the alternate root's INSTALLROOT/var/opt/CommsInstaller/log directory.
messaging, the 32–bit Messaging Server version
messaging64, the 64–bit Messaging Server version
If you run the installer in Silent mode, you are running a non-interactive session. The installation inputs are taken from a silent installation file (also known as a state file), from command line arguments, or defaults.
To run a silent installation, follow these steps:
Run an interactive installation session. (See To Begin Installation.) A state file similar to /var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358 is automatically created.
Copy the state file to each host machine and edit the file as needed. See Silent Mode File Format.
Run the silent installation on each host. See the silent installation usage in commpkg usage.
Command-line arguments override the values and arguments in the state file.
The silent mode file (also known as a state file) is formatted like a property file: blank lines begin with a number sign (#) and properties are key/value pairs separated by an equals (=) sign. You can change the following parameters:
VERB— indicate which function to perform. For example VERB=install
You can add CLI arguments described in commpkg usage, however the —dry-run argument cannot be added to the install function in the state file.
ALTDISTROPATH— indicate an alternate distro path if —distro is not specified. For example, ALTDISTROPATH=SunOS5.10_i86pc_DBG.OBJ/release
PKGOVERWRITE— set this flag if you want to overwrite the existing installation packages. For example, PKGOVERWRITE=YES
INSTALLROOT— specify installation root. For example, INSTALLROOT=/opt/sun/comms
ALTROOT— set this flag if you want to use an alternate root. For example, ALTROOT=yes
EXCLUDEOS— set this flag if you don't want to upgrade Operating System patches. For example, EXCLUDEOS=YES
COMPONENTS— list the components you want to install. For example:
COMPONENTS=MS64 for 64–bit Messaging Server.
COMPONENTS=MS64_L10N for localized 64–bit Messaging Server.
COMPONENTS=MS for 32–bit Messaging Server.
COMPONENTS=MS_L10N for localized 32–bit Messaging Server.
ACCEPTLICENSE- indicate whether or not to accept license. For example, ACCEPTLICENSE=yes.
This property must be specified either in the state file or as a command line argument.
UPGRADESC– indicate whether all shared components should or should not be upgraded without prompting. For example, UPGRADESC=no
For handling shared components, you have two options:
Don't install shared components. To do this, run the installer program with the —excludeSC flag. See commpkg usage.
Install the shared component dependencies such as in the Non-global sparse root zone scenario. This option installs only the shared components that are necessary for the products you are installing. To do this, add a ~ (tilde) to the component number you want to install in the sparse zone. For example, if you plan to install Messaging Server 64–bit in the sparse zone, you select ~3 during the global zone installation. The installer will know to only install dependencies and not the product itself.
Unlike the previous version of the installer, this version allows multiple installations of the same product version on the same machine by using different INSTALLROOTS.
To do so, install the product in the alternate root with the —altroot flag:
Install OS patches and Shared Components in the default INSTALLROOT. See To Begin Installation. To only install the shared components, add a ~ (tilde) to the component number you want to install in the alternate root. For example, if you plan to install Messaging Server 64–bit in the alternate root, you select ~3 during the default installation. The installer will know to only install dependencies and not the product itself.
OS patches are always applied in the default INSTALLROOT, never in the alternate root.
Install Shared Components and Messaging Server in the Alternate Root like the following example:
commpkg install —altroot —installroot /opt/sun/comms2
Be sure to use —installroot with —altroot to specify the alternate root.
You may create as many alternate roots as you would like. However, you should manually keep track of all the alternate roots you have created.
This section explains how to install Messaging Server on Solaris 10 Zones. For an overview of Solaris 10 with Messaging Server, see: Overview of Solaris Zones in Sun Java Communications Suite 5 Installation Guide.
This section describes how to install Messaging Server in the four Solaris 10 Zone scenarios:
Global zone with existing non-global zones
Global zone with no existing non-global zones
Non-global whole root zone
Non-global sparse root zone
This Zone scenario is not recommended for Messaging Server implementation. It requires the same version of shared components be running on each zone. Futhermore, the global zone should be reserved for administrative zone support.
If you install Messaging Server in a global zone with existing non-global zones, you install the appropriate OS patches, shared component patches, and Messaging Server product into the global zone. It will propagate the shared component patches into the non-global zones. To install Messaging Server in a global zone with existing non-global zones:
Follow pre-installation requirements as described in Preparing for Installation
Run the installer in the global zone by following the steps in To Begin Installation.
If you install Messaging Server in a global zone with no existing non-global zones, you need to prepare your installation as if you might add non-global zones in the future. Modifying your deployment at a later time becomes difficult if you don't plan for this step. To do this, follow the steps inGlobal zone with existing non-global zones.
The non-global whole root zone scenario is the equivalent of installing Messaging Server on a single box with no zones. Simply install Messaging Server as described in To Begin Installation.
Any operations performed in the global zone (such as installations, uninstallations, and patching) affects the whole root zones.
To install Messaging Server in a non-global sparse root zone, you first need to install/upgrade the applicable OS patches and shared components in the global zone. You are unable to do so in the sparse root zone, because the /usr directory (where the shared components reside) is a read-only directory in the sparse root zone.
Follow pre-installation requirements as described in Preparing for Installation.
Verify that you are about to install the shared components and OS patches in the global zone and not the sparse root zone.
Run the installer in the global zone and only install/upgrade the OS patches and the Shared Components:
commpkg install -upgradeSC y
See the Installing Shared Components.
Do not install Messaging Server in the global zone. To do this, add a ~ (tilde) to the component number you want to install in the sparse zone. For example, if you plan to install Messaging Server 64–bit in the sparse zone, you select ~3 during the global zone installation. The installer will know to only install dependencies and not the product itself.
Once you have the shared components and OS patches installed, install Messaging Server in the sparse root zone by following the steps in the To Begin Installationsection.
Now that you've performed the basic installation of Messaging Server, this section describes the next steps:
After installing Messaging Server 6.3 64–bit Edition, prepare your directory server for Messaging Server configuration. To do so, run the following script on your directory server machine:/opt/SUNWcomds/sbin/comm-dssetup.pl. See: Running the Directory Preparation Tool in Sun Java Communications Suite 5 Installation Guide
Running the Directory Preparation Tool is only for new configurations, not for configurations created with the migrate-config tool which is described in Upgrading Messaging Server.
After installing Messaging Server 6.3 64–bit Edition and running the comm-dssetup.pl script, run the configure program to create an initial runtime configuration to complete your installation and initial configuration of Messaging Server. For example, if you installed 64–bit Messaging Server, run /opt/sun/comms/messaging64/sbin/configure. For detailed instructions, see: Creating the Initial Messaging Server Runtime Configuration in Sun Java System Messaging Server 6.3 Administration Guide.
Creating an Initial Running Configuration is only for new configurations, not for configurations created with the migrate-config tool which is described in Upgrading Messaging Server.
This section describes three manual options to upgrade to this version of 32–bit or 64–bit Messaging Server:
Choose the first option (To Migrate from 32–bit to 64–bit Messaging Server) if you want to change your existing 32–bit Messaging Server and migrate your data to a 64–bit Messaging Server in a side-by-side upgrade. Note that you will use new directory paths (such as INSTALLROOT) in the upgraded version.
Choose the second option (To Perform a 32–bit to 32–bit Upgrade (Side–by-Side)) if you want a conservative approach to upgrade and an easy method to back out of the upgrade. (Just revert to the old version and stop using the new version.) You can only use this option in a 32–bit to 32–bit upgrade. Note that the upgrade process takes longer to set up. You will use new directory paths (such as INSTALLROOT) in the upgraded version.
Chose the third option (To Perform a 32–bit to 32–bit Upgrade (In place)) if you want a faster method to upgrade. Back out is not as easy as the side-by-side approach. You can only use this option in a 32–bit to 32–bit upgrade. Note that you will use the old directory paths (such as msg-svr-base) in the upgraded version.
If you have a previous version of Messaging Server (32–bit) installed and configured on your system and you want to migrate your data to the 64–bit version, you can do so by following these steps for a side-by-side upgrade:
Using the Messaging Server 6.3 64–bit edition installer, install the 64–bit version of Messaging Server on the same system as your previous version of Messaging Server, but in a different directory (for example, in this procedure, /opt/sun/comms/messaging64/). See To Begin Installation.
To migrate the configuration and Message Store data from the previous version of Messaging Server, run the migrate-config (migration configuration) utility:
/opt/sun/comms/messaging64/sbin/migrate-config old-msg-svr-root
For example:
/opt/sun/comms/messaging64/sbin/migrate-config /opt/SUNWmsgsr
Run /opt/sun/comms/messaging64/sbin/patch-config.
Run /opt/sun/comms/messaging64/sbin/install-newconfig.
To back out the migration, run /opt/sun/comms/messaging64/sbin/migrate-config -u /opt/SUNWmsgsr, where -u is the undo flag.
Once you complete the migration, stop using the old server-root directory:
Update their PATH, any scripts referencing the old server-root location.
If you are using Legato Networker, be sure to update the server-root location in the configuration.
Replace the server-root location with the server-root binary location.
Start the new server with the following command:
/opt/sun/comms/messaging64/sbin/start-msg
If you need to back out the migration, use the —u (undo) flag:
/opt/sun/comms/messaging64/sbin/migrate-config —u old-base-dir
where old-base-dir is the old server-root directory.
To restart the old Messaging Server, use: old-base-dir/sbin/start-msg
Using the Messaging Server 6.3 64–bit edition installer, install Messaging Server on the same system as your previous version of Messaging Server, but in a different directory (for example, in this procedure, /opt/sun/comms/messaging/). See To Begin Installation.
To migrate the configuration and Message Store data from the previous version of Messaging Server, run the migrate-config (migration configuration) utility:
/opt/sun/comms/messaging/sbin/migrate-config old-msg-svr-root
For example:
/opt/sun/comms/messaging/sbin/migrate-config /opt/SUNWmsgsr
Run /opt/sun/comms/messaging/sbin/patch-config.
Run /opt/sun/comms/messaging/sbin/install-newconfig.
To back out the migration, run /opt/sun/comms/messaging/sbin/migrate-config -u /opt/SUNWmsgsr, where -u is the undo flag.
Once you complete the migration, stop using the old server-root directory:
Update their PATH, any scripts referencing the old server-root location.
If you are using Legato Networker, be sure to update the server-root location in the configuration.
Replace the server-root location with the server-root binary location.
Start the new server with the following command:
/opt/sun/comms/messaging/sbin/start-msg
If you need to back out the migration, use the —u (undo) flag:
/opt/sun/comms/messaging/sbin/migrate-config —u old-base-dir
where old-base-dir is the old server-root directory.
To restart the old Messaging Server, use: old-base-dir/sbin/start-msg
To perform an in-place upgrade:
Patchadd the appropriate patch. For details, see: Patch and Package Information for Messaging Server
From the msg-svr-base directory, run patch-config. For example: /opt/SUNWmsgsr/sbin/patch-config
From the msg-svr-base directory, run install-newconfig. For example: /opt/SUNWmsgsr/sbin/install-newconfig
To back out the upgrade, run uninstall-newconfig from the msg-svr-base directory. For example, /opt/SUNWmsgsr/messaging/sbin/uninstall-newconfig
Be sure to patchrm the appropriate patch listed in Patch and Package Information for Messaging Server.
To uninstall Messaging Server, run commpkg uninstallin INSTALLROOT/CommsInstaller/bin/.
It uninstalls the same products that commpkg install installs. However, it does not remove OS patches installed by commpkg install. In addition, it does not remove Shared Components.
A fast way to uninstall Messaging Server in an alternate root is to simply remove the entire alternate root.
The following command-line arguments are used with commpkg uninstall:
Command-line Argument |
Description |
---|---|
—rootdir path |
Specify the path of rootdir, the alternate root used for multi-installation. Supported on Solaris only. |
—silent INPUTFILE |
Run the uninstaller silently, taking the inputs from the INPUTFILE and the command line. The command line arguments override entries in the INPUTFILE. Uninstallation proceeds without interactive prompts. Use —dryrun to test silent uninstallation. |
—dry-run or -n |
Does not uninstall Messaging Server. Performs checks. Silent uninstallation INPUTFILE is created in /tmp. |
If you run the uninstaller in Silent mode, you are running a non-interactive session. The uninstallation inputs are taken from a silent uninstallation file (also known as a state file), from command line arguments, or defaults.
To run a silent uninstallation, follow these steps:
Run an interactive uninstallation session.
A state file similar to /var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358 is automatically created.
The silent installation and uninstallation files have the same file naming convention. You need to scan the contents of the file to determine if it's an installation or uninstallation silent file.
Copy the state file to each host machine and edit the file as needed. .
Run the silent uninstallation on each host. See the silent uninstallation usage.
Command-line arguments override the values and arguments in the state file.
The following is a sample uninstall silent file:
# Silent File for CommsInstaller 5.0-1.03 # Generated on 20070604120325 # root directory ROOTDIR=/ # list of components to uninstall (using mneumonics) COMPONENTS=MS64 MS64_L10N |
This section contains a list of known issues and limitations with Messaging Server 6.3 64–bit Edition:
The http://docs.sun.comSM web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities. To access the following Sun resources, go to http://www.sun.com:
Downloads of Sun products
Services and solutions
Support (including patches and updates)
Training
Research
Communities (for example, Sun Developer Network)
Sun is interested in improving its documentation and welcomes your comments and suggestions.
To share your comments, go to http://docs.sun.comand 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. For example, the title of this book is Sun Java System Messaging Server 6.3 64-bit Installation Technical Note, and the part number is 820-2124-10.