Configuring the Java Service Wrapper
The Java Service Wrapper is a utility program developed by Tanuki Software, Ltd that is used to launch the JVM in which Optimize runs. You can control various aspects of Optimize components using settings that control how the Java Service Wrapper runs. This section describes how to customize some of the settings used by the Java Service Wrapper.
In addition to launching the JVM, the Java Service Wrapper offers features for monitoring the JVM, logging console output, and generating thread dumps. The following sections describe how Optimize uses the features of the Java Service Wrapper. For an overview of the Java Service Wrapper, see the Software AG Infrastructure Administrator's Guide cross-product document.
There are three Optimize components for which Java Service Wrapper configuration settings can be adjusted. These components are Analytic Engine, Web Service Data Collector, and Infrastructure Data Collector. There are numerous Java Service Wrapper settings that can be modified for these components, but Software AG only recommends modifications to only two parameters: log level and memory allocation. Other settings should not be customized unless you are directed to do so by Software AG Support.
For applicable Optimize components, the configuration files for the Java Service Wrapper reside in the following folders.
The Analytic Engine Java Service Wrapper configuration files reside in the following folder:
Software AG_directory /optimize/analysis/conf/wrapper.conf
The Web Service Data Collector Java Service Wrapper configuration file resides in the following folder:
Software AG_directory /optimize/dataCollector/conf/wrapper.conf
The Infrastructure Data Collector Java Service Wrapper configuration file resides in the following folder:
Software AG_directory /profiles/InfraDC/configuration/custom_wrapper.conf
When you start Optimize, property settings in the wrapper.conf and the custom_wrapper.conf files determine the configuration of the JVM and the behavior of the logging and monitoring features of the Java Service Wrapper.
The following table provides more information about the wrapper.conf and the custom_wrapper.conf files.
File name | Description |
wrapper.conf | Contains property settings that are installed by Optimize. You must edit this file directly to change Java Service wrapper settings for Analytic Engine and Web service Data Collector. |
custom_wrapper.conf | For Infrastructure Data Collector, this file contains properties that modify the installed settings in wrapper.conf. If you need to modify the property settings for the Java Service Wrapper for Infrastructure Data Collector, make your changes in this file. |
The following sections describe configuration changes that Optimize supports for Java Service Wrapper. For Optimize, do not make any configuration changes to the Java Service Wrapper other than the ones described in the following sections unless directed to do so by Software AG support.
When the Java Service Wrapper launches the JVM, it provides configuration settings that, among other things, specify the size of the Java heap, the size of the PermGen area, and the directories in the classpath.
The wrapper.java properties in the Java Service Wrapper configuration files determine the configuration of the JVM in which Optimize runs.
The JVM property settings that Optimize installs are suitable for most environments. However, you can modify the following properties if the installed settings do not suit your needs. For procedures and additional information, see the webMethods cross-product document, Software AG Infrastructure Administrator's Guide.