user manual

Chapter 26: VisiConnect overview 283
VisiConnect Features
VisiConnect Features
Among the value-added features provided by VisiConnect as enhancements
to the Connectors standard are the following:
■
VisiConnect Container
■
Local and Remote Connectors Support
■
Additional Classloading Support
■
Secure Password Credential Storage
■
Connection Leak Detection
■
Security Policy Processing of ra.xml Specifications
VisiConnect Container
The VisiConnect Container is designed to support development and
deployment of J2EE applications which bundle Resource Adapters, or
standalone Resource Adapter components. The Borland Enterprise Server
provides integrated VisiConnect Container services. These services enable
the creation and management of integrated VisiConnect Containers or
VisiConnect Containers across multiple partitions. The Container is used to
deploy, run, manage and monitor Resource Adapters. Tools include a
Deployment Descriptor Editor (DDE) and a set of task wizards for packaging
and deploying Resource Adapters and their related descriptor files.
This provides a highly modular environment for running VisiConnect. The
Borland Enterprise Server provides a default VisiConnect Container for
deployment. Additional Containers can be created as needed.. The
VisiConnect Container can be run as a standalone process. For details,
please refer to "Using VisiConnect".
Local and Remote Connectors Support
VisiConnect supports both the Local and Remote types of Connectors.
Local Connectors implement any interface, except java.rmi.Remote, in their
connection factory. These are deployed to the serial jndi context handler of
Borland Enterprise Server and are accessible from VisiConnect running within
a Borland Enterprise Server or standalone, via VisiNaming, Borland's modular
naming service. The deployment of Local Connectors is optimized for access
by components running locally to VisiConnect.
Remote Connectors implement java.rmi.Remote in their connection factory,
along with any other required interfaces. They are deployed to the CosNaming
jndi context handler of Borland Enterprise Server, and are accessible from
VisiConnect running within a Borland Enterprise Server or standalone, via
VisiNaming. The deployment of Remote Connectors is optimized for access
by component running remotely to VisiConnect.