12.11.2014 Views

web server - Borland Technical Publications

web server - Borland Technical Publications

web server - Borland Technical Publications

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuring Partitions<br />

You can also host modules at locations outside the Partition footprint. To do so, open<br />

the partition.xml file for the Partition whose module paths you want to configure.<br />

Search for the element node. See Chapter 30, “Partition XML reference.”<br />

Within this node, you can configure archive repositories for all your archives by type, or<br />

provide the location of a specific archive that you want hosted outside the Partition<br />

repositories. See Chapter 30, “Partition XML reference” for syntax.<br />

In the Management Console, archives hosted within the Partition's footprint are called<br />

“Deployed Modules”. Archives that are hosted outside the Partition's footprint are<br />

called “Hosted Modules”.<br />

Working with Partition services<br />

The Partition allows you to specify which services will run within it and how they will<br />

behave in the context of the Partition instance. You can configure the Partition to<br />

automatically start some or all of its services at Partition startup. You can specify the<br />

order in which Partition services start and shut down. Additionally, you can configure<br />

which Partition services are configurable through the Management Console. Again, the<br />

partition.xml file captures this information as attributes of its element.<br />

Partition handling of services<br />

The element has four attributes, which are:<br />

autostart<br />

startorder<br />

shutdownorder<br />

administer<br />

The services to be started with the Partition.<br />

The startup order imposed on the Partition services included in the<br />

autostart.<br />

The shutdown order imposed on the Partition services running at<br />

shutdown.<br />

The Partition services that will appear in the Management Console<br />

as configurable.<br />

To set any one of these attributes, use either the Management Console or search the<br />

Partition's partition.xml file for the node. The valid value for each attribute<br />

is a space-separated list of Partition service names, which are read left to right. For<br />

example, if you wanted to shutdown a Partition service named ejb_container before a<br />

service named transaction_service, you would set the value of shutdownorder to:<br />

ejb_container transaction_service<br />

Configuring individual services<br />

Each Partition service is configurable within the context of its Partition parent. The<br />

partition.xml file captures information about individual services in the node,<br />

the child node of . In addition, you can use the sub-element<br />

within to set service-specific properties that do not come under the auspices<br />

of the Partition's runtime executable.<br />

If your services are to be included in the service node lists, you must define them with<br />

a service data block and give them a unique name using the name attribute. For a full<br />

description of the attributes that are configurable for Partition services, see Chapter 30,<br />

“Partition XML reference.”<br />

Configuring VisiNaming Service Clusters for BES<br />

To configure a VisiNaming cluster for BES, in addition to the steps outlined in the<br />

Configuring the VisiNaming Service Cluster section, in the VisiBroker for Java<br />

Developer's Guide, and in Configuring the VisiNaming Service Cluster section in the<br />

VisiBroker for C++ Developer's Guide, you must add the name of the factory to the<br />

property jns.name in partition.xml.<br />

20 BES Developer’s Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!