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. Version 5.5 of the adapter for JText 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, 2.4, and 2.5.
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:
Before running the JText connector, create read/write permissions on the event, output, and archive directories that will contain the text files that the connector reads from and writes to. This needs to be done on both the local and remote servers.
The connector has been internationalized so that it can support double-byte character sets, and deliver message text in the specified language. 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 preserves 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 encoding 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. 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 configuration properties, see Appendix