MustGather: Plug-in (remote) install problems
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for plug-in (remote) installation problems with the IBM WebSphere Application Server. Gathering this information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.
 
 
Resolving the problem
If you already contacted support, continue to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.
Plug-in (remote) install specific MustGather information
To begin troubleshooting plug-in (remote) install problems, first verify the following:
  1. Verify the presence of required plug-in libraries and plug-in configuration file (plugin-cfg.xml):
  2. Verify that you are running supported GSKit levels required by the WebSphere Application Server plug-in.

  3. Verify that the plug-in regeneration from the Deployment Manager (or Base, if the product is at the Application Server base level) Administrative Console is performed and that the plug-in configuration file (plugin-cfg.xml) is copied over to the remote Web server. Also, if needed, verify if additional updates were performed.

If your problem occurs at Web server start-up, gather the following information with the WebSphere Application Server plug-in loaded:
  1. Full plug-in trace (LogLevel="Trace" in the plugin-cfg.xml file). The name of the plug-in trace is defined in the Name element of the plugin-cfg.xml file. The default name for the plug-in trace is, http_plugin.log.

  2. Plug-in configuration file (plugin-cfg.xml).

  3. Web server configuration files:

    Web server File
    IBM HTTP Server and
    Apache V1.3 and V2.0
    http.conf plus all IBM HTTP Server and Apache configuration files that are loaded through includes in httpd.conf
    iPlanet magnus.conf and obj.conf
    IIS Screenshot of the ISAPI filters and Windows registry export
    Domino Screenshot of the DSAPI Section window and Windows registry export (for Domino on Windows, it does not apply for Domino on UNIX)

  4. GSKit version.

    Type the appropriate command to display the full GSKit version:

    For releases of IBM HTTP Server V1.3.12
    Windows /program files/ibm/gsk4/bin/gsk4ver.exe
    AIX /usr/opt/ibm/gskit/bin/gsk4ver
    Solaris /opt/ibm/gsk4/bin/gsk4ver
    HP-UX /opt/ibm/gsk4/bin/gsk4ver
    Linux /usr/local/ibm/gsk4/bin/gsk4ver
    For releases of IBM HTTP Server V1.3.19, V1.3.26, and V2.0.42
    Windows /program files/ibm/gsk5/bin/gsk5ver.exe
    AIX /usr/opt/ibm/gskkm/bin/gsk5ver
    Solaris /opt/ibm/gsk5/bin/gsk5ver
    HP-UX /opt/ibm/gsk5/bin/gsk5ver
    Linux /usr/local/ibm/gsk5/bin/gsk5ver
    For releases of IBM HTTP Server V2.0.47
    Windows /program files/ibm/gsk7/bin/gsk7ver.exe
    AIX /usr/opt/ibm/gskkm/bin/gsk7ver
    Solaris /opt/ibm/gsk7/bin/gsk7ver
    HP-UX /opt/ibm/gsk7/bin/gsk7ver
    Linux /usr/local/ibm/gsk7/bin/gsk7ver

  5. Web server logs (access and error logs).

  6. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to plug-in (remote) install problems, search the WebSphere Application Server support site.
 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Plug-in (remote) Install
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1165384
IBM Group: Software Group
Modified date: Feb 20, 2007