This table lists the enhancements and fixes in fix pack version 7.5.0.1. |
Enhancements |
1 | RTC5438/CR103499 | | Monitoring 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 |
1 | RTC5597/CR103402 | JR41054 | Issue 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. |
|
2 | RTC5526/CR103029 | JR41055 | Time 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. |
|
3 | RTC5524/CR103536 | JR41056 | Connection lost after adapter idle in WebSphere Message Broker. |
Symptom: Connection was getting stale if kept idle for long time. |
Resolution: This has been fixed. |
|
4 | RTC5687/CR103627 | JR41057 | Enable detect Illegel XML property only for WID |
Symptom:This property was coming for WMB as well.
|
Resolution: This has been fixed. |
|
5 | RTC5724 | | Adapter 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.
|
|
6 | RTC5700 | | Null 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.
|
|
7 | RTC5766 | | com.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. |
|
8 | RTC5772 | | Exceptions 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. |
|
9 | RTC5987 | | Adapter 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. |
|
10 | RTC5907 | JR41058 | BaseException 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. |
|
11 | RTC6118 | JR41059 | Error 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. |
|
12 | RTC6207 | | ConnectionRetry 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. |
|
13 | RTC6349 | JR41062 | EventManager 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. |
|
14 | RTC6313 | JR41063 | DuplicateRecordFault 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. |
|
15 | RTC6274 | JR41064 | Error 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. |
|
16 | RTC6232 | JR41065 | Connection 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. |
|