|
|||||||||||||||||||||||||||||||||||||||||||||
![]()
|
GT3.2 Beta Information Services (MDS) Release NotesThis 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 FeaturesThe 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 changesThe 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 loggingPerformance 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 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:
org.globus.ogsa.impl.core.registry.RegistryPublishProvider
<parameter name="registrationConfig" value="etc/registration_config.xml" />
Example Registration Configuration File
<?xml version="1.0" encoding="UTF-8" ?> |
||||||||||||||||||||||||||||||||||||||||||||
about globus | grid research | globus toolkit | software development Last modified: 02/05/04 4:04pm. Comments? webmaster@globus.org Globus Project and Globus Toolkit are trademarks held by the University of Chicago |