search cancel

Enable entity logging for the Integration Server for Cloud Data Protection

book

Article ID: 174069

calendar_today

Updated On:

Products

CDP for ServiceNow CDP for Salesforce CDP for Xactly CDP Communication Server CDP for Oracle Sales Cloud CDP for Oracle CRM On Demand CDP Policy Builder CDP for Yammer CDP Integration Server

Issue/Introduction

The purpose of this document is to provide the steps required to enable entity logging for the Integration Server which allows the entire request and response to be logged for debugging purposes.

Resolution

  1. Edit the Integration Server arguments file (default location is /usr/local/perspecsys/reverse-proxy/arguments)
  2. Scroll to the section before the -Dakka parameters
  3. Insert the following two lines
    • -Drequest.logging.enabled=true \
    • -Dresponse.logging.enabled=true \
  4. Restart the Integration Server (service apprtx_intserver restart)

Note: Ensure to remove or comment out the above two lines once the issue has been reproduced.  Enable entity logging is quite resource intensive.

 

Example:

-server
-Dlogback.configurationFile=/usr/local/perspecsys/reverse-proxy/logback.xml
-Dresource.root.path=/usr/local/perspecsys/reverse-proxy/resource
-Dfile.encoding=UTF8
-XX:+HeapDumpOnOutOfMemoryError
-XX:+UseG1GC
-XX:+UseBiasedLocking
-Xmx4g
-Drequest.logging.enabled=true \
-Dresponse.logging.enabled=true \
-Dakka.actor.default-dispatcher.fork-join-executor.parallelism-max=512
-Dakka.cluster.client.receptionist.acceptable-heartbeat-pause=60s
-Dakka.cluster.client.receptionist.failure-detection-interval=60s