MQe provides the following communications adapters:.
- Communications adapters
- MQeMidpHttpAdapter
- Provides support for reading and writing to the network using the HTTP
1.0 protocol in a MIDP environment.
- MQeTcpipHistoryAdapter
- Provides support for reading and writing to the network using the TCP
protocol. This adapter provides the best TCP performance by chaching recently
used data. Therefore, we recommend that you use this adapter.
- MQeTcpipLengthAdapter
- Provides support for reading and writing to the network using the TCP
protocol.
- MQeTcpipHttpAdapter
- Provides support for reading and writing to the network using the HTTP
1.0 protocol. Also provides support for passing HTTP requests through proxy
servers.
Note: If using the Microsoft JVM, the http:proxyHost and http:proxyPort
properties are automatically set by the JVM using the settings in the Internet
Explorer. If the use of proxies is not required for MQe, set the http.proxySet
Java property to false.
- MQeUdpipBasicAdapter
- Provides support for reading and writing to the network using the UDP
protocol. This adapter uses only one port on the server. The behavior of this
adapter is particularly sensitive to the various Java property settings, as
detailed in the MQe Java Programming Reference.
- MQeWESAuthenticationAdapter
- Provides support for passing HTTP requests through MQe authentication
proxy servers and transparent proxy servers.
You can modify the behavior of these adapters using Java properties. For
more information on how to use these properties and their effect on each communications
adapter, refer to the MQe Java API Programming Reference.
You can also write your own adapters to tailor MQe for your own environment.
The next section describes some adapter examples that are supplied to help
you with this task.