Verify databases
After you configure WebSphere Portal to work with your 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 files.
Prerequisites
- Prepare the Windows operating system
- Installing WebSphere Portal on Windows
- Installing DB2 on the same server as WebSphere Portal
- Configure JCR collation support
- Modifying database properties
- Set up databases
- Configure WebSphere Portal to use DB2
- Technotes for database connectivity issues
You can verify the database connection using IBM WAS or by opening WebSphere Portal in a browser.
Verify WebSphere Portal is running using WAS
- Open the administrative console by entering the following address in a browser:
http://hostname.example.com:10027/ibm/console
where hostname.example.com is the fully qualified host name of the machine where WebSphere Portal is running and 10027 is the default transport port that is created by WAS.
- Log into the administrative console.
- Depending on your version of WAS, click the appropriate option:
- For WAS V6.1: Click Resources & JDBC Providers.
- For WAS V7.0: Click Resources > JDBC > JDBC Providers
- Select all scopes (the default setting) or select a specific cell, node, or node/server.
Select the scope that corresponds to your instance of WebSphere Portal. The view refreshes.
- Select the name of the data source that is defined in wkplc_comp.properties. The default data source is wpdbDS.
- Select the name of the JDBC provider specified in wkplc_dbtype.properties.
The default JDBC provider is wpdbJDBC_dbtype, where dbtype is replaced by the value that matches your environment.
- Click Test Connection to verify the database connection.
If configuration parameters have been changed, you might need to restart WAS for the test to complete.
Verify WebSphere Portal is running by opening WebSphere Portal
http://hostname.example.com:10040/wps/portal
where hostname.example.com is the fully qualified host name of the machine where WebSphere Portal is running and 10040 is the default transport port that is created by WAS.
Parent topic:
Set up a single server
Previous topic:
Configure DB2 for large file handling in Web Content Management