This topic provides some configuration tips for getting started
with your Tomcat application server.
Keep in mind that complete documentation on configuring and using the
Tomcat server is available at this URL for the server:
This topic provides some configuration tips that are specific to the
Integrator ETL Server application.
Creating a setenv file
It is recommended that you create a file named
(Linux) and place it in the Tomcat
directory. With this file (which is run by the
scripts), you can change the following
Tomcat environment settings with the
- You can set the minimum
and maximum memory heap size with the JVM
-Xmx parameters. The best limits depend on many
conditions, such as transformations that Integrator ETL should execute. For
Information Discovery transformations, a maximum of 1 GB is recommended. For
example, to set the minimum heap size to 128 MB and the maximum heap size to
1024 MB, use:
- You should set the
maximum limit of the PermGen (Permanent Generation) memory space to a size
larger than the default. The default of 64 MB is not enough for enterprise
applications. A suitable memory limit depends on various criteria, but 256 MB
would make a good choice in most cases. If the PermGen space maximum is too
OutOfMemoryError: PermGen space errors may occur.
You can set the PermGen maximum limit with the following JVM parameter:
- For performance reasons,
it is recommended that the application is run in Server mode. Apache Tomcat
does not run in Server mode by default. You can set the Server mode by using
-server parameter. You can set the JVM parameter in
JAVA_OPTS variable in the environment variable in
The following is an example of a
set "JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx1024m -XX:MaxPermSize=256m -server"
About database connections
By default, Integrator ETL Server uses an embedded Apache Derby
database. This database is suitable for testing and evaluation environments. In
these environments, no additional configuration is necessary.
In production environments, use of the embedded Derby database is not
recommended. In these environments, you should use a robust, production-quality
database, such as an Oracle or MySQL database. For details about configuring
these databases, see the
Integrator ETL Server Guide.