Verify database connections

After WebSphere Portal is configured to work with your database, test the database connection to ensure that it operates correctly.

Do not run the test connection in the admin console.


Prerequisites

Prepare for creation of databases

Create user profiles

Creating remote databases

Modifying database properties

Transferring DB2 for i5/OS manually

You can verify the connection from a browser or from a command line.

To verify that WebSphere Portal is running from a browser, open the portal in a Web browser: http://hostname.yourco.com:port_number/wps/portal, where hostname.yourco.com is the fully qualified host name of the machine where WebSphere Portal is running and port_number is the transport port that is created by IBM WAS. There may be an error if any of the following conditions appear.

Verify the connection from a command line by completing the following steps:

  1. Start a 5250 session on the local machine where WebSphere Portal is installed.

  2. For WebSphere Portal on WAS (UserData path), enter the following on the command line: cd profile_root/ConfigEngine.

  3. Enter the following command:

    ConfigEngine.sh validate-database-connection -DTransferDomainList=release,community,customization,jcr,feedback,likeminds -DWasPassword=password

For security reasons, you should not leave passwords in the wkplc_comp.properties file. Edit the file prior to running a configuration task and insert the passwords that are needed for that task. After the task has run, delete all passwords from the file.

Alternatively, you can specify the password on the command line rather than update the wkplc_comp.properties file.

For example: ConfigEngine.sh -DPortalAdminPwd=password -DWasPassword=password validate-wps-admin-login

When installing WebSphere Portal, the passwords in the wkplc_comp.properties file are automatically removed after configuration.


Parent topic:

Prepare DB2 for i5/OS for a stand-alone production server


Previous topic:

Transferring DB2 for i5/OS manually