Learn / Deployment

Deployment · CERTSKOPE 0.6.15

Deploy to Tomcat and Java keystores

Use configured destinations and preserve unrelated key entries.

Updated 17 November 2026 ·

Target preparation

Java destinations require an installed keytool runtime and an administrator-configured keystore path, type, alias and protected credential. Tomcat also needs the configured connector and service. A platform profile alone does not create a deployment target.

Run and verify

  1. Select the certificate, target and JavaKeystore or Tomcat destination.
  2. Complete independent deployment approval and execution.
  3. Check the receipt for key-entry and fingerprint validation.
  4. For Tomcat, confirm the configured service restarted and the HTTPS endpoint presents the expected certificate.

Recovery

The worker stages the new store and maintains a backup for rollback. Keep the configured alias and store passwords consistent. Unrelated aliases should remain intact. Tomcat service restarts are restricted to configured allowlisted services.

Current scope

The Windows-hosted UAT Tomcat and Java keystore paths have been exercised. This does not establish support for every remote Linux/JVM product or appliance. Use a separate validation plan before enabling a new destination.

Continue exploring

Was this guide helpful?

This guide describes CertSkope 0.6.15. A saved integration profile alone does not activate an external connector. See feature availability.