IBM WebSphere Adapter for Siebel, 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 enhancements and fixes in interim fix version 7.5.0.3.
Enhancements
#CRAPARTitleDetails
Fixes
#CRAPARTitleDetails
1RTC 701143200Show error on empty result set should be unchecked by default for Business Service
Symptom: Show error on empty result set should be unchecked by default for Business Service but its coming as checked. Also this property should be visible in property tab post EMD completion
Resolution:This is now fixed
2RTC 731143205 Logic to check the encoding/codepage to connection establishment is not correct.
Symptom: Logic to check the encoding/codepage to connection establishment is not correct.In some cases currently adapter throws codepage related exception even though the codepage value is correct
Resolution: Currently Siebel Data Bean API jar does not provide any mechanism to detect the codepage error so now the logic to detect illegal codepage is removed from the code.A more generic exception will be thrown now.
3RTC 8474 Enable Inbound Event Monitor not available on Siebel 7.5.0.3
Symptom: Inbound Event Monitor check box missing for Siebel Inbound scenario .
Resolution: This is fixed, check box is now available to enable events.

This table lists the enhancements and fixes in interim fix version 7.5.0.2.
Enhancements
#CRAPARTitleDetails
Fixes
#CRAPARTitleDetails
1RTC 6228Connection retry to Siebel server should not happen in case of invalid username or password.
Symptom: Connection retry was happening for inbound scenario in case of incorrect user or password.
Resolution:This is now fixed
2RTC 6933Individual Adapter changes on Inbound Recovery (Child for AFC defect RTC -6819 ).
Symptom: Inbound polling is not considering XID value while polling .
Resolution:Adapter now polls for event with XID null.
3RTC 7107JR42249Siebel inbound scenario fails if number of records exceed 10,000 in event table.
Symptom: Siebel adapter fails with max record exceeded exception.
Resolution: This is now fixed

This table lists the enhancements and fixes in interim fix version 7.5.0.1_IF01.
Enhancements
#CRAPARTitleDetails
Fixes
#CRAPARTitleDetails
1Upgraded AFC to 7.5.0.1_IF01.
Symptom: Check AFC Read me for details.

This table lists the enhancements and fixes in fix pack version 7.5.0.1.
Enhancements
#RTC/CRAPARTitleDetails
1RTC5438/CR103499Monitoring of Adapter connection events on WMB.
CEI events are now emitted at the following points: connection success, connection failure, connection close and authentication failure.
Resolution: This enhancement is delivered..
Fixes
#RTC/CRAPARTitleDetails
1RTC5597/CR103402JR41054Issue in EMD run while using Position BC under Account - ESP BO.
Symptom:There is no relation between Position BC and Account BC in the generated artifacts.
Resolution: This is now fixed.
2RTC5526/CR103029JR41055Time take to discover top level objects is very high for Siebel adapter.
Symptom: During EMD run, time take to discover top level objects was very high.
Resolution:Performance changes delivered for it.
3RTC5524/CR103536JR41056Connection lost after adapter idle in WebSphere Message Broker.
Symptom: Connection was getting stale if kept idle for long time.
Resolution: This has been fixed.
4RTC5687/CR103627JR41057Enable detect Illegel XML property only for WID
Symptom:This property was coming for WMB as well.
Resolution: This has been fixed.
5RTC5724Adapter error message - 'Failed to establish event manager while deploying inbound module'
Symptom: BO Inbound scenario deployment was failing with mentioned error message.
Resolution: This has been fixed.
6RTC5700Null Pointer Exception when opening adapter in property tab.
Symptom: NPE was coming in property tab for both inbound and outbound.
Resolution: This has been fixed.
7RTC5766com.ibm.adapter.framework.BaseException in Inbound Business Services EMD.
Symptom: Exception was coming when IO is selected after enabling the wrapper property.
Resolution: This has been fixed, wrapper property not applicable for inbound.
8RTC5772Exceptions seen in InvalidRequestFault xsd while saving Business Service Outbound project.
Symptom: Error were coming in the workspace after running EMD.
Resolution: This has been fixed.
9RTC5987Adapter throwing exception in EMD screen - Event types to process: Illegal String format followed by list of operations supported.
Symptom: This exception was coming for BO inbound scenario intermittently.
Resolution: This has been fixed.
10RTC5907JR41058BaseException in last EMD screen for delete,update,insert SiebelContact for BS-Outbound .
Symptom: Artifacts were not getting generated, EMD failing with mentioned error.
Resolution: This has been fixed.
11RTC6118JR41059Error in xsd for delete,update,insert SiebelContact for BS-Outbound .
Symptom: EMD run was completing but xsd had errors, this was coming since only when more then one operation is selected.
Resolution: This has been fixed, duplication bo logic was incorrect.
12RTC6207ConnectionRetry PropertyGroup missing in last but one EMD screen for outbound scenario .
Symptom: ConnectionRetry PropertyGroup missing in last but one EMD screen for outbound scenario .
Resolution: This has been fixed, now property group is coming.
13RTC6349JR41062EventManager unable to close the connection to EIS when a polling related exception occurs and stopPolling property is enabled.
Symptom: Exception was thrown since endpoint was unavailable, but event manager was not shutting down.
Resolution: This has been fixed, logic is added to close the connection only for the first invocation call.
14RTC6313JR41063DuplicateRecordFault not thrown.
Symptom: DuplicateRecordFault not thrown while performing a create operation with account and business address values already existing in the database.
Resolution: This has been fixed.
15RTC6274JR41064Error Thrown - The resource adapter named 'IBM WebSphere Adapter for Siebel Business Applications' returned the following error: 'null'.
Symptom: Exception in EMD for Business Service Outbound - Select Insert and Query in EAI Siebel Adapter and EAI Siebel Adapter I..
Resolution: This has been fixed.
16RTC6232JR41065Connection retry mechanism not working for outbound when code page is not set.
Symptom: Connection retry mechanism not working for outbound when code page property is not set.
Resolution: This has been fixed.


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. To update deployed applications(that have an embedded adapter RAR file) on the WebSphere Process Server,use the following procedure
   a. Stop the application that needs to be updated,using the WebSphere Process Server admin console
   b. Select Update for the corresponding application in the WebSphere Process Server admin Console.
   c. Select Replace or add a single file option with relative path as name of the rar file - CWYES_SiebelAdapter.rar.
   d. Click the Browse button to select the updated RAR file on your local file system.
   e. Select the default values for the consecutive steps and select Finish.This will ensure that existing configurations e.g. MCF,are not changed and the JAR files are only updated.



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