Folks,
TIBCO has announced support for WCF channels back in April – has anything of that materialized by now??
Where and how can I download either these new WCF channel bits, or where can I get my hands on a current .NET 2.0/3.5 version of the ‘TIBCO.EMS .NET client library’ ??
We’re a small ISV without any ties to TIBCO so far, but a large client of ours required us to interop with his TIBCO EMS system, without being able to provide the technical background info we need 🙁
Thanks for any hints and pointers ! Marc
Follow-up – 2009-Jan-14: Not much response here…. those of you using TIBCO EMS – how do you interface with it, e.g. communicate and send data back and forth??
UPDATE (April 2010)
I’ve had an opportunity to check out the ‘native’ TIBCO.EMS.dll from .NET, as well as their WCF implementation, and my conclusion is: use the native API. It’s easy, it’s simple, it works.
The WCF parts are horrendous. They’re incomplete, very unconventional, they don’t feel like a good WCF citizen. TIBCO only provides a transport element – you can’t just use a ready-made emsBinding or something – you’ll have to define that yourself. I was very disappointed – I had expected more from a company the size and reputation of TIBCO….
Your communication stack will be a lot simpler if you simply use Tibco EMS .NET client directly. It’s styled after JMS, which is widely used in enterprise software development. Hence there are a lot of tech books on how to do JMS programming. Java and C# are so similar that it’s easy to do the mental translation to apply that to Tibco EMS .NET client programming.
Having designed and implemented a lot of communications channels for distributed applications, my experience has been the simpler the stack the more reliable and trouble-free in operation.
The problem with abstraction layers of the ilk of WCF is that there is almost always a leaky abstraction issue lurking somewhere.