Deprecations: IBM MQ transport for SOAP client and HTTP Bridge
The IBM® MQ transport for SOAP Java client and listener for JAX-RPC, the IBM MQ transport for SOAP .NET 1 and 2, and the IBM MQ bridge for HTTP are deprecated.
The IBM MQ transport for SOAP Java client
The IBM MQ transport for SOAP Java client and listener for JAX-RPC is deprecated. The functionality that is provided by this client and listener is considered back-level as the JAX-RPC standard on which it depends was deprecated in Java Platform, Enterprise Edition 6. In addition, the status of the Apache Axis1 libraries that underpin the client and listener are now out of service. Use the IBM MQ transport SOAP Java client for JAX-WS as an alternative.
The IBM MQ transport for SOAP .NET 1 and 2
The IBM MQ transport for SOAP .NET 1 and 2 client is deprecated. The functionality that is provided by this client is considered back-level. Use the IBM MQ custom channel for Microsoft Windows Communication Foundation (WCF) as an alternative (see Developing Microsoft Windows Communication Foundation (WCF) applications with IBM MQ ).
The IBM MQ bridge for HTTP
The IBM MQ bridge for HTTP is deprecated. The WebSockets support that is provided by the IBM Messaging Client for JavaScript should be used as an alternative.