EMservice.conf

Contents
apmdevops106
Contents
The
EMService.conf
file, in
<EM_Home>\
bin contains settings that are used when the Enterprise Manager is run as a Windows Service.
Note:
Before you configure these properties, you must unregister the Enterprise Manager Service. After you configure properties, re-register the Enterprise Manager Service.
wrapper.java.command
The Java application wrapper command.
Default
jre\\bin\\java.exe
wrapper.java.mainclass
The Java main class wrapper command.
Default
org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.java.classpath.x
The Java Classpath that includes the
wrapper.jar
. Class path elements should be added in a sequential manner, such as follows:
  • wrapper.java.classpath.1=./lib/ServiceWrapper.jar
  • wrapper.java.classpath.2=./launcher.jar
  • wrapper.java.classpath.3=
wrapper.java.library.path.1
The Java library path is the location of the
Wrapper.DLL
or
libwrapper.so
.
Default
./lib
wrapper.java.additional.x=
More Java parameters are applicable only on 64-bit Windows.
The first parameter must be
-Xrs
. From there, you can add parameters as needed. For example:
  • wrapper.java.additional.1=-Xrs
  • wrapper.java.additional.1=-Djava.awt.headless=false
  • wrapper.java.additional.2=-showversion
  • wrapper.java.additional.3=-XX:+UseConcMarkSweepGC
  • wrapper.java.additional.4=-XX:+UseParNewGC
Default
-Xrs
wrapper.java.initmemory
Wrapper initial memory size in megabytes.
Default
128
wrapper.java.maxmemory
Wrapper maximum memory size in megabytes.
Default
512
wrapper.app.parameter.x
Application parameters. You can add parameters as needed. For example:
  • wrapper.app.parameter.1=org.eclipse.core.launcher.Main
  • wrapper.app.parameter.2=-consolelog
  • wrapper.app.parameter.3=-noExit
  • wrapper.app.parameter.4=-product
  • wrapper.app.parameter.5=com.wily.introscope.em.product
  • wrapper.app.parameter.6=-install
  • wrapper.app.parameter.7=./product/enterprisemanager
  • wrapper.app.parameter.8=-configuration
  • wrapper.app.parameter.9=./product/enterprisemanager/configuration
wrapper.startup.timeout
The number of seconds to allow between the time that the wrapper launches the JVM process and the time that the JVM side of the wrapper responds that the application started. Entering a 0 value means that the system will never time out.
Default
30 (seconds)
wrapper.console.format
The format of output for the console.
Default
PM
wrapper.console.loglevel
The log level for the console output.
Default
INFO
wrapper.logfile
The name and location of the log file that is used for wrapper output logging.
Default
./logs/EMService.log
wrapper.logfile.format
The format of the output for the log file.
Default
LPTM
wrapper.logfile.loglevel
The log level for log file output.
Default
INFO
wrapper.logfile.maxsize
The maximum size that the log file is allowed to grow to before the log is rolled. Size is specified in bytes. With the
0
default value disabling the log roll. You can abbreviate with a
k
(
kb
) or
m
(
mb
) suffix. For example,
10 m = 10 MB
.
Default
0
wrapper.logfile.maxfiles
The maximum number of rolled log files that are allowed before old files are deleted. The default value of 0 implies no limit.
Default
0
wrapper.syslog.loglevel
The log level for the system and event log output.
Default
NONE
Notes
Do not modify any of the following
ntservice
properties when an application using this configuration file has been installed as a service. Uninstall the service before modifying this section. After you have made modifications, the service can then be reinstalled.
wrapper.ntservice.name
Name of the service.
Default
IScopeEM
wrapper.ntservice.displayname
Display name of the service.
Default
Introscope Enterprise Manager
wrapper.ntservice.description
Description of the service.
Default
Introscope Enterprise Manager
wrapper.ntservice.dependency.x
Service dependencies. Add dependencies as needed starting from 1. For example:
  • wrapper.ntservice.dependency.1=
  • wrapper.ntservice.dependency.2=
  • wrapper.ntservice.dependency.3=
wrapper.ntservice.starttype
Mode in which the service is installed.
Settings
include
AUTO_START
or
DEMAND_START
.
Default
AUTO_START
wrapper.ntservice.interactive
Setting this value to
true
, starts the service to interact with the desktop.
Default
False