Many connection problems can be easily fixed by verifying
configuration parameters. There are steps that you must complete to
enable a successful connection.
About this task
If your 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.
Procedure
- Create the authentication data alias. See the
topic, Managing Java 2 Connector Architecture authentication
data entries.
- Create the JDBC provider. See the topic, Configuring
JDBC providers using the administrative console.
- Create a data source. See the topic, Configuring
a data source using the administrative console
- Save the data source.
- Verify the connectivity if you created an authentication
alias. To verify connectivity, restart the server for which
you must verify connectivity.
If you are using scripting or Java
Management Extensions (JMX) to create the authentication alias, you
can use the updateAuthDataCfg MBean. You can use this MBean method
to refresh the authentication data in each server where it is needed.
When you create a data source and the data source has not been used,
you 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.
- Test the connection.
You 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.