Use this page to enable server level security and specify other server level security configurations.
To view this administrative console page, click Servers > Application Servers > server_name > Server Security > Server Level Security.
Configuration tab
Data type | Boolean |
Default | Disable |
If your application policy file is not set up correctly, see Configuring the was.policy file for information on how to configure an application policy file.
Data type | Boolean |
Default | Disabled |
Range | Enabled or Disabled |
Data type | Boolean |
Default | Disabled |
Range | Enable or Disable |
Data type | Integer |
Units | Seconds |
Default | 600 |
Range | Greater than 30 seconds. Avoid setting cache timeout value to 30 seconds or less. |
WebSphere Application Server provides support for policy file management. A number of policy files are included in WebSphere Application Server. Some of these policy files are static and some of them are dynamic. Dynamic policy is a template of permissions for a particular type of resource. In dynamic policy files, the code bases are evaluated at run time using configuration data. You can add or remove permissions, as needed, for each code base. However, do not add, remove, or modify the existing code bases. The real code base is dynamically created from the configuration and run-time data. The filter.policy file contains a list of permissions that an application does not have, according to the J2EE 1.3 Specification. For more information on permissions, see Java 2 security policy files.
Data type | Boolean |
Default | Enabled |
Range | Enable or Disable |
You can use an Object Management Group (OMG) protocol called Common Secure Interoperability Version 2 (CSIv2) for more vendor interoperability and additional features. If all of the servers in your entire security domain are Version 5.0 servers, it is best to specify CSI as your protocol.
Data type | String |
Default | CSI and z/SAS |
Range | CSI, CSI and z/SAS |