Standard system logs

The integration node writes information, warning, and error messages to standard output (STDOUT) and standard error (STDERR). The integration node records this information for the integration server and for the integration node admin agent (bipbroker process).

On some operating systems, the two standard logs are written to separate files, but the system might provide an option for the data to be recorded to a single merged file. On other systems, the two targets are defined to a single, and you might have the option to separate them. Check the documentation that is provided with your operating system for more details about STDOUT and STDERR.

integration nodes write records to both STDOUT and STDERR. Always check the contents of the file or files when an error occurs.

Because the records are written whenever components are active, check occasionally that the location of the file or files has sufficient space, or trim the file contents on a regular basis.

The default location of STDOUT and STDERR depends on the operating system:
Operating system Location of STDOUT and STDERR for integration node admin agent Location of STDOUT and STDERR for integration server Location of STDOUT and STDERR for HTTPListener

Linux platformUNIX platformLinux® and UNIX systems

 /var/mqsi/components/integrationNodeName /var/mqsi/components/integrationNodeName/integration_server_uuid /var/mqsi/components/integrationNodeName/httplistener

Windows platformWindows systems

 A single file, workpath\components\integrationNodeName\console.txt, contains both STDOUT and STDERR data, generated by the admin agent, where workpath is the working directory defined for the integration node. A single file, workpath\components\integrationNodeName\integration_server_uuid\console.txt, contains both STDOUT and STDERR data, where workpath is the working directory defined for the integration node. A single file, workpath\components\integrationNodeName\broker-integrationNodeName-httplistener-console.txt contains both STDOUT and STDERR data.

z/OS platformz/OS® systems

 The job log for the integration node control address space. The job log for the integration server address spaces. The job log for the integration node control address space.

Clearing logs

If you run your integration node with errors, or if you are leaving trace on, you need to clean the logs periodically. To clear the logs, complete the following steps.
  1. Stop the source that is generating the log, such as the broker or integration server.
  2. Back up the contents of the log file.
  3. Restart the source.
You can remove files without stopping the source, but this action might generate an error if the log is being actively updated. If you remove the log file, it is regenerated by the source when the source restarts.