Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | Introduction | Introduction to webMethods Broker Messaging | webMethods Broker | Client Interoperability
Client Interoperability
There is a high degree of interoperability among JMS and C# messaging clients. To the Broker, clients written for either JMS or C# are indistinguishable, since both utilize the same wire format. The webMethods Broker Client C# API is essentially a C# implementation of the JMS API. You can use the same administrative tools to work with both.
Several differences exist between the implementations:
*The webMethods Broker Client C# API is designed to work solely on a Windows-based .NET platform, therefore, it does not support Java EE applications or distributed (XA) transactions.
*Clients written for the webMethods Broker Client C# API must save their administered objects to an LDAP directory. Clients written for the webMethods Broker Client API for JMS can use any of several supported JNDI providers to store administered objects, including a JNDI LDAP provider.
The webMethods Broker APIs for JMS and webMethods Broker C# messaging APIs are not interoperable with the webMethods Broker Java APIs and webMethods Broker C APIs. Interoperability does not exist because the two groups of APIs do not use the same packing rules to access a Broker event.
However, the webMethods Broker API for JMS can interoperate with webMethods Broker Java APIs and webMethods C APIs through a marshalling mechanism (see JMS Marshalling). This mechanism allows users to hook in conversion routines to convert data between the JMS and legacy webMethods Broker client formats. No equivalent mechanism currently exists for C# clients.