Ensemble passthrough configuration
I have tried to create Ensemble SOAP passthrough operation following this guide.
Here's my production configuration (after steps 1-4):
Class Passthrough.Production Extends Ens.Production { XData ProductionDefinition { <Production Name="Passthrough.Production" LogGeneralTraceEvents="false"> <Description></Description> <ActorPoolSize>2</ActorPoolSize> <Item Name="PassthroughOperation" Category="" ClassName="EnsLib.SOAP.GenericOperation" PoolSize="1" Enabled="true" Foreground="false" Comment="" LogTraceEvents="false" Schedule=""> <Setting Target="Adapter" Name="HTTPServer">www.webservicex.net</Setting> <Setting Target="Adapter" Name="URL">|</Setting> </Item> <Item Name="PassthroughService" Category="" ClassName="EnsLib.SOAP.GenericService" PoolSize="0" Enabled="true" Foreground="false" Comment="" LogTraceEvents="false" Schedule=""> <Setting Target="Host" Name="TargetConfigName">PassthroughOperation</Setting> <Setting Target="Adapter" Name="EnableStandardRequests">1</Setting> <Setting Target="Adapter" Name="Port"></Setting> </Item> </Production> } }
Step 5 of the guide says to open the url:
http://localhost:nnnnn/currencyconverter/ConvertCurrencySOAPPassthroughS...
have two web applications in a namespace:
- /csp/passthrough
- /passthrough
I have tried calling the following urls:
- http://localhost:57773/passthrough/PassthroughService/CurrencyConvertor.asmx
- http://localhost:57773/passthrough/PassthroughService/CurrencyConvertor.asmx?CfgItem=PassthroughService
- http://localhost:57773/csp/passthrough/PassthroughService/CurrencyConvertor.asmx
- http://localhost:57773/csp/passthrough/PassthroughService/CurrencyConvertor.asmx?CfgItem=PassthroughService
Yet, I get 404 error. Direct calls to a remote service are successful. How do I call my passthrough service?
Turns out, I forgot to setup DispatchClass for /passthrough application. After setting it to EnsLib.SOAP.GenericService, the following URL works:
Ugh, and this is why I should do a page refresh before posting a comment/answer ...
I was pretty sure it was an issue with the web application definition, but didn't think to remove the dispatch class when I tested ...
Hi Eduard,
(well, nevermind, then ... still a useful exercise for me
)