Partitions - Embarcadero Developer Network

Partitioning and Clustering Demonstration Improve performance for Web and application deployment with Borland Enterprise Server ®

by Joe Overton, U.S. Systems Engineer, Borland Software Corporation

Introduction Rapidly changing business requirements mean corporations must roll out e-business applications faster than ever before. Modern Web applications require a solid deployment platform that supports rich, dynamic content and provides the tools necessary to implement caching, session management, and the database needs of real-world applications. The Borland® Enterprise Server is one of the most reliable and scalable J2EE™ application servers available, with sophisticated clustering, load balancing, fault tolerance, and fail-over. This paper offers demonstrations of clustering and partitioning with the Borland Enterprise Server.

Partitions Partitions provide the environment for J2EE applications

May 2002

running in the Borland Enterprise Server. For example, each AppServer™ Edition partition instance provides: •

Contents Partitions Clustering Homogeneous configuration Naming Service fail-over Conclusion

Web container (Tomcat 4.0)—for hosting JavaServer Pages™ (JSP™) and servlets

1 3 7 9 9

•

EJB™ container—for hosting Enterprise JavaBeans™ (EJB) components

•

Transaction Service—for transaction management, including XA

•

Session Service—JSS or Java™ Session Service provides state management

•

Naming Service—supports both VisiBroker® Edition and AppServer Edition

•

JDataStore™—all-Java™ database from Borland

Borland Enterprise Server

Creating a new partition

Configuration is required prior to starting the partition due to

To create a new partition, run the Borland Enterprise Server

conflicts with other partition services. The common conflicts

server and console. From the console, expand enterprise servers

are:

and your server name. Tomcat HTTP port JDataStore remote JDBC® port

server.xml

8080

jdatastore.properties

2508

Vbroker listener port vbroker.properties JDK® Home (if donor is remote)

partition_server.config

dynamic installDir/jdk

Configuring partitions

Right-click on the partitions folder and select New partition.

Every partition can have its own unique configuration details. This allows multiple J2EE applications to run in an isolated environment within one Borland Enterprise Server. When making configuration changes to the partition services, the console will prompt the user to restart the partition. It is recommended that the user decline the restart until all configurations have been made. Enter a name for the partition and select OK. It is required to change the port number the Web container uses before running a new partition. Right-click on Web container A new partition is created based on the default located at:

and select configure.

\var\defaults\partitions\

Change the port number in the section that reads: The partition is idle (stopped) upon creation. 2

Borland Enterprise Server



represents machine 3 in the diagram. All the services in Machine3 are disabled except the Web container.