Readme for Fix Pack version 4.4.2 of WBI Adapter for Siebel eBusiness Applications


The patch note contains the following sections:
 

 

CONNECTOR REVISIONS

UPGRADE INSTRUCTIONS


CONNECTOR REVISIONS   

This patch contains the following revisions since the last maintenance release:

 

 

Available as of Version

CR Number/APAR#

Feature

Description

4.4.2

34891/JR 19894

In the life time of the adapter a single/reserved databean is used for polling. In Siebel 6.x application proper release of resources is not happening and resources are piling up. So after some point the adapter crashes. So as a solution adapter will refresh the polling bean after the bean has been used for 'DatabeanRefreshInterval' of times.

Adapter against Siebel 6.x Financial is crashing after 1400 poll calls.

4.4.2 33368/JR 19894 Adapter is not restarting even if the RestartRetryCount, RestartRetryInterval standard properties are set. The same has been fixed.
4.4.2 30307/JR 19894 After the update operation, adapter is not dumping the BO even when the update operation is successful. The same has been fixed.

4.4.2

33632/JR 19894

Siebel datatype, DTYPE_NUMBER,  is converted to Integer by the SiebelODA. This needs to be converted to Float.

SiebelODA converts the Siebel datatype, DTYPE_NUMBER to Integer instead of Float.

 

The same is converted as Float now.

Note: The adapter treats all data to be of String datatype and hence does not use the datatypes converted by the ODA

4.4.2

35131/JR 19898

App-text set incorrectly in wrapper business object definition.

SiebelODA sets the app-text in a wrapper business object definition as ObjectName= <object name>, instead of ON=<object name>, where <object name> is the name of the Siebel Business Object.

 

The app-text is now set as ON=<object name>

4.4.1

33305/JR19414

Cleaning up the sessions when shutting down the adapter

All the opened sessions/tasks are shut down with the shutdown of the adapter.

4.4.1

30184/JR19414

Support for retrieval of multiple records with verb RetrieveByContent

The same has been supported by the adapter. Adapter now retrieves multiple records if found when the verb is RetrieveByContent.

4.4.1

30731/JR19414

Creation of child and grand child integration objects not working properly when multiple instances of them were specified.

The issue has been fixed.

4.4.1

 

 

29378/JR19219

 

SiebelODA issue with generation of Integration Objects/Components against older versions of the Siebel Application. (6.2)

The issue has been resolved. A new configuration property ‘SiebelVersion’ has now been added to distinguish between the Siebel Application Versions.  By default, no value needs to be given for this property, if the Siebel Application Version is 7.X (for example 7.5.3).  If the Siebel Application Version is 6.X, (for example 6.2), the value of the property could be set to 6.X. In fact, with the exception of an empty string, 7.X, 7.x or a string of spaces, any other value can be set on this property to connect to Siebel Application Version 6.X.



UPGRADE INSTRUCTIONS

  1. Apply the changes prescribed in each table below, beginning with the entries at the bottom of each table and working up to the most recent patch.

Add, replace, or remove the following files and directories as indicated (Note that these are rolled up in the patch you downloaded):

%APP% is Siebel.

 

 

For Connector Version

Platform 

Add / Replace / Remove

File (Starting from %CROSSWORLDS%/$CROSSWORLDS)

4.4.1

WIN & UNIX

Replace the file

%CROSSWORLDS%\connectors\%APP%\CW%APP%.JAR

%CROSSWORLDS%\ODA\%APP%\%APP%ODA.JARd

 %CROSSWORLDS%\ODA\messages\%APP%OdaAgent.txt

 

 

 

 

 

 

 

 

Configure the following for the patch to work:

 

 

Connector
Version

Platform

Add / Remove

Property/Legal values (Case-Sensitive)

   -

   -

  -

  -


Jan 29, 2004 4:54 PM

© 2004 IBM Corporation. Proprietary and Confidential. All Rights Reserved.