IBM Support

Collecting Data: Common PIM Portlets(CPP) for WebSphere Portal

Recommended Resources


Abstract

Collecting troubleshooting data for ommon Personal Information Managment Portlets(CPP) with IBM® WebSphere® Portal expedites time to resolution by enabling IBM Support to provide informed problem analysis.

Content

If you have already contacted IBM Support or need to collect data to determine the nature of a problem in WebSphere Portal, review the following information as well as the technote Collecting Data: Read first for WebSphere Portal.

Collecting Common PIM Portlet(CPP) specific information

This document covers the following two portlets:

  • Common Mail Portlet
  • Common Calendar Portlet

1. If you are configuring the Common PIM portlets to connect to a Domino mail server, do the following:

A. Verify that you have configured authentication correctly. There are two options for authentication:
    1. Basic
    2. Single Sign-on (SSO) using one of the following: WebSphere/Domino SSO, Tivoli Access Manager (TAM) or Siteminder.
      If the authentication method you are have chosen is WebSphere/Domino SSO, do the following steps to test that SSO is working correctly:
        a. Sign on to WebSphere Portal.
        b. Make sure you have a Domino database where the Access Control List (ACL) has the -Default- and Anonymous access set to "No Access". The example in the next step assumes your database name is test.nsf, and it is located in the Domino \Data directory.
        c. Change the url in the browser to http://dominoserver.domain.com/test.nsf

        If a sign on screen appears, then SSO is not working for the Domino server. If SSO is not working, correctly configure the environment by performing the steps in the technote, "Troubleshooting WebSphere Portal, Domino Extended Products, and Domino SSO issues" (# 1158269).
    B. Verify XML services are enabled on the Domino server.
      To verify XML services are enabled, go to the following URL in a browser: http:// /LWPDominorequest
      The browser should return a message similar to the following message:

      Hello from Domino Web Service
      Accessing: NSF
      Domino Server dominoserver.domain.com


      If the browser does not return the message above, do the following to enable XML services:
        a. Add the following parameter to the Domino server's notes.ini: HTTPDomWSAppSpace=1
        b. Modify the Server document:
          i. Open the Server document in the Domino Directory.
          ii. Go to the Internet Protocols tab > Domino Web Engine tab.
          iii. Go to the Domino XML Services section at the very bottom of the Domino Web Engine tab, and select "Enable" for the 'XML Services' option. Save and close the Server document.
        c. Once XML Services have been enabled, you must restart the Domino HTTP task.

    2. Verify the configuration by performing the steps in the Infocenter for setting up collaborative services and automatic mail file detection

    Data Collection

    1. If you are still having problems please enable the following tracing:

    A. On the Domino server...

      If the back-end mail server is a Domino server, enable trace by typing the following in the Domino console:

      tell http debug session on
      tell http debug thread on
      tell http debug postdata on
      tell http debug responsedata on
      set config WEBAUTH_VERBOSE_TRACE=1
      set config WEBSESS_VERBOSE_TRACE=1
      set config LDAPDEBUG=7

      stop consolelog
      <delete (or move) <domino_dir>/data/IBM_TECHNICAL_SUPPORT/console.log>
      start consolelog

      Note: The trace goes to <domino_dir>/data/IBM_TECHNICAL_SUPPORT/console.log and <domino_dir>/data/IBM_TECHNICAL_SUPPORT/htses*

    B. Enable CPP trace logging by setting the following traceString in accordance with the instructions documented in the topic "Trace Logging" in the WebSphere Portal Information Center:

    com.lotus.cs.*=all=enabled
    com.ibm.workplace.mailbox.*=all=enabled
    com.ibm.workplace.adapter.*=all=enabled

    For further information regarding logging and tracing in the portal, refer to the topic "Logging and Tracing" in the WebSphere Portal Information Center.

    C. Get TCP trace.

      a. Download the tcp trace tool to a client workstation- http://www.pocketsoap.com/tcptrace
      b. Modify the Common PIM Portlet settings based on the type of mail server the portlet is connecting to. For more details, refer to the figure below.
      c. Run the tcptrace tool based on the type of mail server the portlet is connecting to. For more details, refer to the figure below.

    D. Re-create the problem with trace enabled:
      a. Log into Portal
      b. Record the time on the Portal server
      c. Go to the page with the Common PIM portlet
      d. Reproduce the problem.

    2. Collect the following files:

    A. From the Portal Server

    -<wp_profile_root>/logs/WebSphere_Portal/SystemOut.log
    -<wp_profile_root>/logs/WebSphere_Portal/SystemErr.log
    -<wp_profile_root>/logs/WebSphere_Portal/trace.log
    -<was_dir>/config/cells/<node>/security.xml
    -<wp_profile_root>/ConfigEngine/properties/wkplc.properties
    -<wp_profile_root>/PortalServer/config/config/CSEnvironment.properties
    -<wps_dir>/shared/app/cs.jar

    Be certain to indicate the relevant details (date and time, test case, user ID, etc) to IBM Support in your communications, and use specific entries from the log to illustrate the problem reported if possible.

    B. From the Domino server (if this is the configured mail server):

    • version of Domino server including any fixpacks or hotfixes
    • <domino_dir>/data/IBM_TECHNICAL_SUPPORT/console.log
    • <domino_dir>/data/IBM_TECHNICAL_SUPPORT/htses*
    • <domino_dir>/notes.ini
    • copy of email or calendar entry in a blank mail nsf file (if there is a problem reading a particular email or calendar entry)

    C. From the client machine:
    • browser type and version
    • the time recorded in step IV.
    • screen shot of the portlet with the error
    • output from tcptrace tool
    Note: Ideally trace files should contain only the trace output for the application in question, although this is not always possible.

    3. Confirm environmental information where you encountered the problem:

    -WebSphere Application Server version
    -WebSphere Portal version (standalone? test environment?),
    -WebSphere Application Server Developer and Rational Application Developer versions if applicable,
    -Any fixes, fixpacks applied (send event.history for both WebSphere Application Server and WebSphere Portal)

    4. Collecting and submitting logs and configuration data

    1. Reproduce the problem.

    2. Run the following script from <wp_profile>/PortalServer/bin to collect the data:

    Windows: wpcollector.bat
    Linux/Unix/i: wpcollector.sh

    5. Send the files to IBM Support by using the instructions outlined in Exchanging information with IBM Technical Support for problem determination.

    Related Information

    Document information

    More support for: WebSphere Portal
    Problem Determination

    Software version: 7.0, 8.0, 8.5

    Operating system(s): AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS

    Software edition: Enable, Express, Extend, Hypervisor Edition, Server

    Reference #: 1468956

    Modified date: 12 November 2014


    Translate this page: