3.3.2 Types of resource adapters

You can use the resource adapters conforming to the Connector 1.0 specifications or Connector 1.5 specifications with Application Server.

This subsection describes the resource adapters conforming to the respective specifications. This subsection also describes the differences in the DD schema of resource adapters.

Organization of this subsection
(1) Resource adapters conforming to the Connector 1.0 specifications
(2) Resource adapters conforming to the Connector 1.5 specifications
(3) Differences in the schema of the resource adapters conforming to the Connector 1.0 specifications and the Connector 1.5 specifications
(4) Types of RAR files for each resource adapter

(1) Resource adapters conforming to the Connector 1.0 specifications

You can use the following resource adapters with Application Server:

You can use the functionality supported by the Connector 1.0 specifications with these resource adapters.

Note that with DB Connector and DB Connector for Cosminexus RM, you can use the functionality added with Application Server in addition to the functionality supported by the Connector 1.0 specifications. For details on the available functionality, see 3.3.4 Resource adapter functionality.

Hint
With Application Server, apart from these resource adapters, you can use the resource adapters conforming to the Connector 1.0 specifications of the standard specifications. However, when you use the resource adapters conforming to the Connector 1.0 specifications of the standard specifications, the settings in the following tags in the DD (ra.xml) are ignored.
  • <security-permission>
    Use the server.policy file for the security settings.
  • <authentication-mechanism>
    Regardless of the settings, BasicPassword is applied.

(2) Resource adapters conforming to the Connector 1.5 specifications

You can use the resource adapters conforming to the Connector 1.5 specifications with Application Server. From the contracts in the Connector 1.5 specifications, the functionality corresponding to the following contracts can be used with Application Server:

Application Server provides the following resource adapters:

For details on the available functionality, see 3.3.4 Resource adapter functionality.

Also, for resource adapters conforming to the Connector 1.5 specifications, see 3.13.1 Resource adapters used for connection with other resources.

(3) Differences in the schema of the resource adapters conforming to the Connector 1.0 specifications and the Connector 1.5 specifications

This section describes the differences in the DD schema of the resource adapters conforming to the Connector 1.0 specifications and resource adapters conforming to the Connector 1.5 specifications. The DD for a resource adapter is ra.xml.

The following table describes the main changes from the schema defined in the Connector 1.0 specifications to the schema defined in the Connector 1.5 specifications. For the changes other than those described in this table, see the Connector 1.5 specifications.

Table 3-4 Main changes from the schema defined in the Connector 1.0 specifications to the schema defined in the Connector 1.5 specifications

Content changed in the Connector 1.5 specificationsDD content in the Connector 1.5 specifications
Specification of the implementation class of the javax.resource.spi.ResourceAdapter interface<connector>-<resourceadapter>-<resourceadapter-class> tag
<connector>-<resourceadapter>-<config-property> tag
Specification of the Outbound resource adapter<connector>-<resourceadapter>-<outbound-resourceadapter> tag
Specification of the Inbound resource adapter<connector>-<resourceadapter>-<inbound-resourceadapter> tag
Specification of adminobject<connector>-<resourceadapter>-<adminobject> tag

An overview of the content changed in the Connector 1.5 specifications is as follows:

Specification of the implementation class of the javax.resource.spi.ResourceAdapter interface
The implementation class of the javax.resource.spi.ResourceAdapter interface and the elements specifying their configuration properties were added. For details on the functionality that can be implemented with the addition of the javax.resource.spi.ResourceAdapter interface, see 3.16.1 Managing the resource adapter lifecycle and 3.16.2 Managing the resource adapter work.
Specification of the Outbound resource adapter
The elements used for explicitly defining the Outbound resource adapter were added.
Note that you can define multiple connections in one DD with the Outbound resource adapter. For details on specifying multiple connection definitions, see 3.16.6 Specifying multiple connection definitions.
Specification of the Inbound resource adapter
The elements used for explicitly defining the Inbound resource adapter were added.
Specification of adminobject
The elements specifying the information related to the Administered objects were added.

(4) Types of RAR files for each resource adapter

The resource adapters that define properties differ depending on the information such as the types of resources to be connected to and the transactions to be used. This section describes the resource adapters used in the following cases:

(a) To use DB Connectors

The files for DB Connectors differ depending on the database type to be connected to and the transaction type to be used. The following table describes the DB Connector types.

Table 3-5 DB Connector types

