Activity - deliverToGDT

Activity Type: Delivery

Description

Deliver data to another OGSA-DAI service which implements OGSA-DAI data transport operations via invocation of its PutFully or PutBlock operations.

This activity outputs data to a corresponding inputStream activity in the other service.

Connecting deliverToGDT and inputStream activities

Example

<deliverToGDT name="delivery">
  <fromLocal from="dataSource"/>
  <toGDT streamId="sessionID:inputStreamID" resourceName="MySQLResource"
    mode="full">
    http://host:port/path/DataService
  </toGDT>
</deliverToGDT>

Specification

Element deliverToGDT:

• Attribute name - unique name for the activity within the scope of a request.
• fromLocal (required) - input stream.
  • Attribute from - name of an input stream providing the data to deliver.
• Element toGDT (required) - the URL of an OGSA-DAI service which implements the data transport operations and to which the data is to be delivered.
  • Attribute serviceType (optional) - type of the target service.
    • wsi - the target service is OGSA-DAI WSI compliant.
    • wsrf - the target service is OGSA-DAI WSRF compliant.
    • unknown - the type of the target service is unknown. When the activity is run it will contact the service to get its WSDL and so determine the type of the service from that.
    • If omitted the value defaults to unknown.
  • Attribute resourceName - name of a data service resource exposed by a data service and which is to receive the data.
  • Attribute streamId (required) - a session ID and the name of an inputStream activity on the destination service that is running under that session.
    • The session name and stream name are expected to be conjoined with a colon (:).
  • Attribute mode (required) - the data transfer mode. One of:
    • block - the data is transferred in blocks.
    • full - all the data is transferred in one go.

Specifying message level security (WSRF version only)

Message level security can be used to secure the communcation between the two OGSA-DAI servers. To specify that message level security is to be used an additional GSISecureConversation element should be included in the activity specification. For example:

<deliverToGDT name="delivery">
  <fromLocal from="dataSource"/>
  <toGDT streamId="sessionID:inputStreamID" resourceName="MySQLResource"
    mode="full">
    http://host:port/path/DataService
  </toGDT>
  <GSISecureConversation
    protectionLevel="integrity" 
    authorization="host" />
</deliverToGDT>

The protectionLevel attribute specifies the GSI protection level to be used. It can take the following values:

• privacy - Use GSI Secure Conversation with message privacy . Third-parties will be unable to read or alter the data.
• integrity - Use GSI Secure Conversation with message integrity. Third-parties will be able to read the data but be unable to alter the data

The authorization attribute specifies the type of authorization the activity should peform on the remote service. It can take the following values:

• host - host authorization.
• self - self authorization.
• none - no authorization.
• Any other string - identity authorization will be used. This will require the remote server's identity to be identical to that specified in this attribute

When using message level security the client's credential will be used when the activity accesses the remote OGSA-DAI service. It is therefore essential that the client's credential is delegated to the activity. A delegation value of 'limited' or 'full' must threfore be specified in the client's security descriptor.

Input and Output Types

• Input: fromLocal - any Java object.
• Outputs: none

Data Resource Accessor

This activity can operate with any data resource accessor.

XML Schema

OGSA-DAI/schema/ogsadai/xsd/activities/deliver_to_gdt.xsd

Class

uk.org.ogsadai.activity.delivery.wsrf.DeliverToGDTActivity

Client Toolkit Class

uk.org.ogsadai.client.toolkit.activity.delivery.DeliverToDT