3.18 Connection test for resources

After you set up the resource adapter properties, you can verify whether the set up content is correct. This is called the connection test functionality. The content verified by a connection test differs for each connected resource. The following table describes the content to be verified in the connection test for each resource.

For details on the procedure for executing the connection test and resource adapter settings, see 3.3.8 Procedure for resource adapter settings (To deploy and use the resource adapter as a J2EE resource adapter) and 3.3.9 Procedure for resource adapter settings (To include and use the resource adapter in a J2EE application).

Table 3-78 Content to be verified in the connection test

Resource typeConnection methodContent to be verified in the connection test
DatabaseDB Connector
  • The mode is the 1.4 mode
  • The specified transaction support level is available.#1, #2
  • The DB Connector settings are correct.
  • The settings for the JDBC driver to be used are correct.
  • A connection can be established with the database.
  • The SQL statement was issued successfully.
DB Connector (Root resource adapter when the connection pool clustering functionality is used)
  • The mode is the 1.4 mode.
  • The specified transaction support level is available.#1
  • The DB Connector settings are correct.
  • The settings required for starting the root resource adapter are specified.#3
DB Connector (Member resource adapter when the connection pool clustering functionality is used)
  • The mode is the 1.4 mode.
  • The specified transaction support level is available.#1
  • The DB Connector settings are correct.
  • The Oracle JDBC Thin Driver settings are correct.
  • A connection can be established with the database.
  • The SQL statement was issued successfully.
  • The prerequisite functionality for the member resource adapter is being used.#4
  • The functionality that is not available with the member resource adapters is not used.#4
Database queueCosminexus RM
  • The mode is the 1.4 mode.
  • The specified transaction support level is available.#1
  • The settings for Cosminexus RM are correct.
  • DB Connector for Cosminexus RM to be integrated is running.
  • The settings for DB Connector for Cosminexus RM to be integrated are correct.
  • A connection can be established with the database to be used.
DB Connector for Cosminexus RM
  • The settings for DB Connector for Cosminexus RM are correct.
  • DB Connector for Cosminexus RM is running.
  • The settings for Cosminexus RM to be integrated are correct.
  • Cosminexus RM to be integrated is running.
  • The settings for the JDBC driver to be used are correct.
  • A connection can be established with the database to be used.
  • The SQL statement was issued successfully.
OpenTP1TP1/Message Queue - Access
  • The mode is the 1.4 mode.
  • The specified transaction support level is available.#1
  • The settings for TP1/Message Queue - Access are correct.
  • TP1/Message Queue - Access can establish a connection to TP1/Message Queue.
uCosminexus TP1 Connector
  • The mode is the 1.4 mode.
  • The specified transaction support level is available.#1
  • The settings for uCosminexus TP1 Connector are correct.
TP1 inbound adapter
  • A connection test cannot be performed because of the communication with Inbound. If a connection test is attempted, the KDJE48606-E message is output.
CJMSP BrokerCJMSP resource adapter
  • The mode is the 1.4 mode.
  • A connection can be established with CJMSP Broker.
SMTP serverMail configuration
  • A connection can be established with the SMTP server.
OtherResource adapters from other companies
  • The mode is the 1.4 mode.
  • A connection can be established with the resource #5 (if the createManagedConnection method of the implementation class of javax.resource.spi.ManagedConnectionFactory is invoked successfully, the connection with the resource is assumed to have been established).
  • The resource adapters conforming to Connector 1.5 can be started and stopped when the resource adapter is not running (if the start method and stop method of the implementation class of javax.resource.spi.ResourceAdapter are invoked successfully, the resource adapter is assumed to have been started or stopped).

#1: Available if a global transaction (XATransaction) is specified as the transaction support level for a resource adapter and the ejbserver.distributedtx.XATransaction.enabled key in usrconf.properties is true. For details on the transaction support levels, see 3.4.3 Transaction types available for each resource.

#2: You cannot use a global transaction (XATransaction) when the database to be connected to is XDM/RD E2. The physical connection for transaction recovery cannot be obtained, so DB Connector cannot be started.

#3: For details on the settings required for starting the root resource adapter, see 4.3.3 DB Connector settings for the root resource adapter in the uCosminexus Application Server Application Setup Guide.

#4: For details on the prerequisite functionality and the functionality that is not available with member resource adapters, see 3.17.3 Resource adapters used.

#5: If the connection definition required for connecting to a resource does not exist when you perform Outbound communication, the message KDJE48606-E is output and the test fails.