IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Command environment: Linux and UNIX systems

Set up the Linux or UNIX environment to run IBM® Integration Bus 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 (with the file extension .sh) to the directory work_path/common/profiles, where work_path identifies the machine-wide IBM Integration Bus working directory.

To verify the machine-wide IBM Integration Bus working directory, enter the following command in a command console:

echo $MQSI_WORKPATH

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 work_path/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.

A typical reason for adding scripts is to configure access to databases from deployed message flows. For more information, see Running database setup scripts.

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

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.

If you use the zsh shell, issuing the mqsiprofile might cause the terminal session to exit. To resolve this issue, run the unsetopt function_argzero command before you run the mqsiprofile command.
Start the components that you want to run on this system with the mqsistart command.

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 IBM Integration Bus Version 9.0. The mqsiprofile command places the Version 9.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 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.

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 work_path\Common\profiles.
If you cannot update the profile permanently, but have to change it 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 Working with databases for information about setting up your databases for use with the broker.

an26230_.htm |

Last updated Friday, 21 July 2017