Hi,

OK, so there are two ways to call a WF procedure in version 8.1.05 now I might be just lucky these both work, but which call would be the "best practice" one? The scenario here is the WF is called from a bespoke java UI, and the SSO should handle any authentications. I might be missing session tokens as well, so any hints in what I am missing would be good.

/ibi_apps/WFServlet?IBIF_webapp=/ibi_apps&IBIMR_drill=IBFS,RUNFEX,IBIF_ex,true&IBIF_ex=IBFS:/WFC/Repository/POC/spoof/spoof.fex&CALDATE=32032017&VAR1=bofh&VAR2=666


/ibi_apps/run.bip?BIP_REQUEST_TYPE=BIP_RUN&BIP_folder=IBFS:/WFC/Repository/POC/spoof&BIP_item=spoof.fex&CALDATE=32032017&VAR1=bofh&VAR2=666

There are also portals, Java UI calling WF html pages and then directly fexes, oh and RC schedules run off the portals as well as webservices... so a bit of a mixed bag and I'd prefer to make things as much streamlined as possible.

This message has been edited. Last edited by: FP Mod Chuck,

From what I've seen, run.bip has always happened from a portal, and WFServlet from drills and calls from HTML composer.

quote:

...which call would be the "best practice" one?...

Back when we upgraded from 7.7.x to 8.0.x, Information Builders recommended that we begin to use the 'WebFOCUS RESTful Web Service' to run reports from our bespoke web applications, instead of WF servlet.

With WF RESTful, your servlet call example would look something like:

http://localhost:8080/ibi_apps/rs/ibfs/WFC/Repository/POC/spoof/spoof.fex?IBIRS_action=run&CALDATE=32032017&VAR1=bofh&VAR2=666

There is a IB manual on WF RESTful.

(I can send a Summit presentation on WF RESTful, if anyone would like to send me their email address via a PM. The presentation summarizes what is in the manual.)

Perhaps someone from IB will further comment on this topic?

This message has been edited. Last edited by: David Briars,

Thanks, I need to look into the webservices for RC scheduling... though now I ran that and it seems my report is 'restful' in a stuck "Loading" screen (the WFServlet works fine)... darn WebSphere...