Testing a connection with the admin console

After we have defined and saved a data source, we can click the Test Connection button to verify the parameters in the data source definition are correct.

We can select multiple data sources on the data source collection page and test them as a group. Be sure that the following conditions are met before using the Test Connection button:

 

• If testing a connection using a WAS Version 4.0 type of data source, verify the user and password information is set.

• Designate variables appropriately.

  If we used a WebSphere environment entry for the class path or other fields, such as ${DB2_JDBC_DRIVER_PATH}/db2java.zip, make sure that you assign it a value in the WebSphere Variables page.

• Verify that the environment variables exist in the scope of the test. For example, if the node scoped data source you defined uses ${DB2_JDBC_DRIVER_PATH}, check that there exists a node level definition for DB2_JDBC_DRIVER_PATH = c:\sqllib\java( or the system dependent value).

• Restart the dmgr and node agents after you define or edit WebSphere variables.

• Restart the dmgr and node agents after you create or edit an authentication alias for the data source.

• Verify the deployment manager and node agent are up and running.

• We can now test a connection to the data source. On the data source collection page in the admin console, select the data source and click Test Connection . A Test Connection operation can have three different outcomes, each resulting in a different message being displayed in the messages panel of the page on which you press the Test Connection button.

  1. The test can complete successfully, meaning that a connection is successfully obtained to the database using the configured data source parameters. The resulting message states: Test Connection for data source DataSourceName on process ProcessName at node NodeName was successful.

  2. The test can complete successfully with warnings. This means that while a connection is successfully obtained to the database, warnings were issued.

     The resulting message states: Test Connection for data source DataSourceName on process ProcessName at node NodeName was successful with warning(s). View the JVM Logs for more details.

     The View the JVM Logs text is a hyperlink that takes you to the JVM Logs console screen for the process.

  3. The test can fail. A connection to the database with the configured parameters is not obtained. The resulting message states: Test Connection failed for data source DataSourceName on process ProcessName at node NodeName with the following exception: ExceptionText. View the JVM Logs for more details.

     Again, the text for View the JVM Logs is a hyperlink to the appropriate logs screen.

Test connection service

 

Related tasks

Testing a connection using wsadmin

 

Related

Example: Testing a connection using testConnection(ConfigID)