Using SOAP and Web Services with Ensemble - InterSystems ...

Creating an Ensemble Web ServiceMethod OnProcessInputAlt(pInput As %RegisteredObject,ByRef pOutput As %RegisteredObject, pHint As %String) As %Status{if pHint="GetCustomerInfo"{set sc= ..SendRequestSync("GetCustomerInfoBO",pInput,.pOutput)}elseif pHint="GetStoreInfo" {set sc= ..SendRequestSync("GetStoreInfoBO",pInput,.pOutput)}Quit sc}Or, because the business operation has the same name as the corresponding Web method, with BOappended to it, you could use this instead:Method OnProcessInput(pInput As %RegisteredObject,ByRef pOutput As %RegisteredObject, pHint As %String) As %Status{set sc= ..SendRequestSync($Get(pHint)_"BO",pInput,.pOutput)Quit sc}2.8 Enabling SOAP SessionsThe SOAP specification does not include session support. However, it is often useful to maintain asession between a Web client and the Web service that it uses. You can do this with an Ensemble Webservice. If a Web service uses sessions, it establishes a session ID and allows repeated calls on theservice after one successfully authenticated call from a client.Support for SOAP sessions is controlled by the SOAPSESSION class parameter. The default is 0, whichmean that the Web service does not use sessions.To enable SOAP sessions, create a subclass of EnsLib.SOAP.Service and set SOAPSESSION to 1 inthe subclass. Base your Ensemble Web service on this subclass.For more information on SOAP sessions, see the book Using SOAP and Web Services with Caché inthe Caché documentation.2.9 Additional OptionsBecause your Ensemble Web service extends %SOAP.WebService, you can use all the SOAP supportprovided by that class. This support includes options for the following customizations, among others:• Customizing the SOAP headers• Passing attachments in the SOAP messages• Changing the binding style of the SOAP messages from document-style (the default) to rpc-style24 Using SOAP and Web Services with Ensemble