Testing a Queue Based Integration in the TIBCO Scribe® Insight Workbench
Article ID: KB0078895
Updated On:
| Products | Versions |
|---|---|
| TIBCO Scribe Insight | 7.9 |
Description
There are times when a Queue Based Integration fails (either an Adapter Publisher or a Query Publisher) for a particular message and the problem is not readily apparent from the error message in the Execution Log viewer. Perhaps it is an ENDJOB error or an insert was performed rather than the expected update. For those scenarios, the best way to troubleshoot the problem is to try processing the XML message via the TIBCO Scribe® Insight Workbench.
The issue you run into is the XML source for the DTS is a static file that was specified during the DTS design. Each time you open the DTS, the same file is used as the source. What needs to occur is to find the XML message that failed and use that file to overwrite the static file associated with the DTS.
Step 1 – Determine the name and location of the static XML source file that needs to be overwritten.
Open the appropriate DTS from the list of Integrations in the Console.
Edit the Source connection and choose the Change Connection option.
Click through the Source Connection Wizard until you get to the Source Document & Schema section.
This shows you the path and the name of the XML file the DTS is using.
If a path is not specified, it is in the same folder where the DTS is located.
Step 2 – Overwrite the static XML source file with the message that failed.
This can be accomplished a couple of ways.
Method 1 – Execution Log Viewer
This is probably the easiest method since the Execution Log Viewer has advanced search options.
Save the XML file and overwrite the file found in Step 1 above.
Method 2 – ScribeDeadMessage Queue
If the DTS has been configured to send messages to the ScribeDeadMessage queue you can also save the XML body.
This can be more difficult because there may be hundreds of messages in the queue.
Step 3 – Open the DTS and Test
You can verify values and step flow using Test mode and/or enable tracing in the Workbench (see KB article: Tracing in TIBCO Scribe® Insight)
The issue you run into is the XML source for the DTS is a static file that was specified during the DTS design. Each time you open the DTS, the same file is used as the source. What needs to occur is to find the XML message that failed and use that file to overwrite the static file associated with the DTS.
Step 1 – Determine the name and location of the static XML source file that needs to be overwritten.
Open the appropriate DTS from the list of Integrations in the Console.
Edit the Source connection and choose the Change Connection option.
Click through the Source Connection Wizard until you get to the Source Document & Schema section.
This shows you the path and the name of the XML file the DTS is using.
If a path is not specified, it is in the same folder where the DTS is located.
Step 2 – Overwrite the static XML source file with the message that failed.
This can be accomplished a couple of ways.
Method 1 – Execution Log Viewer
This is probably the easiest method since the Execution Log Viewer has advanced search options.
Save the XML file and overwrite the file found in Step 1 above.
Method 2 – ScribeDeadMessage Queue
If the DTS has been configured to send messages to the ScribeDeadMessage queue you can also save the XML body.
This can be more difficult because there may be hundreds of messages in the queue.
Step 3 – Open the DTS and Test
You can verify values and step flow using Test mode and/or enable tracing in the Workbench (see KB article: Tracing in TIBCO Scribe® Insight)
Issue/Introduction
This article provides step-by-step instructions for troubleshooting a Queue Based integration in the TIBCO Scribe® InsightWorkbench. This example uses TIBCO Scribe® Insight 7.9 with Global Connections.
Feedback
Yes
No
Powered by
