3.3.2 Resource types and resource adapters
You can connect with the following resources in the Application Server system:
-
Database (HiRDB, Oracle, SQL Server or XDM/RD E2)
-
TP1/Message Queue of OpenTP1
-
SPP of OpenTP1
-
SUP of OpenTP1
-
CJMSP Broker of Cosminexus JMS provider
-
Mail configuration
-
JavaBeans resources
SUP of OpenTP1 is connected as Inbound. Note that the resource adapter is not required when you use a mail configuration or JavaBean Resources.
The resource adapters used for various types of resources connected by the application are explained as follows:
- Tip
-
In Application Server, you can use resource adapters conforming to Connector 1.0 or Connector 1.5 specifications.
For details about using resource adapters other than those described here, check the description for the resource adapter being used.
- Organization of this subsection
-
-
(1) Resource adapter for connecting to the database (when the JDBC interface is used)
-
(2) Resource adapter for connecting to the database (when the JMS interface is used)
-
(3) Resource adapter for connecting to TP1/Message Queue of OpenTP1
-
(6) Resource adapter for connecting to CJMSP Broker of Cosminexus JMS provider
-
(1) Resource adapter for connecting to the database (when the JDBC interface is used)
Use DB Connector as the resource adapter when connecting to the database using the JDBC interface. When you use the DB Connector, you can use the JDBC interface for accessing the database from servlets, JSPs, Session Beans, Entity Beans, or Message-driven Beans.
Application Server can access HiRDB, Oracle, SQL Server, or XDM/RD E2 databases using resource adapters. The following figures show the respective configurations when you access each type of database with a resource adapter:
-
Configuration for accessing HiRDB
When connecting to HiRDB, the HiRDB Type4 JDBC Driver is required on the same machine where a J2EE server is installed.
The following figure shows the configuration for accessing HiRDB:
Figure 3‒18: Configuration for accessing HiRDB with a resource adapter (for using the HiRDB Type4 JDBC Driver) Note: For other legend items, see 3.2 Description of the system configuration.
-
Configuration when accessing Oracle
When connecting to Oracle, Oracle JDBC Thin Driver is required on the same machine where the J2EE server is installed.
The following figure shows the configuration for accessing Oracle:
Figure 3‒19: Configuration for accessing Oracle with a resource adapter (for using the Oracle JDBC Thin Driver) Note: For other legend items, see 3.2 Description of the system configuration.
-
Configuration for accessing the SQL Server
When connecting to SQL Server, the JDBC driver for SQL Server is required on the same machine as the J2EE server.
The following figure shows the configuration when accessing the SQL Server:
Figure 3‒20: Configuration for accessing the SQL Server with a resource adapter Note: For other legend items, see 3.2 Description of the system configuration.
-
Configuration for accessing XDM/RD E2
When connecting to XDM/RD E2, the HiRDB Type4 JDBC Driver is required on the same machine where the J2EE server is installed.
The following figure shows the configuration required when accessing XDM/RD E2:
Figure 3‒21: Configuration when accessing XDM/RD E2 with a resource adapter (for using the HiRDB Type4 JDBC Driver) Note: For other legend items, see 3.2 Description of the system configuration.
(2) Resource adapter for connecting to the database (when the JMS interface is used)
If you are using the JMS interface for connecting to the database, use DB Connector for Cosminexus RM as the resource adapter. DB Connector for Cosminexus RM is a resource adapter for integrating with Cosminexus RM. If you use Cosminexus RM, you can access the queues implemented on the database from a servlet, JSP, Session Bean, Entity Bean, or Message-driven Bean, by using the JMS interface. In such a case, the Cosminexus RM libraries run on the J2EE server and the queue data is saved in the database. Cosminexus RM is component software of Application Server.
The following figures separately show the configuration for accessing the HiRDB and Oracle databases with Cosminexus RM:
|
Note: For other legend items, see 3.2 Description of the system configuration.
|
Note: For other legend items, see 3.2 Description of the system configuration.
(3) Resource adapter for connecting to TP1/Message Queue of OpenTP1
When connecting to TP1/Message Queue, which is the message queuing function of OpenTP1, use TP1/Message Queue - Access as the resource adapter. If you use TP1/Message Queue - Access, TP1/Message Queue can be accessed using a JMS interface from a servlet, JSP, Session Bean, Entity Bean, or Message-driven Bean. In such cases, TP1/Message Queue - Access is required on the same machine as the J2EE server.
The following figure shows the configuration for accessing TP1/Message Queue using resource adapter:
|
Note: For other legend items, see 3.2 Description of the system configuration.
(4) Resource adapter for connecting to SPP of OpenTP1
When connecting to SPP (Service Providing Program) of OpenTP1, use uCosminexus TP1 Connector and TP1/Client/J as resource adapters. If you are using uCosminexus TP1 Connector and TP1/Client/J, access to SPP of OpenTP1 is possible from a servlet, JSP, Session Bean, Entity Bean, or Message-driven Bean. In such cases, uCosminexus TP1 Connector and TP1/Client/J must be on the same machine as the J2EE server.
The following figure shows the configuration for accessing SPP of OpenTP1 using resource adapter:
|
Note: For other legend items, see 3.2 Description of the system configuration.
(5) Resource adapter for connecting to SUP of OpenTP1
When connecting to SUP (Service Using Program) of Open TP1 by the TP1 inbound integrated function, use TP1 inbound adapter as the resource adapter. If you use the TP1 inbound integrated function, you can access a Message-driven Bean running on a J2EE server as inbound from SUP of OpenTP1. In such cases, a TP1 inbound adapter must be on the same machine as the J2EE server.
The following figure shows the configuration when accessing as inbound from SUP of OpenTP1 using resource adapter:
|
Note: For other legend items, see 3.2 Description of the system configuration.
(6) Resource adapter for connecting to CJMSP Broker of Cosminexus JMS provider
When connecting to CJMSP Broker of Cosminexus JMS provider, use CJMSP resource adapter as the resource adapter. If you use the CJMSP resource adapter, you can access CJMSP Broker using the JMS interface from servlets, JSPs, Session Beans, Entity Beans, or Message-driven Beans. In such cases, a CJMSP resource adapter must be on the same machine as the J2EE server.
The following figure shows the configuration for accessing CJMSP Broker using resource adapter:
|
Note: For other legend items, see 3.2 Description of the system configuration.