29 lines
1.6 KiB
HTML
29 lines
1.6 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head>
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
|
|
|
<title>Configure the was.policy file</title>
|
|
</head>
|
|
|
|
<BODY>
|
|
<!-- Java sync-link -->
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
|
|
|
<h5><a name="seccj2wa"></a>Configure the was.policy file</h5>
|
|
|
|
<p>Java 2 Security uses several policy files to determine the granted permission for each Java program. The was.policy file is a application-specific policy file for an enterprise application. It is embedded in the EAR file (META-INF/was.policy).</p>
|
|
|
|
<p>The union of the permission contained in the java.policy file, server.policy file, the app.policy file, the application's was.policy file, and the permission specification of ra.xml file are applied to the enterprise application.</p>
|
|
|
|
<p>If the default permissions for enterprise application are enough, no action is required. If an application must access a specific resource, you may need to update the was.policy file. Note that syntax errors in the policy file may cause the application server to fail to start.</p>
|
|
|
|
<p>To create or update the was.policy file for your application, See <a href="seccupol.htm">Create and edit policy files with the policy tool</a>. After you have created the was.policy file, you must add it to your application. See <a href="secaddwp.htm">Add the was.policy file to applications</a> for more information.</p>
|
|
|
|
<p>Restart your enterprise application for the changes to take effect.</p>
|
|
|
|
</body>
|
|
</html>
|
|
|