IBM WebSphere IBM WebSphere Adapter Foundation Classes, version 7.5.0.5_IF02 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.5_IF02
Fixes
#CRAPARTitleDetails
1 20741 When SAP adapter receives multiple values of a complex type element in BAPI/RFC, the adapter is processing only the first value and ignoring the others. This is now fixed ,logic for detecting next element using start element tag in Despi XML [CI] was corrected.
2 a 8792 BAPI/RFC fails when structure contains deep nested table type and line types. This is now fixed, this was applicable only for Despi XML [CI]

This table lists the enhancements and fixes in interim fix version 7.5.0.5_IF01
Fixes
#CRAPARTitleDetails
1 ci 16483 Adapter fails while resetting cursor to root level for Despi XML [CI]This is now fixed, adapter is resetting cursor correctly.

This table lists the enhancements and fixes in fix pack version 7.5.0.5
Fixes
#CRAPARTitleDetails
1 ForwardFit JR44116SAP NODE AND JMS NODE IN SAME EG, WILL RESULT IN JMS NODE GETTING SAP NODES INITIAL CONTEXT.NEED TO PASS INITIALCONTEXTNow the adapters implement the initial context as part of the Activation Spec properties.



This table lists the enhancements and fixes in fix pack version 7.5.0.3.
Enhancements
#CRAPARTitleDetails
There are no enhancements in this fix pack.
Fixes
#CRAPARTitleDetails
16824Provide 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.
27793 [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.
37230Incomplete 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.
47824 [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
57822 [7147]Adapter foundation classes should provide a method to retrieve all the events in the event persistence table
Symptom: Adapters require to query all the events in the event persistence table. Currently there is no helper method in foundation classes to retrieve all the events.
Resolution: A method getAllEvents() is provided to retrieve all the events from the event persistence table.
66783Processing methods for illegal XML characters section is seen in WMB in the generated .adapter file.
Symptom: Processing methods for illegal XML characters section is seen in WMB in the generated .adapter file.
Resolution: Illegal XML characters property group is meant for WPS only. AFC returns the property group if it is valid for the tooling. Check to determine the tooling was incorrect that led to the observed behavior on WMBTK.


This table lists new connector properties
#VersionPlatformAdd or RemoveProperty (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.5_IF02, 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.


Sep 25th, 2012 6:00 PM
(C) 2012 IBM Corporation. Proprietary and Confidential. All Rights Reserved.