MustGather: Issues with the IBM Web Administration for i5/OS GUI

Technote (troubleshooting)


Problem(Abstract)

This document explains how to collect data for issues with the IBM Web Administration for i5/OS GUI. Gathering this MustGather information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.

Resolving the problem

This document explains how to collect data for issues with the IBM Web Administration for i5/OS GUI. Gathering this MustGather information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.

An IBM Web Administration for i5/OS GUI error is generally indicated when the Administrative GUI screen throws an exception, resulting in a java stack or the administrative functions do not work as intended.

If you have already contacted IBM Support, continue through this document as requested by your support representative. Otherwise, refer to the Support for IBM System i main portal at the following URL: http://www-947.ibm.com/systems/support/supportsite.wss/brandmain?brandind=5000027.

IBM Web Administration for i5/OS GUI Error specific MustGather information

If you encounter an error when accessing the IBM Web Administration for i5/OS Page (HTTPAdmin), you should collect the following information when the internal application server and application(s) are experiencing the problem:

1. If the issue involves accessing or modifying a WebSphere Application Server Profile, refer to the following Appendix.
Appendix A: How to trace the HTTP Admin GUI for WebSphere issues
2. If the issue does not involve accessing or modifying a WebSphere Application Server Profile, refer to the following Appendix.
Appendix B: How to trace the HTTP Admin GUI for non-WebSphere issues
3. Execute and gather the httpAdmincollector tool and output.
Appendix C: How to execute and gather the httpAdmincollector tool and output
4. Follow the instructions to collect and send the data into IBM Support.
Appendix D: How to collect and send diagnostic information to IBM Support

For a listing of all technotes, downloads, and educational materials specific to the IBM i Server components, search the Support for IBM System i Web site at the following URL:

