Partitioning and Clustering Demonstration
28 Pages
English

Partitioning and Clustering Demonstration

-

Downloading requires you to have access to the YouScribe library
Learn all about the services we offer

Description

Partitioning and Clustering
Demonstration
Improve performance for Web and application
®deployment with Borland Enterprise Server
A Borland White Paper
By Joe Overton, U.S. Systems Engineer, Borland Software Corporation
August 2002 ®Borland Enterprise Server
Contents
Introduction......................................................................... 3
Partitions ............................................................................ 3
Creating a new partition........................................................................................................3
Configuring partitions........................................................................................................... 5
Cloning partitions.................................................................................................................. 7
Clustering 8
Web Edition .......................................................................................................................... 8
Web Edition demo............................................................................................................................ 9
Persistent Manager....... 11
IIOP connector........................................................................................................................... 11
® ™VisiBroker and AppServer Editions ............................................................................... 17
Homogeneous configuration............................................ ...

Subjects

Informations

Published by
Reads 167
Language English
Document size 1 MB
Partitioning and Clustering Demonstration
Improve performance for Web and application
deployment with Borland®Enterprise Server
A B o r l a n d W h i t e P a p e r
By Joe Overton, U.S. Systems Engineer, Borland Software Corporation
August 2002
Borland®Enterprise Server
C o n t e n t s
I n t r o d u c t i o n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
P a r t i t i o n s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Creating a new partition ........................................................................................................ 3 Configuring partitions ........................................................................................................... 5 Cloning partitions.................................................................................................................. 7 C l u s t e r i n g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Web Edition .......................................................................................................................... 8 Web Edition demo............................................................................................................................ 9 Persistent Manager .................................................................................................................... 11 IIOP connector........................................................................................................................... 11 VisiBroker®and AppServerEditions ............................................................................... 17 H o m o g e n e o u s c o n f i g u r a t i o n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 7
H e t e r o g e n e o u s c l u s t e r i n g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 0
N a m i n g S e r v i c e f a i l - o v e r . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 0
S o n i c M Q®. . . . . . . . . . . 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  c l u s t e r 4
C o n c l u s i o n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 8
2
Borland®Enterprise Server
I n t r o d u c t i o n 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®of the most reliable and scalable J2EEEnterprise Server is one 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.
P a r t i t i o n s Partitions provide the environment for J2EE applications running in the Borland Enterprise Server. For example, each AppServerEdition partition instance provides:  Web container (Tomcat 4.0)for hosting JavaServer Pages(JSP) and servlets  EJBcontainerfor hosting Enterprise JavaBeans(EJB) components  Transaction Servicefor transaction management, including XA  Session ServiceJSS or JavaSession Service provides state management  Naming Servicesupports both VisiBroker®Edition and AppServer Edition  JDataStoreall-Javadatabase from Borland
Creating a new partition
To create a new partition, run the Borland Enterprise Server 5.1 server and console. From the console, expand enterprise servers and your server name.
3
Borland®Enterprise Server
Right-click on the partitions folder and selectNew partition.
Enter a name for the partition and selectOK.
A new partition is created based on the default located at: <installroot>\var\defaults\partitions\
4
Borland®Enterprise Server
The partition is idle (stopped) upon creation.
Configuration is required prior to starting the partition due to conflicts with other partition services. The common conflicts are: Tomcat HTTP port server.xml 8080 JDataStore remote JDBC®port jdatastore.properties 2508 Vbroker listener port vbroker.properties dynamic JDK®Home (if donor is remote) partition_server.config installDir/jdk
Configuring partitions
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
5
Borland®Enterprise Server
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.
It is required to change the port number the Web container uses before running a new partition. Right-click onWeb containerand selectconfigure.
Change the port number in Set Connector Properties section.
6
Borland®Enterprise Server
This is the minimum configuration required to get new partitions up and running.
Cloning partitions
After a partition is configured, it is often useful to make a copy. The cloning feature provides this function. To clone a partition, right-click on thepartitionand selectclone. It is required that the user stops the partition to be cloned. Configuration is required to eliminate any conflicts with the original partition.
7
Borland®Enterprise Server
Choose a name and a server for the cloned partition.
Note: you can choose the server for which the new cloned partition will run. This makes it very easy to create clustered partitions across many physical servers.
C l u s t e r i n g The following demos go through the clustering features of each edition of Borland Enterprise Server and focus on the services found in the AppServer, VisiBroker, and Web editions. Each enterprise application is unique and has its own configuration requirements.
Web Edition
Clustering the Web Edition requires two or more partitions with Web Edition services running (containers/JSS). This demo illustrates clustering multiple Web containers and synchronizing their sessions with a central JSS. The setup includes two partitions with Web containers, one partition with the JSS and the core services Smart Agent,and Apacherunning at the server level. Each Web container uses the JSS. Apache connects to each of the Web containers using the IIOP®plug-in. The lookup happens via the Smart Agent. This configuration allows for load balancing and fail-over at the Web container level.
8
Borland®Enterprise Server
Load balancing: The Smart Agent will round-robin requests from Apache to the Web containers. 
Fail-over: The Smart Agent will round-robin requests to the next available Web container. The Web container will load the current state from the JSS.
Diagram from Chapter 3 of the Developers Guide.
Web Edition demo The Developers Guide states:Borland Enterprise Server, Web Edition provides an operational Apache Web Server and Tomcat Web Container connection as out of the box
9
Borland®Enterprise Server
upon startup. The two components are connected with each other via the IIOP Plug-in. This Plug-in allows both Apache and Tomcat to communicate via Internet Inter-ORB Protocol (IIOP) to one another with no required configuration.
As an exercise, this demo will go through each configuration detail by modifying the defaults when possible. Do not start any partitions of services until instructed.
Step 1: Create a new Partition called JSSPartition, which represents machine 4 in the diagram. Disable all services except the Session Service. Right-click on theSession Serviceand configure. Change the factory name toJSSMachine4.
View of Console after step one refresh is required to show new factory name.
1 0
Borland®Enterprise Server
Step 2: Create a new Partition called Machine2, which represents machine 2 in the diagram. Disable all the services in Machine2 except the Web container. Right-click theWeb containerand configure. This brings up an editor with the Web containers configuration properties. General Tabserver.xml. Modify the following xml located near the button: Persistent Manager Uncomment the Manger XML, change the default storeName (jss_factory) toJSSMachine4, change the default maxIdleBackup (-1) to6 seconds. This setting is available to both the HTTP and IIOP connectors. For this example, change the setting for the IIOP connector. IIOP connector Change the default name (tc_inst1) to demon_connection and change the storeName to JSSMachine 4.
<Service name="IIOP"> <Connector name="demo connection" debug="0" _ className="org.apache.catalina.connector.iiop.IiopConnector"/> <Engine defaultHost="localhost" debug="0"name= "IIOP"> <Realm className="org.apache.catalina.realm.MemoryRealm"/> <Host debug="0" name="localhost" appBase="wars" unpackWARs="false" <Context debug="0" path="/examples"> <!Uncomment the following line for storing your session data in JSS --> <Manager className="org.apache.catalina.session.PersistentManager" debug="0" maxIdleBackup="-1" checkInterval="60"> <Store className="org.apache.catalina.session.BorlandStore" storeName="JSSMachine4" debug="0"/> </Manager>
Note: The Web Container also supports native session management. This allows Tomcat to talk directly to JDataStore. Using the JSS is recommended because of the following advantages:  given name, it can run anywhere in the localOnce you have defined a JSS with a network. Afterwards, stopping the initial JSS and starting a new one requires no changes to the configuration entries. This is called location transparency.
1 1