Troubleshooting SRA
Appendix D Troubleshooting Your Portal Deployment 163
gateway-install-root
/SUNWam/config/
AMConfig-
instance-name
.properties
2. Set the debug level:
com.iplanet.services.debug.level=
The debug levels are:
error
- Only serious errors are logged in the debug file. Rewriter usually stops
functioning when such errors occur.
warning
- Warning messages are logged.
message
- All debug messages are logged.
off
- No debug messages are logged.
3. Specify the directory for the debug files in the following property of the
AMConfig-
instance-name
.properties
file:
com.iplanet.services.debug.directory=/var/opt/SUNWam/debug
where
/var/opt/SUNWam/debug
is the default debug directory.
4. Restart the Gateway from a terminal window:
gateway-install-root
/SUNWps/bin/gateway -n
gateway-profile-name
start
Introduction to
shooter
The
shooter
tool captures all the information that the development and support
team will require to troubleshoot problems in your deployment of the Sun Java
System Portal Server Secure Remote Access product. You can also run this tool on a
Portal Server machine.
This tool captures the following data:
• Installation type - determines if the installation has Sun Java System Portal
Server with Sun Java System Secure Remote Access core, or Portal Server with
SRA
• System configuration related information -determines the host, domain,
operating system, version, CPU type and speed, clock speed, and memory
available
• Processors, processor sets, and the SRA processes bound to them
• SRA installation log
•The
platform.conf
file(s)