Fix (APAR):  JR29736

Status:  Fix

Release:  6.1.0.2,6.1.0.1

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  NONE

CMVC Defect:  JR29736

Byte size of APAR:  22013

Date: 2008-07-18

Abstract:  The Fixed width data handler is unable to determine the number of objects in the list dynamically.

Description/symptom of problem:  
JR29736 resolves the following problem:

ERROR DESCRIPTION:                                              
Using the FixedWidth or delimited databindings does not allow   
for variable length arrays.  Since length of arrays is often not
known prior to runtime, this is unacceptable.                   
                                                                
This functionality was present in legacy versions for use with  
the WBIAdapters                                                 

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
Websphere Process Server and Websphere
Enterprise Bus Server 6.1.0.x users who are
using the Fixed width data handler and have
lists with variable length objects.

PROBLEM DESCRIPTION:
The Fixed width data handler is
unable to determine the number of
objects in the list dynamically.

RECOMMENDATION:
None

The problems is fixed by adding an annotation in the business
object schema to indicate the business object property that
corresponds to the count of the objects in the list at runtime.

PROBLEM CONCLUSION:                                             
Applying this interim fix will resolve the problem.             


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information:  Problem:
WebSphere Process Server user is unable to determine the number of child objects dynamically.

Solution:
Consider the following scenario. There is a customer business object that contains a list of address business objects. The number of address business objects that are received at runtime is determined by the value of the property called ?count? in the Customer business object. This is indicated by an annotation on the address property in the Customer schema.

Customer.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bons0="http://www.ibm.com/crm1" targetNamespace="http://www.ibm.com/crm1">
	<xsd:include schemaLocation="AnnotatedAddress.xsd"/>
	<xsd:annotation>
    <xsd:appinfo source="commonj.connector.asi">
    	<asi:annotationSet xmlns:asi="commonj.connector.asi" asiNSURI="http://www.ibm.com/wbiserver/datahandlers/metadata">
    	</asi:annotationSet>
    </xsd:appinfo>
  </xsd:annotation>
 
<xsd:complexType name="AnnotatedCustomer">
    <xsd:sequence>
        <xsd:element minOccurs="0" name="id" type="xsd:string"/>
	  <xsd:element minOccurs="0" name="count" type="xsd:int"/>
	  <xsd:element maxOccurs="unbounded" minOccurs="0" name="address"  type="bons0:AnnotatedAddress">
            <xsd:annotation>
		    <xsd:appinfo source="http://www.ibm.com/wbiserver/datahandlers/metadata">
 		        <metadata:BOPropertyNameASI xmlns:metadata="http://www.ibm.com/wbiserver/datahandlers/metadata">
                    <metadata:propertyNameForCount>count</metadata:propertyNameForCount>
						</metadata:BOPropertyNameASI>
        	    </xsd:appinfo>
		</xsd:annotation>
	</xsd:element>
    </xsd:sequence>
</xsd:complexType>
</xsd:schema>

Please note that the count field has to appear before the list field in the schema. When specifying the field width in the properties for this case, the width for every field of address is listed only once.
The first annotation is for the business object to be anchored with the application specific editor in WID.