Summary
Question
In some cases it may be necessary to update the Java Cryptography Extension (JCE) to allow connectivity to a database which uses encrypted communications
Answer
1) Download the JCE from here: https://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
Note that a newer version may be available. Make sure the version used aligns with the JDK/JVM currently used.
2) Extract the downloaded .zip. One file is the readme, the other two files “local_policy.jar” and “US_export_policy.jar”
Now, where these files are placed is a variable. In short they need to be placed within a couple of locations within the ALM or Octane installation paths where the java resides.
Mind that this path differs from where ALM is deployed.
ALM 12.5x
Linux...
/root/ALM/ALM/jre/lib/security
And
/root/ALM/ALM/java/jre/lib/security
Windows...
<drive>\Program Files\HP(E)\ALM\ALM\java\jre\lib\security
And
<drive>\Program Files\HP(E)\ALM\ALM\jre\lib\security
ALM 12.60, 15.00, or Octane...
Linux
1) Open a shell and type: whereis java
2) Note the path, denoted as '<path>' below...
<path>/jre/lib/security/policy/limited/
<path>/jre/lib/security/policy/unlimited/
Windows
<drive>\Program Files\Java\jdk1.8.0_<minor_version>\jre\lib\security
And
<drive>\Program Files\Java\jre1.8.0_<minor_version>\lib\security
Note: Be mindful when updating on Linux because there can be wide variances where a JDK/JVM is located and used by ALM or Octane. If the correct JDK/JVM isn't updated this procedure will have no effect. Risk is low however as this isn't likely to break anything.
The files “local_policy.jar” and “US_export_policy.jar” need to be placed in both of the paths above.
3) Restart ALM or Octane for the changes to take effect