Verify database connections for iSeries

 

+
Search Tips   |   Advanced Search

 

You are here

  1. Planning for DB2 for iSeries
  2. Creating schemas and users for DB2 for iSeries
  3. Transferring DB2 for iSeries manually
  4. Verifying database connections for iSeries (Current task)

After IBM WebSphere Portal is configured to work with the preferred database, test the database connection to ensure that it operates correctly. We can do this by:

  • logging into WebSphere Portal from a Web browser

  • verifying from a command prompt

 

Verify WebSphere Portal is running from a browser

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

  • When trying to access the portal you may get a 503 error.

  • If you had any locale problems with the database, you could see invalid characters, such as ????, after logging in. This may happen if the character set of the database is not UTF-8 compliant.

  • If something went wrong with the data that was transferred, you may not be able to login. Portal will indicate you entered an invalid user ID and password even though you know it is valid.

 

Verifying the connection from a command line

We can also verify the database connection from a command line by performing the following steps:

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

  2. Type strqsh on the command line.

  3. Press Enter.

  4. For WebSphere Portal on WebSphere Application Server (UserData path), type the following on the command line: 

    cd  portal_server_root/config

  5. Press Enter.

  6. Type in the following information:

    WPSconfig.sh -profileName profile_root validate-database-connection-schema_name -DDbPassword=password

    ...where profile_root is the name of the WebSphere Application Server profile, schema_name is the name of the database schema, and password is the database administrator password.

  7. Press Enter.

Note on passwords: For security reasons, you should not leave passwords in the wpconfig_dbdomain.properties file. IBM recommends that you edit the wpconfig_dbdomain.properties file prior to running a configuration task, and insert the passwords that are needed for that task. After the task has run, you should delete all passwords from the wpconfig_dbdomain.properties file. For more information, see Delete passwords from configuration scripts. Alternatively, we can specify the password on the command line rather than update the wpconfig_dbdomain.properties file. For example:

WPSconfig.sh -profileName profile_root -DPortalAdminPwd=password validate-wps-admin-login

If you select the Install and Configure option when installing WebSphere Portal the passwords in the wpconfig_dbdomain.properties file are automatically removed after configuration.

 

Next steps

You have completed this step. Continue to the next step by choosing the following topic:

 

Parent topic:

Configuring databases