Provides troubleshooting information on the IBM® Welcome Page V1.1 application.
Before you begin to troubleshoot problems with the IBM Welcome Page V1.1 application, answer the following questions to help solve some common problems when using the application:
- Are all of the product prerequisites installed? See Verify the prerequisites for more information.
- Is your LDAP server started?
- Is your IBM Welcome Page application started?
- Is your application server started?
- Is your HTTP server started?
Use the following information if you are still having problems with your application:
Troubleshoot setup
| Problem | Cause | Solution |
|---|---|---|
| Your installation failed with the following message: ldap_search: Insufficient access | You entered the wrong LDAP server administrator password. | Obtain the correct password or reset the password. |
| Your setup script failed with the following messages: ldap_search: No such object Error 32 verifying LDAP settings | There might be a problem with the base DN not existing on the LDAP server. | There is a problem with the base LDAP server configuration. See Troubleshoot Directory Server in the Directory Server (LDAP) topic for more information. |
| IBM Business Solutions (5722-BZ1) is not listed when the RSTLICPGM command is run for a preinstalled and preconfigured iSeries™ server | IBM Business Solutions is not installed on your server. | Reinstall both the IBM Telephone Directory V5.2 application and the IBM Welcome Page V1.1 application. |
Troubleshoot authentication
| Problem | Cause | Solution |
|---|---|---|
| Log in fails | In the application, user IDs and passwords must contain characters that map to the job CCSID that is used by the HTTP server. Otherwise, authentication fails. | Make sure that your characters map to the job CCSID that is used by the HTTP server. For more information, see Notices and limitations in the IBM Telephone Directory V5.2 topic. |
| URL fails or the application does not appear | If you did not start the IBM Welcome Page application, the URL fails (http://your.server.name:port/ibm-bizApps/welcome/home.do or http://your.server.name:port/ibm-bizApps/welcome/admin.do). | Start the IBM Welcome Page application. |
Troubleshoot usage
| Problem | Cause | Solution |
|---|---|---|
| Administration user ID confusion | It might be confusing as to which user ID you should input for authentication to the application when you (the administrator) need to update or register a user in a closed enrollment environment. | The default user ID is Administrator, and the password is set up during installation. Do not enter your personal user ID and password. Application user IDs are always viewable to everyone. If you do not know the user ID for an entry, use the application's search page to find the entry. The user ID is displayed under the picture. |
| Special characters (such as ", &, <, or >) not handled correctly | The IBM Welcome Page V1.1 application has been written to accept and handle all characters correctly, even those identified as special characters (or metacharacters) for HTML, JavaScript™, and LDAP filters and attribute values. | There are known cases when the IBM Welcome Page V1.1 application handles
special characters for LDAP attribute values correctly, according to the RFC
2253 standard. However, the iSeries Directory
Services (LDAP) directory server does not fully support the standard. For
these cases, there is nothing that can be done other than to avoid the use
of such characters. The quote (") character is an example of this problem. The RFC 2253 standard specifies that the character must be escaped by preceding it with a backslash (\) to be accepted as a literal character in an LDAP attribute value. Since the current version of iSeries Directory Services (LDAP) does not fully support RFC 2253, the server saves both the backslash character as well as the quote character. |
Error logging and debugging
- Error logs
The application server has a variety of logs to which messages are written. For example, system message, which can be written by any application server component or application are written to general purpose logs such as the JAVA Virtual Machine (JVM) logs and the IBM Service logs. Other logs are very specific in nature and are scoped to a particular component or activity. For example, the HTTP Server plugin maintains a component-specific plugin log.
The general purpose logs, such as JVM and IBM Service, are used to monitor the health of the application server and assist in troubleshooting. Troubleshooting for specific components might require additional log analysis, such as component or product specific log files.
- Trace statements
Application trace statements can be enabled for the purpose of debugging problems. If problems persist, and you have to call IBM Service for help, one of the first thing they might ask you for is a copy of the application's trace output. Trace statements are enabled by adding a line to the application's configuration file and restarting the application.
The application will read the new configuration when it is started. Application trace statement will be enabled at that time. When enabled, trace statements are written to the server's SystemOut.log file.
- LDAP and HTTP server trace
See the following information for details on LDAP and HTTP server trace:
General troubleshooting information
These resources provide general troubleshooting assistance.
- For WebSphere® Application Server - Express V5, see the associated Troubleshooting topic.
- For WebSphere Application Server - Express for iSeries V5.1, see the associated Troubleshooting topic.
- For WebSphere Application Server for iSeries V5, see the associated Troubleshooting topic.
- For WebSphere Application Server for iSeries V5.1, see the associated Troubleshooting topic.
- For WebSphere Application Server for OS/400® V6 (including Express), see the associated Troubleshooting topic.
- Read the WebSphere Application Server - Express V5.1 Release
Notes
- Read the WebSphere Application Server - Express V5 Release
Notes
- Read the WebSphere Application Server and WebSphere Application
Server - Express V6 Release Notes
- Read the WebSphere Application Server V5.1 Release Notes
- Read the WebSphere Application Server V5 Release Notes