web server - Borland Technical Publications

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