IBM WebSphere Adapter for IBM i, version 7.5.0.3 notes

This document contains the following sections:
Enhancements and fixes
New and modified connector properties
Upgrade notes


This table lists the fixes in Fix Pack version 7.5.0.3
Fixes
#CRAPARTitleDetails
17755JR41731 Sample CL program needs to be changed and compiled for different IBM i server date formats.
Symptom: Sample CL programs are not working when the IBM i server format is different than MDY format. User needs to modify the CL program and compile.
Resolution: The CL program is generalized to accept all IBM i server date formats.
27756JR43208 IBM i Adapter not polling the events from staging queue if adapter is restarted at 00:00 hours.
Symptom: IBM i Adapter is not polling the events from staging queue until the next day if the adapter is restarted at 00:00 hours.
Resolution: The sample CL program is modified and the adapter is polling the events from staging queue properly.
37823 In some recovery cases, there is inconsistency between staging queue and event table.
Symptom: In some recovery(abruptly shutdown) cases, there is inconsistency between staging queue and event table. It may cause duplicate events deliver to end point in recovery.
Resolution: This issue is fixed and staging queue and event table contains same events.





This table lists the enhancements and fixes in interim fix version 7.5.0.2.
Enhancements
#CRAPARTitleDetails
1CR 103523 Upgradation of the third party API(JTOpen) of IBM i adapter to 7.5.1
JTOpen(Third Party API) 7.5.1 is bundled with the adapter
2CR 103744 IBM i Adapter Certification on IBM i/iSeries V7R1 System
Adapter is certified on IBM i/iSeries V7R1 system
Fixes
#CRAPARTitleDetails
16318(RTC) Event Type should be disabled since it is NA for IBMi
Symptom: In Event Delivery properties, Event Type is enabled. Needs to disable it due to its NA for IBMi
Resolution: Event Type inside the Event Delivery properties is disabled for IBM i adapter.
27142(RTC) In some recovery cases, there is inconsistency between staging queue and event table.
Symptom: In some recovery(abruptly shutdown) cases, there is inconsistency between staging queue and event table. It may cause duplicate events deliver to end point in recovery.
Resolution: Now, staging queue and event table contains same events.
37232(RTC) XSD generation should pop-up error if space is provided for the "folder" field in the Composite Properties screen.
Symptom: while discovery, if space is provided for the "folder" field in the Composite Properties screen, adapter is not generating the XSD's and not providing the reason for failure.
Resolution: Now adapter displays the error with reason of failure.


This table lists the fixes in Fix Pack version 7.5.0.1.
Fixes
#CRAPARTitleDetails
1103551JR39653 In some cases,the adapter throws exception when user uses the structure inside array of nested structures
Symptom: When the user uses the structure inside array of nested structures and runs a simple outbound operation, the adapter fails.
Resolution: Now the user can use the structure inside array of nested structures with the adapter for an outbound operation.
2103552JR39817 In some cases,the adapter throws exception when user uses the nested array of structures or array of simple data types inside complex array of nested structures.
Symptom: When the user uses the nested array of structures or array of simple data types inside complex array of nested structures and runs a simple outbound operation, the adapter fails.
Resolution: Now the user can use the nested array of structures or array of simple data types inside complex array of nested structures with the adapter for an outbound operation.
3103550JR39476 In some cases, the adapter doesn't show RPG and COBOL program names properly while discovery.
Symptom: While discovery, the adapter displays the RPG and COBOL program names incorrectly.
Resolution: Now the adapter displays the RPG and COBOL program names properly.
4103548 Descriptions(tooltips) of Object type to discover and Globalization should be changed.
Symptom: Descriptions(tooltips) of Object type to discover and Globalization should be changed.
Resolution: Descriptions are changed with appropriate data.
5078510 Description(tooltip) of invalid pcml should provide the reason for invalidity.
Symptom: Description(tooltip) of invalid pcml should provide the reason for invalidity.
Resolution: Description(tooltip) of invalid pcml have changed with the reason for invalidity.
66306(RTC)JR40935 For the PCML having multiple programs(more program tag elements in PCML), then the adapter generating the BO's for one program only.
Symptom: For the PCML having multiple programs(more tag elements in PCML), then the adapter generating the BO's for one program only.
Resolution: Now, Adapter generating the BO's for all the program tag elements in the PCML.




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.3, 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 EMD, delete the connector project in the WID, 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 WPS.
   a. Select "Update" for the corresponding application on the WPS Admin Console.
   b. Select "Single Module" with relative path as name of the rar file - CWYIS_ios.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.



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