Before you begin
Java 2 security uses several policy files to determine the granted permission for each Java program. See Dynamic policy for the list of available policy files. The Java Development Kit provides the Policy Tool tool to edit these policy files. This tool is recommended for editing any policy file to verify the syntax of its contents. Syntax errors in the policy file cause an AccessControlException exception during application execution, including the server start. Identifying the cause of this exception is not easy because the user might not be familiar with the resource that has an access violation. Be careful when you edit these policy files.Steps for this task
%{was.install.root}/java/jre/bin/policytool
The Policy Tool window opens. The Policy Tool looks for the .java.policy file in your home directory. If it does not exist, an error message displays.
app_server_root/InstalledApps/testcase.earwhere the app_server_root variable represents your installation location.
Result
A policy file is updated. If any policy files need editing, use the Policy Tool tool. Do not edit the policy file manually. Syntax errors in the policy files can potentially cause application servers or enterprise applications to not start or function incorrectly. For the changes in the updated policy file to take effect, restart the Java processes.Related concepts
Java 2 security policy files
Related tasks
Configuring Java 2 security policy files
Configuring static policy files
Protecting system resources and APIs (Java 2 security)