Thanks Stefan.
I had read that, and understand how with SOAPSESSIONs enabled, soap calls can utilise the same session on the back-end. My tests definitely show this working.
What I was hoping to discover however, is if license unit consumption is effected or not effected, with the SOAPSESSION=1 model, which is what is implied by the comment against the parameter which says ".Also effects license consumption".
My tests show that license unit consumption for SOAP requests that are session based are no different to others - so - I still can't see that there are an license unit consumption implications.
In fact - it seems that no SOAP calls seem to be consuming licenses in the scenarios I have tested described below when using SOAP UI from an different IP address to the web service server...:
(a) with and without SOAPSESSION=1 set (and where set, CSP header is used by the web client)
(b) with or without Unauthenticated or Password access set on the CSP Application.
(c) with a hang of,say, 10 seconds in the web method (allows me to gather license counts).
(d) web service hosted as a standalone Cache web service, or, as a webservice that's part of a Business Service in a running Ensemble production (csp Gateway used for access).
In all scenarios and combinations of each above, it seems, no license units are consumed at all. I would have expected that (at least for SOAPSESSIONs enabled) a license unit would have been consumed for the duration of the session. My tests do not confirm this, hence the question on trying to clarify what the license implication actually are.. :)
Perhaps a broader understanding of how SOAP requests consume and then release license units is a better approach to addressing this thread.
(Note that my license key does not have the Web-Add option enabled. This is 2015.1.)
Steve
- Log in to post comments