gLite Data Management Single Catalog (Fireman)
This release contains the gLite Data Management Single Catalog (Fireman) for MySQL module v. 2.0.2. 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 Data Management Single Catalog, please refer to the gLite Installation and User Guides.
This release doesn’t contain any functional change, but the database schema has changed. If the service is upgraded from gLite 1.3 to 1.4, the --db_force_create option of the glite-data-single-catalog-config.py script must be used when configuring the service for the first time. All existing data is destroyed. The service doesn’t provide ways of migrating an existing database to the new schema.
The following new parameters have been added to the glite-data-single-catalog.cfg.xml file:
Parameter name |
Default value |
Description |
The following parameters have been changed in the glite-io-client.cfg.xml file:
Parameter name |
Old value |
New value |
Description |
catalog-service-fr-mysql.DBURL |
jdbc:mysql://localhost:3306/${catalog-service-fr-mysql.DBNAME}?zeroDateTimeBehavior=convertToNull |
jdbc:mysql://localhost:3306/${catalog-service-fr-mysql.DBNAME} |
URL of the database |
rgma.servicetool.service_type (FiremanCatalog servicetool instance) |
org.glite.data.FiremanCatalog |
org.glite. FiremanCatalog |
The service type. This should be uniquely defined for each service type. The naming convention is org.glite.subsystemname.componentname for gLite components and corresponding names for external components. |
rgma.servicetool.service_type (SEIndex servicetool instance) |
org.glite.data.SEIndex |
org.glite. SEIndex |
The service type. This should be uniquely defined for each service type. The naming convention is org.glite.subsystemname.componentname for gLite components and corresponding names for external components. |
The following parameters have been removed from the glite-io-client.cfg.xml file:
Parameter name |
Comment |
db.force.create |
This is not anymore a parameter in the config file, but a command line option of the config script: --db_force_create |
The gLite I/O WN module includes the following sub-modules:
- gLite Security Utilities
- gLite R-GMA Servicetool
The sub-modules are automatically installed with the Fireman module unless differently specified. For more information about these sub-modules please refer to the specific release notes and installation instructions.
The gLite Data Management Single Catalog v. 2.0.2 is composed of the following gLite components:
Component name |
Description |
Version |
File |
glite-config |
gLite configuration scripts |
1.4.5 |
|
glite-data-catalog-service-fr-mysql |
gLite Data Catalog Service (MySQL version) |
1.4.2 |
|
glite-data-common |
common files for gLite Data Management web-services |
1.3.0 |
|
glite-data-single-catalog-config |
gLite Fireman Catalog for MySQL node configuration files |
2.0.2 |
|
glite-rgma-api-java |
Java API for R-GMA |
4.1.5 |
|
glite-rgma-base |
R-GMA basic configuration and documentation |
4.1.19 |
|
glite-rgma-common-config |
gLite rgma common configuration items installation |
5.0.0 |
|
glite-rgma-servicetool |
R-GMA service tool |
4.1.19 |
|
glite-rgma-servicetool-config |
gLite R-GMA servicetool installation |
5.1.0 |
|
glite-rgma-stubs-servlet-java |
Java client implementation stubs for R-GMA |
4.1.13 |
|
glite-security-trustmanager |
The java certificate path checkin for proxy certs in SSL with plugins for tomcat and axis. |
1.7.3 |
|
glite-security-util-java |
The java utilities library for security |
1.1.2 |
|
glite-security-utils-config |
gLite Security Utilities configuration files |
1.0.6 |
The gLite Data Management Single Catalog module has the following dependencies:
Component name |
Version |
RPM file name |
MySQL-server |
4.1.11 |
|
MySQL-client |
4.1.11 |
|
Tomcat |
5.0.28 |
|
Java SDK/JRE |
1.4.2 |
http://java.sun.com/j2se/1.4.2/download.html |
This
release has the following 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
.
Known open bugs:
The following bugs have been fixed in this or previous releases, but not yet tested:
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