WebSphere Message Brokers
File: an26230_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:34:01

Command environment: Linux and UNIX systems

On Linux and UNIX systems, when you start a runtime component it inherits the environment from where you issue the mqsistart command.

You must therefore initialize the environment before you start a component; the command mqsiprofile located in the directory install_dir/bin, performs this initialization. If you are starting a broker, you might also need to initialize the environment for any databases that are accessed by the broker.

You must not change the location of the mqsiprofile command, or make user modifications to the command, because it might be replaced if you install service, or an update, to the product. If you need to run your own additional environment settings, add a script called your_file_name.sh to the profiles directory:

workpath/common/profiles 

When mqsiprofile runs, it automatically calls these additional user-written scripts.

Two typical reasons for adding scripts are Running database setup scripts and Running with Java 5.

When you have configured any additional setup, you can initialize the runtime environment for components and commands:

  1. Issue the mqsiprofile command:
    . install_dir/bin/mqsiprofile

    You must include the period and space preceding the location for this invocation to work correctly. Add this command to your login profile if you want it to be run at the start of every session.

    This command accesses additional scripts that you have copied to the common/profiles directory, therefore the environment is initialized for runtime components and other resources such as databases.

  2. Start the components that you want to run on this system using the mqsistart command.

Check if following conditions apply to your environment:

Running database setup scripts

A broker requires access to a database to maintain operational and state data, and might also require access to user databases from deployed message flows.

When you install a database product on Linux and UNIX systems, some database managers provide a profile to perform the environment set up that the database requires, or provide details of actions that you must take in their documentation. Always check the database product documentation for environment setup details; the information provided here is for general guidance only and might not be complete.

If you have installed 64-bit instances of DB2 or 64-bit Oracle databases, you need to complete additional setup steps, including adding 32-bit libraries to MQSI_LIBPATH32. Detailed instructions are provided in Setting your environment to access databases, Creating a DB2 database on Linux and UNIX systems, and Connecting to a database from Linux and UNIX systems.

  1. If you can update the profile to provide permanent values for the details that are required (for example, the database server name or the installation directory):
    1. Complete the changes to the profile.
    2. Copy the profile file to the directory workpath\common\profiles.
  2. If you cannot update the profile permanently, but need to make changes each time, you must run it independently of the mqsiprofile command:
    1. Run the appropriate profiles to initialize the environment for the database:
      • For DB2, issue the following command for the relevant DB2 instance:
        . db2_instance_directory/sqllib/db2profile
      • For Oracle, export ORACLE_HOME and ORACLE_SID, then issue the following command:
        . ${ORACLE_HOME}/bin/oraenv
      • For Sybase, issue the following command, specifying your installation directory:
        . Sybase_installation_directory/SYBASE.sh
      • For Informix, check the documentation for the client on your broker system for details of the actions that you must take. For example, you might have to specify the following environment variables:
        export INFORMIXDIR=/installation_directory_of_informix_client_software
        export PATH=${INFORMIXDIR}/bin:${PATH}
        export INFORMIXSERVER=server_name
        export INFORMIXSQLHOSTS=${INFORMIXDIR}/etc/sqlhosts     
        export TERMCAP=${INFORMIXDIR}/etc/termcap
        export TERM=vt100
        export LIBPATH=${INFORMIXDIR}/lib:${INFORMIXDIR}/lib/esql:
                       ${INFORMIXDIR}/lib/cli:$LIBPATH

        where server_name is defined in the file sqlhosts (the required value is typically the machine name), and the location of the file sqlhosts is set up as part of the installation process.

        To configure your system to run this setup at the start of every session, add these statements to the login profile of the user that is going to run the broker.

When your environment has been set up, see Configuring databases for information on setting up your databases for use with the broker.

Running with Java 5

WebSphere Message Broker supplies Java version 5 (also known as version 1.5).

To check what level of Java you are currently working with, enter the following command:
java -fullversion
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:34:01

an26230_ This topic's URL is: