Sandbox.cfg implementation properties

You can supply parameters in the sandbox.cfg for Implementation properties.

The following are the sandbox.cfg Implementation properties and descriptions.

Property
Description
Implementation
These are properties that can be changed after installation.
LOAD_FACTORY_SETUP
Indicates whether or not you want to load factory setup defaults during installation or manually after installation.
AUDIT_LOAD_DEFAULTS
Valid values are true or false. When set to true the audits are generated when the loadDefaults script is run.
LOG_DIR
Use to override the logging directory. For example, if you want to deploy the ear on another server you could set the parameter to a new value, run setupfiles, then build the ear. The application would then log to the directory you mentioned.
MAX_MEMORY
The maximum amount of memory.

Example: 512

NO_DBVERIFY
Valid values are true or false. When set to true during installation and install service, dbverify will not be run. This means that Sterling™ Order Management System Software will not generate DDL to make the database like the XML entity repository.
INDEXES_NOT_CREATED
Sets the name and location of the index-creation-suppression file. This file contains a list of indexes for which schema generation tools, such as dbverify, do not generate "IndexAdds" SQLs. The file is created by users. When creating the file, ensure that the name of each index is located on a separate line of the file. The default name and location is <INSTALL_DIR>/extensions/schemagenerator/index_not_created.txt.
Example: INDEXES_NOT_CREATED=<INSTALL_DIR>/extensions/schemagenerator/indexes_not_created.txt
REINIT_DB
Whether Sterling Order Management System Software should initialize the database or not. Valid values are Yes (default) or No.