http://www.ibm.com/systems/support/i/
    • - Appendix A. How to trace the IBM Web Administration for i5/OS GUI for WebSphere Issues



      V6R1+ Tracing Instructions

      1. To stop the HTTP Admin GUI, on the operating system command line type the following:

      ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

      and press Enter.
      2. Issue the following command:

      EDTF STMF('/qibm/userdata/os/admininst/admin4/wlp/usr/servers/admin4/server.xml')

      In the file there is a line that looks like the following:

      <logging suppressSensitiveTrace="true"/>

      Insert the following lines AFTER this line:

      <logging maxFileSize="0"
      maxFiles="0"
      logDirectory="${server.output.dir}/logs"
      messageFileName="messages.log"
      traceFileName="trace.log"
      traceSpecification="com.ibm.as400.httpsvr=finest"
      traceFormat="ENHANCED"
      consoleLogLevel="INFO"
      copySystemStreams="true" />

      Hit F3 twice to save/exit the file.
      3. Issue the following command:

      EDTF STMF('/qibm/userdata/os/admininst/admin4/wlp/usr/servers/admin4/jvm.options')

      Insert the following lines into the file:

      -Dcom.ibm.websphere.os400.express.AdminWrapperTracing=true
      -Dcom.ibm.websphere.os400.express.AdminWrapperTracingDetail=true
      -DtraceSettingsFile=wasAdminTracing.properties

      Hit F3 twice to save/exit the file
      4. Restart the HTTP Admin server. On the operating system command line, type the following:

      STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

      and press Enter.
      5. In the Web browser, add the following text to the end of your URL '?debug=finest'. Your URL should look like the following:

      http://systemname:2001/HTTPAdmin?debug=finest

      This will enable extra tracing of the GUI functions inside the IBM Web Administration GUI interface.
      6. Re-create the problem in the GUI.
      7. Turn off the tracing by reversing the changes made in step 2 and step 3 above.
      8. Run through Appendix C to gather the httpAdmincollector.
      9. End and restart the HTTP Admin.



      V5R4 Tracing Instructions

      1. To stop the HTTP Admin GUI, on the operating system command line type the following:

      ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

      and press Enter.
      2. Issue the following command:

      CALL PGM(QSYS/QLWIWASTRC) PARM(DETAIL)
      3. Modify the following file to enable detailed LWI logging. Note: This step should be done regardless of Websphere version on V5R4.

      /QIBM/UserData/OS/OSGi/LWISysInst/admin2/lwi/conf/overrides/logging.properties

      Change the following line:

      java.util.logging.ConsoleHandler.level=WARNING

      to

      java.util.logging.ConsoleHandler.level=FINEST
      4. Restart the HTTP Admin server. On the operating system command line, type the following:

      STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

      and press Enter.
      5. In the Web browser, add the following text to the end of your URL '?debug=finest'. Your URL should look like the following:

      http://systemname:2001/HTTPAdmin?debug=finest

      This will enable extra tracing of the GUI functions inside the IBM Web Administration GUI interface.
      6. Re-create the problem in the GUI.
      7. Turn off the WebSphere GUI tracing with the following command:

      CALL PGM(QSYS/QLWIWASTRC) PARM(DISABLE)
      8. Modify the following file to disable detailed LWI logging. Note: This step should be done regardless of Websphere version on V5R4. It is not required for V6R1 or V7R1:

      /QIBM/UserData/OS/OSGi/LWISysInst/admin2/lwi/conf/overrides/logging.properties

      Change the following line:

      java.util.logging.ConsoleHandler.level=FINEST

      to

      java.util.logging.ConsoleHandler.level=WARNING
      9. Run through Appendix C to gather the httpAdmincollector.
      10. End and restart the HTTP Admin.
      • - Appendix B. How to trace the IBM Web Administration for i5/OS GUI for non-WebSphere issues

        1. To stop the HTTP Admin GUI, on the operating system command line type the following:

        ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

        and press Enter.
        2. Modify the following file to enable detailed LWI logging.

        V5R4:

        /QIBM/UserData/OS/OSGi/LWISysInst/admin2/lwi/conf/overrides/logging.properties

        V6R1 and V7R1:

        /QIBM/UserData/OS/OSGi/LWISysInst/admin4/lwi/conf/overrides/logging.properties

        Change the following line:

        java.util.logging.ConsoleHandler.level=WARNING

        to

        java.util.logging.ConsoleHandler.level=FINEST
        3 Add the following environment variable to the system to enable detailed tracing of the Integrated Application Server:

        ADDENVVAR ENVVAR(QIBM_LWI_TRACE) VALUE(ALL) CCSID(*JOB) LEVEL(*SYS)
        4. Restart the HTTP Admin server. On the operating system command line, type the following:

        STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN '-vv')

        and press Enter.
        5. In the Web browser, add the following text to the end of your URL '?debug=finest'. Your URL should look like the following:

        http://systemname:2001/HTTPAdmin?debug=finest

        This will enable extra tracing of the GUI functions inside the IBM Web Administration GUI interface.
        6. Re-create the problem in the GUI.
        7. Modify the following file to disable detailed LWI logging.

        V5R4:
          /QIBM/UserData/OS/OSGi/LWISysInst/admin2/lwi/conf/overrides/logging.properties

        V6R1 and V7R1:
          /QIBM/UserData/OS/OSGi/LWISysInst/admin4/lwi/conf/overrides/logging.properties

        Change the following line:

        java.util.logging.ConsoleHandler.level=FINEST

        to

        java.util.logging.ConsoleHandler.level=WARNING
        8.



        9.
        Remove the environment variable we added in Step 3:

        RMVENVVAR ENVVAR(QIBM_LWI_TRACE) LEVEL(*SYS)

        Run through Appendix C to gather the httpAdmincollector
        10. Restart the HTTP Admin server.
        • - Appendix C: How to execute and gather the HTTPAdmincollector for IBM i (HTTPADMCOL)



          R610/R710/720 HTTPADMCOL INSTRUCTIONS

          1.
          2.
            ADDLIBLE QMGTOOLS
          3. HTTPADMCOL ARE_FLAG(ADMIN2) FTPRSP(Y) PMR(55555) BRANCH(555) +
          COUNTRY(555) EMAIL(YOUREMAIL@COMPANY.COM)

          *The above command will run for 5-15 minutes and will automatically FTP the /tmp/collectorscripts/data/httpadmincollector.zip file to ecurep and forward to the PMR number noted. If the local IBM i does not have FTP access, it will fail to upload, and the zip file will need to be uploaded manually to
          http://www.ecurep.ibm.com/app/upload
          For full instructions on using HTTPADMCOL from QMGTOOLS, note document http://www-01.ibm.com/support/docview.wss?uid=nas8N1020078

          R540 httpAdminCollector Instructions

          R540 does not support QMGTOOLS. The tool that is used for this is in httpAdminCollectTools.zip. This needs to first be downloaded and installed using the below instructions.


          1. On the i5 command line, type mkdir '/home/httpcollector'
          2. Download the 'httpAdminCollectorTools.zip' file from the link below and place it in the '/home/httpcollector' IFS directory on the IBM i:

          ftp://public.dhe.ibm.com/services/us/igsc/cta/httpAdmin/httpAdminCollectTools.zip
          3. On the i5 command line, type STRQSH and press Enter.
          4. Type cd /home/httpcollector and press Enter.
          5. Type jar -xf httpAdminCollectTools.zip and press Enter.
          6. Type httpAdmincollector.sh and press Enter.
          7. You will receive the following prompt:

          Will this httpAdmincollector.zip file be uploaded to ecurep for a PMR? (This requires JDK 6.0) Y or N?

          If you response with a 'Y', you will be prompted to enter your PMR number and an e-mail address. The collector data will automatically be uploaded to IBM and attached to the PMR. If you respond with a 'N' (or you do not have JDK 6.0 installed), the data will be written to '/home/httpcollector/httpAdmincollector.zip'. You should send the httpAdmincollector.zip file into IBM Support for review.




          • - Appendix D: How to collect and send diagnostic information to IBM Support



            • - 1. Collect the httpAdmincollector.zip file from the /tmp/COLLECTORSCRIPTS/data directory on the IFS of the System i.



              Directions for collecting files located in the IFS

              To retrieve the file(s), do the following:

              1. Open the System i Navigator.
              2. Expand your system where the files are located. Log in with your user ID (preferably QSECOFR or equivalent).
              3. Expand File Systems, and drill down to the directory that contains the file(s) requested by this document.
              4. Locate the following file:
              httpAdmincollector.zip file from the '/tmp/COLLECTORSCRIPTS/data' directory on the IFS of the System i.
              5. Finally, drag and drop the files from System i Navigator to your desktop.


            • - 2. Upload the data to IBM Support



              Transferring files to IBM


              • - For transferring files to IBM that are smaller than 2GB each (files may exceed 2GB in total)




                • - If you have an existing PMR



                  1. Go to our ECUREP upload site at the following address:
                  http://www.ecurep.ibm.com/app/upload

                  2. Enter your PMR number, select OS/400 for the Upload is for field, then supply your e-mail address (a confirmation of the upload will be sent to you). Click Continue.

                  3. On the next screen click on the Choose File button to select the file you would like to upload to IBM Support. Click Submit to transfer the file and associate it with your PMR.



                • - If you are opening a new PMR



                  1. Sign on to the SR tool at the following URL:
                  http://www.ibm.com/support/entry/portal/open_service_request

                  2. Select Open a new service request.

                  3. Follow the steps to create a Service Request until you have come to the final page prior to submitting your request.

                  4. Scroll down to the Attach additional files section.

                  5. Click Browse to start adding files to your PMR. Note that there is a 2GB limit per file.

                  6. Click Submit when you are done adding files and are ready to submit your PMR to IBM Service.





              • - For transferring files to IBM that exceed 2GB each


                Important Note: You must have a PMR created to complete these steps.

                1. Prepare your files for transfer:

                a. You should compress (if possible) each file, or multiple files, into one zip archive. This will speed up the transfer process and make the overall process easier.
                b. Rename your file(s) prior to transfer. Use the following file naming convention to name your file:

                Caution: The file must use this format to be associated with the PMR; this is the complete PMR record number. Using any other file name will cause the file to be deleted.

                Enter your PMR record information and file type as follows:
                xxxxx.bbb.ccc.yyy.zzz

                where:
                xxxxx = PMR number
                bbb = Branch
                ccc = Country code
                yyy = Unique file name
                zzz = File type or file extension

                Example

                12345.055.000.collector01_29_Aug_06.zip

                2. From a command prompt, terminal window, or FTP client, FTP to the following site:

                ftp testcase.boulder.ibm.com

                3. Log in as anonymous.

                4. Enter your e-mail address as the password.

                5. Using the cd command, change to the following directory:

                cd /toibm/os400

                6. Enter the following command to place the file on the server:

                put file_name

                7. Enter the quit command to end your transfer session.






          Historical Number

          533853574

          Document information


          More support for:

          IBM i
          Communications-TCP

          Software version:

          5.4.0, 5.4.5, 6.1, 6.1.0, 6.1.1, 7.1, 7.1.0

          Operating system(s):

          IBM i

          Reference #:

          N1012789

          Modified date:

          2013-05-28

          Translate my page

          Content navigation