web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
VisiConnect Features VisiConnect Features Among the value-added features provided by VisiConnect as enhancements to the Connectors standard are the following: ■ ■ ■ ■ ■ VisiConnect Partition Service Additional Classloading Support Secure Password Credential Storage Connection Leak Detection Security Policy Processing of ra.xml Specifications VisiConnect Partition Service The Borland Partition with the VisiConnect service enabled is designed to support development and deployment of J2EE applications which bundle Resource Adapters, or standalone Resource Adapter components. The Borland Enterprise Server Partition provides integrated VisiConnect services. 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 Service in Partitions for deployment. Additional Classloading Support VisiConnect supports the loading of properties or classes that are specified in ClassPath entry of the Resource Adapter's Manifest.mf file. The following is a description of how you configure properties and classes that are in and used by a Resource Adapter. The Resource Adapter (RAR) archive file and the application component using it (for example, an EJB jar) are contained in an Enterprise Application (EAR) archive. The RAR requires resources such as Java properties that are stored in a JAR file, and that JAR file is contained within the EAR file (not in the RAR itself). You specify a reference to the RAR Java classes by adding a ClassPath= entry in the RAR Manifest.mf file. You can also store the EJB Java classes in the same JAR file that is contained within the EAR. This scenario provides a “support” JAR file that contains Java classes for the components in the EAR that require them. Secure Password Credential Storage VisiConnect provides a standard method for Resource Adapter deployers to plug in their specified authorization/authentication mechanism through secure password credential storage. This storage mechanism is used to map user roles (Borland Enterprise Server roles, which may be associated with Borland Enterprise Server username and password combinations or credentials) to resource roles (EIS roles, which may be associated with EIS user name and password combinations or credentials). Connection Leak Detection VisiConnect provides two mechanisms for preventing connection leaks: ■ ■ Leveraging a garbage collector Providing an idle timer for tracking the usage of connection objects Chapter 26: VisiConnect overview 255
Resource Adapters Resource Adapters Security Policy Processing of ra.xml Specifications VisiConnect provides a set of security permissions for execution of a Resource Adapter in a managed runtime environment. Borland Enterprise Server also grants a Resource Adapter explicit permissions to access system resources. Source code for several Resource Adapters are provided with VisiConnect as examples. These Resource Adapters are wrappers for JDBC 2.0 calls, some using the CCI and some not. Deployment descriptors supporting the three transaction levels are provided for each Resource Adapter. Simplified application examples for these JDBC Resource Adapters are provided with VisiConnect. An EJB is used to model the data in the EIS, and a J2EE client and a Servlet are used to query the Resource Adapter and display the output. The example uses any RDBMS which is supported by a JDBC 2.0 compliant driver. By default, the examples are configured to use JDataStore as the EIS, but it is a straightforward task to configure them to use any JDBC 2.0 RDBMS. The components are packaged as a J2EE Application. For more information, refer to the VisiConnect example README provided with the Borland Enterprise Server. 256 BES Developer’s Guide
- 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 and 256: Creating the JAR file Creating the
- Page 257 and 258: Components Components The Connector
- 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: Packaging and Deployment Figure 26.
- 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
- Page 307 and 308: Using the iastool command-line tool
- Page 309 and 310: Using the iastool command-line tool
- Page 311 and 312: Using the iastool command-line tool
- Page 313 and 314: Using the iastool command-line tool
- Page 315 and 316: Using the iastool command-line tool
VisiConnect Features<br />
VisiConnect Features<br />
Among the value-added features provided by VisiConnect as enhancements to the<br />
Connectors standard are the following:<br />
■<br />
■<br />
■<br />
■<br />
■<br />
VisiConnect Partition Service<br />
Additional Classloading Support<br />
Secure Password Credential Storage<br />
Connection Leak Detection<br />
Security Policy Processing of ra.xml Specifications<br />
VisiConnect Partition Service<br />
The <strong>Borland</strong> Partition with the VisiConnect service enabled is designed to support<br />
development and deployment of J2EE applications which bundle Resource Adapters,<br />
or standalone Resource Adapter components. The <strong>Borland</strong> Enterprise Server Partition<br />
provides integrated VisiConnect services. Tools include a Deployment Descriptor<br />
Editor (DDE) and a set of task wizards for packaging and deploying Resource Adapters<br />
and their related descriptor files.<br />
This provides a highly modular environment for running VisiConnect. The <strong>Borland</strong><br />
Enterprise Server provides a default VisiConnect Service in Partitions for deployment.<br />
Additional Classloading Support<br />
VisiConnect supports the loading of properties or classes that are specified in<br />
ClassPath entry of the Resource Adapter's Manifest.mf file. The following is a<br />
description of how you configure properties and classes that are in and used by a<br />
Resource Adapter.<br />
The Resource Adapter (RAR) archive file and the application component using it (for<br />
example, an EJB jar) are contained in an Enterprise Application (EAR) archive. The<br />
RAR requires resources such as Java properties that are stored in a JAR file, and that<br />
JAR file is contained within the EAR file (not in the RAR itself).<br />
You specify a reference to the RAR Java classes by adding a ClassPath= entry in the<br />
RAR Manifest.mf file. You can also store the EJB Java classes in the same JAR file<br />
that is contained within the EAR. This scenario provides a “support” JAR file that<br />
contains Java classes for the components in the EAR that require them.<br />
Secure Password Credential Storage<br />
VisiConnect provides a standard method for Resource Adapter deployers to plug in<br />
their specified authorization/authentication mechanism through secure password<br />
credential storage.<br />
This storage mechanism is used to map user roles (<strong>Borland</strong> Enterprise Server roles,<br />
which may be associated with <strong>Borland</strong> Enterprise Server username and password<br />
combinations or credentials) to resource roles (EIS roles, which may be associated<br />
with EIS user name and password combinations or credentials).<br />
Connection Leak Detection<br />
VisiConnect provides two mechanisms for preventing connection leaks:<br />
■<br />
■<br />
Leveraging a garbage collector<br />
Providing an idle timer for tracking the usage of connection objects<br />
Chapter 26: VisiConnect overview 255