To Collect Required Debug Data for Any Portal Server Problem

All problems described in this technical note need basic information collected about when the problem occurred and about the system having the problem. Use this task to collect that basic information.

For problems with Portal Server Secure Remote Access (gateway), you need to collect data from both the portal and gateway hosts if they are separate (the usual configuration in a production environment). If possible, provide the output from Sun Explorer Data Collector (SUNWexplo) of the machine where the problem occurred.

1. Note the day(s) and time(s) the problem occurred.

2. Provide a graphical representation of your deployment. Include all hosts and IP addresses, host names, operating system versions, role they perform, and other important systems such as load balancers, firewalls, and so forth.

3. For Solaris OS systems, use the ps6info.sh script to gather all the necessary information. For HP-UX, Linux, and Windows platforms, or if you do not have the ps6info.sh script, continue with the remaining steps.

4. Note the operating system.

   Solaris OS

   uname -a

   HP-UX

   uname -r

   Linux

   more /etc/redhat-release

   Windows

   C:\Program Files\Common files\Microsoft Shared\MSInfo\msinfo32.exe /report C:\report.txt

5. Note the patch level.

   Solaris OS

   patchadd -p

   HP-UX

   swlist

   Linux

   rpm -qa

   Windows

   Already provided in the C:\report.txt file above.

6. Get the /etc/opt/SUNWps/.version file (or .version-sra for the Portal Server Secure Remote Access).

7. Note the web container (Sun Java System Web Server, Sun Java System Application Server, BEA WebLogic, or IBM WebSphere).

8. Get the log files.

   UNIX and Linux

   /var/opt/SUNWps/*

   Windows

   server-root\instance-dir\portal\logs\*

   ---

   Note –

   If possible, provide just the relevant extracts of log files for the same time period that show the problem, with sufficient context to see what else was occurring during the error occurrence and shortly before. Thus for relatively short log files, send the entire log file, whereas for long-running hence large log files, an extract might be more appropriate, though be sure to include all the material from the time of the error as well as at least some lead-in logging from before the error apparently occurred.

   ---

9. Get the configuration file.

   UNIX and Linux

   more /etc/opt/SUNWps/.version (or .version-sra for Secure Remote Access)

   Windows

   more server-root\.version (or .version-sra for Secure Remote Access)