Host On-Demand tracing checklist

Use the following instructions to help you gather some of the more common traces requested by the IBM Host On-Demand Support Team.

1. Basic traces
2. Advanced Traces: Enable Transport traces
3. Advanced Traces: Enable IPMonitor (or IPMON) traces

1. Basic Traces

   These traces gather information on problems when the client does not download as expected. This trace also captures the Host On-Demand configuration information.

   1. Back up your existing Deployment Wizard HTML and zip files to create a new debug version of these files.
   2. Edit your existing Deployment Wizard HTML file to create a debug copy of your files and save it with a new name.
   3. If you use the Cached client or Web Start client, take the following steps:
      1. On the Additional Options window, click Cache/Web Start options.
      2. Click the Basic Options tab.
      3. Click Yes for Debug installation process?.
      4. Click OK to return to the Additional Options window.
   4. Click Advanced Options.
   5. Click HTML parameters in the tree view.
      1. Type DebugCode in the Name field.
      2. Type 65535 in the Value field.
      3. Click Set.
   6. Click OK to return to the Additional Options window.
   7. Complete editing the file and give it a new name, for example, debug.
   8. Deploy the updated file to your Web server.
   9. Start the Host On-Demand client using the new debug file you created with the Deployment Wizard.
   10. Switch to the emulator window and recreate the problem. Do not close the trace window.
   11. When the problem occurs again, open the browser's Java console and copy the contents to a *.txt file. Make sure you obtain all the Java console entries. The Java console might be multiple windows in length. For more information, refer to Displaying the Java Console.
2. Advanced Traces: Enable Transport traces

   These traces capture the telnet traffic between Host On-Demand and the host telnet server. The basic traces are also included.

   1. Back up your existing Deployment Wizard HTML and zip files to create a new debug version of these files.
   2. Edit your existing Deployment Wizard HTML file to create a debug copy of your files and save it with a new name.
   3. If you use the Cached client or Web Start client, take the following steps:
      1. Click Cache/Web Start options.
      2. Click the Basic Options tab.
      3. Click Yes for Debug installation process?.
      4. Click OK to return to the Additional Options window.
   4. Click Advanced Options.
   5. Click HTML parameters in the tree view.
      1. Type DebugCode in the Name field.
      2. Type 65535 in the Value field.
      3. Click Set.
      4. Type TraceOptions in the Name field.
      5. Type the following value: SaveLocation=Local,OutputFile=c:\temp\hodtrace.txt,HACL.Transport=3
      6. Click Set.
   6. Click Problem determination in the tree view and click Yes for Problem determination.
   7. Click OK to return to the Additional Options window.
   8. Complete editing the file and give it a new name, for example, debug.
   9. Deploy the updated file to your Web server.
   10. Start the Host On-Demand client using the new debug file you created with the Deployment Wizard. The Host On-Demand desktop appears. Then the Host On-Deamand Automatic Component Trace window appears noting that tracing has started.

       You might have to move other windows around to find this window.

   11. Click on the session icon, if the session does not auto-start.
   12. Switch to the emulator window and recreate the problem. Do not close the trace window.
   13. When the problem occurs again, select the Host On-Demand Automatic Component Trace window. The window might now be hidden behind other windows. Select the "END" trace option and click OK.
   14. Open the browser's Java console and copy the contents to a *.txt file. Make sure you obtain all the Java console entries. The Java console might be multiple windows in length. For more information, refer to Displaying the Java Console.
3. Advanced Traces: Enable IPMonitor (or IPMON) traces

   This trace is useful to determine problems within the datastream, as this traces captures the traffic between Host On-Demand and the host telnet server. Basic traces are also included.

   1. Back up your existing Deployment Wizard HTML and zip files to create a new debug version of these files.
   2. Edit your existing Deployment Wizard HTML file to create a debug copy of your files and save it with a new name.
   3. On the Host Sessions window, look for the name of the session you want to trace, for example, MYSESSION.
   4. If you use the Cached client or Web Start client, take the following steps:
      1. Click Cache/Web Start options.
      2. Click the Basic Options tab.
      3. Click Yes for Debug installation process.
   5. Click Advanced Options.
   6. Click HTML parameters in the tree view.
      1. Type DebugCode in the Name field
      2. Type 65535 in the Value field.
      3. Click Set.
      4. Type IPMonitor in the Name field.
      5. Type the following value: SessionName=MYSESSION,TraceFile=IPMONtrc.txt

         Where MYSESSION is the session name in the Deployment Wizard configuration. This must match exactly.

      6. Click Set.
   7. Click Problem determination in the tree view and click Yes for Problem determination.
   8. Click OK to return to the Additional Options window.
   9. Complete editing the file and give it a new name, for example, debug.
   10. Deploy the updated file to your Web server.
   11. Start the Host On-Demand client using the new debug file you created with the Deployment Wizard. The Host On-Demand desktop appears.
   12. Right click on the session icon and select Start Session with IPMONITOR.
   13. The IPMonitor V1.0 for Java, automatic mode window appears noting the trace has started.

       You might have to move other windows around to find this window.

   14. Switch to the emulator window and recreate the problem. Do not close the trace window.
   15. When the problem occurs again, select the IPMonitor V1.0 for Java, automatic mode window. The window might now be hidden behind other windows. Click Stop and then click Save and Exit. Confirm the location where the trace file is saved and the file's name.
   16. Open the browser's Java console and copy the contents to a *.txt file. Make sure you obtain all the Java console entries. The Java console might be multiple windows in length. For more information, refer to Displaying the Java Console.