Before you begin

1. Feature summary

Features new in release 4.1.3:

  • None

Other Supported Features

  • Extensible plugin interface to support various mechanisms to gather monitoring information and XSLT transforms.
  • Plugins to acquire monitoring information via resource property mechanisms.
  • Plugin to acquire XSLT transforms by reading from local files.

Deprecated Features

  • None

2. Tested platforms

Tested Platforms for WebMDS:

  • The WebMDS server has only been tested with Tomcat version 5.0.28; it has been tested on RedHat Linux (i386) and, to a lesser extent, on Windows XP.
  • On the client side, WebMDS should be accessible from any web browser on any platform.

2.1. Installing WebMDS on Windows

Although the WebMDS server is not officially supported on non-Unix platforms, and no Windows installer exists for WebMDS, it is possible to run WebMDS on Windows. The following instructions describe how to install WebMDS on a Windows platform.

  1. Install Tomcat and set your CATALINA_HOME environment variable to the directory into which Tomcat was installed.
  2. Install the Globus Java WS-Core distribution from the Globus Toolkit download page. Set your GLOBUS_LOCATION environment variable to the directory into which you installed Globus Java WS-Core
  3. Check the ws-mds distribution out of the Globus CVS repository, using the globus_4_0_branch tag.
  4. Install the servicegroup package:

    cd c:\wherever\ws-mds\servicegroup\schema
    ant deploy
    cd ..\source
    ant deploy
    

    where wherever is the directory into which you checked out the ws-mds sources.

  5. Install WebMDS:

    cd c:\wherever\ws-mds\webmds
    ant deploy
    
  6. Create the webmds context file (this tells Tomcat where to find WebMDS):

    %GLOBUS_LOCATION%\lib\webmds\bin\webmds-create-context-file %CATALINA_HOME%\conf\Catalina\localhost
    
  7. Restart Tomcat.

WebMDS can then be configured and used as described in the rest of the documentation: WebMDS.

3. Backward compatibility summary

Protocol changes since GT version 4.0.5:

  • None

API changes since GT version 4.0.5:

  • None

Exception changes since GT version 4.0.5:

  • None

Schema changes since GT version 4.0.5:

  • None

4. Technology dependencies

WebMDS depends on the following GT components:

  • Java WS Core

WebMDS depends on the following 3rd party software:

5. Security considerations

By default, the WebMDS plugins distributed as part of the Toolkit do not use authentication credentials -- they retrieve information using anonymous SSL authentication or no authentication at all, and thus retrieve only publicly-available information.

The ResourcePropertyNodeSource and ResourcePropertyQueryNodeSource plugins can be configured either to allow users to specify what resources they want to query or to only allow users to query resources pre-configured by the web administrator. The standard WebMDS deployment allows users to specify the resources they want to query; to disallow this (for example, to ensure that people don't use your site's bandwidth to view information about some other site's services), remove the files $GLOBUS_LOCATION/lib/webmds/conf/openEndedRP and $GLOBUS_LOCATION/lib/webmds/conf/openEndedQuery.