Command environment - UNIX systems and Linux

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

The basic settings are made by the mqsiprofile command which is located in the
<product_install_path>/bin
directory.

You must not change the location of the mqsiprofile command, or make user modifications to the command, as it might be replaced if you install service, or an update, to the product. If you need to run your own settings, add a script to the profiles directory as described below.

mqsiprofile can call additional user-written scripts for you, if you place any files called *.sh in the specific location:
 <workpath>/common/profiles 
You might want to use this method to run database environment setup scripts.

To work with a broker, you need to set up the required environment for its databases and you are recommended to do this by running the vendor-provided profile for the database manager.

Note that the environment setup depends on the database manager being used. You run the appropriate script, as follows:
  • DB2, run db2profile for the relevant DB2 instance.
  • Oracle, run oraenv (Note that you must export ORACLE_HOME and ORACLE_SID prior to running oraenv)
  • Sybase, run SYBASE.sh

Once your environment is set, see Configuring component databases for information on setting up your databases for use with the broker.

  1. Run your database profile. For example, if you use DB2, run
    . <db2 instance directory>/sqllib/db2profile
  2. Run the WebSphere Event Broker product file
    . <install_dir>/bin/mqsiprofile

    You must include the period and space preceding the location for this invocation to work correctly. You might find it easier to add these to your login profile.

Note the following:
  • If you have a previous version of the product on the system, ensure that you run the correct profile before using Version 6.0. The mqsiprofile command places the Version 6.0 commands and libraries at the front of your search path.
  • If you use the same user ID, and you run multiple profiles (from multiple different installations or versions), you might get unexpected results. Log off and log on again before you run the specific profile you require.
  • ODBC settings on Linux and UNIX systems are picked up from a text file. This is found from the ODBCINI environment variable, which defaults to
    /var/mqsi/odbc/.odbc.ini
    This filename was also used by earlier versions of the product but the format has changed. If you are coexisting multiple versions, you need to create a different odbc.ini file for each, and override the ODBCINI environment variable setting in mqsiprofile.
Related tasks
Configuring component databases
Setting up a command environment
Command environment - Windows platforms
Related reference
Runtime commands