|
This table lists the enhancements and fixes in fix pack version 6.1.0.6_IF01.
|
|
Enhancements
|
|
There are no enhancements in this fix pack.
|
|
Fixes
|
|
1
|
101832
|
JR37499
|
Connection lost if resonate support throws exception
|
|
Symptom: If Siebel adapter is active and is idle for a long time(resonateSupport = true), then an error will be thrown in the next attempt of connection.
|
|
Resolution: Make a login call if attach call is failed for this scenario.
|
|
|
2
|
100872
|
JR36029
|
At run time null BO getting generated in inbound Siebel Adapter
|
|
Symptom: If the returned BO has more than one child BO, then this BO will contain some null children BO.
|
|
Resolution: Fix the conversion problem for BO has multiple children BO.
|
|
|
This table lists the enhancements and fixes in fix pack version 6.1.0.6.
|
|
Enhancements
|
|
There are no enhancements in this fix pack.
|
|
Fixes
|
|
1
|
77992
|
JR33660
|
In WID, Enterprise service Discovery(ESD) does not work properly: Does not retrieve complete list of BOs from Siebel System.
|
|
Symptom: In WID, ESD does not work properly: Does not retrieve complete list of BOs from Siebel System.
|
|
Resolution: Iteratively adding all the BOs which are selected.
|
|
|
2
|
99998
|
|
Make adapter 6.1 comply with the new WPS v7.0 SDO implementation
|
|
Symptom: Currently the Adapter 6.1 version only supports EMF, and doesn't support XCI.
|
|
Resolution: A fix has been delivered to make Adapter 6.1 comply with the new WPS v7.0 SDO implementation.
|
|
|
3
|
93528
|
JR34574
|
When two different business objects have the same name but different namespaces, inbound/outbound operations may fail.
|
|
Symptom: In multiple applications, if some Business Objects have the same BO name but different BO namespaces, inbound or outbound operation may fail, e.g., retreive may report NullPointerException. This issue impacts both inbound and outbound.
|
|
Resolution: Delivered a fix to not only use BO name but also namespace to differentiate BO during runtime.
|
|
|
4
|
100313
|
JR34869
|
Adapter does not use connectionpool in the first pollcycle during "unordered" delivery
|
|
Symptom: When using "unordered" delivery mode with "maximum connections" larger than 1, connection pool will not be used during the first poll cycle and NPE will be thrown.
|
|
Resolution: A fix has been delivered to have the ActivationSpec for one specific endpoint to be configured before polling for the first cycle, thus enable connection pool be used for "unordered" mode.
|
|
|
This table lists the enhancements and fixes in fix pack version 6.1.0.5.
|
|
Enhancements
|
|
There are no enhancements in this fix pack.
|
|
Fixes
|
|
1
|
76491
|
JR32073
|
SIEBEL ADAPTER THROWS "BASE EXCEPTION" DURING EMD.
|
|
Symptom: When processing EMD for BO,if there is special characters in BC's attributes and select short name, BaseException will be thrown.
|
|
Resolution: Add the support for special characters in BC's attributes in short name situation.
|
|
|
2
|
76490
|
JR32074
|
SIEBEL ADAPTER DOES NOT RETRIEVE CALCULATED VALUE FIELD.
|
|
Symptom: When generating BO, the Calculated fields can't be generated.
|
|
Resolution: Add a new function to generate Calculated fields.
|
|
|
3
|
76333
|
JR31795
|
ADAPTER POLLING STOPS WHEN SIEBEL DB GOES DOWN AND NEVER PROCESS.
|
|
Symptom: For inbound, if the database crashed, the adapter can't resume polling after the database's recovery.
|
|
Resolution: Add a new function to retry after database crash.
|
|
|
4
|
76895
|
|
Adapters don't clean up stale connection after EIS shutdown
|
|
Symptom: After EIS shutdown and restart, adpater may get stale connection for outbound process.
|
|
Resolution: Add function to enable to validate connection before a outbound process.
|
|
|
This table lists the enhancements and fixes in fix pack version 6.1.0.4.
|
|
Enhancements
|
|
There are no enhancements in this fix pack.
|
|
Fixes
|
|
1
|
75833
|
JR30339
|
ESD FAILS WITH ERROR, WHEN PARENT AND CHILD SIEBEL BCS ARE SELECTED.
|
|
Symptom: The issue is during the ESD when a Parent BC and a Child BC is chosen then customer is gettting Operation name 'XXXXXX' matchesanother operation name. Operation overloading is not allowed..
|
|
Resolution: change the code to make sure when adding a non-primary Child BC, the primary BC will be automatically added into the selection list
|
|
|
2
|
76111
|
JR31009
|
PROBLEM CREATING THE BO WITH HYPHENIN ITS NAME THROUGH WID
|
|
Symptom: EMD can not work well with Business object having hyphenin characters in its name.
|
|
Resolution: use unicode character to represent hyphenin characters during EMD
|
|
|
3
|
75915
|
|
Null name space support in base class
|
|
Symptom: Base class doesn't support null namespace using 6.1 adapter
|
|
Resolution: One is adding the Head Alias "xsd:" to all vocabulary scoped in w3c namespace. The other is that cut off those alias with declaration of null namespace from schema.
|
|
|
4
|
93006
|
JR30832
|
Failed to retrievaAll View with a child BO that has one child BO itself
|
|
Symptom: retrieveAll a View with a child BO that has one child BO itself.There is no error message any more, but the result of the query does not match the data in the database.
|
|
Resolution: Change the source code on retrievaAll method and add support for this kind of case
|
|
|
5
|
93077
|
|
"Method is deprecated messages" in the log/console
|
|
Symptom: A lot of warning messages appears in the log/console when the websphere adapter is running
|
|
Resolution: Remove this message from system out.
|
|
|
6
|
93143
|
JR30855
|
Infinite inbound loop when assuredOnceDelivery is false
|
|
Symptom: Infinite inbound loop when assuredOnceDelivery is false
|
|
Resolution: Change the source code to support the case when assuredOnceDelivery is false
|
|
|
7
|
93148
|
|
Improve the adapter exception case
|
|
Symptom: crash or hang situation appears since Base Class does not handle the exception
|
|
Resolution: Fix it by catching the exception thrown by logging and ignore it for making sure the work completion status could be notified to workcontroller.
|
|
|
8
|
93155
|
|
TypeFactory is using ext classloader instead of application classloader in WAS
|
|
Symptom: forName method could not find the record and throws bo not found exception
|
|
Resolution: Change the source code to make sure correct classloader is used
|
|
|
9
|
93182
|
|
English text over the Progress Monitor Indicator
|
|
Symptom: The progress monitor in the first screen of the EMD has hard coded english text.
|
|
Resolution: Modify some source files and also message files to solve this issue
|
|
|
This table lists the enhancements and fixes in fix pack version 6.1.0.2.
|
|
Enhancements
|
|
1
|
95575
|
|
"Finish" button and "Next" button do not get activated
|
|
Symptom: In EMD, when a component that starts with "BCBS" is selected, either the "Finish" button or "Next" button (or both) is not activated.
|
|
Resolution: If a dependent component is added alone, the primary business component is automatically added to the import list.
|
|
|
2
|
89947
|
|
Improve discovery relationships using Siebel API.
|
|
Symptom: Siebel business objects can be discovered in a more efficient way.
|
|
Resolution: A new algorithm for discovering MultiValue lists has been implemented to improve Siebel business object discovery.
|
|
|
Fixes
|
|
1
|
95578
|
JR28322
|
NullPointerException on Siebel Adapter cleanup method
|
|
Symptom: A NullPointerException occurs within the Siebel Adapter cleanup method.
|
|
Resolution: This has been fixed.
|
|
|
2
|
95446
|
JR28059
|
Siebel adapter connnection issue
|
|
Symptom: Because some connections are not successfully logged off during a transaction, new connections being created cause the maximum connection limit to be reached.
|
|
Resolution: The log off problem has been fixed.
|
|
|
This table lists the enhancements and fixes in fix pack version 6.1.0.6_IF01.
|
|
Enhancements
|
|
There are no enhancements in this fix pack.
|
|
Fixes
|
|
1
|
90957
|
|
Configuable retry for failed events.
|
|
Symptom: The adapter continues to redeliver failed events indefinitely.
|
|
Resolution: A new property, FailedEventRetryLimit, has been added to the ActivationSpec. FailedEventRetryLimit allows you to set the number of times the adapter will attempt to deliver an event before marking it as FAILED. This only applies to failures that are normally retried; data binding errors and function selector errors are excluded. If the adapter or server is shut down and restarted, the adapter will start fresh and deliver the event the specified number of times, not counting any retries that were attempted before the adapter was shut down.
|
|
|