Introduction to the IBM Message Service Client for .NET

IBM® Message Service Client for .NET provides an application programming interface (API) called XMS that has the same set of interfaces as the Java Message Service (JMS) API. IBM Message Service Client for .NET contains a fully managed implementation of XMS, which can be used by any .NET compliant language.

XMS supports:

  • point-to-point messaging
  • publish/subscribe messaging
  • Synchronous message delivery
  • Asynchronous message delivery
An XMS application can exchange messages with the following types of application:

  • An XMS application
  • An IBM MQ classes for JMS application
  • A native IBM MQ application
  • A JMS application that is using the IBM MQ default messaging provider
An XMS application can connect to, and use the resources of, any of the following messaging servers:

    IBM MQ queue manager
    The application can connect in either bindings or client mode.

    WebSphere Application Server Service Integration Bus
    The application can use a direct TCP/IP connection, or it can use HTTP over TCP/IP.

    IBM Integration Bus
    Messages are transported between the application and the broker using WebSphere MQ Real-Time Transport. Messages can be delivered to the application using WebSphere MQ Multicast Transport.

By connecting to a IBM MQ queue manager, an XMS application can use WebSphere MQ Enterprise Transport to communicate with IBM Integration Bus. Alternatively, an XMS application can publish and subscribe by connecting to IBM MQ.