Overview

iWay Service Manager (iSM) provides a collection of tools and facilities that are designed for troubleshooting and debugging purposes. One of the key challenges in any debugging scenario is to identify the level (or area) where the error is occurring. As a starting point, asking the following questions can help during the early stages of an investigation:

In actual scenarios, issues may not occur at a specific level, but between levels. For example, as a message or transaction passes between the process flow and channel levels.

Based on the answers to these questions, the appropriate troubleshooting or debugging tool can be identified. The following diagram illustrates this logic and the various levels that a typical application may traverse.

The primary goals of this best practices guide is to:

  1. Identify the troubleshooting and debugging facilities that are provided by iSM.
  2. Identify iWay-recommended third-party tools if the troubleshooting or debugging level scope falls outside of the iWay framework.
  3. Identify scenarios where the appropriate tool or facility can be best used to troubleshoot and debug the issues as they occur.