IBM BS029ML - WebSphere Portal Server Self Help Manual page 120

Depending on the environment, you may want to increase the size of log file and the historical
copies of these files to a larger value. For example, you can set the file size to 20 MB and the
number of files to 10. Thus, you would effectively have about around 200 MB of log data at
any time for analysis. Figure 4-5 shows the example settings.
Figure 4-5 Trace log settings
Tip: In a stand-alone environment of WebSphere Portal Version 6, the WebSphere
Application Server Administrative Console can be accessed through the application
WebSphere_Portal (the default port 10027). You do not need to start server1.
Portal traces
After the initial troubleshooting steps, if it is not obvious what had caused the problem, you
may need to enable additional traces. Here we try to give some generic trace strings that are
applicable to many situations. If you have reason to believe that more specific strings are
required, we would suggest an analysis of the Java stacktrace following the error message(s)
in the log. The stacktrace should show certain calling code patterns that should give clues to
what to trace.
On the WebSphere Portal support Web site, we have published a set of MustGather
TechNotes that contain some typical cases for security related problems, covering a broad
range of problems encountered in debugging portal security problem. They are accessible at:
http://www-1.ibm.com/support/docview.wss?rs=688&uid=swg21236371
For most Portal security related problems, we recommend WMM traces (<wmmbase>):
com.ibm.websphere.wmm.*=all:com.ibm.ws.wmm.*=all:WSMM=all
106
IBM WebSphere Portal V6 Self Help Guide