RAR file nameExplanation
DBConnector_HiRDB_Type4_CP.rarSelect this file when you use HiRDB Type4 JDBC Driver to connect to HiRDB or XDM/RD E2 without using a local transaction or transaction management.
DBConnector_HiRDB_Type4_XA.rarSelect this file when you use HiRDB Type4 JDBC Driver to connect to HiRDB using a global transaction.
DBConnector_Oracle_CP.rarSelect this file when you use Oracle JDBC Thin Driver to connect to Oracle without using a local transaction or transaction management.
DBConnector_Oracle_XA.rarSelect this file when you use Oracle JDBC Thin Driver to connect to Oracle using a global transaction.
DBConnector_SQLServer_CP.rarSelect this file when you use SQL Server JDBC Driver to connect to SQL Server (only in Windows) without using a local transaction or transaction management.
DBConnector_CP_ClusterPool_Root.rarThis is the root resource adapter of the connection pool clustering functionality. Select this file when a member resource adapter belonging to the root resource adapter connects to Oracle without using a local transaction or transaction management.
DBConnector_Oracle_CP_ClusterPool_Member.rarThis is the member resource adapter of the connection pool clustering functionality. Select this file when you use Oracle JDBC Thin Driver to connect to Oracle without using a local transaction or transaction management. Note that you cannot specify this file in the resource references of J2EE applications.

Note: When you prepare a new DB Connector RAR file, you can use the template files of the HITACHI Connector Property files provided with Application Server to define properties. The template files of the HITACHI Connector Property files are provided for all the DB Connector RAR files. For details on the provided template files, see 4.1.14 Template files of the HITACHI Connector Property files in the uCosminexus Application Server Application and Resource Definition Reference Guide.


(b) To use DB Connector for Cosminexus RM and Cosminexus RM

When you connect to a database by integrating the system with Cosminexus RM, you must import both, resource adapter for the Cosminexus RM integration (DB Connector for Cosminexus RM) and the resource adapter provided with Cosminexus RM. For details on the resource adapter provided with Cosminexus RM, see the manual uCosminexus Application Server Reliable Messaging.

The files for DB Connector for Cosminexus RM differ depending on the transaction type to be used and the database type to be connected to. The following table describes the types of DB Connector for Cosminexus RM.

Table 3-6 DB Connector for Cosminexus RM types

RAR file nameExplanation
DBConnector_HiRDB_Type4_CP_Cosminexus_RM.rarSelect this file when you use HiRDB Type4 JDBC Driver to connect to HiRDB without using a local transaction or transaction management.
DBConnector_HiRDB_Type4_XA_Cosminexus_RM.rarSelect this file when you use HiRDB Type4 JDBC Driver to connect to HiRDB using a global transaction.
DBConnector_Oracle_CP_Cosminexus_RM.rarSelect this file when you use Oracle JDBC Thin Driver to connect to Oracle without using a local transaction or transaction management.
DBConnector_Oracle_XA_Cosminexus_RM.rarSelect this file when you use Oracle JDBC Thin Driver to connect to Oracle using a global transaction.

Note: When you prepare a new RAR file for DB Connector for Cosminexus RM, you can use the template files of the HITACHI Connector Property files provided with Application Server to define properties. The template files of the HITACHI Connector Property files are provided for all the DB Connector RAR files. For details on the provided template files, see 4.1.14 Template files of the HITACHI Connector Property files in the uCosminexus Application Server Application and Resource Definition Reference Guide.


Hint
When you use DB Connector for Cosminexus RM and Cosminexus RM for accessing the JDBC and JMS in the same transaction, you can use a local transaction and conclude the single-phase commit operations for a global transaction by sharing the same physical connection. The conditions for concluding the single-phase commit operations are as follows:
  • The database system used for DB Connector for Cosminexus RM and Cosminexus RM is the same, and the sign-on method and the security information (user name and password) is identical.
  • The value Shareable is specified in the <res-sharing-scope> tag in the property files of the J2EE applications using the resource adapters (such as the Session Bean property file and Entity Bean property file).
(c) To use other resource adapters

To connect to OpenTP1 SPP and Outbound, you use the resource adapters uCosminexus TP1 Connector and TP1/Client/J. For details, see the uCosminexus TP1 Connector documentation and the OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/J.

To connect from OpenTP1 SUP using Inbound, you use the TP1 inbound adapter. For details, see 4. Invoking Application Server from OpenTP1 (TP1 Inbound Integrated Function).

Also, to connect to CJMSP Broker when you use Cosminexus JMS Provider, you use the CJMSP resource adapter. For details, see 7. Cosminexus JMS Provider.

Note that to use a new RAR file for the TP1 inbound adapter or the CJMSP resource adapter, you can use the template file provided with Application Server to define properties. For details, see 4.1.14 Template files of the HITACHI Connector Property files in the uCosminexus Application Server Application and Resource Definition Reference Guide.

To connect to TP1/Message Queue, use the resource adapter TP1/Message Queue - Access. For details, see the OpenTP1 Version 7 TP1/Message Queue - Access User Guide.

With Application Server, you can also connect to any resource by using the resource adapters conforming to the Connector 1.0 specifications or Connector 1.5 specifications. To use these resource adapters, see the documentation for resource adapters.