Creating a specific command environment for an integration node or an integration server
Extend or change the command environment that is used when you run a specific integration node or integration server.
- 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
- For an integration node:
- On Linux®: 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
- For an integration node:
- work_path
- Specifies the machine-wide IBM® Integration Bus working directory.
- integrationNodeName
- Specifies the name of your integration node.
- server_name
- Specifies the name of your integration server.
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.
- 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:
- 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.