The Future of Query As A Web Service (Qaaws)

[Former Member]

We are looking to evaluate various solutions to distribute data throughout the enterprise. One of which is SAP Query As A Web Service.

During our research, we find out that the Query As A Web Service (Qaaws) Designer only sees UNV universes (note 1579730). The only way to create a web service using UNX universes is to use Web intelligence Rich Client. This means that we have to go through a WebI document to be able to achieve what we need. This creates another layer in between that we have to maintain.

SAP also announced that they are going to move away from WebI Rich Client. With that, would Qaaws go away?

I just wanted to know the future of Qaaws before spending a whole lot of resources looking at this solution.

Any answers/comments would be appreciated.

[denis_konovalov]

Please provide a link to something official that says "SAP announcing move away from Webi Rich client"

I do not think that is correct, I think you might be confusing WRC with Java report panel.

As far as future of QAAWS - there are no public documents that describe it. All public roadmap documents point to QAAWS and UNV's as existing for the foreseeable future.

[Former Member]

Thanks for the insight.

Maybe I misunderstood the road map document (https://www.sap.com/documents/2017/06/da257423-c37c-0010-82c7-eda71af511fa.html). It states that dHTML client is strategic and keep Rich Client for offline usage. So I assumed that Rich Client would eventually be replaced by dHTML.

Either way, as long as Qaaws is still in the picture, we can pursuit this as a long term solution.

[denis_konovalov]

That presentation does not show any "move away from WRC".
It shows that dHTML will be enhanced to have full functionality of the Java Report panel.
And WRC which is client version of Java Report panel was always offline first.
It is Java Report Panel that is being phased out because all major browsers stopping java support.