web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
The Partition and its services JMS Borland Enterprise Server provides support for standard JMS pluggability, and currently bundles the Tibco messaging service. Additionally, BES is certified to support SonicMQ. Refer to the “JMS Provider Puggability” section for vendor-specific information on JMS services. Smart Agent Note The Smart Agent is a distributed directory service provided by the VisiBroker ORB used in BES. The Smart Agent provides facilities used by both client programs and object implementations, and must be started on at least one host within the local server network. Users of the Web Edition do not have to use the Smart Agent if they expect their Web server and Web containers to communicate through HTTP or another Web protocol. To leverage the IIOP Plug-in (and, by extension, the ORB provided with the Web Edition), however, the Smart Agent must be turned on. More than one Smart Agent can be configured to run on your network. When a Smart Agent is started on more than one host, each Smart Agent will recognize a subset of the objects available and communicate with the other Smart Agents to locate objects it cannot find. In addition, if one of the Smart Agent processes should terminate unexpectedly, all implementations registered with that Smart Agent discover this event and they will automatically re-register with another Smart Agent. It should be noted that If a heavy services lookup load is necessary, it is advisable to use the Naming Service (VisiNaming). VisiNaming provides persistent storage capability and cluster load balancing whereas the Smart Agent only provides a simple round robin on a per osagent basis. For more information, go to the “Using the SmartAgent” sections. 2PC Transaction Service The Two-Phase Commit (2PC) Transaction Service exists provides a complete recoverable solution for distributed transactional CORBA applications. Implemented on top of the VisiBroker ORB, the 2PC Transaction Service simplifies the complexity of distributed transactions by providing an essential set of services, including a transaction service, recovery and logging, integration with databases, and administration facilities within one, integrated architecture. The Partition and its services A Partition is an application's deployment target. The Partition provides the J2EE server-side runtime environment required to support a complete J2EE 1.3 application. While a Partition is implemented as a single native process, its core implementation is Java. When a Partition starts, it creates an embedded Java Virtual Machine (JVM) within itself to run the Partition implementation and the J2EE application code. Partitions are present in each BES Edition and product but they host less diverse archives in the Web Services, Team and VisiBroker Editions. This section describes the full-featured functional Partitions offered in the full Borland Enterprise Server. Each Partition instance provides: ■ “Connector Service” on page 10 ■ “EJB Container” on page 10 ■ “JDataStore Server” on page 10 Chapter 2: Borland Enterprise Server overview and architecture 9
The Partition and its services ■ “Lifecycle Interceptor Manager” on page 10 ■ “Naming Service” on page 10 ■ “Session Storage Service” on page 11 ■ “Transaction Manager” on page 11 ■ “Web Container” on page 11 Connector Service The Connector Service, also known as VisiConnect, is the Borland implementation of the Connectors 1.0 standard, which provides a simplified environment for integrating various EISs with the Borland Enterprise Server. The Connectors provide a solution for integrating J2EE-platform application servers and EISs, leveraging the strengths of the J2EE platform - connection, transaction and security infrastructure - to address the challenges of EIS integration. For more information see Chapter 26, “VisiConnect overview.” EJB Container The Borland Enterprise Server provides integrated EJB container services. These services allow you to create and manage integrated EJB containers or EJB containers across multiple Partitions. Use this service to deploy, run, and monitor EJBs. Tools include a Deployment Descriptor Editor (DDEditor) and a set of task wizards for packaging and deploying EJBs and their related descriptor files. EJB containers can also make use of J2EE connector architecture, which enables J2EE applications to access Enterprise Information Systems (EISs). JDataStore Server Borland's JDataStore is a relational database service written entirely in Java. You can create and manage as many JDataStores as desired. For more information on JDataStore, see the JDatastore online documentation at www.borland.com/techpubs/ jdatastore. Lifecycle Interceptor Manager You can use Lifecycle Interceptors to further customize your implementation. Partition Lifecycle Interceptors allow you to perform operations at certain points in a Partition's lifecycle. For more information see Chapter 25, “Implementing Partition Interceptors.” Naming Service The Naming Service is provided by the VisiBroker ORB. It allows developers, assemblers, and/or deployers to associate one or more logical names with an object reference and store those names in a VisiBroker namespace. It also allows application clients to obtain an object reference by using the logical name assigned to that object. Object implementations can bind a name to one of their objects within a namespace which client applications can then use to resolve a name using the resolve() method. The method returns an object reference to a naming context or an object. For more information refer to the Using the VisiNaming Service for Java and C++ sections. 10 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: BES services overview Figure 0.1 Bo
- Page 23 and 24: Borland Enterprise Server and J2EE
- Page 25 and 26: 14 BES Developer’s Guide
- Page 27 and 28: Creating Partitions Creating Partit
- 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
The Partition and its services<br />
JMS<br />
<strong>Borland</strong> Enterprise Server provides support for standard JMS pluggability, and<br />
currently bundles the Tibco messaging service. Additionally, BES is certified to support<br />
SonicMQ. Refer to the “JMS Provider Puggability” section for vendor-specific<br />
information on JMS services.<br />
Smart Agent<br />
Note<br />
The Smart Agent is a distributed directory service provided by the VisiBroker ORB<br />
used in BES. The Smart Agent provides facilities used by both client programs and<br />
object implementations, and must be started on at least one host within the local <strong>server</strong><br />
network.<br />
Users of the Web Edition do not have to use the Smart Agent if they expect their Web<br />
<strong>server</strong> and Web containers to communicate through HTTP or another Web protocol. To<br />
leverage the IIOP Plug-in (and, by extension, the ORB provided with the Web Edition),<br />
however, the Smart Agent must be turned on.<br />
More than one Smart Agent can be configured to run on your network. When a Smart<br />
Agent is started on more than one host, each Smart Agent will recognize a subset of<br />
the objects available and communicate with the other Smart Agents to locate objects it<br />
cannot find. In addition, if one of the Smart Agent processes should terminate<br />
unexpectedly, all implementations registered with that Smart Agent discover this event<br />
and they will automatically re-register with another Smart Agent. It should be noted that<br />
If a heavy services lookup load is necessary, it is advisable to use the Naming Service<br />
(VisiNaming). VisiNaming provides persistent storage capability and cluster load<br />
balancing whereas the Smart Agent only provides a simple round robin on a per<br />
osagent basis.<br />
For more information, go to the “Using the SmartAgent” sections.<br />
2PC Transaction Service<br />
The Two-Phase Commit (2PC) Transaction Service exists provides a complete<br />
recoverable solution for distributed transactional CORBA applications. Implemented on<br />
top of the VisiBroker ORB, the 2PC Transaction Service simplifies the complexity of<br />
distributed transactions by providing an essential set of services, including a<br />
transaction service, recovery and logging, integration with databases, and<br />
administration facilities within one, integrated architecture.<br />
The Partition and its services<br />
A Partition is an application's deployment target. The Partition provides the J2EE<br />
<strong>server</strong>-side runtime environment required to support a complete J2EE 1.3 application.<br />
While a Partition is implemented as a single native process, its core implementation is<br />
Java. When a Partition starts, it creates an embedded Java Virtual Machine (JVM)<br />
within itself to run the Partition implementation and the J2EE application code.<br />
Partitions are present in each BES Edition and product but they host less diverse<br />
archives in the Web Services, Team and VisiBroker Editions. This section describes<br />
the full-featured functional Partitions offered in the full <strong>Borland</strong> Enterprise Server. Each<br />
Partition instance provides:<br />
■<br />
“Connector Service” on page 10<br />
■<br />
“EJB Container” on page 10<br />
■<br />
“JDataStore Server” on page 10<br />
Chapter 2: <strong>Borland</strong> Enterprise Server overview and architecture 9
Change language