IBM WebSphere IBM WebSphere Adapter Foundation Classes, version 7.5.0.1 IF05 notes

This document contains the following sections:

Enhancements and fixes

New and modified connector properties

Upgrade notes

This table lists the enhancements and fixes in interim fix version 7.5.0.1 IF05. Fixes # CR APAR Title Details 1 7230 Incomplete XSD namespace package generated [RAD] Symptom: When regenerating the Business Object classes using an XSD schema file from SAP or PeopleSoft WebSphere Adapters, an incorrect package name is returned when the targetNamespace does not start with www Resolution: Problem in the logic that converts the namespace to package name in the RecordGeneratorHelper class. 2 7220 ALEInbound does not work when PI is enabled. Problem with the package name generated in RAD when the namespace is urn Symptom: RecordGeneratorHelper where the namespace to package conversion happens does not handle the namespace that is of urn type. Resolution: Support to handle namespace of urn type added in RecordGeneratorHelper. 3 7162 Generated Java bindings have incorrect xsdLocation in the commented code section Symptom: Generated Java bindings have incorrect xsdLocation in the commented code section Resolution: The method generateDataBinding now returns only one top level root node matching to the business object previously mutliple root nodes were returned,hence the databindings had incorrect namespace 4 7187 CI Default value should be populated for attributes in the generated schemas for idocs, no support in AFC for enum types Symptom: CI Default value should be populated for attributes in the generated schemas for idocs, no support in AFC for enum types Resolution: Support for enum types for xsd attributes added in AFC

This table lists the enhancements and fixes in interim fix version 7.5.0.1 IF04. Fixes # CR APAR Title Details 1 7184 JR42433 FileNotFound issue during databinding generation in WBIDataBindingGenerator, when schema URL points to file within a jar Symptom: FileNotFound issue during databinding generation in WBIDataBindingGenerator, when schema URL points to file within a jar Resolution: Problem was occurring because the AFC code assumed that the schema URL will always point to a file, support for other protocols was not provided. This is corrected to enable support for all protocols for schema URL.

This table lists the enhancements and fixes in interim fix version 7.5.0.1 IF03. Fixes # CR APAR Title Details 1 Task 7088 Handle the noClassDefFoundError thrown during EMD when trying to log an ffdc while running on RAD Symptom: When the adapter tries to log an ffdc during EMD a noClassDefFoundError is thrown. This happens since the Manager class is missing from the ffdc jar available in the classpath during discovery Resolution: Introduced additional check in LogUtils class verifying the existence of Manager class in the classpath before ffdc is logged

