Verify the database user registry
You are here
- Database user registry
- Configure a database user registry
- Verify the database user registry (Current task)
If you have configured security while configured to use a database other than Cloudscape, do not rerun the database-transfer task. This task will not transfer the data inserted during the enable-security task and will cause the Portal to become inoperable.
To recover from this situation, you would have to disable and re-enable security.
- Open a Web browser and enter the portal page URL...
http://hostname.example.com:port/wps/portal...where hostname.example.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 WebSphere Application Server. For example...
http://www.ibm.com:10038/wps/portalThis value is also stored in the WpsHostPort property in the wpconfig.properties file in the following directory:
- Windows and UNIX: portal_server_root/config/
i5/OS:
portal_server_root/config/
If you customized the portal page URL, for example by modifying the base URI portion of the default URL (wps) or the portal page (portal), be sure to enter the customized URL.
- The portal should load in the browser.
If you get an Internal Server Error, WebSphere Application Server might not have completely started yet. Wait a couple of minutes to ensure that WebSphere Application Server has completely started and try to access the portal page again.
- Verify that you are still able to log in as the portal administrator now that security is enabled. Click Log in and then enter the administrative user ID and password. Click Log in again.
Related Information
Parent Topic
Database user registry