'Input Array' option at InfoShere Information Server(IIS)
-
- Participant
- Posts: 104
- Joined: Sat Dec 24, 2005 1:26 am
- Location: Bengaluru
'Input Array' option at InfoShere Information Server(IIS)
Hi all,
How to have 'Input Array' option to appear while Grouping Arguments into Structure at InfoShere Information Server(IIS) -- exposing job as web service
Datastage job is to run on Demand by external world and pass the array of data into Datastage. ie.,( use ISD output stage)
How to have 'Input Array' option to appear while Grouping Arguments into Structure at InfoShere Information Server(IIS) -- exposing job as web service
Datastage job is to run on Demand by external world and pass the array of data into Datastage. ie.,( use ISD output stage)
The best way to do this is to instead set this up as an "always on" job that uses ISD input Stage....and then group that into an array. The WSDL will reflect an array and ISD at run time will accept multiple rows being input.
Ernie
Ernie
Ernie Ostic
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
-
- Participant
- Posts: 104
- Joined: Sat Dec 24, 2005 1:26 am
- Location: Bengaluru
play with setting minimum instances to zero and a fairly small timeout value....then it's theoretically always on, but starts with the first incoming request, and if never called again, will eventually shut down that instance.
Ernie
Ernie
Ernie Ostic
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
-
- Participant
- Posts: 104
- Joined: Sat Dec 24, 2005 1:26 am
- Location: Bengaluru
That's how it was designed...and probably because there isn't much need for it.
An always on service is infinitely faster (milliseconds as opposed to seconds) than a simplistic Job that only has ISDOutput.
Further, an "always on" job is shared by anyone and everyone that invokes it......and the overhead of leaving it on is usually far less and far cheaper than having "100's of jobs launched" each time someone connects.
So in the end, it's always better to go with an always on scenario, for response time and overall resource consumption. There are exceptions, and that is what min=0 is for.
Ernie
An always on service is infinitely faster (milliseconds as opposed to seconds) than a simplistic Job that only has ISDOutput.
Further, an "always on" job is shared by anyone and everyone that invokes it......and the overhead of leaving it on is usually far less and far cheaper than having "100's of jobs launched" each time someone connects.
So in the end, it's always better to go with an always on scenario, for response time and overall resource consumption. There are exceptions, and that is what min=0 is for.
Ernie
Ernie Ostic
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
-
- Participant
- Posts: 104
- Joined: Sat Dec 24, 2005 1:26 am
- Location: Bengaluru
Congrats! ....that's not a "workaround" though. . It really is an advanced use of ISD and its settings!
Ernie
Ernie
Ernie Ostic
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>