IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


Setting up a command environment

Runtime components, and commands that administer runtime components, must be run from a command environment. You must initialize this environment by running the mqsiprofile command.

About this task

The mqsiprofile command places the Version 11.0 commands and libraries at the front of your search path, and can override any combination of PATH, CLASSPATH, or library PATH.

ODBC settings on Linux systems are found in a text file that is defined by the ODBCINI environment variable. If you are using Linux, set ODBCINI to point to a copy of the sample file install_dir/server/ODBC/unixodbc/odbc.ini, where install_dir is the IBM® App Connect Enterprise installation directory.

On Linux, if you want to use WebSphere® MQ features, you must set the WebSphere MQ environment where you want the integration server to run; for more information, see Setting the WebSphere MQ environment on Linux.

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

The following steps explain how to initialize your command environment, either by explicitly running the mqsiprofile command (on Linux) or by starting the command console (on Windows):

This command also runs any additional scripts that you copied to the common\profiles directory (on Windows) or the common/profiles directory (on Linux 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 App Connect Enterprise. For example, you can configure and start an integration server, as described in Configuring an integration server by using the server.conf.yaml file and Starting an integration server.


an26190_.htm | Last updated 2018-11-02 14:45:59