Creating a specific command environment for an integration node or integration server

Extend or change the command environment that is used when you run a specific integration node or integration server.

If you want to run your own additional environment settings for an integration node or integration server, add command files to the following directories:

On Windows: Add one or more command files (with the file extension .cmd) to the following directories:
- For an integration node:
  work_path\config\integrationNodeName\profiles
- For an integration server:
  work_path\config\integrationNodeName\server_name\profiles
On Linux® and UNIX: Add one or more command files (with the file extension .sh) to the following directories:
- For an integration node:
  work_path/config/integrationNodeName/profiles
- For an integration server:
  work_path/config/integrationNodeName/server_name/profiles

where:

work_path: Specifies the machine-wide IBM® App Connect Enterprise working directory.
integrationNodeName: Specifies the name of your integration node.
server_name: Specifies the name of your integration server.

To verify the machine-wide IBM App Connect Enterprise working directory, enter the following command in a command console:

echo %MQSI_WORKPATH%

Ensure that the name of the integration nodes and integration servers contain only characters that are valid on your file system. You might also need to create the required directory structure.

To diagnose any problems, log files are written that list the profile scripts and the environment that is used by the integration node and the integration server. The log files are found in the following locations:

On Windows:
- work_path\Common\log\integrationNodeName.profilelog (for the integration node)
- work_path\Common\log\integrationNodeName\server_name.profilelog (for the integration server)
On Linux and UNIX:
- work_path/common/log/integrationNodeName.profilelog (for the integration node)
- work_path/common/log/integrationNodeName/server_name.profilelog (for the integration server)

Profile scripts are not removed automatically when an integration node or integration server is deleted. Therefore, if you created profile files for an integration node or integration server, you must delete these profile files manually if they are no longer required.