Monitoring concepts

How you monitor the status, performance and integrity of resources used by FTM SWIFT depends on the nature of these resources and the information to be obtained:
  • Integration nodes and queue managers run as independent processes, and you can use the capabilities provided by the operating system to monitor them; for example, to determine whether they are running.
  • Queues, tables and indexes, and message flows operate under the control of their corresponding resource managers. Use the capabilities provided by the resource managers (IBM® MQ, Db2®, and IBM Integration Bus) to monitor them. For example, to monitor the health of a message flow:
    • Check the depth of its input queue. If the depth is continually increasing, the message flow is not processing messages quickly enough and might have stopped.
    • Use the Integration Nodes view of the IBM Integration Toolkit to check whether the message flow is started or stopped.
    • Check the contents of the operator console for messages that indicate an error situation that affects the message flow.
    • Check whether the error queues used by the message flow contain any messages.
  • The processing of FTM SWIFT message flows can be monitored using the monitor service, which is described in Event monitoring. This service routes FTM SWIFT event messages to the command-line interface (CLI), the operator console, or a queue.
  • Changes to relationship management (RM) authorisations can be monitored using the monitor service. You can distinguish between changes that require user action and changes that requires export of authorisations (if you are distributing RM data using RM distribution files).
  • You can use means provided by Db2, for example, SQL, to evaluate the data written by FTM SWIFT to the audit and message warehouse tables, and thereby monitor your business processes. For more information about this data and these tables, see Auditing and Message warehouse. For example, you can use the contents of these tables to determine such things as the message traffic of an OU, or the location and state of a message with a particular ID.
  • For information on how to monitor the software integrity of the files installed by FTM SWIFT refer to Monitoring software integrity.
  • For information on how to monitor the data integrity of your FTM SWIFT database tables refer to Monitoring data integrity.