user manual

22 BES Developer’s Guide
Configuring Partitions
Any output sent to System.out or System.err is redirected as log4j events to the
logs. System.out is logged at the INFO level and System.err is logged at the
ERROR level.
If your application uses log4j then to configure application logging you should
edit the Partition's <partitionpath>/adm/properties/logConfiguration.xml file.
Configuring Partitions
Partitions offer a variety of fully-configurable services. This section discusses
how to work with Partition services, including archives, security, application
services, and statistics.
Application archives
Application components are hosted in the Partition itself. You can dynamically
deploy application archives to Partitions prior to running them or when they
are running. If the application archive is already hosted by the Partition, then it
is unloaded and the new archive loaded. To deploy modules to a Partition,
simply right-click its icon in the Management Console's Navigation Pane, and
select Deploy Modules. The deployed modules appear in the Partition
footprint, as shown in the Partition Footprint figure in “Creating Partitions” on
page 18.
You can also host modules at locations outside the Partition footprint. To do
so, open the partition.xml file for the Partition whose module paths you want
to configure. Search for the <archives> element node. Within this node, you
can configure archive repositories for all your archives by type, or provide the
location of a specific archive that you want hosted outside the Partition
repositories. See <archives> element in Chapter 30, “Partition XML reference”
for syntax.
In the Management Console, archives hosted within the Partition's footprint
are called "Deployed Modules". Archives that are hosted outside the
Partition's footprint are called "Hosted Modules".
Working with Partition services
The Partition allows you to specify which services will run within it and how
they will behave in the context of the Partition instance. You can configure the
Partition to automatically start some or all of its services at Partition startup.
You can specify the order in which Partition services start and shut down.
Additionally, you can configure which Partition services are configurable
through the Management Console. Again, the partition.xml file captures this
information as attributes of its <services> element.