Users Guide

Optimizing Your System | Getting Started
OMNM 6.5.3 User Guide 111
Optimizing Your System
To optimize you system, you can perform the following tasks needed:
•
Overriding Properties
• Tuning Memory (Heap & Portal)
• Tuning Application Features’ Performance Impact
• MySQL Resizing, Starting and Stopping
Overriding Properties
You can fine-tune various features of the application. Rather than lose those changes if and when
you upgrade or patch, best practice is to override changes.
To do this for the Web portal, first rename the provided file
\oware\synergy\conf\server-
overrides.properties.sample
to server-overrides.properties , and enable the
properties within it by uncommenting them, and altering them to fit your needs. The comments in
this file provide more information.
You can also override application server-related properties in
\owareapps\installprops\lib\installed.properties.
Both of these properties files remain as you previously configured them if you install an upgrade,
but upgrades overwrite the
server-overrides.properties.sample , so keep a copy if it has
anything you want to preserve.
Screen names —One possible configuration property
(
com.synergy.validation.screenmame.min.length ) specifies a minimum length
for user screen names. For the existing user base then any screen names that are shorter than
the value must change to the required length on the next edit/save for that user.
Tuning Memory (Heap & Portal)
You can adjust the memory footprint of any installed server’s virtual machine (VM) by configuring
it in the Heap configuration installation screen that appears during most package installations.
Within limits, using more memory, if it is available, generally means better performance.
Launching a server without sufficient memory produces the following error:
Error occurred
during initialization of VM Could not reserve enough space for object
heap.
You can re-set these after installation too, with the following properties in
\owareapps\installprops\lib\installed.properties :
oware.server.min.heap.size=3072m
oware.server.max.heap.size=3072m
For Windows and Linux valid settings range from 512m to the limit of available RAM minus
operating system needs.
While you can enter any number within these constraints, the following are values that are
supported during upgrade. Other values are ignored during upgrade and you must choose again
from supported value list during installation/upgrade.