Since several components and environments in integration scenarios are connected together, it's possible that some part of the pipeline fails and breaks the connection. To identify the issue, please follow this troubleshooting guide.

Identifying the problem

The starting point of troubleshooting is usually the job log of a failed job. The job log can be displayed in transaction SM37. Glue jobs always start with ZDVD_GLUE, so this pattern can be used to filter Glue jobs.

To display logs, select the desired job, and click the Job log option in the toolbar.

Job log should direct you further down through the troubleshooting process - in our example, the error occurs in the Datavard Java connector during the execution of an SQL query.  

Since Glue works with several types of storages, please refer to the storage type specific troubleshooting guide below for more information.

ADD STORAGE SPECIFIC LINKS

Collecting logs for analysis

All relevant logs can be conveniently collected and downloaded either for further investigation or to initiate the involvement of the Datavard support team.

To collect logs, go to transaction /DVD/GLUE. In the drop-down menu, that is displayed after clicking on the Datavard logo, select the option Download logs

In the pop-up window fill the desired location for logs and the time period when an error occurred.

The downloaded archive can be now sent to the Datavard support team for further analysis.