Before installing, configuring, and using the adapter, you must understand its environment requirements. In addition to the text below, hardware and software requirements are also available in the Techdoc at
http://www.ibm.com/support/docview.wss?uid=swg27006249
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.2.x version of the adapter for Enterprise JavaBeans architecture is supported on the following versions of the adapter framework and with the following integration brokers:
See Release Notes for any exceptions.
For WebSphere InterChange Server (ICS), see the System Installation Guide for UNIX or for Windows.
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
The adapter is written to the Enterprise JavaBeans 2.1 specification and as such is compatible with a J2EE-compliant application server that is based on this standard, such as WebSphere Application Server, version 5.x.
The adapter supports entity beans and session beans. Message-driven beans are not supported in this release.
The adapter is compliant with the Java Authentication and Authorization Service (JAAS), release 1.0.
For information about EJB software architecture, see http://java.sun.com/products/ejb/
The adapter runs on the following platforms:
The ODA for the EJB architecture adapter requires the j2ee.jar file, which is delivered with the adapter.
The connector has been internationalized so that it can support delivery of double-byte character sets going into an EJB interface that also supports 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 run time 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.