12.11.2014 Views

web server - Borland Technical Publications

web server - Borland Technical Publications

web server - Borland Technical Publications

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Creating Partitions<br />

Creating Partitions<br />

By enabling and disabling the various Partition containers and services, and<br />

configuring the Partition's environment, you can “right-size” the Partition to its specific<br />

task. Typical use cases for a Partition include:<br />

■<br />

■<br />

■<br />

Providing a complete isolated J2EE <strong>server</strong> platform for an application with all<br />

relevant J2EE container and services enabled.<br />

Providing a platform for a component of a distributed application such as its Web<br />

Tier with just the Web Container and Session Service enabled.<br />

Providing a central service such as a platform for the BES UDDI <strong>server</strong> with just its<br />

Web Container enabled.<br />

■<br />

Providing a diagnostic platform for an application such as running under Optimizeit.<br />

Avoiding monolithic J2EE <strong>server</strong> Partitions hosting many applications also allows you<br />

to fine tune the Java environment the application needs. The version and type of JDK<br />

together with such configuration as heap space available ensures a satisfactory<br />

environment in which to run, while not over-allocating resources. Limits on pooled<br />

resources such as threads and connections may similarly be configured for optimal<br />

total performance. Partitions also have their own individual security settings for<br />

authentication mechanisms, authorization tables, and so on. A user who has authority<br />

to access all resources in a development Partition may be granted much more limited<br />

authority in a production Partition.<br />

Partitions are created as Managed Objects in a “configuration” from templates provided<br />

in the <strong>Borland</strong> Management Console. Typically the Partition disk footprint is created in:<br />

/var/domains//configurations//<br />

You can specify another location for the Partition and add a pre-existing Partition to a<br />

configuration. The Management Console provides a rich configuration experience for a<br />

Partition and is discussed in the Management Console User's Guide. Most<br />

configuration data for the Partition and its services is captured in its partition XML<br />

reference file. See Chapter 30, “Partition XML reference.”<br />

16 BES Developer’s Guide

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

Saved successfully!

Ooh no, something went wrong!