The IBM WebSphere InterChange Server 4.2.2 release and the IBM
WebSphere Business Integration Adapter 2.4.0 release provide the
following new functionality in the Java connector library:
- A Java connector now uses the IBM Java Object Request Broker
(ORB) instead of the third-party VisiBroker ORB.
- A Java connector can now support access to the serialized data
sent or or received from a data handler. In previous releases, the
connector could access serialized data as a Java String. It can now
provide access in any of the following new forms.
- As an input stream: boToStream() and
streamToBO()
- As a Java byte array: boToByteArray() and
byteArrayToBo()
- As a Reader object: readerToBO()
In addition, all data-handler methods now support the ability to
identify the character encoding and locale for the data handler to
associate with the serialized data. For more information, see the
descriptions of these methods in Calling a data handler.
- The Java connector library now provides the following features
for an event store (which the CWConnectorEventStore class
represents):
- The setEventStoreStatus() method has been renamed to
setEventStatus() to better identify its functionaliy. This
method sets the status of an event.
- The getBO() method now provides the ability to return
an integer status value to its calling method. The default
implementation of getBO() continues to use the form that
does not provide an internal status value. For more
information, see the description of the getBO() method in
the CWConnectorEventStore class.
- The Java Connector Development Kit (JCDK) now provides a more
consistent way to create startup scripts for Java connectors. It
also provides a template (for both Windows and UNIX-based systems)
for the creation of this startup script. For more information, see
Starting up a new
connector.
In addition, the Adapter Development Kit (ADK) now includes an
adapter sample in the DevelopmentKits\Twineball_sample
subdirectory of the product directory. This adapter sample includes
a Java connector.
