Before installing, configuring, and using the adapter, you must understand its environment requirements. They are listed in the following section.
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 2.0.0 of the adapter for QAD MFG/PRO is supported on the following adapter framework and integration brokers:
See Release Notes for any exceptions.
The adapter is supported on the following application platforms and databases:
Operating systems:
Databases:
Third-party software:
You must install the QXtend and the Q/LinQ MQSeries MOM products from QAD, but not necessarily on the same machine as the adapter.
For event generation, the QAD product DataSync is also needed. It is installed on top of Q/LinQ, but is sold as a seperate product.
The adapter for QAD MFG/PRO has the client library/API dependencies shown in Table 1.
Library/API | Version | Operating systems |
---|---|---|
IBM JRE | 1.3.1.6 | All supported OSs |
Java libraries for MQSeries and JMS | 5.2+ | All supported OSs |
Xerces | 1.4.3 | All supported OSs |
dom4j | 1.4 | All supported OSs |
JNDI | 1.2.1 | All supported OSs |
Apache SOAP | 2.3.1 | All supported OSs |
WSDL4J | 1.0 | All supported OSs |
IBM JSSE | 1.0.2 | All supported OSs |
This adapter is DBCS (double-byte character set)-enabled and is translated. It 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 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.
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 A, Standard configuration properties for connectors.