Windows stand-alone: Verify the database configuration

After you configure IBM WebSphere Portal to work with the database, test the database connection to ensure that it operates correctly. Then verify that all database transactions work properly within the WebSphere Portal environment.

For example, all portal pages should display without HTTP 404 errors, and there should be no database layer-related exceptions in the SystemOut.log and SystemErr.log filesPortalServer joblog.

We can verify the database connection using IBM WAS or by opening WebSphere Portal in a browser.

• Verify the WebSphere_Portal application server is running:

  1. Open the WAS admin console:
     http://hostname.example.com:10042/ibm/console

     10042 is the default transport port.

  2. Log into the WAS admin console.

  3. Click Resources > JDBC > JDBC Providers.

  4. Select all scopes (the default setting) or select a specific cell, node, or node/server. Select the scope that corresponds to the instance of WebSphere Portal. The view refreshes.

     • Standalone WebSphere Portal: Select Server scope.

     • Clustered WebSphere Portal: Select Cluster scope.

  5. Select the name of the JDBC provided specified in wkplc_dbtype.properties. The default JDBC provider is wpdbJDBC_dbtype, where dbtype is replaced by the value that matches your environment.

  6. Select the name of the data source defined in wkplc_dbdomain.properties. The default data source is wpdbDS.

  7. Click Test Connection to verify the database connection. If configuration parameters have been changed, we might need to restart WAS for the test to complete.

• Verify portal is running:
  http://hostname.example.com:10039/wps/portal

  10039 is the default transport port.

Parent: Windows stand-alone: Configure the portal to use a database