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 12.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 IBM MQ features, you must set the IBM MQ environment where you want the integration server to run; for more information, see Setting the IBM MQ environment on Linux and AIX.
Ensure that you use this environment each time you run an administrative command, or start an integration server.
The mqsiprofile command also runs extra scripts that are copied to the common\profiles directory (on Windows) or the common/profiles directory (on Linux systems). These scripts can be used to initialize the environment for runtime components and other resources, such as databases.
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).
Procedure
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 modifying the server.conf.yaml file and Starting an integration server.