See information about the latest product version
Command environment: Linux and UNIX systems
Set up the Linux or UNIX environment to run WebSphere® Message Broker commands.
When you start a runtime component on Linux and UNIX systems, 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 want to run your own additional environment settings, add a script that is called your_file_name.sh to the broker's work_path directory which contains the /common/profiles subdirectory.
When you run mqsiprofile again, the command automatically calls the additional user-written scripts in this location.
You must log out and log back in, to pick up the new files in the /common/profiles directory, before you run mqsiprofile again.
The newly added script is not picked up if you run the mqsistart command from an existing initialized command shell.
echo $MQSI_WORKPATH
A typical reason for adding scripts is Running database setup scripts.
When you have configured any additional setup, you can initialize the runtime environment for components and commands:
Check whether the following conditions apply to your environment:
- If you have a previous version of the product on the system, ensure that you run the correct profile before using WebSphere Message Broker Version 8.0. The mqsiprofile command places the Version 8.0 commands and libraries at the front of your search path, and calls any user profiles that you have supplied that can override any combination of PATH, CLASSPATH, or library 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 that you require.
- ODBC settings on Linux and UNIX systems are found in a text
file defined by the ODBCINI environment
variable. Set ODBCINI to point
to a copy of the sample file install_dir/ODBC/unixodbc/odbc.ini.
You can check that your ODBC environment is configured correctly by running the mqsicvp command. This command also validates the connection to all data sources that are listed in the odbc.ini file that have been associated with a broker by using the mqsisetdbparms command. For more information, see mqsicvp command.
Running database setup scripts
A broker might 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 setup 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.
When your environment has been set up, see Working with databases for information about setting up your databases for use with the broker.