FAQ
Site Index
Contact Us

About
Support
Download
Documentation
Advisories
CoG Kits
Bugzilla
License

Toolkit
Components
Core
Security
Data
Management
Resource
Management
Information
Services

Activities
News & Archives
Meetings

Site Search:

GT3.2 Beta Information Services (MDS) Release Notes

This 3.2 Beta release of the GT Information Services components contains bug fixes, performance and stability improvements, and a few new features.  There has also been considerable reworking of Service Data Aggregation concepts into a component-based API to allow for a more flexible programming model capable of handling multiple data aggregation strategies.  As a result of these changes, the Index Service (and other services that incorporate the Aggregator components)  can now aggregate service data from other services by using the ServiceGroup port type and IndexingServiceGroup operation provider. 

Service Data aggregated in this fashion will be stored in the EntryContent field of the ServiceGroupEntry that represents the registered service.  The default ServiceData aggregation format (an array of SDE values) is still available, and either storage mode (or both) may be enabled by the service administrator via the server-config.wsdd file.

For a complete list of changes since 3.2 Alpha, visit here.

New Index Service Features

The Index service now publishes the contents of the index-service-config.xml as SDEs.  Default executed providers are published in the SDE QName: http://www.globus.org/namespaces/2003/04/service_data_provider_execution}defaultProviderExecution.  Default aggregations are published in the SDE QName: {http://www.globus.org/namespaces/2003/09/data_aggregator}defaultAggregation. 

The  following options (defaults shown) are now supported in server-config.wsdd:

<parameter name="aggregateServiceGroupEntryContent" value="true"/>

This parameter enables storing aggregated Service Data as ServiceGroupEntryContent.

<parameter name="aggregateServiceData" value="true"/>

This parameter enables storing aggregated Service Data as an array of Service Data values.

<parameter name="messageGateway" value="false"/>

This parameter enables the relay of incoming messages to any listening subscribers of the SDE named "MessageGateway". This can be used to remotely monitor the messages received by the Index service.

<parameter name="minNotificationInterval" value="5"/>

This parameter limits outbound message traffic by the specified number of seconds.  For any given subscription, messages will be sent no faster than the interval specified.  Subscribing services may override this setting on a per-subscription basis by specifying a minInterval in the subscription request.  This parameter may also be removed from server-config.wsdd if message delivery rate limiting is not desired.

Aggregator changes

The DataAggregationType schema has been changed to support subscription of multiple Service Data names, and more flexible source and sink addressing. Please see the data_aggregation_port_type.gwsdl for the schema, and etc/index-service-config.xml file for and example of the serialized form. 

API refactoring into Source/Sink model for flexibility.

Additional logging

Performance logging and additional diagnostic messages have been added to key information services components.  Enabling the following entries in log4j.properties to monitor performance and service events:

#log4j.category.org.globus.ogsa.impl.base.aggregator.DataAggregationManager=INFO
#log4j.category.org.globus.ogsa.impl.base.aggregator.DataAggregationManager.performance=DEBUG
#log4j.category.org.globus.ogsa.impl.core.service.ServiceDataNameUpdateEvaluator=DEBUG
#log4j.category.org.globus.ogsa.impl.core.service.ServiceDataNameUpdateEvaluator.performance=DEBUG
#log4j.category.org.globus.ogsa.impl.base.providers.servicedata.ServiceDataProviderManager=DEBUG
#log4j.category.org.globus.ogsa.impl.base.providers.servicedata.ServiceDataProviderExecutionTask.performance=DEBUG
#log4j.category.org.globus.ogsa.impl.base.index.IndexingServiceGroupRegistrationProvider.performance=DEBUG

Registering any grid service to the GT3.2 Index Service (RegistryPublishProvider)

Any GT3.2 service can be registered to a GT3.2 index service using the core RegistryPublishProvider. The RegistryPublishProvider should be configured in the WSDD of each resource service (for example the MMJFS) by the administrators of those services.

Note: The administrator of the index service does not need to take action in order for a new resource service to register.

Before you begin, you'll need:

  • A working resource service (for example, MMJFS). You will need permissions to edit the configuration of the service (server-config.wsdd, etc).
     
  • An index service. You will not need permission to edit the configuration;, however you will need to know the GSH of the Index service.
  1. Make an XML configuration file for the registration in (for example) $GLOBUS_LOCATION/etc/registration_config.xml

    An example is included below.

    Edit the fields as appropriate -- most importantly, edit the registry parameter to refer to the index service you want to register with.
     
  2. Edit the resource service's deployment descriptor in server-config.wsdd:

  3.  
    • Add the RegistryPublishProvider operation provider:

    •  
      • Load server-config.wsdd into a text editor
         
      • Find the <service> definition for the resource service
         
      • Find the operationProviders parameter for that service
         
      • Add the following string to the end of the operationProviders parameter. Note that this is a space-separated (not comma-separated) field:

      org.globus.ogsa.impl.core.registry.RegistryPublishProvider

       

    • Add a new parameter to the resource service's deployment descriptor:
    • <parameter name="registrationConfig" value="etc/registration_config.xml" />

Example Registration Configuration File

<?xml version="1.0" encoding="UTF-8" ?>
<serviceConfiguration
xmlns:ogsi="http://www.gridforum.org/namespaces/2003/03/OGSI"
xmlns:aggr="http://www.globus.org/namespaces/2003/09/data_aggregator"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<registrations>
  <registration
  registry="http://examplehost.isi.edu:8080/ogsa/services/base/index/IndexService"
  keepalive="true"
  lifetime="1200"
  remove="true">
  <aggr:DataAggregation>
    <ogsi:params>
     <aggr:AggregationSubscription>
      <ogsi:serviceDataNames>
      <ogsi:name xmlns:ce="http://glue.base.ogsa.globus.org/ce/1.1">ce:Host</ogsi:name>
      </ogsi:serviceDataNames>
      <aggr:lifetime>60000</aggr:lifetime>
     </aggr:AggregationSubscription>
    </ogsi:params>
   </aggr:DataAggregation>
   </registration>
 </registrations>
</serviceConfiguration>