- Java 8 or later, which is available at http://www.oracle.com/technetwork/java/javase/downloads/index.html
If you're not sure which version you have, you can run 'which java' to see if Java is already installed.
JAVA_HOME must point to the JRE/JDK. You can run ‘echo $JAVA_HOME’ (Linux) or 'echo %JAVA_HOME%' (Windows) to verify this.
PATH must include the path to java executable. You can run ‘java’ to verify that the executable is found.
CTP downloaded (via download link). You can request a download link by sending an email to your Parasoft representative.
Linux (Red Hat)
- Download Apache Tomcat 8 or higher from http://tomcat.apache.org/.
- Log in to the system as root.
- Extract Tomcat.
tar –zxvf apache-tomcat-<version>
This will create a new folder containing Tomcat.
- (Recommended) Move the extracted folder to a common installation location, such as
You may also want to configure Tomcat to start automatically when the server starts. There are two ways to do this:
- Edit init.d and using that to start/stop Tomcat, or
- Directly call
Edit the file to look like this:
TOMCAT_OWNER=parasoft references a user named ‘
parasoft’ to run the Tomcat service.
To start the Tomcat service:
To stop the Tomcat service:
To restart the Tomcat service:
To ensure that Tomcat gets started automatically at boot:
chkconfig tomcat on
Directly Calling <apache-tomcat-home>/bin/startup.sh
Alternatively, you can start Tomcat by directly calling the
<apache-tomcat-home>/bin/startup.sh script on Linux. If starting Tomcat this way, you will need to create a
<apache-tomcat-home>/bin/setenv.sh file with the following contents:
- Download the Apache Tomcat 8 or later 32-bit/64-bit Windows Service Installer from
- Run the installer. Select the Service Startup option during installation.
- After installation, open the Tomcat configuration controls from the system tray.
- For Java Options, set the perm gen size using
(note that Java Options are separated by new lines, not spaces) and set the maximum heap size to 768 MB.
Configuring SSL/HTTPS on Tomcat
CTP receives user passwords over a web interface. To ensure that passwords are encrypted when they are sent over the network, Tomcat should be configured to use only the HTTPS connector. For instructions on how to configure HTTPS in Tomcat, see the Apache Tomcat SSL/TLS Configuration HOW-TO topic (http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html or http://tomcat.apache.org/tomcat-8.0-doc/ssl-howto.html).
Be sure that the Tomcat secure connector sslEnabledProtocols only include "TLS" and not any "SSL" protocols. SSL protocols are vulnerable to "Padding Oracle On Downgraded Legacy Encryption" (POODLE) man-in-the-middle attacks.
Here's an example of what a Tomcat secure connector might look like:
Additional Configuration for UTF-8 Encoding
To ensure proper parsing of Japanese characters and other non-ASCII characters, add
URIEncoding="UTF-8" to the
<Connector> in Tomcat's server.xml. For example: