The library.policy file is the template for Java library classes. Shared libraries can be defined and be used by multiple enterprise applications. For information about defining and managing shared libraries, see Administer shared libraries in the Administration topic.
If the default permissions for shared library (which is the union of the permissions that are defined in the java.policy file, the app.policy file, and the library.policy file) are adequate, no action is required. If a specific change is required to access a shared library in the cell, update the library.policy file.
Note: Do not place the codebase keyword or any other keyword after the grant keyword. The Signed By and the Java Authentication and Authorization Service (JAAS) principal keywords are not supported in the library.policy file. However, the Signed By keyword is supported in the following policy files: java.policy and server.policy. The JAAS principal keyword is supported in a JAAS policy file when it is specified by the Java Virtual Machine (JVM) system property, java.security.auth.policy. You can statically set the authorization policy files in java.security.auth.policy with auth.policy.url.n=URL where n is an integer and URL is the location of the authorization policy.
The union of the permissions that are contained in the java.policy file, the app.policy file and the library.policy file are applied to the shared libraries.
The WebSphere Application Server - Express library.policy file in located in the /QIBM/UserData/WebASE51/ASE/instance/config/cells/cell/nodes/node directory, where instance is the name of your instance, cell is the name of your cell, and node is the name of your node.
By default, the file contains empty permission entry:
grant {
};
Use the policy tool to update the library.policy file for your instance. For more information, see Create and edit policy files with the policy tool.