Data collection and symptom analysis

There is one method to collect data and analyze symptoms for problem determination scenarios. You run a task that can collect and optionally send the data for you.

Run the wpcollector task to collect data and analyze symptoms for problem determination scenarios:
  1. If the support team has requested tracing, enable it now as instructed and then re-create the problem. If no tracing is requested, skip to the next step.
  2. Open a command prompt and change to the wp_profile_root/PortalServer/bin/ directory.
    Attention: You must run the wpcollector task from the wp_profile_root/PortalServer/bin/ directory. If you run the task from a different directory, the task fails.
  3. Run the following script to collect data:
    • Windows: wpcollector.bat
    • AIX®SolarisLinux: ./wpcollector.sh
    • IBM® i: wpcollector.sh
    Tip: The wpcollector script can automatically FTP the logs to IBM so that you dont need to manually transfer them. To begin the collection and FTP the results to IBM correctly, use the -Dpmr=pmr_number parameter to identify the collection with your PMR (Problem Management Record) number. Format the number using either periods or commas. For example: wpcollector.bat -Dpmr=12345.xxx.000

    To collect files for the Deployment Manager profile, use the -Ddmgr.root=dmgr_root parameter either alone or in conjunction with -Dpmr=pmr_number.

  4. If you did not automatically FTP your results, locate the wp.mustgather.zip file or the pmr-wp.mustgather-timestamp.zip file in the wp_profile_root/filesForAutoPD/ directory. Follow the instructions in "Exchanging information with IBM Technical Support for problem determination" to manually FTP your results.
Restriction: If you try to extract the wp.mustgather.zip file, some collections might not expand properly if the path name exceeds the 256 character limitation.