This article provides instructions for enabling ODBC trace for the Integration Flows running in a  container environment.

Assuming you already have a running integration flow  that interacts with database over ODBC interface.  Now your integration flow has encountered  some runtime error while interacting with database  and you would like to enable ODBC trace to investigate further.

Please follow below steps to enable ODBC trace for your Integration Server running in  a docker container.

1) Clone the latest ot4i/ace-docker repo

git clone https://github.com/ot4i/ace-docker.git

2) Create a folder 'extensions' under  ../sample/initial-config/

3) Create a odbcinst.ini file as :

[ODBC]
;# To turn on ODBC trace set Trace=yes
Trace=yes
TraceFile= /home/aceuser/ace-server/config/common/log/odbctrace.out
Threading=2

4) Zip the odbcinst.ini in archive named as extensions.zip and place it under ..\sample\initial-config\extensions\

5) Rebuild the docker image as described in  https://github.com/ot4i/ace-docker/tree/master/sample

6) Run the docker image by mounting the initial-config folder as described in https://github.com/ot4i/ace-docker/tree/master/sample . For example :

docker run --name aceapp -p 7600:7600 -p 7800:7800 -p 7843:7843 --env LICENSE=accept --env ACE_SERVER_NAME=ACESERVER --mount type=bind,src=/temp/initial-config,dst=/home/aceuser/initial-config ace:latest

(you may pass on other env var as necessary for your usecase).

7) The odbc trace will get generated under /home/aceuser/ace-server/config/common/log/odbctrace.out
#BestPractices