user manual

24 BES Developer’s Guide
Configuring Partitions
Security management and policies
Each Partition can have its own security settings. You can specify the security
manager to use for each Partition by specifying a valid security class. You can
also set the Policy to use for that manager (generally using a .policy file). You
can configure security using either the Management Console or by setting the
attributes of the <security> node of partition.xml. For more information, see
Chapter 30, “Partition XML reference”.
Classloading policies
You can configure the Partition's classloading policies, including the prefixes
to load, the classloader policy, and whether or not to verify JARs as they are
being loaded. You can configure classloading either using the Management
Console or by setting attributes of the <container> node of partition.xml.
The system.classload.prefixes attribute takes a comma-separated list of
resource prefixes as its value. These prefixes are delegated from the custom
classloader to the system classloader prior to attempting its own load. The
classloader.classpath attribute contains a semicolon-separated list of JARs to
be loaded by each instance of the application classloader. To verify the JARs
as they load, set the verify.on.load attribute to true, the default.
The classloader policy is set in the classloader.policy element. There are two
acceptable values:
Partition Lifecycle Interceptors
You can use Partition Lifecycle Interceptors to further customize your
implementation. Partition Lifecycle Interceptors allow you to perform
operations at certain points in a Partition's lifecycle. You deploy a Java class
that implements:
com.borland.enterprise.server.Partition.service.PartitionInterceptor
and contains code to perform operations at one or more of the following
interception points:
■
At Partition initialization before any Partition services (Tomcat, for example)
are created and initialized.
per_module Creates a separate application
classloader for each deployed module.
This policy is required for hot
deployments (deployments while the
Partition is running).
container Loads all deployed modules in the
shared classloader. This policy
prevents the ability to hot deploy.