web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Chapter 26 26VisiConnect overview Chapter Important For documentation updates, go to www.borland.com/techpubs/bes. J2EE Connector Architecture In the information technology environment, enterprise applications generally access functions and data associated with Enterprise Information Systems (EIS). This traditionally has been performed using non-standard, vendor-specific architectures. When multiple vendors are involved, the number of architectures involved exponentiate the complexity of the enterprise application environment. With the introduction of the Java 2 Enterprise Edition (J2EE) 1.3 Platform and the J2EE Connector Architecture (Connectors) 1.0 standards, this task has been greatly simplified. VisiConnect, the Borland implementation of the Connectors 1.0 standard, provides a simplified environment for integrating various EISs with the Borland Enterprise Server. The Connectors provides 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. With the Connectors, EIS vendors need not customize integration to their platforms for each application server. Through VisiConnect's strict conformance to the Connectors, the Borland Enterprise Server itself requires no customization in order to support integration with a new EIS. Connectors enables EIS vendors to provide standard Resource Adapters for their EISs. These Resource Adapters are deployed to the Borland Enterprise Server, each providing the integration implementation between the EIS and the Borland Enterprise Server. With VisiConnect, the Borland Enterprise Server ensures access to heterogeneous EISs. In turn, the EIS vendors need provide only one standard Connectors-compliant resource adapter. By default, this resource adapter has the capability to deploy to the Borland Enterprise Server. Chapter 26: VisiConnect overview 245
Components Components The Connectors environment consists of two major components - the implementation of the Connectors in the application server, and the EIS-specific Resource Adapter. In the J2EE 1.3 Architecture, the Connectors is an extension of the J2EE Container, otherwise known as the application server. In compliance with the J2EE 1.3 Platform and Connectors 1.0 specifications, VisiConnect is an extension of the Borland Enterprise Server, and not a service in and of itself. The following diagram illustrates VisiConnect within the Borland Enterprise Server Architecture: Figure 26.1 VisiConnect within the Borland Enterprise Server (VisiConnect is represented above by the module titled “Connectors.”) A Resource Adapter is a system-level driver specific to an EIS, which provides access to that EIS. To put it simply, a Resource Adapter is analogous to a JDBC driver. The interface between a Resource Adapter and the EIS is specific to the EIS. It can be either a Java interface or a native interface. The Connectors consists of three main components: ■ System Contracts that provide the integration between the Resource Adapter and the application server (Borland Enterprise Server). ■ Common Client Interface that provides a standard client API for Java applications, frameworks, and development tools to interact with the Resource Adapter. ■ Packaging and Deployment that provides the capacity for various Resource Adapters to plug into J2EE applications in a modular manner. The following diagram illustrates the Connectors architecture: 246 BES Developer’s Guide
- Page 205 and 206: Disabling and Enabling a Deployed D
- Page 207 and 208: Configuring JDBC Datasources In the
- Page 209 and 210: Configuring JDBC Datasources To add
- Page 211 and 212: Defining the Connection Pool Proper
- Page 213 and 214: Defining the Connection Pool Proper
- Page 215 and 216: Descriptions of Borland Enterprise
- Page 217 and 218: Advanced Topics for Defining JDBC D
- Page 219 and 220: Connecting to JDBC Resources from J
- Page 221 and 222: Configuring JMS Connection Factorie
- Page 223 and 224: Defining Connection Pool Properties
- Page 225 and 226: Obtaining JMS Connection Factories
- Page 227 and 228: JMS and Transactions and its accomp
- Page 229 and 230: JMS and Transactions For instance:
- Page 231 and 232: 220 BES Developer’s Guide
- Page 233 and 234: Configuring JMS administered object
- Page 235 and 236: Tibco Creating Clustered JMS Servic
- Page 237 and 238: Sonic serverUrl String localhost:72
- Page 239 and 240: Sonic Creating Clustered JMS Servic
- Page 241 and 242: OpenJMS Even though OpenJMS can be
- Page 243 and 244: OpenJMS Important If you use OpenJM
- Page 245 and 246: OpenJMS openjms.clean_messages_on_s
- Page 247 and 248: OpenJMS Table 24.1 Property Name De
- Page 249 and 250: Other JMS providers The following a
- Page 251 and 252: 240 BES Developer’s Guide
- Page 253 and 254: Creating the Interceptor Class For
- Page 255: Creating the JAR file Creating the
- Page 259 and 260: System Contracts Connection Managem
- Page 261 and 262: System Contracts Security Managemen
- Page 263 and 264: Common Client Interface (CCI) Conne
- Page 265 and 266: Packaging and Deployment Figure 26.
- Page 267 and 268: Resource Adapters Resource Adapters
- Page 269 and 270: Connection management Connection ma
- Page 271 and 272: Security management with the Securi
- Page 273 and 274: Security management with the Securi
- Page 275 and 276: Resource Adapter overview Note Reso
- Page 277 and 278: Deployment Descriptors for the Reso
- Page 279 and 280: Developing the Resource Adapter Con
- Page 281 and 282: Deploying the Resource Adapter Pack
- Page 283 and 284: Application development overview 8
- Page 285 and 286: Application development overview //
- Page 287 and 288: Application development overview
- Page 289 and 290: Other Considerations Other Consider
- Page 291 and 292: Other Considerations To illustrate,
- Page 293 and 294: Other Considerations } } { cf = new
- Page 295 and 296: General syntax and usage General sy
- Page 297 and 298: Syntax and usage for iastool Table
- Page 299 and 300: Syntax and usage for java2iiop Exam
- Page 301 and 302: Syntax and usage for appclient Tabl
- Page 303 and 304: Building and running the BES exampl
- Page 305 and 306: Using the iastool command-line tool
Components<br />
Components<br />
The Connectors environment consists of two major components - the implementation<br />
of the Connectors in the application <strong>server</strong>, and the EIS-specific Resource Adapter.<br />
In the J2EE 1.3 Architecture, the Connectors is an extension of the J2EE Container,<br />
otherwise known as the application <strong>server</strong>. In compliance with the J2EE 1.3 Platform<br />
and Connectors 1.0 specifications, VisiConnect is an extension of the <strong>Borland</strong><br />
Enterprise Server, and not a service in and of itself. The following diagram illustrates<br />
VisiConnect within the <strong>Borland</strong> Enterprise Server Architecture:<br />
Figure 26.1<br />
VisiConnect within the <strong>Borland</strong> Enterprise Server<br />
(VisiConnect is represented above by the module titled “Connectors.”)<br />
A Resource Adapter is a system-level driver specific to an EIS, which provides access<br />
to that EIS. To put it simply, a Resource Adapter is analogous to a JDBC driver. The<br />
interface between a Resource Adapter and the EIS is specific to the EIS. It can be<br />
either a Java interface or a native interface.<br />
The Connectors consists of three main components:<br />
■<br />
System Contracts that provide the integration between the Resource Adapter and<br />
the application <strong>server</strong> (<strong>Borland</strong> Enterprise Server).<br />
■<br />
Common Client Interface that provides a standard client API for Java applications,<br />
frameworks, and development tools to interact with the Resource Adapter.<br />
■<br />
Packaging and Deployment that provides the capacity for various Resource<br />
Adapters to plug into J2EE applications in a modular manner.<br />
The following diagram illustrates the Connectors architecture:<br />
246 BES Developer’s Guide
Change language