Typical Portal Traces For Different Security Scenarios - IBM BS029ML - WebSphere Portal Server Self Help Manual

files, such as ConfigTrace.log, SystemOut.log, and SystemErr.log, as well as trace.log, if any
traces are enabled. Always keep the evidence for the "crime scene".
A verification checklist of a working system with security enabled
After the security is enabled, the first thing we would like to do is to verify whether the
configuration is correct. The following is a generic list, which should be applicable to most
cases:
The configuration task ran successfully. (BUILD SUCCESSFUL!)
You can start the application server and portal server using the administration user
(WasUserid) configured for WebSphere Application Server.
You can log in to WebSphere Administrative Console and Portal using the administration
users respectively.
The portal administration users are able to navigate to the administration portlets and
conduct administration operations, such as create pages, search and add users and
groups, install portlets, create virtual portals, and so on.
The portal administrator user can assign users and groups of access permissions to
resources, and verify them with proper user IDs

4.3.2 Typical portal traces for different security scenarios

Here we discuss typical portal traces for different security scenarios.
Recommendations for log settings
How many times have we seen that customers spent several hours or even days to try to
recreate a scenario, and ended up with a small log file without capturing the real data? This
happens often because the default settings for runtime log and diagnostic trace files are
usually too small, and should be changed to accommodate more data.
Important: Always change the default size and historical copy settings for the runtime and
diagnostic trace log files, such that critical error conditions are logged.
Chapter 4. WebSphere Portal security
105