gLite R-GMA SERVICETOOL
This release contains the gLite R-GMA Servicetool module v. 5.1.0. The following sections provide additional information about the release content, the module dependencies, the know bugs and issues and a list of bugs closed since the previous release. For information about installing and using the gLite R-GMA Servicetool, please refer to the gLite Installation and User Guides.
The R-GMA servicetool supports now the publishing of additional parameters for each services. The newly added parameters are:
o List of VOs that this service is considered part of.
o List of service names that this service is associated with.
o List of extra parameters for the service.
In addition it is no longer necessary to specify the common set of parameters
o rgma.servicetool.status_interval
o rgma.servicetool.publish_interval
o rgma.servicetool.url_wsdl
o rgma.servicetool.url_semantics
for each servicetool instance in each servicetool instance if you want to use the default values. See section 2.2 for details.
The configuration of the module has changed. Please update your configuration if you upgrade from a previous version of the R-GMA servicetool.
The following configuration parameters have been added:
File: glite-rgma-servicetool.cfg.xml |
||
Parameter |
Default value |
Description |
Advanced Parameters |
||
The following parameters have been added to the file to be used as default parameter if they are not defined in an individual servicetool instance. |
||
rgma.servicetool.
|
60 |
How often to check and publish service status (running/not running). This parameter can be also specified separately per servicetool instance in your service configuration file. The value defined here is the fallback value if no value is defined in the individual servicetool instance. Example: 60 [Type: 'string'] [Unit: 'seconds'] |
rgma.servicetool.
|
3600 |
How often to publish the service details like endpoint, WSDL, URL. As this information is not changing so much, the interval can be lower than 'rgma.servicetool.status_interval' to reduce the load for R-GMA and the amount of data that is archived. This parameter can be also specified separately per servicetool instance in your service configuration file. The value defined here is the fallback value if no value is defined in the individual servicetool instance. Example: 3600 [Type: 'integer'] [Unit: 'seconds'] |
rgma.servicetool.
|
not available |
URL of a WSDL document for the service. Put 'not available' if no wsdl url is available. This parameter can be also specified separately per servicetool instance in your service configuration file. The value defined here is the fallback value if no value is defined in the individual servicetool instance. Example:
http://example.rl.uk/service?WSDL |
rgma.servicetool.
|
not available |
URL of a document containing a detailed description of the service and how it should be used. Put 'not available' if not url is available. This parameter can be also specified separately per servicetool instance in your service configuration file. The value defined here is the fallback value if no value is defined in the individual servicetool instance. Example: http://example.rl.ac.uk/service/semantics.html [Type: 'string'] |
The following parameters are new configuration parameters. They have been also added to the file to be used as default parameter if they are not defined in an individual servicetool instance. |
||
rgma.servicetool.vo
|
|
List of VOs that this service is considered part of. This parameter can be also specified separately per servicetool instance in your service configuration file. Optional parameter - you can specify one or several or it can be left empty or be removed. The value defined here is the fallback value if no value is defined in the individual servicetool instance. Example: EGEE [Type: 'string'] |
rgma.servicetool.
|
|
List of service names that this service is associated with. This parameter can be also specified separately per servicetool instance in your service configuration file. The value defined here is the fallback value if no value is defined in the individual servicetool instance. Optional parameter - you can specify one or several or it can be left empty or be removed. Example: YOURhostname_YOURvoname_YOURservicetype [Type: 'string']"> |
rgma.servicetool.param
|
|
List of extra parameters for the service to be published. The structure for each entry is key=value. This parameter can be also specified separately per servicetool instance in your service configuration file. The value defined here is the fallback value if no value is defined in the individual servicetool instance. Optional parameter - you can specify one or several or it can be left empty or be removed. Example: yourkey=yourvalue [Type: 'string'] |
The following table contains the values that are newly supported by the R-GMA servicetool for the servicetool instances in the service specific configuration files. These values can be added to each servicetool instance, they are however optional.
File: glite-rgma-servicetool-serviceName.cfg.xml |
||
Parameter |
Default value |
Description |
Advanced Parameters |
|
|
rgma.servicetool.vo
|
|
List of VOs that this service is considered part of. Optional parameter - you can specify one or several or it can be left empty or be removed. Example: EGEE [Type: 'string'] |
rgma.servicetool.
|
|
List of service names that this service is associated with. Optional parameter - you can specify one or several or it can be left empty or be removed. Example: YOURhostname_YOURvoname_YOURservicetype [Type: 'string']"> |
rgma.servicetool.param
|
|
List of extra parameters for the service to be published. The structure for each entry is key=value. Optional parameter - you can specify one or several or it can be left empty or be removed. Example: yourkey=yourvalue [Type: 'string'] |
No parameter has been removed in this release.
No parameter has changed the name or the value in this release.
This release introduces a set of bug fixes (for the full list of fixed bug see sections 5.2 and 5.3):
· org.glite.rgma.stubs-servlet-java
The gLite R-GMA Servicetool module installs/uses the following set of gLite deployment modules:
Please see the corresponding release notes of these modules for details.
The gLite R-GMA Servicetool module is composed of the following gLite components (list includes the gLite components of the other used gLite deployment modules in section 3.1):
Component name |
Description |
Version |
File |
glite-config |
gLite configuration scripts |
1.4.2 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-config-1.4.2-1.noarch.rpm |
glite-rgma-api-java |
Java API for R-GMA |
4.1.5 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-api-java-4.1.5-1.noarch.rpm |
glite-rgma-base |
R-GMA basic configuration and documentation |
4.1.19 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-base-4.1.19-1.noarch.rpm |
glite-rgma-common-config |
gLite rgma common configuration items installation |
5.0.0 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-common-config-5.0.0-1.noarch.rpm |
glite-rgma-servicetool |
R-GMA service tool |
4.1.19 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-servicetool-4.1.19-3.noarch.rpm |
glite-rgma-servicetool-config |
gLite R-GMA servicetool installation |
5.1.0 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-servicetool-config-5.1.0-1.noarch.rpm |
glite-rgma-stubs-servlet-java |
Java client implementation stubs for R-GMA |
4.1.13 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-stubs-servlet-java-4.1.13-1.noarch.rpm |
glite-security-trustmanager |
The java certificate path checkin for proxy certs in SSL with plugins for tomcat and axis. |
1.7.3 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-trustmanager-1.7.3-1.noarch.rpm |
glite-security-util-java |
The java utilities library for security |
1.1.2 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-util-java-1.1.2-2.noarch.rpm |
glite-security-utils-config |
gLite Security Utilities configuration files |
1.0.4 |
../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-utils-config-1.0.4-1.noarch.rpm |
The gLite R-GMA Servicetool module has the following dependencies:
Component name |
Version |
RPM file name |
gLite-essentials-java |
1.2.0 |
For the list of dependencies of the gLite sub-deployment modules, listed in section 3.1, please see the release notes of the corresponding modules for their list of dependencies.
This release has no known bugs and issues. Bug numbers refer to the gLite Bug Tracking system database hosted on the CERN Savannah system at https://savannah.cern.ch/bugs/?group=jra1mdw.
This release fixes the following bugs and issues. Bug numbers refer to the gLite Bug Tracking system database hosted on the CERN Savannah system at https://savannah.cern.ch/bugs/?group=jra1mdw
Bug number |
Description |
ConnectionTimeOutExceptions are passed back to the producer client |
|
Bad location of the wsdl file as required by glite-rgma-servicetool-serviceName.cfg.xml ? |
|