Show Contents / Index / Search

Changing the JVM

PKI Services Manager uses Java technology to support running on multiple platforms. PKI Services Manager installs its own Java Virtual Machine (JVM) and uses this installed JVM by default. It is also possible to configure PKI Services Manager to use a different JVM.

Note: If you upgrade your JVM (whether manually or automatically) it is installed to a new directory, so you'll need to repeat the following procedures to copy the unlimited strength policy files to the new directory and update the pointers to the new directory.

Apply the Unlimited Strength Jurisdiction Policy Files to your JVM

  1. Download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files from Oracle.
  2. Uncompress and extract the downloaded file, and locate the following two policy files.



  3. Replace the existing limited strength policy files (located in <java-home>\lib\security on Windows or <java-home>/lib/security on Unix) with the unlimited strength versions you extracted in the previous step.

To change the JVM on Windows

  1. Open the Windows Registry Editor and navigate to the following key (or create this key if it does not yet exist).


    (On 64-bit systems, use HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Attachmate\ReflectionPKI.)

  2. Create a new string value named JvmPath and set the value to point the full path where jvm.dll is located (<java-home>\bin\client).
  3. (Optional) You can create and edit a value called JvmParams for supplying any additional parameters or arguments. Use this feature if you are also configuring connections via a SOCKS proxy.

Note: The path to the JVM can also be set using the environment variable PKID_JVM_PATH on Windows systems. If the path is specified in both the registry and using the environment variable, the environment variable takes precedence.

To change the JVM on UNIX

To configure a JVM on UNIX you need to define an environment variable called PKID_JVM_PATH configured to point to the JVM shared library (either or depending on your UNIX operating system). For example, on Linux:

export PKID_JVM_PATH = /usr/java/default/jre/lib/amd64/server/

To create a persistent variable, you can use the following procedure.

  1. Log in as root.
  2. Open the pkid init script in a text editor.The default path is:

    Linux and Solaris:/etc/init.d/pkid

    HP-UX: /sbin/init.d/pkid

  3. Under the line that reads "export PKID_HOME" add lines to define and export the new variable. For example:

    PKID_JVM_PATH = /usr/java/default/jre/lib/amd64/server/

    export PKID_JVM_PATH

  4. Save the modified script.

Note: You can also configure an environment variable called PKID_JVM_PARAMS for supplying any additional parameters or arguments. Use this feature if you are also configuring connections via a SOCKS proxy.