Filter
Top Products
Recommendation Test Production Comments
JVM version C C You must ensure that you install
Sterling B2B Integrator on certified
JVM versions and levels.
Run the –version command in the
command prompt to ensure that you
have installed the correct version.
Verbose GC statistics NA C You can enable verbose GC statistics
collection. Understanding the health
of GCs for each JVM is critical for
performance.
Paging C C The JVM heap must be resident in
the memory. The performance can
noticeably degrade if the operating
system has to page portions of the
heap out to disk.
OutOfMemory
Exceptions
C C OutOfMemory exceptions can cause
unpredictable behavior. You should
ensure that you have allocated
sufficient physical memory to
Sterling B2B Integrator based on
your processing requirements.
JVM VM mode C C For HotSpot JVM, the server mode is
applicable for long-running
workloads.
Heap size C C Correct heap size configuration is
critical for both performance and
availability. If the heap size is too
big, the GC pauses can be long.
Similarly, if the heap size is too
small, it can lead to OutOfMemory
exceptions. You should ensure that
heap size is not set larger than
physical memory to avoid thrashing.
Sterling B2B Integrator supports both
32-bit and 64-bit JVMs. You should
allocate more heap space when you
are running a 64-bit JVM.
Database
Monitor and regulate
indexes
C C Sterling B2B Integrator comes with a
default set of indexes. In some cases,
the indexes may not apply to your
operational environment.
You should regularly monitor the
resource cost of frequently used
queries to check if additional indexes
are required. Similarly, you can also
monitor the database to delete
indexes if they are not required.
8 Sterling B2B Integrator: Performance Management