To debug a process that is run from a trigger or business process in IntegrationServer7:
- Put a pub.flow:savePipelineToFile as the first entry in the flow service and enter a filename.
- Execute the code that hits the trigger or business process.
- Look at the file on the IntegrationServer/pipeline directory to check the data.
- To debug, disable the savePipelineToFile and add a pub.flow:restorePipelineFromFile with the same filename
- Step through the flow service and you can now see exactly how it behaved and find your problem.
And in IntegrationServer8 (as mentioned in the comments) it gets much easier:
- Open the service and change the pipeline debug option to "Save". (You may have to click on the title bar of the service to get to the right properties screen)
- Execute the code that hits the trigger or business process.
- The data is saved in the IntegrationServer/pipeline directory
- Now select the service again as in step 1, but change the pipeline debug option to either "Restore" option.
- Step through the flow service and it will start out with your restored pipeline.
In webMethods 8 there is an even better option that allows debugging a flow service without changing the code itself. You could use the flow service property "Pipeline Debug" and set it to "Save" to store the pipeline.
ReplyDeleteWe are still on 7.x, but that sounds really cool!
ReplyDelete