Post Installation Tasks
Hardening & performance ..
Post‑installation Hardening & Tuning
Optional settings you can apply after installation to harden Tomcat/Pentaho and tune behaviour:
Hide Tomcat Server header
By default, Tomcat sends a Server header exposing version information. You can override it to reduce information leakage.
Edit the Tomcat connector in
server.xml.
sudo nano /opt/pentaho/server/pentaho-server/tomcat/conf/server.xmlAdd or update the
serverattribute on the HTTP connector and (if used) AJP connector, then save.
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
server=" "
redirectPort="8443" />Restart Pentaho Server.
sudo systemctl restart pentaho-serverJava Security Manager (deprecated/removed)
The legacy Java Security Manager is deprecated and not available on modern Java LTS versions (including Java 21). Do not use -security with Tomcat on Java 21. Prefer OS‑level hardening, least‑privilege users, network scoping, and container/AppArmor/SELinux policies as appropriate.
Change the web application context path
Change the context path if you do not want the application accessible at /pentaho.
Stop the Pentaho Server.
cd /opt/pentaho/server/pentaho-server
sudo ./stop-pentaho.shEdit
context.xml.
sudo nano /opt/pentaho/server/pentaho-server/tomcat/webapps/pentaho/META-INF/context.xmlUpdate the context path.
<Context path="/company" docBase="webapps/company/" />Rename the webapp folder to match the new context name.
sudo mv /opt/pentaho/server/pentaho-server/tomcat/webapps/pentaho \
/opt/pentaho/server/pentaho-server/tomcat/webapps/companyUpdate the redirect in
ROOT/index.jsp.
sudo nano /opt/pentaho/server/pentaho-server/tomcat/webapps/ROOT/index.jspChange the meta refresh to:
<meta http-equiv="refresh" content="0;URL=/company">Update the server URL.
sudo nano /opt/pentaho/server/pentaho-server/pentaho-solutions/system/server.propertiesfully-qualified-server-url=http://localhost:8080/company/Start the server and test.
sudo ./start-pentaho.shUpgrades may overwrite deployed webapps. Reapply customizations after upgrades, or use reverse proxy path mapping instead.
Change to HTTPs
Default port is 8080.
Stop the Pentaho Server.
cd /opt/pentaho/server/pentaho-server
sudo ./stop-pentaho.shChange the connector port.
sudo nano /opt/pentaho/server/pentaho-server/tomcat/conf/server.xml<Connector URIEncoding="UTF-8"
port="8443"
protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150"
SSLEnabled="true"
scheme="https"
secure="true"
clientAuth="false"
sslProtocol="TLS"
keystoreType="PKCS12"
keystoreFile="/opt/pentaho/pentaho-server/tomcat/ssl/keystore.p12"
keystorePass="changeit"
/>Update the server URL.
sudo nano /opt/pentaho/server/pentaho-server/pentaho-solutions/system/server.propertiesfully-qualified-server-url=http://localhost:8090/pentaho/Start the server and verify.
sudo ./start-pentaho.sh
curl -I http://localhost:8090/pentaho/ | head -n 1Change default HTTP port
Default port is 8080.
Stop the Pentaho Server.
cd /opt/pentaho/server/pentaho-server
sudo ./stop-pentaho.shChange the connector port.
sudo nano /opt/pentaho/server/pentaho-server/tomcat/conf/server.xml<Connector URIEncoding="UTF-8"
port="8090" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443"
relaxedPathChars="[]|"
relaxedQueryChars="^{}[]|&"
maxHttpHeaderSize="65536" />Update the server URL.
sudo nano /opt/pentaho/server/pentaho-server/pentaho-solutions/system/server.propertiesfully-qualified-server-url=http://localhost:8090/pentaho/Start the server and verify.
sudo ./start-pentaho.sh
curl -I http://localhost:8090/pentaho/ | head -n 1Harden or disable the Tomcat shutdown port
By default Tomcat listens on a local shutdown port (8005) for the SHUTDOWN command.
Disable the port by setting
port="-1", orChange both the port and the shutdown command to unpredictable values.
Edit the
<Server>element inserver.xml.
Examples:
or
Restart Pentaho Server.
Custom error pages (404, 403, 500)
Define application‑level error pages to avoid exposing defaults.
Create an error page in your webapp.
Add error mappings in the webapp
web.xml.
Restart the server and test.
Increase Karaf startup wait time
If server startup times out while Karaf installs features, increase the wait time.
Stop the server.
Edit
server.properties.
Uncomment or add:
Start the server.
Remove sample data from the server
Remove evaluation samples before moving to production.
Stop the server.
Delete the
samples.zipfrom default content (path may vary by version).
Edit the webapp
web.xmland remove the HSQLDB sample definitions and the SystemStatusFilter (dev‑only).
Remove blocks similar to:
Optionally remove the server
data/directory if only sample content was used (verify your environment before deleting).
Start the server and remove sample folders via PUC (Browse Files → Public → Move to Trash).
Hide Home perspective widgets
Hide Getting Started and other widgets from the PUC Home page.
Stop the server.
Edit the Home perspective configuration.
Add or update:
Start the server and log in to verify.
Turn off autocomplete on the login page (advanced)
Changing vendor JSPs may be overwritten on upgrade. Prefer SSO or reverse proxy controls. If you must, edit the login JSP.
Stop the server.
Edit
PUCLogin.jsp.
Set autocomplete to off for user/password inputs.
Start the server.
Increase CSV upload limits
Adjust upload limits and (optionally) staging database.
Edit
pentaho.xml.
Change the staging database for CSV files (optional) in
data-access/settings.xml.
In PUC, go to Tools → Refresh System Settings, then restart PUC (or the server) to apply.
Last updated
Was this helpful?