This table lists the enhancements and fixes in interim fix version 7.5.0.1 IF02. Enhancements # CR APAR Title Details 1 6824 Provide option in DESPI XML to add and remove namespance and type from response xml [CI related] Symptom: The namespace and type attributes in the response xml schema should be optionally generated and should be controlled by a configuration parameter Resolution: Introduced new boolean variable skipNamespaceType_ with its mutator and accessor . This variable will be used by CI to determine the choice of generating response xml schema with or without namespace and type attributes. This table lists the enhancements and fixes in interim fix version 7.5.0.1 IF01. Enhancements # CR APAR Title Details There are no enhancements in this interim fix. Fixes # CR APAR Title Details 1 Task 6422 The cached business object schema is used when the schema is changed. Symptom: During the execution in CastIron runtime, the business object metadata cached in the foundation classes will be reused if the schema is modified and deployed without restarted the runtime. Resolution: The foundation classes has been modified to ensure cached schema will be overwritten based on the appropriate API call while working with Cast Iron runtime. This table lists the enhancements and fixes in fix pack version 7.5.0.1. Enhancements # CR APAR Title Details 1 103499 Extend the Adapter Monitoring Capabilities by Including Event Points for Connection and Authentication to EIS. Additional event points were introduced in AFC to capture the connection and authentication related events: WBI.JCAAdapter.Connection.SUCCESS, WBI.JCAAdapter.Connection.FAILURE, WBI.JCAAdapter.Connection.LOST, WBI.JCAAdapter.Connection.CLOSE, WBI.JCAAdapter.Authentication.FAILURE 2 103559 Enterprise metadata discovery code for the adapter should be thread safe. Cast Iron Runtime requires the adapter to support thread safe Enterprise metadata discovery, for this requirement the adapter implements thread safe EMD. 3 102699 Extend the DESPI to support XML Types Cast Iron Runtime requires the adapter to support XML data types for sending and receiving business objects from adapters, for this requirement the adapter extends the DESPI implementation for support XML types. Fixes # CR APAR Title Details 1 103614 Adapter uses Java timer for polling, when JCA timer is not abilable from the container, the adapter polling thread hangs in this situation. Symptom: The non-daemon Java timer polling thread hangs with WebSphere Message Broker runtime, during inbound operation when the JCA timer is not available from the container. Resolution: When the JCA Timer is not available from the container, the adapter uses the older approach of using the WorkManager to manage and execute the polling thread. 2 103512 Adapter Inbound throws UnsupportedOperationException on WebSphere Message Broker. Symptom: The startup of the Adapter fails with the UnsupportedOperationException since WebSphere Message Broker does not support a JCA timer in its bootstrap context and the Adapter expects one to be available. Resolution: Adapter catches the UnsupportedOperationException exception and uses the WorkManager to manage and execute the polling thread, when the JCA timer is not available from the container 3 103589 Remove the transaction code from EventPersistenceMemoryImpl Symptom: EventPersistenceMemoryImpl suspends and resumes the global transaction while the adapter is running with a in-memory persistence configuration, this could potentially affect the performance. Resolution: Removed the code that performs suspend and resume of the global transaction for the in-memory persistence configuration. 4 103584 Schema generation should support to set the maxOccurs to a desired number. Symptom: The schema generator code does not allow to set the value of maxOccurs attribute to the desired number, instead only allows to set 0, 1 or unbounded. Resolution: The schema generator code is fixed to allow for setting the value of maxOccurs attribute to the desired number. 5 103302 XML attribute support in DESPI XML Symptom: Current XML DESPI implementation does not consider xml attribute for processing. Resolution: Support provided for processing xml attributes in DESPI XML. 6 103539 Synchronous BAPI inbound fails in Node level deployment with the lazy BO parsing. Symptom: SAP adapter throws exception in sync callback in lazy-mode node level deployment. Error is thrown when maxlength annotation is read. Resolution: The issue has been fixed in Adapter foundation classes to ensure that the node level deployment works fine with lazy BO parsing. 7 103796 JR41084 Detect Illegal XML Character property should be visible only on IBM Integration Designer tooling Symptom: The detect illegal XML property should be visible only for IBM Integration Designer and not seen on Rational Application Developer / WebSphere Message Broker toolkit. Resolution: Modified the AFC code such that the EMDUtil class returns null for the DetectIllegalXML property group if the runtime is other than IBM Integration Designer. 8 103797 JR41085 JDBC Adapter outbound behavior with illegal xml returns ResourceException. Symptom: JDBC Adapter throws exception when illegal xml character is used during outbound. The detect illegal XML property options does not work as expected. JDBC adapter uses setObject() method to set the string property. Resolution: The validation of the illegal character is now done on setObject() method of the accesssor too if the parameter is a string. 9 103800 Perform validation in EMD and runtime for the Inbound properties. Symptom: External Service wizard allows and accepts negative values for the following properties (Interval between polling periods, Maximum events in polling period and Time between retries in case of system connection failure). Resolution: Validation is now performed for these properties to not accept negative values during External Service wizard and in the runtime. 10 103802 The tracing of the Adapter foundation classes version for outbound request should be at FINEST level. Symptom: The tracing of the AFC version for each individual outbound request should be at FINEST level. Currently, the tracing is done at INFO level which causes a lot of I/O and unneccessary logs in high load conditions for each outbound request. Resolution: The AFC version information is now traced only at the FINEST level. 11 103803 Use UOWManager as the transaction API for Event Persistence Symptom: Event persistence classes are currently using the deprecated WAS API. This change is to implement the new WAS API for Transaction handling in Event persistence classes. Resolution: Modified the Event persistence classes now to use the UOWManager as its transaction API. 12 103804 Modify getEventWithXid method in EventPersistence implementation Symptom: getEventWithXid method is called during the adapter recovery path. This method uses incorrect event peristence column names. Resolution: Fixed the getEventWithXid method to use the appropriate event persistence column name. 13 103848 JR41086 Adapter tries to shutdown Event manager repeatedly Symptom: When an exception occurs while trying to shutdown the Event Manager, the adapter tries to shutdown the event manager repeatedly. Resolution: Cancel the JCA Timer even if there is an exception in Event Manager shutdown.

This table lists new connector properties # Version Platform Add or Remove Property (Note that property names are case sensitive) There is no new connector property introduced/modified for this version of fix pack.

To upgrade to the fix pack version 7.5.0.1 IF01, do the following: 1. Ensure you have followed the 'Installation Instructions' section in the download link before proceeding further. 2. If you need to use the Fix Pack for External Service, delete the connector project in the IBM Integration Designer, import the new rar and apply the EIS specific dependency files. The following steps describe how to do the same.    a. Open the Java Build Path for the SCA module and remove the Connector project selected on projects tab.    b. Open the dependency editor and remove the connector project.    c. Delete the connector project from workspace.    d. Import the new rar file. Add any dependency files from EIS specific APIs as needed.    e. Open Java build path for the SCA module and select the Connector project selected on projects tab.    f. Open the dependency editor and add the connector project if it is not already present and check "Deploy with Module". 3. If you need to update deployed applications on the IBM Process Server.    a. Select "Update" for the corresponding application on the IBM Process Server Admin Console.    b. Select "Single Module" with relative path as name of the rar file - CWYFT_FTPFile.rar.    c. Click the "Browse" button on local file system to select the updated rar file that has the changes.    d. Select the default values in the remaining steps and click 'Finish'. This will ensure that existing configurations e.g. MCF, are not changed and jars will be merely updated.

Nov 24th, 2011 6:00 PM

(C) 2011 IBM Corporation. Proprietary and Confidential. All Rights Reserved.