Configure the CCMS Scheduler's Java wrapper

The Java wrapper offers utility methods used to manipulate application values. IXIA CCMS Scheduler's wrapper.conf file identifies its Java libraries, defines the Java heap's maximum size, and identifies the type of information it logs.

1. Open the wrapper.conf file in the %SchedulerDir%/conf directory.
   Note: If this is a first-time modification of the wrapper.conf file, locate the wrapper.conf.empty file, remove the empty suffix, and save it as wrapper.conf.
2. Edit the wrapper.java.command value so that it points to your Java executable.
   Windows example:

   #********************************************************************
   # Wrapper Java Properties
   #********************************************************************
   # Java Application
   wrapper.java.command=c:\Program Files\Java\jre<version of java>\bin\java.exe

   Linux example:

   #********************************************************************
   # Wrapper Properties
   #********************************************************************
   # Java Application
   wrapper.java.command=/usr/java/jdk1.7.0_51/jre/java

3. Configure the Java heap size:

   # Maximum Java Heap Size (in MB)
   wrapper.java.maxmemory=1024

   Note: Maximum heap size is the maximum amount of unused dynamic memory the Java Virtual Machine (JVM) is allowed to allocate for Scheduler activities. The recommended value is 1024 MB.
4. Configure the log level for Scheduler events:

   # Log Level for log file output.  (See docs for log levels)
   wrapper.logfile.loglevel=INFO

   Note: Possible event levels are listed in order of severity: DEBUG, INFO, WARN, ERROR. Events are logged for the indicated level and all severity levels above it. For example, if you enter WARN as the level, it logs both WARN and ERROR events.
5. Configure any additional wrapper parameters.
6. Save and close the wrapper.conf file.