test

Sun Java System Message Queue 3.7 UR1 Installation Guide

ProcedureTo Install Message Queue on Linux

  1. Accept the license agreement on the Message Queue product download site.

  2. Download the Message Queue product distribution file from the Web site into an empty, temporary download directory, temp_directory.

    The download file is: mq3_7-ent-linx86.zip

  3. Change to the temp_directory and uncompress the distribution file.

    unzip mq3_7-ent-linx86.zip

    The unzip command creates an mq3_7-ent directory, which contains the distribution files: LICENSE, README, and COPYRIGHT files; mqinstall utility; mquninstall utility; mqmigrate utility; and an rpms directory.

    The following table describes the Message Queue RPM packages in the rpms directory. If any of these files already exist on your system, you need to check whether the version number is greater than that provided by Message Queue. If it is, you should do a custom install.

    RPM 

    Description 

    Notes 

    sun-mq-config

    /etc files

    		 

    sun-mq-var

    /var files

    		 

    sun-mq

    /opt files for the Message Queue Core RPM

    Depends on the files 

    sun-javahelp

    sun-mq-jmsclient

    sun-mq-config

    sun-mq-var

    sun-mq-jaxm

    Message Queue Java API for XML Messaging (JAXM): API 

    Depends on sun-saaj.

    sun-mq-jmsclient

    JMS: API and runtime 

    No dependencies 

    sun-mq-xmlclient

    XML Client 

    Depends on sun-jmsclient and sun-saaj.

    sun-mq-capi

    C-API 

    Depends on sun-nspr, sun-nss.

    sun-mq-compat

    Symlinks to 3.5 locations. 

    Depends on sun-mq.

    Not installed by default. Use if your existing client applications contain scripts that depend upon former file locations (such as jar files). 

    sun-mq-[locale]

    L10N files 

    No dependencies. 

    sun-mq-len

    Legacy Enterprise license file. 

    No longer used. 

    sun-javahelp [This package is shared by a number of Sun Java System products. This package is not installed by default. You must manually install any shared packages after installing Message Queue packages.]

    JavaHelp: API and runtime 

    Supports JavaHelp viewer for Admin Console help. 

    This RPM is not installed by default. 

    sun-nss

    Network Security Services (NSS) libraries. 

    Needed to support C language clients. 

    This RPM is not installed by default. 

    sun-nspr

    Netscape Portable Runtime (NSPR) libraries 

    Needed to support C clients. 

    This RPM is not installed by default. 

    sun-saaj

    SOAP with Attachments API for Java: API and runtime 

    Required to support Java clients using SOAP/JAXM API. 

    This RPM is not installed by default. 

    sun-jaxp

    Message Queue Java API for XML Processing (JAXP): API and runtime 

    Required to support Java clients using SOAP/JAXM API. 

    This RPM is not installed by default. 

    sun-javamail

    JavaMail: API and runtime 

    Required to support Java clients using SOAP/JAXM API. 

    This RPM is not installed by default. 

    sun-jaf

    JavaBeans Activation Framework: API and runtime 

    Required to support Java clients using SOAP/JAXM API. 

    This RPM is not installed by default. 

  4. Change to the directory containing the Message Queue distribution files.

    cd mq3_7-ent

  5. Log in as root or change to superuser.

    For example, type the following at a command prompt:

    su root

    When prompted, type your root password.

    Note –

    Remember to migrate data if necessary. See Migrating Files from an Earlier Installation for more information.

  6. If you intend to install all of the Message-Queue-specific RPM packages (packages which start with sun-mq), you will need to run the mqinstall script.

    Please note that the install script will overwrite all Message-Queue-specific RPM packages, and will not install any shared RPM packages. You must install shared RPM packages manually, as described in Step 7.

    1. Run the mqinstall script.

      ./mqinstall

      The script lists the distribution RPM packages including their version numbers, if any, that are already installed, and then lists the RPM packages about to be installed.

      Note –

      If any of the Message Queue RPM packages listed is already installed and its version is newer, then you will probably not want to install the corresponding Message Queue RPM package. In that case, enter n (no) and continue with Step 7.

      The mqinstall script does not install the sun-mq-compat RPM package by default and you should only have it installed if you need it. For example, if your existing client applications contain scripts that depend upon former file locations (such as jar files), you will need to install the sun-mq-compat RPM package. To install this RPM package, see Step 7.

    2. Enter y (yes) if you want to install all the Message-Queue-specific RPM packages. Otherwise, enter n (no) and continue with Step 7.

      If you run the script, it creates a log file in the following directory:

      /var/sadm/install/logs

      The /opt/sun/mq directory and its contents are created, and files are placed in other locations as well (see Migration Issues).

  7. If you want to install a subset of the Message QueueRPM packages, if you want to install shared RPM packages, or if you do not want to overwrite later versions of RPM packages, do the following:

    1. Change to the rpms directory.

      cd rpms

    2. Run the rpm install command to install the RPM packages.

      rpm -ivh --nodeps rpmPkg1.rpm rpmPkg2.rpm rpmPkg3.rpm

  8. Back up the imq3_7-ent-linx86.zip 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.

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

    Note –

    The instance data for any pre-existing broker instance is owned by the user that created that instance. Therefore, once installation is complete, be sure to run any Message Queue broker instance (using the -name instanceName option) as the owner with privileges to the /var/sun/mq/instances/instanceName directory. This applies to the default broker instance (named imqbroker) as well.