user manual

288 BES Developer’s Guide
VisiConnect Container
Container Overview
The VisiConnect Container is a complete implementation of the Connectors
1.0 specification, including all optional functionality.
Every Resource Adapter object in the deployed Connector is simultaneously
both a Resource Adapter object and a CORBA object.
The VisiConnect Container can be deployed as a standalone, 100% pure Java
service or as a fully-distributed deployment. This flexibility enables adjustment
of the application's scalability and availability based on user requirements.
Unlike other Connectors implementations, the VisiConnect Container server
has no restrictions on partitioning. Any number of Resource Adapters can go
into any number of containers running on any number of machines. Plus,
support for distributed transactions protocol allows Resource Adapters to be
partitioned arbitrarily. Partitioning enables you to configure the application
during deployment to optimize its overall performance.
Container built on top of VisiBroker and RMI-IIOP
The VisiConnect Container is built on top of Borland VisiBroker.
Communication between clients and Resource Adapters, among Resource
Adapters, and between Resource Adapters and other CORBA-based
applications is all done using IIOP by way of VisiBroker. VisiBroker is fully
compliant with the CORBA 2.3 specification which specifies that RMI-over-
IIOP must be implemented in terms of objects-by-value. RMI-over-IIOP must
be implemented in terms of objects-by-value for true interoperability. As such,
VisiConnect is interoperable with any other server supporting RMI-over-IIOP.
Security credentials are propagated by VisiBroker. This ensures that a client's
credentials are propagated from the client to the server.
Transactional context is propagated by VisiBroker. This ensures that when a
CORBA client begins a transaction and then accesses the VisiConnect
Container's server, transactional context is propagated in the call to the server
and the server uses this transaction context when making calls to various
resources in its environment.
Two-phased commit transactions are managed by Borland VisiTransact
Transaction Manager. Two-phase commit is supported if the Resource
Adapter supports it. If the Resource Adapter in use does not support it, then
two-phase commit cannot be done.
Container is a CORBA Server
Borland's java2iiop compiler, as well as the VisiConnect Container runtime, is
CORBA compliant. The VisiConnect Container understands RMI method calls
used for Resource Adapters but it uses IDL definitions internally to store the
interface definitions. Although the java2iiop compiler takes the Java interfaces
and generates stubs and skeletons from them, you can also generate IDL