Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anchor
configureTomcat
configureTomcat
Configure tomcat

context.xml: cache settings

The default Tomcat cache settings are insufficient for PhixFlow:

Add <Resources ... /> to at the end of the <Context/> block in context.xml so that the file looks something like this:

Code Block
languagexml
<Context>
    <!-- lines omitted -->
	<Resources cachingAllowed="true" cacheMaxSize="1000000" />
</Context>

Remember to enable this port in the server’s firewall (if enabled).

server.xml: Port Specification

...

(Optional)

By default, Tomcat will use ports 8080 for HTTP and 8443 for HTTPS.

If you need to use different ports, you can set them in $TOMCAT/conf/server.xml to specify the port that PhixFlow will use (usually 8081). Find the following lines and change as needed:. E.g.

Code Block
languagexml
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
    <Connector
		port="8081"
		maxHttpHeaderSize="8192" …

...

Code Block
languagexml
<session-config>
	<session-timeout>600<timeout>720</session-timeout>
</session-config>

...

Windows

  • Run the Tomcat Monitor
  • Open the Tomcat Monitor system tray Configure … menu
  • Select the Java tab
  • Set the Initial memory Pool (see table above)
  • Set the Max Memory Pool (see table above)
  • Add the following lines to the Java Options scrollable field:
Code Block
-XX:MaxPermSize=150m-Xms1024m
-Xmx1024m
-verbose:gc
-Djava.awt.headless=true

Unix/Linux

If you have installed the scripts in tomcat login scripts, these option will already be set however for clarity, these options are defined in the JAVA_OPTS environment variable set in the tomcat user’s shell startup file (e.g. .profile / .bash_profile / .cshrc in the user’s home directory – the actual startup file is determined by the user’s default shell settings).

Code Block
JAVA_OPTS=’-Xms1024m -Xmx1024m -XX:MaxPermSize=150m -verbose:gc -Djava.awt.headless=true’

...

As the root user, install the tomcat script listed in in tomcat service scripts and create a softlink soft link to it from the appropriate run-level directory. The actual run-level directories are specific to the particular unix variant.