'Input Array' option at InfoShere Information Server(IIS)

getsatish_gk · Post by **getsatish_gk** » Wed Apr 17, 2013 12:58 pm

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)

eostic · Post by **eostic** » Wed Apr 17, 2013 2:35 pm

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

getsatish_gk · Post by **getsatish_gk** » Wed Apr 17, 2013 3:09 pm

I can do it by using ISD input stage.. but this will make job to run always.
the requirement is to have job invoked 'on demand' externally.

OR are you asking to use ISD stage and let it reflect an array in the WSDL document and then remove it from the job?

eostic · Post by **eostic** » Wed Apr 17, 2013 3:39 pm

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

getsatish_gk · Post by **getsatish_gk** » Thu Apr 18, 2013 9:35 am

So, ISD input stage is a must required to have 'Input Array' option to appear while Grouping Arguments into Structure at InfoShere Information Server(IIS)?

wondering, why ETL job design can't impose IIS to have 'Input Array' at IIS

eostic · Post by **eostic** » Thu Apr 18, 2013 9:40 am

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

getsatish_gk · Post by **getsatish_gk** » Thu Apr 18, 2013 2:52 pm

Thanks a lot eostic... helped me to resolve this issue to an extent
played around the provider setting at IIS and able to accept array and run job only on demand (yet using ISD input stage)

eostic · Post by **eostic** » Thu Apr 18, 2013 7:43 pm

Congrats! ....that's not a "workaround" though.

. It really is an advanced use of ISD and its settings!

Ernie

chulett · Post by **chulett** » Thu Apr 18, 2013 9:15 pm

Resolved.