Abstract
This provider connects to a web server. If the connection can
successful be made the server is registered as alive, otherwise it is
down.
This provider is an execution aggregator provider. These providers
are quite useful as is and additionally serve as an example of how to
create others. The perl script and configuration file can be modified
to the users liking once installed.
This provider has a perl script and an xml configuration file. The
perl script is used to obtain information and formated the information
into xml output. The output is written to stdout where it is gathered
and put into the Index Service. The xml file is of a common format
that is explained here.
After installing the package the xml configuration files will be
copied to
$GLOBUS_LOCATION/etc/globus_wsrf_mds_index/default_providers/ where
the DefaultIndexService will find them and use them to register the
provider.
You can download a PDF version of Web Check Information Provider information here.
Table of Contents
Table of Contents
This provider connects to a web server. If the connection can
successful be made the server is registered as alive, otherwise it is
down.
This provider is an execution aggregator provider. These providers
are quite useful as is and additionally serve as an example of how to
create others. The perl script and configuration file can be modified
to the users liking once installed.
This provider has a perl script and an xml configuration file. The
perl script is used to obtain information and formated the information
into xml output. The output is written to stdout where it is gathered
and put into the Index Service. The xml file is of a common format
that is explained here.
After installing the package the xml configuration files will be
copied to
$GLOBUS_LOCATION/etc/globus_wsrf_mds_index/default_providers/ where
the DefaultIndexService will find them and use them to register the
provider.
Features new in release 4.2.0:
This provider determines if a Web (HTTP) server is online.
This information provider depends on the following GT components:
This information provider depends on the following 3rd party software:
- A working Perl installation
Tested Platforms for this information provider:
- N/A
Tested containers for this information provider
- Java WS Core container
See Chapter 2, GT 4.2.0: Web Check Information Provider Reference for more information about this information provider.
Table of Contents
This provider connects to a web server. If the connection can
successful be made the server is registered as alive, otherwise it is
down.
This provider is an execution aggregator provider. These providers
are quite useful as is and additionally serve as an example of how to
create others. The perl script and configuration file can be modified
to the users liking once installed.
This provider has a perl script and an xml configuration file. The
perl script is used to obtain information and formated the information
into xml output. The output is written to stdout where it is gathered
and put into the Index Service. The xml file is of a common format
that is explained here.
After installing the package the xml configuration files will be
copied to
$GLOBUS_LOCATION/etc/globus_wsrf_mds_index/default_providers/ where
the DefaultIndexService will find them and use them to register the
provider.
This is an execution aggregator source based information provider.
The following configuration is required for this information provider:
In order to grant permission to the installed perl scripts the user must edit the file: $GLOBUS_LOCATION/etc/globus_wsrf_mds_index/jndi-config.xml such that the tags:
<parameter> <name>executableMappings</name> <value> aggr-test=aggregator-exec-test.sh, pingexec=example-ping-exec </value> </parameter>includes the new provider. For example:
<parameter> <name>executableMappings</name> <value> web-info=web-check.pl </value> </parameter>This provider connects to a web server. If the connection can successful be made the server is registered as alive, otherwise it is down. To change what server is monitored edit the tag:
$GLOBUS_LOCATION/etc/globus_wsrf_mds_index/default_providers/web-info-reg.xml
and change the line:
<RegistrantEPR xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing" xmlns:agg="http://mds.globus.org/aggregator/types"> <wsa:Address>http://www.SITE.COM</wsa:Address> </RegistrantEPR>from "http://www.SITE.COM" to the webserver of your choice.
Data appears as part of the ServiceGroupEntry RP
General security considerations associated with the container and all MDS services apply. See: Aggregator Framework.
Additionally the user should consider that publishing system specific information as is the intention of this provider can have security ramifications.
By default, the aggregator sources do not use authentication credentials -- they retrieve information using anonymous SSL authentication or no authentication at all, and thus retrieve only publicly-available information. If a user or administrator changes that configuration so that a service's aggregator source uses credentials to acquire non-privileged data, then that user or administrator must configure the service's aggregator sink to limit access to authorized users.