Host System Scanner

The Host System scanner ensures that your operating system settings are optimal for Sterling B2B Integrator.

Host System Scanner

HealthCheck functions on Windows, Linux, and UNIX systems. You can ensure that your operating system settings, such as CPU usage, system processes, and system memory, are optimal for Sterling B2B Integrator with the Host System scanner.

Dump Files

The Dump Files test ensures that no Java core or heap dump files were generated in Sterling B2B Integrator. Java core and heap dump files are generated to the install_dir/noapp/bin directory. Java core files are generated manually or by your Java virtual machine (JVM) during an event, error, or malfunction. The Java core file contains information about the event that caused the issue, including environment, stack trace, and garbage collection information. Heap dump files The presence of Java core or heap dump files might indicate a serious issue with your JVM. Ensure that the Java core or heap dump files were not manually generated. If the files were generated as a result of an error malfunction, investigate your JVM.

The Dump Files test has a severity of 2, ERROR.

Disk Free

The Disk Free test ensures that a reasonable amount of disk space remains for Sterling B2B Integrator directories. The test compares the remaining disk space to the threshold that is defined in the Min Free property to determine whether a reasonable amount of disk space remains for the documents, logs, and tmp directories. Ensure that each directory has at least 1 GB of freed disk space.

The Disk Free test has a severity level of 3, SEVERE.

Document Directory Count

The Document Directory Count test ensures that a reasonable number of files exist in the document directory and its child directories. The document directory is divided into child directories that are generated depending on the frequency of the document_dir_extension property. The test compares the number of files in each individual child directory to the threshold that is defined in the Threshold parameter. Use the customer_overrides.properties file to overwrite the document_dir_extensionin the jdbc.properties file. Change document_dir_extension to a lower frequency in SimpleDateFormat.

The Document Directory Count has a severity level of 2, ERROR.

Old Logs

The Old Logs test determines whether there are old logs in the log directory. Ensure that you regularly delete old or unnecessary logs from Sterling B2B Integrator to conserve system resources.

The Old Logs test has a severity level of 1, WARNING.

Thread Count

The Thread Count test determines whether the number of overall threads in your system is excessive. Sterling B2B Integrator creates approximately 300 threads that are grouped under system threads, adapter threads, common JVM threads, third-party software threads, and several other threads that occur only once for different purposes. Examine your system threads to determine which threads for which components are running. Ensure that unused HTTP or FTP adapters do not contribute unnecessary threads to the system. For more information about managing system threads, see Optimizing and Controlling the System Threads.

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

ULimit

The ULimit test ensures that the setting for the time parameter for limit or ulimit in your operating system, matches the setting that is required for Sterling B2B Integrator. In most environments, ensure that the limit or ulimit parameter is set to unlimited or 4096.

The ULimit test has a variable severity.

Note: ULimit is implemented for Linux/UNIX environments only.
CPU Used

The CPU Used test determines what percentage of the CPU is used by Sterling B2B Integrator. Examine your operating system loads to determine why the CPU usage is high.

The CPU Test has a severity level of 3, SEVERE.

IO Wait

The IO Wait test determines the percentage of time the CPU was idle due to an outstanding disk input/output request. Examine your operating system loads to determine why the CPU idling is high. You might consider deploying Sterling B2B Integrator on a dedicated system.

The IO Wait Test has a severity level of 1, WARNING.

Note: IO Wait is implemented for Linux/UNIX environments only.
Processes

The Processes test determines the number of all system processes running in your operating system. Running too many system processes can diminish system resources, and negatively affect Sterling B2B Integrator performance. Ensure that you close unnecessary processes when you run Sterling B2B Integrator. You might also consider upgrading your disk or deploying Sterling B2B Integrator on a dedicated system.

The Processes Test has a severity level of 2, ERROR.

NFS Mount

The NFS Mount test ensures that the document directory is not NFS (Network File System) mounted. A network file system is a distributed file system protocol that allows network access to data stored on a remote mount. Accessing remote storage is slower than accessing local storage. Therefore, consider mounting the document directory locally and cross mount to other boxes if necessary.

The NFS test has a severity level of 1, WARNING.

Note: NFS Mount is implemented for Linux/UNIX environments only.

The Host System 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.