Share This:

          As a member of the Customer Support Team, We are starting a new blogging section for trending topics in each month for Footprints, And that's the reason I thought it would be good to look at what has been trending over the last couple of months since we released of supporting OpenJDK and Tomcat 8.5. I used this data to identify areas and I would like to share some tips I’ve learned from working closely with our Footprints user base.

 

Install OpenJDK and Tomcat 8.5 for an upgrade or a fresh install of Footprints 20.XX

 

The following Apache Tomcat versions are supported.

 

FootPrints VersionTomcat Version
FootPrints 20.18.03 , 20.19.XApache Tomcat Version 8.5.x (64-bit)

 

Footprints and supported JAVA versions:

 

FootPrints VersionJava Version
FootPrints 20.19.03OpenJDK 13.0.2
FootPrints 20.19.02OpenJDK 12.0.2
FootPrints 20.19.01OpenJDK 11.0.2

   

How to install OpenJDK for usage in FootPrints Service Core 20.19.X onwards:

 

 

  • Open a command window with admin rights and run the following commands to set the JAVA_HOME and PATH environment variables to point to the correct Java Version

                   setx -m JAVA_HOME "C:\Progra~1\Java\jdk-11.0.2"          

                   setx -m PATH "%PATH%;%JAVA_HOME%\bin";           

 

Note :-The SETX -m PATH command does not work correctly if the PATH has more than 1024 characters. If you have a larger path you will need to make sure that the path is correct by editing your entire path. Set JAVA_HOME environment variable and add it to the path variable too (make sure in Path variable the location is added at the beginning)

Install and Configure Tomcat 8.5 :

   

Post-installation steps to configure Tomcat by following these steps:

  • Go to the Tomcat installation folder e.g. “C:\Program Files\Apache Software Foundation\Tomcat 8.5\bin”
  • Start the Tomcat Service Wrapper (Tomcat8w.exe)
  • Select JVM from C:\Program Files\Java\jdk-11.0.2\bin\server\jvm.dll.
  • The options that you should set and the values they are set to depend on your version of Java and the application server that you use (check below table)
  • In the Initial memory pool box, enter a value of 4096.
  • In the Maximum memory pool box, enter a value not more than 80% of your maximum server memory.

 

FootPrints VersionJava OptionsJava 9 Options
FootPrints 20.19.X-Dfile.encoding=UTF-8
-XX:+UseParallelGC
-Djava.awt.headless=true
--illegal-access=permit

 

 

User-added image

 

 

For all advanced configuration settings please go through the below article.

 

https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000010914

 

 

Some issues and troubleshooting steps:

 

1. “unable to find the Catalina/localhost folder” FootPrints 2018 Release 3 requires that administrators manually upgrade Tomcat to version 8.5  If the Tomcat service is not started immediately after installation, the Catalina/localhost folder will not be created under the /conf folder. The absence of the said folder would lead to the failure of the FootPrints upgrade/install. If you have attempted the upgrade and it failed, the subsequent attempts would fail, since the installer attempts to “move” the footprints#servicedesk.xml (or footprints.xml, depending on the name you had given) file. Due to the initial failure, this file will not be available in subsequent attempts. In this scenario, please follow the steps to install Tomcat 8.5 and copy the sample footprints#servicedesk.xml file, with modifications to suit the current setup (installed location, application name, etc) File is attached below.

 

 

2. Tomcat service must be configured to use Local System service account

  1. Click Start, point to Administrative Tools, and then click Services.
  2. Right-click on Apache Tomcat service, and then click Properties.
  3. Click the Log On tab, select Local system radio button, and then click Apply.
  4. Click the General tab, and then click Start to restart the service.

 

User-added image

 

 

3. High HTTP traffic and performance issue.

 

Sometimes you may notice that there is high HTTP traffic, and you may determine that it's because the server is attempting to return high volumes of data back to the browser. In this case, if you are running Tomcat, you have the added option of turning on compression at the application server level. To enable compression adding following attribute in server.xml file in the Connector port="8080"

 

compression="on" compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressibleMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/x-javascript,
application/javascript,application/xml,application/extjson,x-font/otf,application/x-font-woff,x-font/ttf,x-font/eot"

 

 

 

 

Thanks for reading the article. Please rate the blog and add comments to share your experiences.