web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Chapter 3 Chapter 3Partitions Important This section explains what Partitions are and how they work. It explores the Partition's footprint, facilities, configuration, and how to run a Partition. For documentation updates, go to www.borland.com/techpubs/bes. Partitions Overview Partitions are the runtime hosting environment for J2EE and web service application components. A Partition is a process that can be tuned to suit the application it is hosting. You can create any number of Partitions to isolate, scale, or cluster your application deployment to meet your own requirements. Extensive tooling enables you to simply create, configure, and distribute Partitions to your needs. A Partition provides containers and services needed for your applications: ■ Web Container ■ EJB Container ■ Naming Service ■ Session Service ■ Transaction Service ■ Connector Service ■ JDataStore Database Server ■ Partition Lifecycle Interceptor Service Additional applications and application components are also provided that can be used in your applications: ■ ■ ■ ■ ■ UDDI Server Apache Struts Apache Cocoon Petstore J2EE blueprint application SmarTicket J2EE blueprint application Chapter 3: Partitions 15
Creating Partitions Creating Partitions By enabling and disabling the various Partition containers and services, and configuring the Partition's environment, you can “right-size” the Partition to its specific task. Typical use cases for a Partition include: ■ ■ ■ Providing a complete isolated J2EE server platform for an application with all relevant J2EE container and services enabled. Providing a platform for a component of a distributed application such as its Web Tier with just the Web Container and Session Service enabled. Providing a central service such as a platform for the BES UDDI server with just its Web Container enabled. ■ Providing a diagnostic platform for an application such as running under Optimizeit. Avoiding monolithic J2EE server Partitions hosting many applications also allows you to fine tune the Java environment the application needs. The version and type of JDK together with such configuration as heap space available ensures a satisfactory environment in which to run, while not over-allocating resources. Limits on pooled resources such as threads and connections may similarly be configured for optimal total performance. Partitions also have their own individual security settings for authentication mechanisms, authorization tables, and so on. A user who has authority to access all resources in a development Partition may be granted much more limited authority in a production Partition. Partitions are created as Managed Objects in a “configuration” from templates provided in the Borland Management Console. Typically the Partition disk footprint is created in: /var/domains//configurations// You can specify another location for the Partition and add a pre-existing Partition to a configuration. The Management Console provides a rich configuration experience for a Partition and is discussed in the Management Console User's Guide. Most configuration data for the Partition and its services is captured in its partition XML reference file. See Chapter 30, “Partition XML reference.” 16 BES Developer’s Guide
- Page 1 and 2: Developer’s Guide Enterprise Serv
- Page 3 and 4: Contents Chapter 1 Introduction to
- Page 5 and 6: Entity beans . . . . . . . . . . .
- Page 7 and 8: Chapter 23 Using JMS 209 Configurin
- Page 9 and 10: Entity Bean Properties (applicable
- Page 11 and 12: Figures 0.1 Borland Enterprise Serv
- Page 13 and 14: BES Products and Editions overview
- Page 15 and 16: Documentation conventions Important
- Page 17 and 18: Contacting Borland support World Wi
- Page 19 and 20: BES services overview Figure 0.1 Bo
- Page 21 and 22: The Partition and its services ■
- Page 23 and 24: Borland Enterprise Server and J2EE
- Page 25: 14 BES Developer’s Guide
- Page 29 and 30: Running Partitions Table 3.1 Option
- Page 31 and 32: Configuring Partitions You can also
- Page 33 and 34: JMX support in Partitions ■ ■ A
- Page 35 and 36: JMX support in Partitions Figure 3.
- Page 37 and 38: Thread pools Partition properties r
- Page 39 and 40: 28 BES Developer’s Guide
- Page 41 and 42: Apache web server implementation Fo
- Page 43 and 44: Borland web container implementatio
- Page 45 and 46: Borland web container implementatio
- Page 47 and 48: Borland web container implementatio
- Page 49 and 50: Smart Agent implementation Smart Ag
- Page 51 and 52: 40 BES Developer’s Guide
- Page 53 and 54: Apache web server to Borland web co
- Page 55 and 56: Apache web server to Borland web co
- Page 57 and 58: Apache web server to Borland web co
- Page 59 and 60: Large data transfer Downloading lar
- Page 61 and 62: Large data transfer Uploading large
- Page 63 and 64: IIS web server to Borland web conta
- Page 65 and 66: IIS web server to Borland web conta
- Page 67 and 68: IIS web server to Borland web conta
- Page 69 and 70: Session management with JSS If an i
- Page 71 and 72: Managing and configuring the JSS Co
- Page 73 and 74: The Borland IIOP connector BES supp
- Page 75 and 76: Setting up your web container with
Chapter<br />
3<br />
Chapter 3Partitions<br />
Important<br />
This section explains what Partitions are and how they work. It explores the Partition's<br />
footprint, facilities, configuration, and how to run a Partition.<br />
For documentation updates, go to www.borland.com/techpubs/bes.<br />
Partitions Overview<br />
Partitions are the runtime hosting environment for J2EE and <strong>web</strong> service application<br />
components. A Partition is a process that can be tuned to suit the application it is<br />
hosting. You can create any number of Partitions to isolate, scale, or cluster your<br />
application deployment to meet your own requirements. Extensive tooling enables you<br />
to simply create, configure, and distribute Partitions to your needs.<br />
A Partition provides containers and services needed for your applications:<br />
■<br />
Web Container<br />
■<br />
EJB Container<br />
■<br />
Naming Service<br />
■<br />
Session Service<br />
■<br />
Transaction Service<br />
■<br />
Connector Service<br />
■<br />
JDataStore Database Server<br />
■<br />
Partition Lifecycle Interceptor Service<br />
Additional applications and application components are also provided that can be used<br />
in your applications:<br />
■<br />
■<br />
■<br />
■<br />
■<br />
UDDI Server<br />
Apache Struts<br />
Apache Cocoon<br />
Petstore J2EE blueprint application<br />
SmarTicket J2EE blueprint application<br />
Chapter 3: Partitions 15
Change language