uCosminexus Application Server, Common Container Functionality Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
(1) Types of connectable databases
The databases that can be connected by using DB Connector for Cosminexus RM and Cosminexus RM include HiRDB and Oracle. Note that you cannot connect to SQL Server and XDM/RD E2.
(2) Mapping the databases and JDBC drivers
To use DB Connector for Cosminexus RM and Cosminexus RM to connect to a database, you require a JDBC driver compatible with the database.
The following table describes the database to be connected to and the available JDBC drivers.
Table 3-35 Database to be connected to and the available JDBC drivers (for connecting to a database queue)
| Database |
JDBC driver |
| HiRDB Type4 JDBC Driver |
Oracle JDBC Thin Driver |
| HiRDB Version 8 |
Y |
N |
| HiRDB Version 9 |
Y |
N |
| Oracle |
N |
Y |
- Legend:
- Y: Available
- N: Not available
Note the following when you use DB Connector for Cosminexus RM and Cosminexus RM to connect to a database:
- A JDBC-specific transaction control cannot be executed with the JDBC connection (java.sql.Connection. Connection) provided by DB Connector for Cosminexus RM. If a JDBC-specific transaction control is executed, an exception occurs when the setAutoCommit(boolean)method is invoked with the argument false, and when the releaseSavepoint(SavePoint)method, rollback(Savepoint) method, setSavepoint() method, and setSavepoint(String) method are invoked. Use DB Connector when you want to execute a JDBC-specific transaction control.
- The collection points and event ID of the trace based performance analysis for DB Connector for Cosminexus RM partially differs from that for DB Connector.
For a JDBC connection (java.sql.Connection. Connection), the trace based performance analysis is output at the two trace collection points of JDBC connection of DB Connector for Cosminexus RM with one-time access, and the JDBC connection in DB Connector.
Also, the trace based performance analysis is output at the same trace collection points as DB Connector for the JDBC connection products (such as java.sql.Statement). The trace based performance analysis is only output at the trace collection points for DB Connector for Cosminexus RM for java.sql.DataSource.
- When the operation information is monitored with DB Connector for Cosminexus RM, incorrect values are output for the following items of DB Connector for Cosminexus RM resource adapter. DB Connector for Cosminexus RM obtains a connection via Cosminexus RM; therefore, the monitored information of the integrated resource adapter is accumulated and output to Cosminexus RM.
- Transaction support level
- Current value of the pool (total)
- Number of connections in use
- Number of unused connections
- Execution count of the createManagedConnection() method of ManagedConnectionFactory
- Execution count of the getConnection() method of ManagedConnection
- Execution count of the cleanup() method of ManagedConnection
- Execution count of the destroy() method of ManagedConnection
- Execution time of the allocateConnection() method of ConnectionManager
- Execution time of the createManagedConnection() method of ManagedConnectionFactory
- Failure count of the allocateConnection() method of ConnectionManager
- Number of times the FATAL error occurred in ManagedConnection
- DB Connector for Cosminexus RM shares the connection pool of the integrated Cosminexus RM. Therefore, you need not specify the settings for each functionality of the connection pool in DB Connector for Cosminexus RM.
- To use a resource adapter, you must resolve the references from the J2EE application to the resource adapter. When you customize a J2EE application that uses the resource adapters, resolve the references from the J2EE application to the resource adapter.
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.