Home > user > design > Apache Tomcat Pack

Apache Tomcat Pack

The Tomcat pack provides the user with the ability to use Apache Tomcat as a platform in their assembly.

Example - Log file catalina.out

The default log file for Tomcat is catalina.out and both System.out and System.err are redirected to it. The location of the file is configured via LogFilesPath and defaults to /log/apache-tomcat. The system logrotate is used to control the rotation and retention on the basis of eight days or 2GB per compute.

Keep in mind that compute storage is ephemeral and log as therefore not kept. For all critical application logging and statistics gathering usage of logmon is recommended.

Example - SSL Termination for Tomcat

SSL configuration for Tomcat is similar to the usage with the apache pack relying on the certificate component. As a Java application, Tomcat also requires configuration of the keystore component.

At Load Balancer

In this method communication from client to the load balancer is encrypted (HTTPS), but the communication from load balancer to Tomcat is server is in clear text (HTTP).

  1. Add a new lb-certificate component to the tomcat platform design and configure the certificate details.
  2. Disable the Enable TLSv1 configuration on the tomcat component.
  3. Add a load balancer lb component and set the Listeners to https 443 http 8080.
  4. Commit the design changes and proceed with deployment as usual.

Directly at Tomcat

In this method communication is encrypted from client to load balancer (HTTPS) and from load balancer to Tomcat (HTTPS).

  1. Add a new certficate component to the tomcat platform in design and configure the certificate.
  2. Add a keystore component and configure it.
  3. Configure the SSL Port in your tomcat component as needed. The default is 8443.
  4. If desired, disable the HTTP Connector in the tomcat component.
  5. Add a load balancer lb component and set the Listeners to ssl_bridge 443 ssl_bridge 8443. 7.Commit the design changes and proceed with deployment as usual.

Example - Configure Tomcat HttpConnector Attributes

To add attributes to a connector element or change the default value of a connector attribute, follow the steps below. For additional details, refer to the Tomcat Connection documentation.

  1. Go to the Tomcat configuration in your design.
  2. Change the protocol to what is appropriate for your application or port. (Normally you would do this in design.) The default value is the same as the Tomcat default which is 'HTTP/1.1'.

    Key ‘HTTP/1.1’ Value ‘HTTP/1.1’
    Blocking Java connector org.apache.coyote.http11.Http11Protocol
    Non blocking Java connector org.apache.coyote.http11.Http11NioProtocol
    The APR/native connector org.apache.coyote.http11.Http11AprProtocol
  3. Change the attributes that require tuning by using Additional attributes needed for connector config.*
   <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080 -->

    <!-- A "Connector" using the shared thread pool-->
    <Connector executor="tomcatThreadPool"
               <!--  All additional Attributes go here eg below -->

    <!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation -->

<!-- opted in to ssl activation w/ keystore -->
<Connector port="8443"
protocol="HTTP/1.1" SSLEnabled="true"
scheme="https" secure="true"
clientAuth="false"  sslProtocol="TLSv1" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2"
 <!--  All additional Attributes go here eg below -->

Currently you can not add multiple connectors to Tomcat. It is important to test performance on these settings in the lower environment before you do it in production.

The SSL connector is only configured, if you have KeyStore and certificate optional component. For instructions on how to enable SSL, refer to SSL Certificate Component