This project is read-only.

Protocol bridging via MSE?

Topics: Technical Questions, Usage Scenarios
Mar 19, 2010 at 10:07 PM
Edited Mar 20, 2010 at 12:56 AM

Can MSE / WCF 4 do protocol bridging between consumer and provider?   I understand that in MSE an operation can be added to separate endpoints, each endpoint having a separate binding.   This would suggest that the consumer can use one protocol to interact with the MSE runtime and the virtual endpoint and the runtime could use another protocol to interact with the actual external service.   However, I'm not sure this is true, that MSE provides protocol abstraction.   For example, if an external service running on a CRM server exposed a set of asmx web services, hosted in IIS.   If these services were imported into MSE, could I expose the related CRM operations as virtual end points to clients (ie consumers) using a different protocol than http or wshttp (the protocol bound to asmx services)?

Biztalk via the ESB toolkit I believe offers in and out ramps that provide such protocol translations to allow a consumer to use one protocol (e.g. http) but for the actual provider to provide the service in another protocol (e.g. tcp) but I don't see how MSE is managing this for similar external services.