How to get WebSphere Application Server V3.x snoop servlet running

Technote (FAQ)
Problem
Verifying that snoop servlet can be served confirms a successful WebSphereŽ Application Server installation and configuration.
Solution
To get Snoop running for WebSphere Application Server V3.02.x and V3.5.x
  1. Make sure that the Web server (HTTP, Netscape Enterprise, and so forth) is running.

  2. Make sure that the plug-in for the Web server is installed. This is done as part of the WebSphere installation (custom installation, select plug-in(s) on the right side of the screen).

    For example, check for the following three lines in the httpd.conf file with Apache or IBM HTTP Server:

    LoadModule ibm_app_server_module /WebSphere/AppServer/bin/mod_ibm_app_server.dll
    Alias /IBMWebAS/ "C:/WebSphere/AppServer/web/"
    NcfAppServerConfig BootFile C:\WEBSPH~1\APPSER~1
    \properties\bootstrap.properties ServerTokens Full


    Check obj.conf for iPlanet and Netscape Web servers.

    If you installed a Web server after installing WebSphere, you must reinstall the plug-in. To do this, start the WebSphere installation and do not select to upgrade (it looks like you are doing a new WebSphere installation). Instead, select the custom installation option, then deselect everything but the plug-in you want).

    If the lines are in the plug-in configuration file, make sure that the trace.log.xxx file, in the WebSphere logs directory, is created and written to after the Web server starts. Examples of file names for plug-in trace log:
      1. IBM HTTP Server: trace.log.ibmhttp.* (where * is the date-time stamp)
      2. Apache: trace.log.apache.
      3. *IIS: trace.log.iis.
      4. *Netscape/iPlanet: trace.log.ns.*
  3. Make sure that the WebSphere Default Server is running (from the administrative console, select the topology tab, then select the default server; the button at the top should be red). If the server is not running, the button is green; click the green button to start the default server.

  4. If you selected to install the sample configuration so that install.initial.config property is set to true in the admin.config file, when you start the administrative server, the sample configuration is created, which creates the default application server, container and servlet engine.

  5. If you did not install the sample configuration, you will not have a default server:
    1. Stop WebSphere (including closing the administrative console).
    2. Edit admin.config in the \WebSphere\AppServer\bin directory.
    3. Change install.initial.config=false to install.initial.config=true.
    4. Restart WebSphere and the administrative console to verify that the default server is installed in the node.

  6. Make sure that the default_app classpath points to where snoop resides; by default it is in \WebSphere\AppServer\hosts\default_host\default_app\servlets. To see it, select default_app under default server > servletEngine, and under the Advanced tab on the right side of the screen look at classpath.

  7. Make sure you are invoking snoop correctly. The default servlet Web path for snoop is default_host/servlet/snoop or default_host/servlet/snoop2. To check it, select snoop servlet under default server > servletEngine > default_app, and under the General tab on the right side of the screen, look at Servlet Web Path in use. In a browser, type:

    http://<hostname>/servlet/snoop
    • where hostname is "localhost", the IP address, or the actual hostname
    • ping <hostname> should return a valid IP address

  8. After the IBM WS AdminServer service restarts, start the administrative console, then start the Default Server:

    Click Topology page > expand WebSphere AdminDomain > expand node > select Default Server > click green circle icon.

  9. After the Default Sever starts, enter the following URL in your browser to invoke the servlets:
  10. http://<Host name of the Default Server>/servlet/snoop


WAS 3.5 Solaris
  1. Ping snoop from the administrative console. Does it run?

  2. Pull up your properties files located in the Temp directory under AppServer, and look for: queues.properties.

    Note: this file tells which port and type the Web server (in this case iPlanet) will use.

  3. Select WebSphere Administrative Console > Default Server >
    1. Highlight Default Servlet Engine.
    2. Click the Advanced tab.
    3. Click on setting:

      What is the Transport type? On Solaris it can not be Local Pipes.
      1. Change your port and type to the same in queues.properties file (or vice versa).
      2. Select Apply > Regen Plugin Co, and regenerate the plug-in.
      3. Stop Websphere, then iPlanet, restart iPlanet, then restart Websphere, including the Default Server.
      4. Try http://localhost/servlet/snoop.

  4. Confirm in the configuration that the default domain was incorrect. In some cases internal DNS issues prevent the plug-in from accurately completing the servlet requests; for example, the local hosts file being searched after the domain name server:
    • In Solaris, check /etc/nsswitch.conf to find out how hostnames are resolved
    • In AIX, check /etc/netsvc.conf to find out how hostnames are resolved











Document Information

Product categories: Software, Application Servers, Distribut, ed Application & Web Servers, WebSphere Application Server, Install
Operating system(s): Multi-Platform
Software version: 3.0, 3.5
Software edition: Standard, Advanced
Reference #: 1044471
IBM Group: Software Group
Modified date: 2004-11-15