Setting up a command environment

Runtime components, and commands that administer runtime components, must be run from a command environment. This command environment is initialized by running the mqsiprofile command.

Before you begin

Check whether the following conditions apply to your environment:

If you have a previous version of IBM® Integration Bus on this system, then ensure that you run the correct profile before you use Version 10.0. The mqsiprofile command places the Version 10.0 commands and libraries at the front of your search path, and 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.
If you are using Linux® or UNIX, then ODBC settings on Linux and UNIX systems are found in a text file that is defined by the ODBCINI environment variable. Set ODBCINI to point to a copy of the sample file install_dir/server/ODBC/unixodbc/odbc.ini, where install_dir is the IBM Integration Bus installation directory.
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 (listed in the odbc.ini file) that are associated with an integration node by using the mqsisetdbparms command. For more information, see mqsicvp command.

About this task

The following steps explain how to initialize your command environment by running the mqsiprofile command.

If required, you can perform the following customizations before you run the command:

Extend the initialization that is performed by this profile; for example, for databases, or for other products that you want to use within the integration node; see Running database setup scripts.
On Linux and UNIX, if you want to use WebSphere® MQ features, then you must set the WebSphere MQ environment where you want the integration node to run; see Setting the WebSphere MQ environment on Linux and UNIX.
Configure a different command environment for a specific integration node or integration server; see Creating a specific command environment for an integration node or an integration server.

Ensure that you use this environment each time you run an administrative command, or start an integration node.

On Windows 7 and Windows 2008:
- Open a command console by clicking Start > All Programs > IBM Integration Bus 10.0.0.n > IBM Integration Console 10.0.0.n.
On Windows 8 and Windows 2012:
- Open a command console by searching for IBM Integration Console. If you have multiple installations of IBM Integration Bus, make sure that you are running the IBM Integration Console from the build of the IBM Integration Bus installation that you want to administer.
On Linux or UNIX systems: Locate and run the mqsiprofile.sh script in the directory in which you installed the appropriate product.
```
. install_dir/server/bin/mqsiprofile
```
You must include the period and space for this command to work correctly. Add this command to your login profile if you want it to be run at the start of every session.

If you use the zsh shell, then running 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.

This command also runs any additional scripts that you copied to the common\profiles directory (on Windows) or the common/profiles directory (on Linux or UNIX systems), so that the environment is initialized for runtime components and other resources such as databases.

What to do next

From the command line in the initialized environment, you can run commands to administer IBM Integration Bus.