Before installing, configuring, and using the adapter, you must understand its environment requirements. They are listed in the following sections:
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. Version 5.3 of the adapter for e-Mail is supported on the following versions of the adapter framework and with the following integration brokers:
Adapter framework: WebSphere Business Integration Adapter Framework versions 2.1, 2.2, 2.3.x, and 2.4.
Integration brokers:
See the Release Notes for any exceptions.
For message brokers (WebSphere MQ Integrator Broker, WebSphere MQ Integrator, and WebSphere Business Integration Message Broker), see Implementing Adapters with WebSphere Message Brokers, and the installation documentation for the message broker. Some of this can be found at the following Web site: http://www.ibm.com/software/integration/mqfamily/library/manualsa/.
For WebSphere Application Server, see Implementing Adapters with WebSphere Application Server and the documentation at: http://www.ibm.com/software/webservers/appserv/library.html.
The adapter is supported on the following platforms:
The adapter has been internationalized so that it can support double-byte character sets, and deliver message text in the specified language. When the adapter transfers data from a location that uses one character code set 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 WebSphere business integration system components, there is no need for character conversion.
To log error and informational messages in the appropriate language and for the appropriate country or territory, configure the Locale standard configuration property for your environment. For more information on these properties, see Appendix A, "Standard configuration properties for adapters"