Question

The setup at the current employer has one set of back office functions on a Java platform and another group of functions on two separate .NET-based platforms. There is no overall architect.

The Java guys decided to go for Apache QPID and AMQP for messaging, presumably amongst themselves, with the .NET systems and other external systems.

.NET architecture involves WCF services hosted in IIS/WAS and Windows Server AppFabric.

Does anyone have any experience of AmqpBinding and IIS/WAS, if there are any possible pitfalls?

Was it helpful?

Solution

I think your first problem will be IIS/WAS/AppFabric because non HTTP services hosted in WAS have additional requirements for infrastructure which consists of additional process (listener) running usually as as a windows service and communicating with worker process. This process is responsible for receiving and sending messages and allows service activation in WAS. I don't think that the QPID project has the listener process already created. You will most probably have to implement the listener yourselves - check this sample for custom UDP activator.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top