Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Working with webMethods Messaging Triggers | Debugging a webMethods Messaging Trigger
 
Debugging a webMethods Messaging Trigger
 
Enabling Trace Logging for All webMethods Messaging Triggers
Enabling Trace Logging for a Specific webMethods Messaging Trigger
To debug and test a webMethods messaging trigger, you can:
*Run the webMethods messaging trigger using a launch configuration. You can use the launch configuration to verify that the subscription, filters, and trigger service work as expected.
*Publish a document to which the webMethods messaging trigger subscribes. You can do this by creating a launch configuration for a publishable document type and then running the launch configuration. Alternatively, you can create a service that uses one of the pub.publish* services to publish a document to which the trigger subscribes and then run the service to publish the document.
*Instruct Integration Server to produce an extra level of verbose logging. You can enable debug trace logging for all webMethods messaging triggers or an individual webMethods messaging trigger.
Note:Integration Server generates additional logging for triggers that receive messages from Universal Messaging or through Digital Event Services only.