Debugging a JMS Trigger
To debug and test a JMS trigger you can:
Instruct
Integration Server to produce trace logging for the trigger. To do this, configure the JMS connection alias used by the trigger to produce enhanced logging for message consumers. You can indicate that
Integration Server writes additional log messages for a specific JMS trigger or all JMS triggers that use the JMS connection alias. For more information about enhanced logging for JMS triggers, see
webMethods Integration Server Administrator’s Guideextra level of verbose logging.
Send messages to which the JMS trigger subscribes to the JMS provider. You can create a service that sends the messages. Alternatively, you can create a launch configuration that publishes a JMS message that contains an instance of a specified IS document type to the JMS provider.