Adapter environment

Before installing, configuring, and using the adapter, you must understand its environmental requirements:

Adapter platforms

The adapter is supported on the following platforms:

Adapter prerequisites

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.

Locale-dependent data

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. Standard configuration properties for connectors.

This adapter supports the processing of bidirectional script data for languages such as Arabic, Hebrew, Urdu, Farsi and Yiddish. To use the bidirectional capacity, you must configure the bidirectional standard properties. For more information, refer to the standard configuration properties for connectors inAppendix. Standard configuration properties for connectors.

Copyright IBM Corp. 2004, 2005