JAVAOPTS is not a variable recognized by JVM (atleast by the Oracle/Sun/OpenJDK JVM). A search of OpenJDK source code including the hotspot native C/C code shows that while it does have knowledge of some env vars like JAVAHOME / JREHOME / CLASSPATH / JAVAOPTIONS, it does not refer to JAVAOPTS anywhere. From: Marco Antonio mailto:hidden email Subject: Re: How to set JAVAOPTS variable in tomcat6.0.16 Hi, just need to have the variable JAVAOPTS exported. # export JAVAOPTS='-Xms1024m -Xmx1024m' That works for Linux (except for the leading # that turns it into a comment), but says nothing for Windows script or service usage. Setting Environment variables and System properties for Tomcat Server. Windows Environment: Create a file called setenv.bat in tomcat bin directory. Example: tomacta/bin/ setenv.bat. Set JAVAOPTS=% JAVAOPTS% -Djava.awt.headless=true The following is example for setting multiple properties.

1. Java_opts Environment Variables
2. Java_opts Environment Variable Examples
3. Java Opts Environment Variable
4. Java_opts Environment Variable Example

Transformer includes several environment variables that you can modify to customize the following areas:

• User and group used to start Transformer as a service
• Java configuration options, including the Java heap size, remote debugging, and garbage collection
• Security Manager that restricts the runtime permissions of user libraries
• Path to JAR files to be added to the root classloader

Modifying Environment Variables

The method that you use to modify environment variables depends on the Transformer

Java_opts Environment Variables

installation type:

Tarball installation started manually from the command line

When you start Transformer manually from the command line on any operating system, edit the $TRANSFORMER_DIST/libexec/transformer-env.sh file to modify environment variables.

Java_opts Environment Variable Examples

Use a text editor to edit the transformer-env.sh file. Some of the environment variables in the file are commented out and do not reflect the default values. Be sure to uncomment the line when you change a variable value.

After you edit the file, restart Transformer from the command prompt to enable the changes.

RPM installation started as a service on operating systems that use the SysV init system

When you start Transformer as a service on CentOS 6, Oracle Linux 6, or Red Hat Enterprise Linux 6, edit the $TRANSFORMER_DIST/libexec/transformerd-env.sh file to modify environment variables.

Use a text editor to edit the transformerd-env.sh file.

Java Opts Environment Variable

After you edit the file, restart Transformer to enable the changes.

RPM installation started as a service on operating systems that use the systemd init system

When you start Transformer as a service on CentOS 7, Oracle Linux 7, or Red Hat Enterprise Linux 7, edit the /usr/lib/systemd/system/transformer.service file to modify environment variables.

Override the default values in the transformer.service file using the same procedure that you use to override unit configuration files on a systemd init system. For an example, see 'Example 2. Overriding vendor settings' in this systemd.unit manpage.

After overriding the default values, use the following command to reload the systemd manager configuration:

Java_opts Environment Variable Example

Then restart Transformer to enable the changes.