RTI package
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 36
- Joined: Mon Mar 27, 2006 12:23 am
- Location: Chennai
RTI package
whats is RTI package .what is its usage.
The 'RTI package' no longer exists, it is now known as the 'SOA Edition'. RTI stood for Real Time Interface and SOA allows jobs to be deployed as web services and run in 'real time'. There's more to it than that, but there's the Executive Summary. ![Wink :wink:](./images/smilies/icon_wink.gif)
![Wink :wink:](./images/smilies/icon_wink.gif)
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Pardon my ignorance. I'm searching to see how this whole picture fits together. We have the Datastage 8.0.1 Server Edition installed. I'm reading in many places that I can expose my DS jobs in a web service, which would be brilliant for for requirements. I'm searching through the console and documentation and I'm really struggling to come close to a solution.chulett wrote:The 'RTI package' no longer exists, it is now known as the 'SOA Edition'. RTI stood for Real Time Interface and SOA allows jobs to be deployed as web services and run in 'real time'. There's more to it than that, but there's the Executive Summary.
1) Do I need extra software or another edition of DS?
2) if not, where and how do I expose the DS jobs to a web service?
~The simpliest solutions are always the best~
~Trick is to understand the complexity to implement simplicity~
~Trick is to understand the complexity to implement simplicity~
Thanks for the advice. That really helped for future development.
The WISD allows your jobs to accept web service posts and returns data.
However, what about my current jobs that I want to just be able to execute when ever necessary? i.e. expose the jobs to a web service where you can just execute them. And once successful continue. with the rest of the application.
The WISD allows your jobs to accept web service posts and returns data.
However, what about my current jobs that I want to just be able to execute when ever necessary? i.e. expose the jobs to a web service where you can just execute them. And once successful continue. with the rest of the application.
~The simpliest solutions are always the best~
~Trick is to understand the complexity to implement simplicity~
~Trick is to understand the complexity to implement simplicity~
AFAIK, both sets of functionality should be there "out of the box" - for jobs to access web services and to expose a job as a service. The "RTI Input" and "RTU Output" stages are used for that, but for all I know they have new names as well.
Maybe Ernie will wander in here and add some Words of Wisdom on the subject.
Maybe Ernie will wander in here and add some Words of Wisdom on the subject.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers