Inspecting Log files

The first place to look when performance problems are reported is the B2Bi metrics log file contents. There you will find output, generated once an hour for each monitored B2Bi server, by the three main threads in a GISNodeService used to monitor B2Bi servers:
  • GetAftHistoryTask

    To monitor the advanced file transfer data, also known as protocols

  • GetBpHistoryTask

    To monitor business process activity

  • GetFgHistoryTask

    Used to monitor Sterling Filegateway activity

These threads are responsible for:
  • Converting the data received into Control Center Monitor events or SCCNotifications
  • Doing pre-rule processing that is, looking for a rule match so that RuleService time from having to do so
  • Storing the events generated in the EVENTS, EVENTS_EXT and appropriate _STATS_LOG tables
  • Notifying the ProcessSummaryService about processes seen to have started and ended
  • Passing events on to the RuleService for processing
Note: GetAftHistoryTask thread also handles the retrieval of other information from the B2Bi server, such as adapter status information, in addition to its primary function – getting protocol activity data.
Tip: Monitoring the adapter status on B2Bi servers is an onerous process and has a negative impact on performance. The default Monitor Rest Time for updating the status of B2Bi adapters is one minute. You can lessen the impact on performance of B2Bi monitoring by increasing this value, via the monitored server’s Server Properties Settings dialog.