WebService architecture for flexible SQL-WHERE condition
Posted: Fri Jan 08, 2010 2:38 pm
Hi,
I am looking for the best architecture or job design for following problem:
I have to create an RTI WebService to run a SQL statement against DB2. The service will get about 30 parameters which are potentially part of the WHERE condition - filtering the answer set.
The problem is now that I can get maybe only one filter criteria (so only one WHERE condition attribute) or 25 of them (or even 30) but I want only a single WebService for that.
Some guys suggested an always on WebService with an RTI Input and RTI-Output stage. Having this I have to have a multi-row lookup which is possible in an ODBC stage and I would habe all the thirty (theoretical possible) fields als lookup key. This would then need a way to kind of default the unsused filter fields...
Any ideas how this can be done in an optimal manner?
The alternative in my eyes is a WebService with only a TI-Output stage - so it would be more like batch mode and not "always on" - I know how to handle that one I think.
Any ideas and suggestions are welcome
Thanks in advance
Michael
I am looking for the best architecture or job design for following problem:
I have to create an RTI WebService to run a SQL statement against DB2. The service will get about 30 parameters which are potentially part of the WHERE condition - filtering the answer set.
The problem is now that I can get maybe only one filter criteria (so only one WHERE condition attribute) or 25 of them (or even 30) but I want only a single WebService for that.
Some guys suggested an always on WebService with an RTI Input and RTI-Output stage. Having this I have to have a multi-row lookup which is possible in an ODBC stage and I would habe all the thirty (theoretical possible) fields als lookup key. This would then need a way to kind of default the unsused filter fields...
Any ideas how this can be done in an optimal manner?
The alternative in my eyes is a WebService with only a TI-Output stage - so it would be more like batch mode and not "always on" - I know how to handle that one I think.
Any ideas and suggestions are welcome
Thanks in advance
Michael