Logging and tracing
If you are experiencing a problem, you might want to enable tracing and then re-create the problem to capture more log information. You can enable logging and tracing for software that is shipped with WebSphere® Portal. Enabling tracing makes log output more verbose. For example, you can enable tracing within WebSphere Application Server to obtain information about application servers and other processes.
Refer to the MustGather data collection
lists used in troubleshooting various problems in WebSphere Portal and IBM® Web Content
Manager. Collecting MustGather
data early, even before opening a PMR, helps IBM Product Support quickly
determine if:
- Symptoms match known problems (rediscovery).
- There is a non-defect problem that can be identified and resolved.
- There is a defect that identifies a workaround to reduce severity.
- Locating the root cause can speed development of a code fix.
Simplify this process even more by using the IBM Support Assistant Lite for WebSphere Portal to automate the collection of the diagnostic data needed to troubleshoot most of these situations. You can use the information gathered to help solve your own problems or to report an issue to IBM Product Support.
Links to important WebSphere Portal tracing questions
- How do I turn on WebSphere Portal trace logging?
- See Trace logging for information.
- What are the different trace settings and where are the logged?
- See WebSphere Portal run-time logs for information.
- How do I change the location of my logs?
- See Changing the log file name and location