Before installing, configuring, and using the adapter, you must understand its environmental requirements:
The adapter framework that an adapter uses must be compatible with the version of the integration broker (or brokers) with which the adapter is communicating. The 1.0 version of the adapter for HTTP is supported on the following adapter framework and integration broker:
See the Release Notes for any exceptions.
Review the following assumptions and software requirements before you install the connector for HTTP:
The adapter runs on the following platforms (operating systems):
A variety of standards and technologies give access to their functionality over a network.
The standards used by the adapter are as follows:
The APIs used by the adapter are as follows:
Depending on your configuration, you may need to install additional software. The sections below discuss these contingencies.
If you plan to use SSL, you must use third-party software for managing your keystores, certificates, and key generation. No tooling is provided to set up keystores, certificates, or for key generation. You may choose to use keytool (shipped with IBM JRE) to create self-signed certificates and to manage keystores. For further information, see SSL.
The connector has been globalized so that it can support double-byte character sets. When the connector transfers data from a location that uses one character code to a location that uses a different code set, it performs character conversion to preserve the meaning of the data.
The Java runtime environment within the Java Virtual Machine (JVM) represents data in the Unicode character code set. Unicode contains encodings for characters in most known character code sets (both single-byte and multibyte). Most components in the WebSphere business integration system are written in Java. Therefore, when data is transferred between most integration components, there is no need for character conversion.
This section discusses globalization and the connector.
The connector uses pluggable protocol listeners for event notification. The protocol listeners extract the message from the transport and invoke the data handler specified in the message meta-data. For further information on listener processing, see HTTP and HTTPS protocol listener processing.
The connector uses a pluggable HTTP-HTTPS protocol handler framework for request processing. The protocol handlers invoke the data handler. For further information, see HTTP-HTTPS protocol handler processing.
You can configure the HTTP adapter to use any data handler. For an overview of data handler configuration, see Configuring the data handler.