42 lines
3.3 KiB
HTML
42 lines
3.3 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Testing a connection with the administrative console </title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h6><a name="datatestadmin"></a>Testing a connection with the administrative console</h6>
|
||
|
|
|
||
|
|
<p>After you have defined and saved a data source, you can use the Test Connection functionality to make sure that the parameters in the data source definition are correct. On the Collection panel, you can select multiple data sources and test them all at once. Make sure that the following conditions are met before using Test Connection:</p>
|
||
|
|
|
||
|
|
<p>To test a connection with the administrative console, perform the following steps:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><p>Make sure that a valid Authorization Data alias exists and is used on the data source panels.</p></li>
|
||
|
|
<li><p>If you are testing a connection using a WebSphere Application Server Version 4.0 data source, make sure that the user and password information is filled in.</p></li>
|
||
|
|
<li><p>If you are using a WebSphere Environment entry for the classpath or other fields, such as ${DB2_JDBC_DRIVER_PATH}/db2java.zip, make sure that you assign it a value in the Manage WebSphere Variables page. The values of ${OS400_NATIVE_JDBC_DRIVER_PATH} and ${OS400_TOOLBOX_JDBC_DRIVER_PATH} are set automatically on an iSeries server.</p>
|
||
|
|
<p><strong>Note:</strong> If you add or modify a new WebSphere Environment Variable, the process (nodeagents and Deployment manager) must be restarted.</p>
|
||
|
|
</li>
|
||
|
|
<li><p>Verify that the environment variables used exist in the scope of the test.</p>
|
||
|
|
<p>For example, if the node scoped data source you defined uses ${DB2_JDBC_DRIVER_PATH}, check that a node level definition exists for DB2_JDBC_DRIVER_PATH = c:\sqllib\java (or your system dependent value).</p>
|
||
|
|
</li>
|
||
|
|
<li><p>Make sure that the Deployment manager and nodeagent are up and running.</p></li>
|
||
|
|
<li><p>Click <strong>Test Connection</strong>.</p>
|
||
|
|
<p>A Test Connection operation can have three different outcomes, each resulting in a different message displayed in the messages panel of the page on which you click Test Connection.</p>
|
||
|
|
<ul>
|
||
|
|
<li><p>The test can successfully complete, meaning that a connection is successfully obtained to the database using the configured data source parameters. The resulting message states: Test Connection for DataSource DataSourceName on process ProcessName at node NodeName was successful.</p></li>
|
||
|
|
<li><p>The test can successfully complete with warnings. This means that while a successful connection is obtained to the database, warnings are issued. The resulting message states: Test Connection for DataSource DataSourceName on process ProcessName at node NodeName was successful with warning(s).View the JVM Logs for more details.</p></li>
|
||
|
|
<li><p>The test can fail. A connection to the database with the configured parameters is not obtained. The resulting message states: Test Connection failed for DataSource DataSourceName on process ProcessName at node NodeName with the following exception: ExceptionText. View the JVM Logs for more details.</p></li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|