Collecting troubleshooting data for Security configuration issues with IBM® WebSphere® Portal 8.0 expedites time to resolution by enabling IBM Support to provide informed problem analysis.
If you have already contacted IBM Support and must collect data to determine the nature of a problem in WebSphere Portal, review the information below for the available methods of data collection. Otherwise, review Collecting Data: Read first for WebSphere Portal 8.0.
Collecting Security Configuration information
Security configuration issues can include:
* Enabling standalone ldap user registry (wp-modify-ldap-security)
* Enabling federated ldap user registry (wp-create-ldap)
* Validation tasks (validate-federated-ldap, validate-standalone-ldap)
* Database User Registry (wp-create-db)
* Change WebSphere Application Server admin user (wp-change-was-admin-user) or Websphere Portal admin user (wp-change-portal-admin-user)
* Other configuration tasks related to security such as updating realms, base entries, entity types, etc.
* Configuration Wizard
Note: If you are using an LDAP server, send in LDIFs of the problematic users and/or groups. You can use ldapsearch to obtain the LDIFs.
Automated log collection is available for this data collection and is the recommended method for improving accuracy of the data collection.
IBM Support Assistant Data Collector (ISADC) for WebSphere Portal version 8
Download Tool | Access the Quick Start Guide
After downloading the IBM Support Assistant Data Collector, perform the following steps to collect the data and send to IBM Support:
1. Extract the contents of the downloaded file to the <wp_profile_root>\PortalServer directory, which will create the subdirectory "ISADC" (e.g. c:\WebSphere\wp_profile\PortalServer\ISADC).
2. Run the isadc.bat file (Windows) or isadc.sh (UNIX or Linux) from the ISADC directory (e.g. c:\WebSphere\wp_profile\PortalServer\ISADC\isadc.bat).
3. Once the tools begins in Console Mode, provide the file name of the collection to be created: "<PMR #>.isadc.zip" (e.g. 22222,111,000.isadc.zip).
4. Select the following options from the next set of command prompts: WebSphere Portal->Installation and Configuration->Portal Configuration Problem.
5. Next follow the series of prompts to set the tracing and reproduce the issue. For additional information on usage, access the Quick Start Guide. If you choose not to FTP the files to IBM via ISADC, follow the instructions in Exchanging information with IBM Technical Support for problem determination.
If you are unable to use IBM Support Assistant Data Collector (ISADC) for WebSphere Portal for automatic log collection, use the following instructions for manually collecting the necessary information.
Collecting and submitting logs and configuration data
1. Reproduce the problem. Collect screenshots, userId, and timestamp information as appropriate.
2. Run the following script from <wp_profile>/PortalServer/bin to collect the data:
- Windows: wpcollector.bat
- Linux/Unix/i: wpcollector.sh
Note: If you wish to use wpcollector to FTP the files to IBM Support, include the -Dpmr=<pmr_number> parameter to indicate the relevant PMR #. For example: wpcollector.bat -Dpmr=11111,222,333
For a clustered environment, please also collect files for the Deployment Manager profile: use the -Ddmgr.root=<dmgr_root> parameter either alone or in conjunction with -Dpmr=<pmr_number>
Note: If you are manually submitting the files from both the WebSphere Portal server and the Deployment manager, please ensure that IBM Support can differentiate between the two sets of files.
3. If you did not FTP your files via wpcollector, locate the "wp.mustgather.zip" file or the "<pmr #>-wp.mustgather-timestamp.zip" file in <wp_profile_root> /filesForAutoPD/. Send the files to IBM Support by using the instructions outlined in Exchanging information with IBM Technical Support for problem determination.
Note: When sending in logs for review, include any relevant screenshots, timestamps, userIds, etc. in order to expedite analysis of the issue.