Windows clustered server: Verify DB2 for IBM i database connections
Prerequisites
Windows clustered server: Modify DB2 for IBM i database properties
Windows clustered server: Create DB2 for IBM i user profiles
Windows clustered server: Set up IBM DB2 for i databases automatically
Windows clustered server: Transfer DB2 for IBM i manuallyYou 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
There may be an error if any of the following conditions appear.
Verify the connection from a command line:
- When trying to access the portal you get a 503 error.
- If you had any locale problems with 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. WebSphere Portal will indicate you entered an invalid user ID and password even though you know it is valid.
- Open a command line on the local machine whereWebSphere Portal is installed.
- For WebSphere Portal on WAS (UserData path):
cd WP_PROFILE/ConfigEngine
- Enter the following command:
ConfigEngine.sh validate-database-connection -DTransferDomainList=release,community,customization,jcr,feedback,likeminds -DWasPassword=foo
You can specify the password on the command line rather than update wkplc_dbdomain.properties. For example:
ConfigEngine.sh -DPortalAdminPwd=foo -DWasPassword=foo validate-database
When installing WebSphere Portal, the passwords in wkplc_dbdomain.properties are automatically removed after configuration.
Parent
Windows clustered server: Set up a remote DB2 for IBM i database
Previous
Windows clustered server: Transfer DB2 for IBM i manually