Home

 

Testing a database connection

After installing Lotus Connections, test each feature's connection to the database to ensure that is working correctly.


The installation wizard automatically tests each connection. Use this procedure if you want to manually test the connection to a database.

You can use the SQL Server JDBC driver in both the app_server_root/lib directory and the driver downloaded from Microsoft, but the installation wizard checks the connection for the Microsoft JDBC driver only. If you are using the bundled driver, use this topic to manually test the connection.


To test a database connection...

  1. From the main page of the Integrated Solutions Console, select Resources > JDBC > Data sources.

  2. Select the check box beside the feature whose data source you want to test. The data sources are named as follows:

  3. Click Test connection.

  4. If the connection fails, make sure the JAAS Auth alias information is correct.

    1. Click a data source to review its settings.

    2. Click JAAS - J2C authentication data and then click the JAAS entry for the feature. The JAAS entries are named as follows:

      • Activities: activitiesJAASAuth

      • Blogs: blogsJAASAuth

      • Communities: communitiesJAASAuth

      • Dogear: dogearJAASAuth

      • Files: filesJAASAuth

      • Homepage: homepageJAASAuth

      • News: newsJAASAuth

      • Profiles: profilesJAASAuth

      • Search: searchJAASAuth

      • Wikis: wikisJAASAuth

    3. Make sure that the ID in the user ID field is the same User ID that you provided during installation when you were asked to specify a user ID for the database connector. The user ID should be one of the following:


      Default user ID for Lotus Connections databases

      Feature DB2 database DB2 User ID Oracle database Oracle User ID SQL Server database SQL Server User ID
      Activities OPNACT lcuser ORCL ACTIVITIES OPNACT OAUSER
      Blogs BLOGS lcuser ORCL BLOGS BLOGS BLOGSUSER
      Communities SNCOMM lcuser ORCL SNCOMMUSER SNCOMM SNCOMMUSER
      Dogear DOGEAR lcuser ORCL DOGEARUSER DOGEAR DOGEARUSER
      Files FILES lcuser ORCL FILESUSER FILES FILESUSER
      Homepage HOMEPAGE lcuser ORCL HOMEPAGE HOMEPAGE HOMEPAGEUSER
      News HOMEPAGE lcuser ORCL HOMEPAGE HOMEPAGE HOMEPAGEUSER
      Profiles PEOPLEDB lcuser ORCL PROFUSER PEOPLEDB PROFUSER
      Search HOMEPAGE lcuser ORCL HOMEPAGE HOMEPAGE HOMEPAGEUSER
      Wikis WIKIS lcuser ORCL WIKISUSER WIKIS WIKISUSER

      Consider reentering the password to make sure that the value that you specified is correct.

    4. After applying any changes, click OK. Return to the data source properties page, and then click Test connection.

  5. If the connection fails again, make sure the JDBC driver library location information is getting picked up by WebSphere Application Server.

    1. From the Integrated Solution Console navigation bar, expand Environment, and then click WebSphere Variables.

    2. Scroll down the list to find the database location variable. The variables are named as follows:

      • Activities: ACTIVITIES_JDBC_DRIVER_HOME

      • Blogs: BLOGS_JDBC_DRIVER_HOME

      • Communities: COMMUNITIES_JDBC_DRIVER_HOME

      • Dogear: DOGEAR_JDBC_DRIVER_HOME

      • Files: FILES_JDBC_DRIVER_HOME

      • Homepage: HOMEPAGE_JDBC_DRIVER_HOME

      • News: NEWS_JDBC_DRIVER_HOME

      • Profiles: PROFILES_JDBC_DRIVER_HOME

      • Search: SEARCH_JDBC_DRIVER_HOME

      • Search: WIKIS_JDBC_DRIVER_HOME

    3. Make sure that the corresponding file path in the Value column is the same file path that you specified in the JDBC driver library field when you ran the installation wizard. For example:

        C:\IBM\DB2\SQLLIB\java
        

      If the file path is incorrect, click the variable name and edit the file path in the Value field.

    4. Select JDBC > Data sources to return to the data source. Select the check box next to the data source, and then click Test connection.


Post-installation tasks


+

Search Tips   |   Advanced Search