Skip to end of metadata
Go to start of metadata

Introduction

Verbose logging is used in troubleshooting issues with certain connectors used with Private Agents. You may be asked by Jitterbit Support to enable verbose logging using the steps on this page.

NOTE: The steps here should only be used when directed by Jitterbit Support. 

Verbose logging is supported for these connectors. Use the entries under Connector Name in step 5 of Enabling Verbose Logging:

ConnectorConnector Name 

BigCommerce

bigcommerce

BMC Helix ITSM

bmchelixitsm

Coupa

coupa

Epicor ERP

epicorerp

HubSpot

hubspot

Jira

jira

Magento

magento

Shopify

shopify

Slack

slack

Square

slack

Workday

workday

Workday Prism Analytics

workdayprismanalytics

This list will be updated as verbose logging functionality is added to more connectors.

Enabling Verbose Logging

Verbose logging is not enabled by default. To use it, you must edit the log4j.properties file:

  1. Make a backup of any files you are going to edit. 
  2. Stop the Tomcat server. 
  3. On Windows, go to C:\Program Files\Jitterbit Agent\tomcat\webapps\axis\WEB-INF\lib or C:\Program Files (x86)\Jitterbit Agent\tomcat\webapps\axis\WEB-INF\lib and open the log4j.properties file in an editor.
    On Linux, go to /opt/jitterbit/tomcat/webapps/axis/WEB-INF/lib and open the log4j.properties file in an editor.
  4. Find the lines:

    log4j.logger.org.springframework=WARN
    log4j.logger.org.hibernate.engine.jdbc.internal.JdbcResourceRegistryImpl=ERROR
    
    # Debug options can be turned on by uncommenting these lines
  5. Just before the line starting with # Debug, add the following line, replacing <connector_name> with the name of the connector. Connectors are listed in the Introduction:

    log4j.logger.org.jitterbit.connector.verbose.logging.<connector_name>=DEBUG

    The code should look like this:

    log4j.logger.org.springframework=WARN
    log4j.logger.org.hibernate.engine.jdbc.internal.JdbcResourceRegistryImpl=ERROR
    log4j.logger.org.jitterbit.connector.verbose.logging.workday=DEBUG
    
    # Debug options can be turned on by uncommenting these lines

    NOTE: Verbose logging can be used with multiple connectors. Add a separate line for each connector.  

  6. Save the file and restart the Tomcast server. 

Disabling Verbose Logging

To disable verbose logging when it is no longer needed, edit the log4j.properties file:

  1. Make a backup of any files you are going to edit. 
  2. Stop the Tomcat server. 
  3. Go to C:\Program Files\Jitterbit Agent\tomcat\webapps\axis\WEB-INF\lib or C:\Program Files (x86)\Jitterbit Agent\tomcat\webapps\axis\WEB-INF\lib and open the log4j.properties file in an editor.
    On Linux, go to /opt/jitterbit/tomcat/webapps/axis/WEB-INF/lib and open the log4j.properties file in an editor.
  4. Find the line that contains the verbose logging information and change DEBUG to OFF. For example, change:

    log4j.logger.org.jitterbit.connector.verbose.logging.workday=DEBUG

    to

    log4j.logger.org.jitterbit.connector.verbose.logging.workday=OFF
  5. Save the file and restart the Tomcat server.

Viewing the Logs

Entries are written to the jitterbit-axis.log file. Open the logs in an editor to view the entries. Logs are saved in these locations:

  • 32-bit Windows: C:\Program Files (x86)\Jitterbit Agent\tomcat\logs
  • 64-bit Windows: C:\Program Files\Jitterbit Agent\tomcat\logs
  • Linux: /opt/jitterbit/tomcat/logs

To find entries, search for DEBUG or verbose.logging in the file. Entries may include messaging, schemas, and other information you and Jitterbit Support can use when debugging. An excerpt is shown here:

DEBUG org.jitterbit.connector.verbose.logging.epicorerp.VerboseLogger:22 - org.jitterbit.epicor.adapter.common.CommonResponseGenerator.statusCode, msg: 200




On This Page

Related Articles


Related Topics


Last updated:  Feb 04, 2021