The patch note contains the following sections:
This patch contains the following revisions since the last maintenance
release:
|
Available as of
Version |
APAR/CR Number |
Feature |
Description |
| 2.5.1 | JR 20440 CR 59609 CR 59112 CR 58660 CR 59817 |
Execution of afterretrievebycontent stored procedure in a business object. Adapter fails to open new connection after database went down. Usage of Stored procedure with OP=RS fails. Return Dummy BO with OP=RS |
The adapter failed to execute the stored procedure associated to AfterRetrieveByContentSP.The
same has been resolved. There was an issue with the cleaning of the connection pool when the database went down. This lead to leak of stale connections. The same has been fixed. The tracing mechanism had a defect and has been corrected. The Dummy BO created,when result set is null or empty in a retrieveSP for container, was not being returned . The same has been resolved. |
| 2.5.0.1IF | CR 35078 CR 43390 CR36188 |
Adapter should return APPRESPONSE TIMEOUT if the SPBeforePoll Call Fails. Retrieve of large clob data>30k fails when used with stored procedures for Retrieve. Connector property RetryCountAndInterval does not work for child BO data |
The adapter will now return appresponsetimeout if the stored procedure
call before polling fails. The Retrieve of large clob data using stored procedure is now enabled. The adapter has been enabled to retry retreive on child retrieval failures. |
|
2.4.4 |
JR 20005/ CR 31759/35455/ 35954 |
When collaboration is down, the error message should be emailed if
email collaboration is setup.Currently email is not being sent. For the Delete verb, if the parent BO is a Wrapper BO, multiple
cardinality children of the Wrapper BO are not deleted. When using Copy Attributes to propogate
values down through a hierarchy of Business Objects, such values were not
being propagated for N-cardinality child BOs |
To enable email to be setup , the error
message should be logged with severity. Change has been done to log message
with severity if the severity is FATAL. Unsubscribed objects are now logged
as errors of FATAL type. Multiple cardinality child BOs of a Wrapper
BO are now being deleted when processing the Delete verb. Copy attribute values are now being propagated for N-cardinality
child business objects. |
1. If the connector version is 2.2.0 or above, please check the following:
o Infrastructure version should be 4.0 or above.
o The lib directory under WBI Adapter installation should contain the WBIA.jar
Add, replace, or remove the following files and directories as indicated (Note that these are rolled up in the patch you downloaded):
%APP% is one of: JDBC, i2ADW, OracleApps or MCS.
|
For Connector Version |
Platform |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
| 2.5.1 | WIN & UNIX | Replace the file | %CROSSWORLDS%\connectors\%APP%\CW%APP%.JAR |
|
2.4.4 |
WIN & UNIX |
Replace the file |
%CROSSWORLDS%\connectors\%APP%\CW%APP%.JAR |
Configure the following for the patch to work:
|
Connector |
Platform |
Add / Remove |
Property/Legal values (Case-Sensitive) |
|
- |
- |
- |
- |
5 May 2004
© 2004 IBM Corporation. Proprietary and Confidential. All Rights Reserved.