Since in integration scenarios several components and environments 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

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 desired job, and click Job log option in the toolbar.

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

Since Glue works with several types of storages, please refer to storage type specific troubleshooting guide below for 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 an involvement of Datavard support team.

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

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

Downloaded archive can be now sent to Datavard support team for analysis.