Externalizing log files and thread dumps

For a Sterling B2B Integrator docker installation, the log files and thread dumps are externalized.

These files are generated inside the container in the /ibm/trace/ directory. To make them available on the host machine, you need to map the directory to an external volume during the execution of the docker run command.


docker run -e LICENSE="accept" -e KEY=<key> -e TZ=<Time Zone> -d --name=<container name> --net=host 
-v <local dir>:/ibm/resources -v <local dir2>:/ibm/trace <image-id> b2bi_run all 1

Here the <local dir2> has the log files, thread dumps, Liberty log files, ops dumps, and Adapter Container dump traces.

Log Files

The Sterling B2B Integrator log files and the Liberty log files are automatically generated and available in the mapped local directory.

Log files location -

<local dir2>/logs/node<node num>/

Liberty log files location -

<local dir2>/logs/node<node num>/liberty/

Thread Dumps

Follow these steps to generate the thread dumps on Unix/Linux environment:
1. Find the process ID of the noapp java process. Execute the following command.
```
[root@oley1 ~]# ps -ef | grep noapp
OR
[root@oley1 ~]# ps -ef | grep NoAppServer
```
2. Identify the child process and execute the following command using the process ID.
```
[root@oley1 ~]# Kill -3 <process-id>
```
Thread dumps location -
```
<local dir2>/dumps/node<node_number>/
```
Follow these steps to generate the Liberty thread dumps on Unix/Linux environment:
1. Find the process ID. Execute the following command.
```
[root@oley1 ~]# ps -ef | grep SIServer
```
2. Identify the child process and execute the following command using the process ID.
```
[root@oley1 ~]# Kill -3 <process-id>
```
Liberty thread dumps location -
```
<local dir2>/dumps/node<node_number>/liberty/
```
Follow these steps to generate the Ops thread dumps on Unix/Linux environment:
1. Find the process ID. Execute the following command.
```
[root@oley1 ~]# ps -ef | grep ops
```
2. Identify the child process and execute the following command using the process ID.
```
[root@oley1 ~]# Kill -3 <process-id>
```
Ops dumps location -
```
<local dir2>/dumps/node<node_number>/ops/
```
Follow these steps to generate the Adapter Container thread dumps on Unix/Linux environment:
1. Find the process ID. Execute the following command.
```
[root@oley1 ~]# ps -ef | grep <ac name>
```
2. Identify the child process and execute the following command using the process ID.
```
[root@oley1 ~]# Kill -3 <process-id>
```
Adapter Container dumps location -
```
<local dir2>/dumps/node<node_number>/<ac name>/
```