| This table lists the enhancements and fixes in fix pack version 7.0.0.4. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 103474 | JR39584 | IBM WebSphere Adapter for Oracle EBS is unable to generate interface. |
| Symptom: The complex type contained in Recrod/table/Array/Object has different type owner with current user's schema.In current version adapter will retreive the metadata of type with the same schema as current user's schema, which will cause the miss type found error. |
| Resolution: Fix the problem and find the type with its own type owner. |
|
| 2 | 103275 | JR39285 | ORACLE EBS- ESD FAILS FOR PROCEDURE WITHOUT PARAMETERS WITH NPE. |
| Symptom: When a procedure is being bind and this procedure doesn't have
input and output parameters a null exception is shown and EMD process can't be finished. |
| Resolution: Fix the problem and handle the exception. |
|
| 3 | 103291 | JR39341 | ORACLE EBS.ESB WRAPPER PROCEDURE NAMES WITH SIMILAR NAMES WERE OVERWRITTEN. |
| Symptom: When generating wrapper with the adapter on procedures with
similar name, a new wrapper procedure name will overwrite
the old wrapper procedure name. |
| Resolution: Fix the problem and add the suffix in the last of new package name. |
|
| 4 | 103294 | JR39340 | ORACLE EBS. INCORRECT SCHEMA CREATED FOR ROWTYPE RECORDS. |
| Symptom: When IBM-ESB reads a procedures schema from Oracle package,
if there is a record or table which is typed as %rowtype.The ESB won't build the record business object fields and schema correctly. |
| Resolution: Fix the problem and generate the wrapper correctly. |
|
| 5 | 102715 | JR38594 | When no PL/SQL Record of table/array returned, the exception throw out during the runtime. |
| Symptom: When generating a procedure call with the WebSphere adapter for oracle e-business suite, the adapter will build a wrapper package. If the original procedure contains the parameter with Table/Array of PL/SQL Record type, the exception will throw out when no record found and returned. |
| Resolution: Fix the problem and handle the exception. |
|
| 6 | 102751 | JR38671 | Discover the stored procedure with Record parameter in other schema failed. |
| Symptom: When using oracleebs adapter connect to EIS with customer's username and passoword, customer try to discover the stored procedure with PL/SQL Record type related parameters in other user's schema, the oracleebs adapter generated the wrapper procedure in current user's schema, which will cause 'datatype missing' problem. |
| Resolution: Fix the problem and generate the wrapper procedure in right schema. |
|
| 7 | 101456 | | Detecting illegal XML characters in SDO DESPI of Adapters. |
| Symptom: We are facing an issue in which a runtime exception is being thrown when the BO generated by the Adapter is being serialized down the line to be transferred over the wire during the BOXML serialization because of invalid xml characters in the BO. |
| Resolution: Provide options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently we have 3 options: (a) Do not validate BO content for illegal XML characters (default); (b) Throw exceptions if BO content contains illegal XML charaters;(c) Discard illegal XML characters in BO content and log. |
|
| This table lists the enhancements and fixes in fix pack version 7.0.0.1. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 77930 | | Printing out the AdapterFoundationClasses version in the Logs/traces. |
| Symptom: Currently with all the adapters , The AFC version is not printed out in the logs/traces. It would be really helpful to have this information printed out to the logs/traces especially in debugging issues due to conflicting AFC being loaded at runtime.
|
| Resolution: print AFC version in the trace |
|
| 2 | 93532 | | Replace XSMode SPI of XSMetaData with SDOUtil.getMaxLength method. |
| Symptom: The method of "getMaxLength" doesn't work fine for the XSMetaData as it can't be resolved by the lastest WPS version(0947.08). So the XSMode SPI of XSMetaData should be replaced with new API of "SDOUtil.getMaxLength". |
| Resolution: Replaced the WAS SPI from the class "com.ibm.xml.sdo.spi.XSMetaData" with new WAS API "com.ibm.websphere.sdox.SDOUtil.getMaxLength()". |
|
| 3 | 99888 | | When adapter gets ARM transaction factory name to process ARM transaction a WAS internal private API is being used. It should be replaced with public interfaces. |
| Symptom: When adapter gets ARM transaction factory name to process ARM transaction a WAS internal private API is being used. It should be replaced with public interfaces. |
| Resolution: Switched to Invoke PmiRmJmxService MBean, a set of public interfaces exposed by WAS to get ARM transaction fatory name. |
|
| 4 | 100262 | | Ambiguous semantics of the max connection number in the event delivery config |
| Symptom: Adapter will not use connection pool for event delivery if max connection number is 1 and delivery mode is "UNORDERED". In this situation, multiple thread will share one connection without thread safe mechanism, which will cause exception.
|
| Resolution: The fix makes connection pool be used when max connection number is 1, connection pool keep thread safe and thus is recommended to use under "UNORDERED" and "ORDERED BY KEY" delivery mode; If user preferred not to use connection pool, he/she could set max connection number to 0, while thread safe will not be guaranteed.
|
|
| 5 | 100346 | | Remove the WAS private API call in adapter code(transaction relate code). |
| Symptom: Some WAS private APIs were used in the previous adapter code. |
| Resolution: Change some transaction relate code by using applicable WAS APIs. |
|
| 6 | 100356 | | Adapter throws NullPointerException when working with two or more modules with the sme business obeject name but different namespace and structure. |
| Symptom: When adapter creates 2 or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. |
| Resolution: Redefined the methods of "hashCode()" and "equals()" in the SDOV1Type class. Then individual adapter can distinguish those BO correctly by "namespace + name" if those BOs name are equal. |
|
| 7 | 100381 | | When "assuredOnceDelivery" is false and there is a event delivery failure, the status of the event is "0" and not changed to "-1". |
| Symptom: When "assuredOnceDelivery" is false and there is a event delivery failure, the status of the event is "0" and not changed to "-1" and the event will be polled infinitely. |
| Resolution: When "assuredOnceDelivery" is false and there is a event delivery failure, the status of the event becomes "-1" successfully. |
|
| 8 | 100406 | | When an application is restarted with Adapter deployed in standalone mode, Adapter throws NullPointerException when querying the ASI information from the cache. |
| Symptom: For Adapter inbound and outbound operation(standalone deployment), after the application is restarted, the NullPointerException will appear when the adapter tries to query the ASI from cache. |
| Resolution: The Business Object's namespace and name has been preserved as Business Object instance's fields. After the application is restarted, adapter can still get them from those instance's field rather than the stale data cache. |
|
| 9 | 100430 | | Memory leak in WAS Inbound with BeanType. |
| Symptom: When adapter caches some BeanTypes that have a great deal of properties, java OutOfMemmory Exception be thrown during performing inbound and outbound operation with some events (persisting 20-50 times in WAS broker). |
| Resolution: The BeanType's class names are preserved as key of cache, rather than BeanType's instance. When broker is WAS, adapter can get BeanType structure referred to its class name. |
|
| 10 | 100710 | | Comes back to "Standard" even if you change to "user-Defined(Dynamic)", When editing the inbound event property "event query type for processing events" in assembly diagram properties view. |
| Symptom: In adapter end-point configuration, the "event query for processing events" property always gets set back to Standard, even if you change the setting. For example, if customer set the property to User-Defined(Dynamic), save it, exit,go back into assembly diagram, the "event query for processing events" property is set back to "Standard" always. |
| Resolution: Change this property listner implementtation, the value will changed by customer selection. |
|