The JDBC data source Test connection fails with Information Server 11.3 installed with a WebSphere cluster.

Resolving The Problem

For Information Server 11.3.1.2, this issue is resolved by restarting the WebSphere Deployment Manager
For all releases of 11.3 prior to 11.3.1.2, perform the following:

1. Open the WebSphere Administrative Console
2. Go to Resources => JDBC => JDBC Providers and click ASB JDBC Provider
3. Under Additional Properties click data sources
4. Click ASB JDBC DataSource
5. Under Related items click JAAS - J2C authentication data
6. Click New
7. In the Alias field enter "ASB DB user". Use spaces in between, not underscores.
8. Put in the user name and password for the xmeta database. Click Apply and save in the messages box at the top
9. Click New
10. For the next Alias name enter "imamJ2eeAuthAlias"
11. Enter the user name and password for the xmetasr database. Click Apply and Save
12. Sync the nodes
13. Go back to the ASB JDBC DataSource and scroll down to the Security Settings and click the drop down for Component-managed authentication alias. You will now see nodename/ASB DB user. Select that user for both the Component-managed authentication alias and Container-managed authentication alias. Be sure to pick the newly created alias with the node name
14. Complete step 12 for the JReport JDBC DataSource using the newly created nodename/ASB DB user alias
15. Go back to JDBC providers and click ASB XA JDBC Provider
16. Under Additional properties click data sources
17. Click the ASB JDBC Staging XA DataSource
18. Change the Component-managed authentication alias and Container-managed authentication alias to both use nodename/imamJ2eeAuthAlias
19. Click Apply and Save
20. Next click on the ASB JDBC XA DataSource
21. Change Authentication alias for XA recovery, Component-managed authentication alias and Container-managed authentication alias to the nodename/ASB DB user alias
22. Restart the nodes, cluster and Deployment Manager