Initializing help system before first use

Create the SSL Certificate Keystore

This topic explains how to create a keystore containing your existing SSL certificate and private key. The certificate within the keystore is used to encrypt the SSL connection.
Important: You must create keystores on both the server and each worker.
  1. Make sure the files for the SSL certificate (certificate.pem) and private key (privatekey.pem) are saved in the OS-dependent <SERVER_CONFIG_DIR> or <WORKER_CONFIG_DIR> directory.
    (For more information, see Finding Configuration Files.)
  2. Convert the PEM files into a temporary PKCS12 keystore file. You will be prompted to supply a password for this new keystore.
    On the server:
    openssl pkcs12 -export -name insight-server-https -in certificate.pem -inkey privatekey.pem -out temp-keystore.p12
    On a worker:
    openssl pkcs12 -export -name insight-worker-https -in certificate.pem -inkey privatekey.pem -out temp-keystore.p12
  3. Convert the PKCS12 keystore file into a Java keystore file. You will be prompted to enter the same password entered in the previous step, and to provide a password for the destination Java keystore.
    On the server:
    keytool -importkeystore -destkeystore insight-keystore -srckeystore temp-keystore.p12 -srcstoretype pkcs12 -alias insight-server-https
    On a worker:
    keytool -importkeystore -destkeystore insight-keystore -srckeystore temp-keystore.p12 -srcstoretype pkcs12 -alias insight-worker-https
  4. Remove the temporary PKCS12 keystore file (temp-keystore.p12).
  5. Remove the SSL certificate (certificate.pem) and private key (privatekey.pem), ensuring you retain a copy in a secure location for future reference.
Make sure you complete these steps on the server and each worker.

© 2001-2026 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.