Install Java Cryptography Extension (JCE) in RHEL6
 

I want to install Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files patch in RHEL6.4, can any one tell me step by step process to install. In my newly build virtual Redhat server, I have Oracle SunJDK 1.7.0.45 and Jboss 6.1.1 EAP installed and are running.

I have download Unlimited JCEP Policy JDK7.zip. Here 7 means it is for Oracle SunJDK1.7 right??

Thank you very much in advance.

...and putting "how to install Java Cryptography Extension Unlimited Strength Jurisdiction Policy Files patch in RHEL6.4" into Google yields:
http://www.oracle.com/technetwork/ja...ion/index.html
http://docs.oracle.com/cd/E13205_01/...n.html#1053703

...and since you're using Red Hat Enterprise, you can use their support for more assistance should you need it, since you're paying for RHEL, right?

Anyway Thank you very much, I solved the problem. My virtual machine is running RHEL6.4 and application software oracle JDK1.7. So, I used Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7. unziped it and there is two files local_policy.jar and US_export_policy.jar copied to /usr/java/ jdk1.7.0_60/jvm/jre/lib/security. It should be noted that there is previously two jar file of same name (local_policy.jar and US_export_policy.jar) so delete those and put the new jar files.

Glad you solved the problem...but isn't what you posted exactly what the instructions say to do???

yes... there are bunches of resources but where I was stucked is how to find the path location that I have specified above in my comment. I googled and in some articles they have mentioned the path as /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/security and in some /usr/lib64/jvm/java-1_4_2-ibm-1.4.2_sr10/jre/lib/security. Finally, little hard work I was able to find the path where I need to put those jar files. sorry to say I am not that level of expert :) . Anyway Thank you very much TBone

That path location varies from machine to machine, which is why the instructions don't provide it. Running "find / -name <filename>", would tell you where a file is, as would the "locate" command.