Verify a data source connection
If the connection is still not successful after completing these steps and reviewing the applicable information, check the SystemOut.log for warning or exception messages.
On Z/OS check the SYSOUT for the servant for warning or exception messages.
IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure. We view HPEL log and trace information using the logViewer .
Tasks
- Create the authentication data alias. See the topic, Managing Java 2 Connector Architecture authentication data entries.
- Create the JDBC provider.
- Create a data source.
- Save the data source.
- Verify the connectivity if we created an authentication alias. To verify connectivity, restart the server for which verify connectivity.
If we are using scripting or Java Management Extensions (JMX) to create the authentication alias, we can use the updateAuthDataCfg MBean. Use this MBean method to refresh the authentication data in each server where it is needed. When we create a data source and the data source has not been used, we can use the updateAuthDataCfg MBean method. After a data source is used, its contents are instantiated in the server memory and generally cannot be changed.
- Test the connection.
We can test your connection from the data source collection view or the data source details view. Access either view in the administrative console, and then select a connection from the list. Click Test Connection on the connection.
Related:
Test connection service JDBC providers Data sources Resource reference benefits Data source lookups for enterprise beans and web modules Use High Performance Extensible Logging to troubleshoot applications Configure a JDBC provider Configure a data source Configure a JDBC provider for a clustered environment Create and configure a JDBC provider and data source using the JMX API Manage Java 2 Connector Architecture authentication data entries for JAAS Data source collection JDBC provider collection Support home