Download and install the new
policy files. Important: Your country of origin
might have restrictions on the import, possession, use, or re-export
to another country, of encryption software. Before downloading or
using the unrestricted policy files, you must check the laws of your
country, its regulations, and its policies concerning the import,
possession, use, and re-export of encryption software, to determine
if it is permitted.
- Click Java SE 6
- Scroll down the page then click IBM SDK Policy files.
The
Unrestricted JCE Policy files for SDK 6 Web site displays.
- Click Sign in and provide your IBM®.com
ID and password.
- Select Unrestricted JCE Policy files for SDK 6 and
click Continue.
- View the license and click I Agree to continue.
- Click Download Now.
- Extract the unlimited jurisdiction policy files that are packaged
in the ZIP file. The ZIP file contains a US_export_policy.jar file
and a local_policy.jar file.
- In your WebSphere Application Server installation, go to the $JAVA_HOME/lib/security directory
and back up your US_export_policy.jar and local_policy.jar files.
- Replace your US_export_policy.jar and local_policy.jar files
with the two files that you downloaded from the IBM.com
Web site.
Following is an example of this copy operation.
$JAVA_HOME/demo/jce/policy-files/unrestricted/* to
$JAVA_HOME/lib/security
The embedded
Software Development Kit (SDK) ships with the unrestricted jurisdiction
policy Java™ archive (JAR) files.
Therefore, instead of downloading these files from the Web site, you
can symbolically link to the files as allowed by your local country
regulations. These unrestricted policy files are located in the install_root/java/demo/jce/policy-files/unrestricted/ directory.
The following UNIX-based commands enable you to symbolically link
to these files:
# Export the paths. You can find the values of the following
# variables in the joblog by searching for was.install.root,
# java.home, and so on:
export was.install.root=<was.install.root>
export java.home=<java.home>
# The previous paths apply to both 31- and 64-bit configurations
# of WebSphere Application Server for z/OS. For a 64-bit
# configuration, the java.home path points to the 64-bit embedded
# Java virtual machine (JVM).
# Delete the original policy .jar files. Because a backup is
# automatically present in the smpe.home HFS, an explicit
# backup is not needed:
cd $java.home/lib/security
rm US_export_policy.jar
rm local_policy.jar
# Issue the following commands on separate lines to create
# the symbolic links to the unrestricted policy files:
ln -s $java.home/demo/jce/policy-files/unrestricted/US_export_po licy.jar US_export_policy.jar
ln -s $java.home/demo/jce/policy-files/unrestricted/local_policy .jar local_policy.jar
Issue
the following UNIX-based commands to remove the symbolic links to
the unrestricted policy files in the demo directory and link to the
original files:
# Export the paths. You can find the values of the following
# variables in the joblog by searching for was.install.root,
# java.home, and so on:
export was.install.root=<was.install.root>
export java.home=<java.home>
export smpe.install.root=<smpe.install.root>
# The previous paths apply to both 31- and 64-bit configurations
# of WebSphere Application Server for z/OS. For a 64-bit
# configuration, the java.home path points to the 64-bit embedded
# Java virtual machine (JVM).
# Delete the current policy .jar files. You might want
# to back up the following files:
cd $java.home/lib/security
rm US_export_policy.jar
rm local_policy.jar
# Issue the following commands on separate lines to create
# symbolic links to the smpe HFS where the original files
# are kept:
ln -s $smpe.install.root/java/lib/security/US_export_policy.jar US_export_policy.jar
ln -s $smpe.install.root/java/lib/security/local_policy.jar local_policy.jar
![[Updated in December 2010]](../../deltaend.gif)
dec2010