What does the QAAWS background user on the server do?

[Former Member]

What does the QAAWS background user on the server do? Is it only used when a web service is published? Or does it also come into play when the web service is invoked?

Could someone explain the process flow?

thanks!

[Former Member]

Hi,

This short post to clarify WSDL files management and to provide information about QaaWS background user.

XI 3.0 and previous versions of QaaWS required the QaaWS servlet to connect the CMS in order to generate the WSDL for a given QaaWS web service according to the description of this QaaWS infoobject. WSDL were hence dynamically generated. This required the servlet to use a background user (QaaWSServletPrincipal with XI 3.0) to connect the CMS, as no user credentials are required to retrieve WSDL information.

Hope this information helps.

Regards,

Shirish

[Former Member]

Through experimentation, we've found that the QAAWS background user on the server side is required to have access to the universe when the web service is created. After the web service is created, however, we can revoke universe access from the QAAWS background user and the web service can still be used.

Therefore we infer this account is needed to create web services, but is not used when the web service is being invoked.

As mentioned, we're just experimenting and inferring results. Can anyone confirm our findings and/or refer us to documentation that explains?

[Former Member]

QAAWS is equivalent to refresh on open WEBI document which hits the databases.