Consolidated support tools

Transcription

1 WebSphere Product Center Consolidated support tools Version 5.3.2

2

3 WebSphere Product Center Consolidated support tools Version 5.3.2

4 Note Before using this information and the product it supports, read the information in Notices on page 7.

5 Contents Chapter 1. Diagnostic tools Notices Chapter 2. Using diagnostic tools Copyright IBM Corp. 2000, 2009 iii

6 iv WPC: Consolidated support tools

7 Chapter 1. Diagnostic tools You can use the diagnostic tools to retrieve all the necessary configuration files when working with IBM Software Support to troubleshoot your issues. The diagnostic tools are a command-line based set of tools that collects information based on the parameters you specify and masks all sensitive data including user names and passwords. Use the diagnostic tools to create a.zip file in the directory you specify. Each.zip file includes a time stamp embedded within each file name and contain a report in both the XML and HTML formats. Stack files that are collected: v WebSphere Product Center version and configuration v Database version and configuration v Operating system version v Application server version v Java version Log files that are collected: v System logs v Application server logs v Database logs v Other log files that you can specify Configuration files that are collected: v common.properties v admin_properties.xml v docstore_mount.xml v data_entry_properties.xml v log.xml Environment information that can be collected: v uname a v ulimit a v Host name v Output of environment You can start or stop the system monitoring to capture system status in the form of logs, for a specific period of time. The system status that can be monitored: v vmstat v iostat v traceroute v File descriptor count Copyright IBM Corp. 2000,

8 2 WPC: Consolidated support tools

9 Chapter 2. Using diagnostic tools If you have not been able to resolve your issue with the troubleshooting and support documentation, you can use the diagnostic tool along with IBM Software Support to help you troubleshoot your issues. The pimsupport.sh shell script allows you similar ways of invoking various data integrity checks for different situations. Before you begin v You must enter a fully qualified file name and directory with the outputdirectory parameter if the default tmp directory is not specified in your common.properties file. v You can run the pimsupport.sh --help command to display the help information for the diagnostic tool. v When collecting your configuration files for submission to IBM Software Support, you must specify all of the optional parameters and set all of the variables to yes or all so that all configuration files are collected and saved in the.zip file. 1. Open a command-line shell. 2. Run the pimsupport.sh shell script in the $TOP/bin directory: Syntax pimsupport.sh --outputdirectory=path_to_store_the_result --collectdbinfo=yes no --collectwpcconf=yes no --collectwpclogs=all appsvr scheduler workflowengine queuemanager admin eventprocessor --collectsysinfo=yes no --collecmonitorlogs=yes no --monitor=start stop --dumpprocess=<pid> --collectwpcconf=yes no --collectappsvrlogs=yes no Parameters for general options --help This parameter is used to print the usage information. --version This parameter is used to print the version number of pimsupport.sh file. --outputdirectory=path_to_store_the_result path_to_store_the_result is the directory where the final output file resides. If the directory is not specified, the default directory is the tmp directory as defined in the $TOP/etc/default/common.properties file. Parameters for information collection options --collectdbinfo=yes no no is the default value yes specifies if relevant details about the database being used are collected. This parameter is used to collect database-related information. For DB2, it is the output of db2support command; for Oracle, it is some dynamic database information. --collectwpcconf=yes no no is the default value. Copyright IBM Corp. 2000,

10 yes specifies that all configuration files are collected. This parameter is used to collect product configuration files. The list of files is defined in the $TOP/etc/default/file_collection.xml file. If you make changes to the file_collection.xml file, you must restart the system before your changes are applied. --collectwpclogs= all appsvr scheduler workflowengine queuemanager admin eventprocessor all specifies that all logs are collected from the $TOP/logs directory. appsvr specifies that all logs are collected from the application server service. scheduler specifies that all logs are collected from the scheduler service. workflowengine specifies that all logs are collected from the workflow engine service. queuemanager specifies that all logs are collected from the queue manager service. admin specifies that all logs are collected from the admin service. eventprocessor specifies that all logs are collected from the event processor service. This parameter is used to collect log files generated by the product. If not specified, no logs are collected. You can specify multiple services by separating each service with the character and enclosing them with quotation marks. --collectsysinfo=yes no no is the default value. yes specifies if the system platform information is to be collected. For example, uname, ulimit, and so on. --collectmonitorlogs=yes no no is the default value. This parameter is used to collect the continuous log output produced by the --monitor=start option. --monitor=start stop This parameter is used to start or stop a background job, which continuously monitors system information, such as vmstat, iostat, and so on. --dumpprocess=<pid> This parameter is used to dump process information for a process with the specified id PID, usually for a process with high CPU usage. --collectsysinfo=yes no no is the default value. yes specifies if the system platform information is to be collected. For example, uname, ulimit, and so on. Parameters for integrity check --integrity= basic workflow serialization full basic is used to check the database tables. 4 WPC: Consolidated support tools

11 workflow is used to check for any ghost items. serialization is used to check for data corruption issues. full is used to check for all three types of integrity in sequence. --code=<company_code> If specified, an integrity check is performed for the company in which the catalog or colarea should be checked. This is a required parameter for all integrity related functions. --colarea=collab_area_name This is an optional parameter. If specified, an integrity check is only performed on the specified collaboration area. Otherwise, the integrity check is performed on all collaboration areas. --catalog=ctg_name This is an optional parameter. If specified, an integrity check is only performed on the specified catalog. Otherwise, the integrity check is performed on all catalogs. --action= verify restore verify is the default value. This is an optional parameter. Example The examples provided below will help you understand the various pimsupport.sh parameters, and their usage: v To check the usage and options of pimsupport.sh utility: pimsupport.sh --help v To start system monitoring for continuously measuring the system status, such as memory, io, cpu, and so on: pimsupport.sh --monitor=start v To gather and collect log files selectively, for example, appsvr and scheduler logs: pimsupport.sh --collectwpclogs="appsvr scheduler" v To perform integrity check on one catalog: pimsupport.sh --integriy=serialization --code=acme --catalog="product Catalog" Chapter 2. Using diagnostic tools 5

12 6 WPC: Consolidated support tools

13 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user s responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Copyright IBM Corp. 2000,

14 Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Silicon Valley Lab Building 090/H Bailey Avenue San Jose, CA U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: 8 WPC: Consolidated support tools

15 (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at copytrade.shtml. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. Notices 9

16 10 WPC: Consolidated support tools

17

18 Printed in USA