Log Scanner

The Log scanner checks logs in Sterling B2B Integrator for irregularities that contribute to diminished system performance.

Log Scanner Details

Sterling B2B Integrator system logs contain useful information about various operations in your system. Sterling B2B Integrator logs are generated in the install_dir/logs directory. The Log scanner checks logs in Sterling B2B Integrator for irregularities that contribute to diminished system performance.

Tip: The Out of Memory test checks all existing log files in the logs directory. The test can take a long time to process if your log files are not regularly cleared. Remove old or unnecessary log files or disable the Out of Memory test to ensure that the HealthCheck utility functions correctly.
DMI Queue

The DMI Queue test scans relevant messages in the log files to determine whether the DMI queue was ever filled. If the DMI queue is continually full, certain Sterling B2B Integrator components might not function. If your database is at or near capacity, the DMI queue can fill quickly with outstanding requests. Consider examining your database to determine how to improve your database performance. You might also consider increasing the number of visibility threads, the size of the queue capacity, or decreasing the number of components that generate DMI event messages in the customer_overrides.properties file.

In the customer_overrides.properties file:

  • Increase the number of visibility threads by increasing the value of dmivisibility.number_visibility_threads.
  • Increase the amount of queue capacity by increasing the value of dmivisibility.event_input_queue_capacity.
  • Replace all with specific components for event generation in dmivisibility.visibility_coverage.

For more information about configuring visibility and the DMI queue, see Changing Advanced File Transfer Settings.

Note: If you also use Sterling File Gateway, ensure that CommBase is included in the visibility coverage. CommBase is required for Sterling File Gateway.

The DMI Queue test has a severity of 3, SEVERE.

Out of Memory

The Out of Memory test scans relevant messages in the log files to determine whether the Java virtual machine (JVM) was ever out of memory. Consider increasing the memory that is allocated, or the amount of physical memory available to your JVM.

For more information about managing Out of Memory errors, see Correcting Out-Of-Memory Errors.

The Schedule test has a severity of 3, SEVERE.

The Log scanner includes tests that help you to determine what are the best practices to follow for your particular system. Tests are designed to ensure that your settings match the settings suggested for Sterling B2B Integrator, but those settings might not necessarily be the best for your particular system or improve performance, nor does a difference in suggested settings indicate a serious system error.