Adapter for i2 environment
Broker compatibility
This adapter runs with the WebSphere Business Integration
Adapter FrameworkV2.6 and requires one of the following:
- WebSphere InterChange ServerV4.2.2,V4.3
- WebSphere MQ IntegratorV2.1
- WebSphere MQ Integrator BrokerV2.1
- WebSphere Business Integration Message BrokerV5.0.1
- WebSphere Application Server EnterpriseV5.0.2, in conjunction
with WebSphere Studio Application Developer Integration EditionV5.0.1
- WebSphere Business Integration Server FoundationV5.1.1
Adapter platforms
In addition to a broker, this adapter requires one of
the following operating systems:
- All operating system environments require the Java compiler
(IBM JDK 1.4.2 for Windows 2000) for compiling custom adapters
- AIX:
AIX 5.1 with Maintenance Level 4
- Solaris:
Solaris 9 (2.9) with Solaris Patch Cluster dated February
11, 2004 or later. This adapter supports 32-bit JVM on a 64-bit
platform.
- HP-UX:
HP-UX 11.i (11.11) with June 2003 GOLDBASE11i and June
2003 GOLDAPPS11i bundles
- Windows:
Windows 2000 (Professional, Server, or Advanced Server) with Service Pack 4
Windows XP with Service Pack 1A, for WebSphere Business Integration Adapter Framework (administrative tools only)
Additional requirements
The WebSphere Business Integration Adapter for i2 also
requires the following hardware and software:
- CIS SDK 6.1
- i2 application 5.2 or above
- JDK 1.4.2 compliant connector.jar
- Appropriate CIS adapter (MetadataService adapter is required
fo the i2 ODA)
- CIS libraries (cis.jar, cis-sso.jar, cis-sso-spi.jar, cis-util.jar,
jdom.jar, jmxri.jar, log4j.jar, jaas.jar, connector.jar)
- IBM WebSphere Business Integration XML datahandler
- IBM WebSphere Business Integration API (WBIA.jar)
- i2 CIS 6.1 SDK properties directory
- If i2 CIS is running with WebSphere MQ bindings, the .bindings
file
Processing locale-dependent data
The connector has been internationalized so that it can
support delivery of double-byte character sets (DBCS) going into
an 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 set 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 set. Unicode contains
encodings for characters in most known character code sets (both
single-byte and multi-byte). 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.
