Config Scanner

The Config scanner tests the configuration of various system components in Sterling B2B Integrator, including queue management, property file configurations, and memory assignment in your particular Java virtual machine.

Config Scanner Details

You can configure Sterling B2B Integrator components, including fair-share scheduling queue management, property file configurations, and Java virtual machine memory allocation. Ensure that you configured Sterling B2B Integrator for optimized performance with the HealthCheck utility. The Config scanner tests the configuration of various system components in Sterling B2B Integrator.

The Configuration scanner has the following tests:

Jetty Threads

The Jetty Threads test ensures that the minimum and maximum number of jetty threads remain at their set values. Jetty is Java-based HTTP framework and web server that handles the Sterling B2B Integrator user interface and any communications that use HTTP, such as AS2. Jetty threads are Java threads that are available to the framework. The Jetty Threads test ensures that an optimal quantity of threads run concurrently to evenly distribute system resources. The Sterling B2B Integrator user interface functions optimally when the maximum number of jetty threads is 100, and the minimum number of jetty threads is 5. Ideally, the number of available jetty threads corresponds to the number of concurrent sessions or processes your system manages at a time. Changing the minimum and maximum number of threads is not suggested. However, if it is necessary, you can adjust the minimum or maximum number of jetty threads if you add the numOfminJettyThread and numOfmaxJettyThread parameters to the customer_overrides.properties file.

For more information about managing threads, see Controlling the Threads.

The Jetty Threads test has a severity level of 2, ERROR.

JGroups

The JGroups test ensures that all nodes remain active in the cluster for clustered Sterling B2B Integrator environments.

The JGroups test fails when the test finds any inactive node in the OPS_NODE_INFO table. You can see the current node status displayed in the HealthCheck tool report message.

Ports

The Ports test ensures that the HTTP Server Adapter, FTP Server Adapter, and the SFTP Server Adapter do not use the same port. Ensure that your adapters are set to different ports.

Note: Multiple adapters that access the same port are acceptable only for clustered environments.

The Ports test has a severity of 2, WARNING.

Overrides

The Overrides test determines whether system properties files were changed. The Overrides test ensures your system's .in property files remain unchanged. Ensure that you edit only the customer_overrides.properties file to override default configurations in Sterling B2B Integrator property files, and do not alter other .properties or .in files.

Note: The Overrides test does not function if the installation data from the installed_data directory is deleted. The installed_data directory contains the base installation data for all installs, patches, and fixes applied to Sterling B2B Integrator. The Overrides test compares the properties files to the original installation data to ensure that they remain unchanged.

The Overrides test has a severity level of 2, ERROR.

Thread Stealing

The Thread Stealing test checks to see whether the StealThreads property is enabled for any queue, and if the AllowStealing property is enabled for at least one queue. If the AllowStealing property is not enabled, an error is shown.

If StealThreads and AllowStealing are enabled for the same queue, HealthCheck reports an error unless AllowStealing is also enabled for other queues. For example, if StealThreads and AllowStealing are only enabled for Queue 2, HealthCheck reports an error because Queue 2 cannot steal from itself. Similarly, if StealThreads and AllowStealing are enabled for Queue 2, and StealThreads is enabled for Queue 3, Queue 3 can steal from Queue 2, but Queue 2 cannot steal from any other queue. HealthCheck reports an error in this case as well.

For more information about configuring queues, see Tuning Queues.

The Thread Stealing test has a severity level of 3, SEVERE.

Expired Certificate

The Expired Certificate test determines whether the validity period of a digital certificate is nearing expiration. Digital certificates that expire within five days of the current date are flagged by the test. Ensure that your digital certificates are up-to-date. It is good practice to replace or update your digital certificates within five days of expiration.

For more information about managing certificate expiration dates, see Check the Expiration Date of a System Certificate.

The Expired Certificate test has a severity of 2, ERROR.

The Heap Water Mark and Nursery to Heap Ratio tests check settings in your particular Java virtual machine (JVM). For information about configuring a HotSpot JVM, see Introduction to HotSpot JVM Performance and Tuning. For information about configuring an IBM JVM, see Introduction to the IBM® JVM Performance and Tuning Guidelines.

Heap High Water Mark

The Heap High Water Mark test ensures that the heap high water mark is less than 25% of the maximum heap size. The maximum heap size is the total memory allocation for the Java virtual machine (JVM). The heap high water mark is the memory usage of the Java virtual machine. If the heap high water mark is consistently less than the suggested usage of the total heap size, consider reducing the maximum heap size. You can reallocate your memory resources elsewhere.

For more information about configuring heap settings for your particular JVM, see Edit Performance Configuration Settings.

The Heap High Water Mark test has a severity of 1, WARNING.

Nursery to Heap Ratio

The Nursery to Heap Ratio test determines whether the percentage of heap consumption by the nursery is excessive. Ensure that your nursery consumes between 1/4 to 1/3 of the total heap size for optimal performance. If more memory is needed for your system, ensure that the nursery consumption does not exceed more than half of the total heap size.

For more information about configuring heap settings for your particular JVM, see Edit Performance Configuration Settings.

The Nursery to Heap Ratio test has a severity level of 1, WARNING.

The Active Connections and Load Balancing tests only appear in the HealthCheck utility if Sterling B2B Integrator runs on an Oracle database in a clustered environment.

Active Connections

The Active Connections test ensures that the Oracle Real Application Cluster (RAC) has a single active connection. The Active Connections test checks the number of actual database connections. Ensure that LOAD_BALANCING is set to OFF.

The Active Connections test has a severity of 2, ERROR.

Load Balancing

The Load Balancing test ensures that load balancing is disabled for the Oracle Real Application Cluster (RAC). Disabled load balancing is an attribute of an Oracle RAC configured for failover support or high availability. Ensure that LOAD_BALANCING is set to OFF, and FAILOVER is set to ON.

The Load Balancing test has a severity of 2, ERROR.

Note: For more information about configuring an Oracle RAC for high availability, see Using Oracle Real Application Clusters (RAC) for High Availability.

The Config 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.