Troubleshoot IBM Survey Creator V1.0

 

Provides troubleshooting information on the IBM® Survey Creator application.

Before you begin to troubleshoot problems with the IBM Survey Creator V1.0 application, answer the following questions to help solve some common problems when using the application:

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 might be a problem with the base LDAP server configuration.
Product 5722-BZ1 is listed when the GO LICPGM command is run for a preinstalled and preconfigured iSeries™ server, but the option to install the IBM Survey Creator 1.0 application does not show up when creating a new WebSphere® Application Server using the wizards of the Admin HTTP Server. IBM Survey Creator V1.0 is not installed on your server. Install the IBM Survey Creator V1.0 application. The initial offering of the IBM Survey Creator V1.0 application is being delivered as a PTF. The HTTP Server for i5/OS® group PTF includes fixes for HTTP Server and other i5/OS products such as IBM Telephone Directory V5.2 and IBM Welcome Page V1.1. To determine which group PTF obtain and install, see both:

 

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. To determine the job CCSID for the HTTP server, enter WRKACTJOB on the CL command line and select Display job definition attributes. The HTTP server CCSID is determined by the HTTP server defaultFSCCSID directive. For more information, see Notices and limitations.
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). Problems also occur if you start the IBM Welcome Page application but do not start the IBM Survey Creator application. If the IBM Survey Creator application is not running, the Welcome Page application does not have links to it. Start the IBM Welcome Page application and the IBM Survey Creator application.
Requests to the application fail If you used the internal HTTP server included with WebSphere Application Server to reference the IBM Survey Creator V1.0 application, certain requests to the application fail. You must use the associated IBM HTTP server to reference the application. Security directives for LDAP server authentication are set up and required by the IBM Survey Creator application during the creation of a new application server instance. WebSphere Application Server's internal HTTP server is not set up with the necessary security directives, and certain requests to the application fail if the internal HTTP server is used. See Interaction with IBM HTTP server for i5/OS for more information.

 

Troubleshoot usage

Problem Cause Solution
Missing link to the application The URL http://your.server.name:port/ibm-bizApps/welcome/home.do takes you to the entry point for IBM Business Solutions, including the IBM Survey Creator V1.0 application. If the link to the IBM Survey Creator V1.0 application is missing, check to ensure that both the IBM Welcome Page application and the IBM Survey Creator application are started.
Object not found error If you receive a 404 - Object not found error in the IBM Survey Creator application, it might be because your plugin-cfg.xml file is corrupt. Perform the following steps to check this file and fix it, if necessary:

  1. Open the plugin-cfg.xml file, which is located at:
    /QIBM/UserData/.../config/
    cells/plugin-cfg.xml

  2. Check to see if the following virtual host specifications are in your file (assuming a virtual host of default_host and a port of 80:
    <VirtualHostGroup Name=
     "default_host"> <VirtualHost Name=
     "80"/>

  3. Check to see if the following URI affinity cookies are in your file:
    <URI AffinityCookie=
     "JSESSIONID" Name="/bizApps/*"/> 
    <URI AffinityCookie=
     "JSESSIONID" Name="/survey/*">

  4. If these specifications are not in your file, open the WebSphere Application Server administration console.

  5. Expand Environment.

  6. Click Update WebServer plugin.

  7. Click OK.

  8. Stop and restart the application server.

  9. Stop and restart the HTTP server.

 

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 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 through the administrative console of the WebSphere Application Server by enabling the trace service.

    The application does not need to be restarted after enabling the trace service. After enabling the trace service, recreate the problem. The trace statements should be written out to the trace log file. After capturing trace information for the recreated problem, disable the tracing service to prevent unwanted or extraneous information from written to the trace 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.

 

Parent topic:

IBM Survey Creator V1.0