How are the J2EE Connector Architecture System Contracts partitioned in VisiConnect ?
The System Contracts are partitioned per Resource Adapter connection factory. As such: • One VisiConnect Connection Pool instance per connection factory. • One VisiConnect Transaction Manager instance per Connector Container. • One VisiConnect Transaction Context wrapper per connection factory. • One VisiConnect Security Manager instance per Connector Container. • One VisiConnect Security Context wrapper instance per connection factory. What this means in terms of deployment is that special parameters for Connection Pooling, Transaction Management and Security Management are passed to VisiConnect for each Resource Adapter, through its deployment descriptors. This is required by the J2EE Connector Architecture in order to support heterogeneous EIS types and implementations – for example, Transaction Processors (TP) such as IBM CICS , Message Queueing Systems (MQ) such as TIBCO ActiveEnterprise and Enterprise Resource Planners (ERP) such as SAP R/3 .
