+

Search Tips   |   Advanced Search

Verify a data source connection

Many connection problems can be easily fixed by verifying configuration parameters. There are steps that you must complete to enable a successful 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. Then use the technical support search function to find known problems.

(zos) If the connection is still not successful after completing these steps and reviewing the applicable information, check the SYSOUT for the servant for warning or exception messages.

This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

  1. Create the authentication data alias. See the topic, Managing Java 2 Connector Architecture authentication data entries.

  2. Create the JDBC provider. See the topic, Configuring JDBC providers using the administrative console.

  3. Create a data source. See the topic, Configuring a data source using the administrative console

  4. Save the data source.

  5. Verify the connectivity if created an authentication alias. To verify connectivity, restart the server for which verify connectivity.

    If we are or JMX to create the authentication alias, we can use the updateAuthDataCfg MBean. We can use this MBean method to refresh the authentication data in each server where it is needed. When creating 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.

    For more information about the updateAuthDataCfg MBean method, see the SecurityAdmin MBean documentation under Reference > Programming interfaces > Mbean interfaces.

  6. 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. See the topic, Test the connection service.


Related concepts

  • Test connection service
  • JDBC providers
  • Data sources
  • Resource reference benefits
  • Data source lookups for enterprise beans and web modules


    Related tasks

  • Use High Performance Extensible Logging to troubleshoot applications
  • Configure a JDBC provider using the administrative console
  • Configure a data source using the administrative console
  • Configure a JDBC provider for a clustered environment
  • Create a JDBC provider and data source using the JMX API
  • Manage Java 2 Connector Architecture authentication data entries for JAAS

  • Data source collection
  • Data source (WebSphere Application Server V4) collection
  • JDBC provider collection


    Related information:

    Support home