This content describes how to manage Java on your client workstation.
To help prevent mismatched CA Privileged Access Manager Java cache contents during or after upgrading a Windows client workstation, clear the Oracle Java cache.
To clear the Java cache, open the Java control panel (Control Panel, Java) and remove all "Temporary Files".
We recommend that you adjust your Java heap so that with 4-GB total memory, 1024 MB is allocated to it.
An example of the adjustment mechanism would be to Assign the Java maximum heap size value in Runtime Parameters:
Note: Do not copy-and-paste the string into a word processor (such as Microsoft Word) before pasting into the Java Control Panel. This action might alter the characters. Instead, if you want to store the string, use a plain-text application such as Notepad.
To confirm that the heap adjustment has taken effect: When your mouse is in focus in the Java console, press: m to display the memory values. If successful, the results are close to the settings.
By default, CA Privileged Access Manager JARs are signed and are validated against a public Certificate Authority (CA). For many customers, this arrangement is sufficient and no further action is required. However, if your end users do not have access to the public Internet, this feature provides an alternative to signing CA Privileged Access Manager applets using an internal CA.
Note: If you are considering self-signing, we suggest you discuss this issue with CA Support.
You can have CA Privileged Access Manager sign its JAR files using certificates issued from any CA, including one located in your internal network, which is isolated from the Internet. To set the signing certificate:
Your clients must be configured to trust the public certificate that is used to sign the CA Privileged Access Manager JARs: