Test a connection with the administrative console

 

+

Search Tips   |   Advanced Search

 

Overview

After you have defined and saved a data source, one can click the Test Connection button to ensure that the parameters in the data source definition are correct. On the collection panel, one can select multiple data sources and test them all at once. Be sure that the following conditions are met before using the Test Connection button.

 

Procedure

  1. Depending on your specific needs, a valid Authentication Data alias might need to exist and be supplied on the data source panels.

  2. If you are testing a connection using a WAS V4.0 type of data source, ensure that the user and password information is filled in.

  3. If you 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. Note that if you add a new WebSphere environment variable, or modify it , the process (node agents and deployment manager) might need restarting.

  4. Verify that the environment variables used 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 your system dependent value).

  5. Ensure that the deployment manager and node agent are up and running.

  6. 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.

 

See Also


Test connection service

 

Related Tasks


Test a connection using wsadmin

 

See Also


Example: Test a connection using testConnection(ConfigID)