The IBM WebSphere InterChange ServerIBM WebSphere InterChange
Server4.2.1 release and the IBM WebSphere Business Integration
Adapter 2.2.0 release provide the following new functionality in
the Java connector library:
- The connector can now provide additional configuration to a data handler
when it calls the data handler. The following methods support a config
argument to specify this additional information:
- boToString()
- stringToBo()
For more information, see the descriptions of these methods in CWConnectorUtil class.
- The Java connector library now provides access to individual name-value
pairs in application-specific information through new forms of the
getAppText() method in the CWConnectorBusObj
class.
For more information, see the description of this method in CWConnectorBusObj class.
- In support of duplicate event elimination (which provides guaranteed event
delivery), the Java connector library provides the setDEEId()
method in the CWConnectorBusObj class to enable a connector to set
a business object's ObjectEventId attribute with the event identifier
(ID). For more information, see Guaranteed event delivery for connectors with non-JMS event stores and the description of the setDEEId() method
in CWConnectorBusObj class.
- The Java connector library now provides the following API methods:
- The getTerminate() and setTerminate() methods (in the
CWConnectorEventStore class) to allow the
pollForEvents() method to better handle the application-timeout
(APPRESPONSETIMEOUT) condition.
- The setLocale() method (in the CWConnectorBusObj class) allows
you to set the locale that is associated with a business object. This
new method complements the getLocale() method that has already been defined in
this same class.
- The cleanupResources() method (in the CWConnectorEventStore class)
allows you to release resources that the event store has used.
- Adding a connector to the business integration system now provides more information on how to add a Java connector
to the WebSphere business integration system, including:
- How to create an initial configuration file for a connector
- How to create a startup script for a Java connector from a sample startup
file
- Use of the new CWConnEnv.bat (Windows) or
CWConnEnv.sh (UNIX) file for system-variable settings
- Designing a connector now provides more information on how to internationalize a
connector.
- Several Java connector library methods have been changed to better handle
status return codes:
- The default implementation of the pollForEvents() method now
takes the following actions:
- It handles the CONNECTOR_NOT_ACTIVE and
NO_SUBSCRIPTION_FOUND status return codes from its call to the
gotApplEvent() method. For more information, see Sending the business object.
- It returns an outcome status of APPRESPONSETIMEOUT if access to
the event store fails. Failure to access the event store can occur in
any of the following event-store methods:
Event-store method
| Exception raised
|
fetchEvents()
| StatusChangeFailedException
|
archiveEvent()
| ArchiveFailedException
|
deleteEvent()
| DeleteFailedException
|
updateEventStatus()
| StatusChangeFailedException
|
- The agentInit() method now returns an outcome status of
FAIL if, when it throws an exception, the exception-detail
object's status value is not set. If the status value is
set within the exception-detail object, agentInit() returns that
status value.
- The doVerbFor() method now returns an outcome status of
APPRESPONSETIMEOUT if, when it throws a
ConnectionFailureException, the exception-detail object's
status value is not set. If the status value is set within
the exception-detail object, doVerbFor() returns that status
value.
