SQL Server Data Services and Amazon S3 support

Aug 22, 2010 at 9:13 PM

Hello, I have a question about the data access layer.

In Trident 1.0 Build 1397.1 there is a possibility to enter an OPC File or Web Service Broker in the "Data Store Connection Manager".

Suddenly I couldn't find Information about these features. In the paper "The Trident Scientific Workflow Workbench" by Roger Barga, Jared Jackson et al. is mentioned, that Trident supports XML store, SQL Server Data Services (SSDS), and Amazon S3 (http://aws.amazon.com/de/s3).

Are the Connections to OPC File and Web Service Broker used to use an XML File, Amazon S3 and SSDS as Registry?

Thanks, Alex

 

Aug 23, 2010 at 5:15 PM

Hi Alex,

While migrating Trident from .net framework 3.5 to .net framework 4.0, we did not migrate Web service broker provider due to technical issues. But the OPC provider is still available in Trident 1.2.1 build.

<< Are the Connections to OPC File and Web Service Broker used to use an XML File, Amazon S3 and SSDS as Registry?>>

No providers are related to each other from Trident point of view. They should have their own implementation and access details. But providers themselves can be designed in such a way that they are related to other providers.

 For example

1.       Web service broker is a wrapper which is used to expose the data layer as the WCF web service. The data layer again can be configured to access either the SSDS/Amazon S3/ XML Store.

2.       OPC provider is not as usual providers, but it is only used to create and import the Trident packages(.twp files).

 Please let us know if this answered your questions.

Thanks,
Trident Support Team.

Aug 25, 2010 at 6:50 AM
Edited Aug 25, 2010 at 6:51 AM


Hi Alex,

Can you please let us know if our reply answered you queries?

Thanks,
Trident Support Team.

 

Aug 25, 2010 at 8:29 AM

Sorry for the late reply,

So in order to use Amazon S3 and SSDS, you have to implement a Service Broker, which would map queries from Trident to Amazon S3 or SSDS operations? Is this already implemented? And can you use it as a primary Registry or do you need the Microsoft SQL Server anyway?

Thanks, Alex

 

Aug 26, 2010 at 5:12 AM

Hi Alex,

Please find answers to your questions below.

 <<So in order to use Amazon S3 and SSDS, you have to implement a Service Broker, which would map queries from Trident to Amazon S3 or SSDS operations?>>
No. We need to implement a separate registry provider for both Amazon S3 and SSDS.

<<Is this already implemented?>>
In latest version of Trident these providers are not implemented.

<<can you use it as a primary Registry or do you need the Microsoft SQL Server anyway?>>
Once you have implemented these providers you can use it as the primary registry.

Please let us know if you need any other information.
Thanks,
Trident Support Team

Aug 26, 2010 at 7:57 AM

Hi,

Thank you for your help it's all clear now.

Thanks, Alex