Service Monitor

The Service Monitor (meta_msg_sys_monitor) resource is part of PointForce iTopia's Messaging Service, which is part of the iTopia Enterprise Application Integration (EAI) module. iTopia EAI supports two types of messaging models that provide a means of allowing integration between two systems.

  • Publish and subscribe
  • Point-to-point

The Service Monitor resource provides the following capabilities:

  • Enables you to monitor all file transfer activities between the TECSYS application and pre-configured non-TECSYS applications (e.g. TrackAbout);

  • Provides visibility to all queues and the number of records to process;

  • Enables you to manually start and stop the various available queue consumers;

  • Enables you to manually start and stop the queue timers, or to refresh the data to process without stopping the application server;

  • Enables you to manually start and stop job executions; and,

  • Enables you to manually start and stop pre-configured subscribers.

The Service Monitor does not stop if the database connection is lost (i.e. the database server or the network goes down). The resource will continue to try to get message IDs from the database. If it fails, because there is no database connection, it will sleep and retry later on. When the database and/or network comes back up, the Service Monitor will continue to process messages (as long as the application is not stopped).

Using the Service Monitor:

  • Click the Start hyperlink to restart the application server associated with the indicated queue. In this case, the application server is restarted and any new or modified records in the queue are processed.

  • Click the Stop hyperlink to stop the application server associated with the indicated queue. In this case, the application server is stopped and any queue records that were lined up to be processed are paused. When the queue is started again, the processing of these records will resume.

  • Click the Refresh hyperlink if queue time records have been added, modified or deleted and you want these to take effect without having to bring down the application server. Note: Refresh does not affect the 'ibis-XML Transaction in' service.