Product Documentation
Abstract
WebSphere Adapters provide periodic fixes for editions of release version 6.2 and 7.0. The following is a listing of those fixes along with the corresponding Rational Application Developer versions with which they are packaged.
Content
The following list describes the WebSphere Adapters versions and the fixes for that version packaged with Rational Application Developer version 7.5.5.2
| Adapter | APAR | Description |
| JDE V7.0.0.1 | When adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | |
| 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 Infor from cache. This has been fixed. | ||
| 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 WebSphere Application Server broker). This has been fixed. | ||
| When adapter gets ARM transaction factory name to process ARM transaction, a WebSphere Application Server internal private API is used for it, which need to be replaced with public interfaces. This has been fixed. | ||
| 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. This has been fixed. | ||
| Currently with all the adapters the AFC version is not printed out in the logs/traces. It is helpful to have this information printed out to the logs/traces especially in debugging issues due to conflicting AFC being loaded at runtime.This has been fixed. | ||
| OracleEBS V7.0.0.1 | Currently with all the adapters the AFC version is not printed out in the logs/traces. It is helpful to have this information printed out to the logs/traces especially in debugging issues due to conflicting AFC being loaded at runtime. This has been fixed. | |
| The method of "getMaxLength" does not work fine for the XSMetaData as it can not be resolved by the lastest WebSphere Process Server version(0947.08). So the XSMode SPI of XSMetaData should be replaced with new API of "SDOUtil.getMaxLength". This has been fixed. | ||
| When adapter gets ARM transaction factory name to process ARM transaction a WebSphere Application Server internal private API is being used. It should be replaced with public interfaces. This has been fixed. | ||
| 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. This has been fixed. | ||
| Some WebSphere Application Server private APIs were used in the previous adapter code. Changed some transaction relate code by using applicable WebSphere Application Server APIs. This has been fixed. | ||
| When adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | ||
| When "assuredOnceDelivery" is false and there is an event delivery failure, the status of the event is "0" and not changed to "-1" and the event will be polled infinitely. This has been fixed. | ||
| 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. 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.This has been fixed. | ||
| 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 WebSphere Application Server broker). The BeanType's class names are preserved as key of cache, rather than BeanType's instance. When broker is WebSphere Application Server, adapter can get BeanType structure referred to its class name.This has been fixed. | ||
| 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. Change this property listner implementtation, the value will changed by customer selection. This has been fixed. | ||
| PeopleSoft V7.0.0.1 | 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. This has been fixed. | |
| 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.This has been fixed. | ||
| When adapter gets ARM transaction factory name to process ARM transaction, a WebSphere Application Server internal private API is used for it, which need to be replaced with public interfaces. This has been fixed. | ||
| When adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | ||
| 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 Infor from cache.This has been fixed. | ||
| 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 WebSphere Application Server broker). This has been fixed. | ||
| SAP V7.0.0.1 | A java.lang.NullPointerException is thrown when an application is configured for AEP Inbound processing with Non Unicode SAP Systems This problem is now fixed. | |
| With the AEP interface, event data being returned as blank eventhough there is data available for the fields. This problem is now fixed. | ||
| BAPI Work Unit doesnt update data successfully when JCO Reset is enabled This problem is now fixed. | ||
| No value fields are being set to "CxIgnore" during AEP Inbound This problem is now fixed. | ||
| AEP - Delete archived events are not being deleted correctly This problem is now fixed. | ||
| AEP - Delete queue events not working This problem is now fixed. | ||
| AEP - Log updates not working This problem is now fixed. | ||
| Error appear when invoke BAPI update two times with JCO reset on WMB7 This problem is now fixed. | ||
| Inbound Processing with extended IDocs does not work This problem is now fixed. | ||
| Error message when building a new SAP request adapter connection (Changing Parameters). This problem is now fixed. | ||
| Empty tags are included in the message if the fields are followed by other populated fields, but all unpopulated fields at the end of a segment do not have empty tags outputted xml. This problem is now fixed. | ||
| BCD Value corrupt during a BAPI call when the underlying locale uses COMMA (,) for a decimal DOT (.) This problem is now fixed. | ||
| SAP Input node doesnt work correctly under SAP Load Balancing setup This problem is now fixed. | ||
| when RuntimeException thrown in Session Bean, two ALEAUD generated This problem is now fixed. | ||
| IDoc Data from the second/child segments is not processed - AEP Oubound This problem is now fixed. | ||
| When you send an IDoc that is not properly constructed from WebSphere Message Broker to SAP using SAP Adapter, the SAP Adapter does NOT pass it over to SAP at all (which is correct behaviour) - but does NOT throw any error message about the fact that the IDoc is not correct. This has to be fixed, so that the adapter will report an error when it receives an invalid IDoc. This problem is now fixed. | ||
| Retries not stopping though the adapter is stopped This problem is now fixed. | ||
| When connection to SAP System with the default value as sapgw00 in EMD, but the system Number is 02, user need to modify it manually to sapgw02 in the last panel of EMD. This problem is now fixed. | ||
| Consecutive requests followed by a failed AEP outbound request FAIL This problem is now fixed. | ||
| Load balancing-Not required connect properties should be disabled This problem is now fixed. | ||
| Problems with BAPI result set call with a queryBO that has multiple entries This problem is now fixed. | ||
| The SAP BAPI fault to show the right error code returned from SAP This problem is now fixed. | ||
| The SAP BAPI fault shows only the ID and does not include the Number This problem is now fixed. | ||
| When BO name is same and BO namespace is different, inbound work may be failed This problem is now fixed. | ||
| Adapter will encoutner NPE after restart the app on server. This problem is now fixed. | ||
| Memory leak in WebSphere Application Server Inbound with BeanType This problem is now fixed. | ||
| Printing out the AdapterFoundationClasses version in the Logs/traces is not available. This problem is now fixed. | ||
| Siebel V7.0.0.1 | 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.This has been fixed. | |
| When adapter gets ARM transaction factory name to process ARM transaction, a WebSphere Application Server internal private API is used for it, which need to be replaced with public interfaces. This has been fixed. | ||
| 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.This has been fixed. | ||
| When adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException.This has been fixed. | ||
| 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 Infor from cache This has been fixed. | ||
| When the name of Integration object (IO) and Integration Component (IC), the schema file for service binding will missed after EMD. Added a prefix "BS" for schema file if generated file has same file name and has been fixed. | ||
| During EMD, NullPointerException will occur if an integration object (IO) has been chosen as input for several times. Added a filter to handle duplicated IO selections and has been fixed. | ||
| If primary key field in WBIA adapter project is not the same as EIS side, runtime will have error after migration to JCA.This has been fixed. | ||
| 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 WebSphere Application Server broker).This has been fixed. |
| Adapter | APAR | Description |
| JDE V6.2.0.3 | JR34574 | When Adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw a NullPointerException. This has been fixed. |
| During Adapter inbound and outbound operations (standalone deployment), after the application is restarted, a NullPointerException is thrown when the adapter tries to query the ASI from cache. This has been fixed. | ||
| When ARM is enabled in WebSphere Process Server/WebSphere Application Server administrative console, but the ARM transaction Factory name is set to ""(empty string), ClassNotFound exception will be thrown when performing inbound/outbound operation. This has been fixed. | ||
| Currently the Adapter V6.2 only supports EMF, and does not support XCI. The adapter V6.2 has been made to comply with the new WebSphere Process Server V7.0 SDO implementation for XCI support. | ||
| WebSphere adapter for JDE can not find the BG of the migrated BO. This has been fixed. | ||
| WebSphere adapter for JDE will throw NullPointException if you migrate your existing project from adapter version 6.1 to 6.2 and then rerun external wizard. This has been fixed. | ||
| WebSphere adapter for JDE can not properly handle the stale connections in the connection pool. This has been fixed. | ||
| Added support for WebSphere Business Monitor. | ||
| Added support for "runOnError" functionality for business function. | ||
| Support returning multiple errors and each error is stored in its own business function. | ||
| JDE Adapter tries to case a JAVA.LONG.INTEGER to a JAVA.LONG.LONG resulting in a ClassCastException. This has been fixed. | ||
| Currency support for JDE tool 8.97. | ||
| OracleEBS V6.2.0.4 | When 'assuredOnceDelivery' is false and there is an event delivery failure, the status of the event is being set as '0' instead of '-1' and the event is polled infinitely. This has been fixed. | |
| When a stored procedure returns more than 1000 resultsets, a NumberFormatException is thrown. This has been fixed. | ||
| The endpoint configuration 'event query type for processing events' gets reset to 'Standard' even if it is changed to 'user-Defined (Dynamic)' and saved. This has been fixed. | ||
| Standalone adapter fails to work in a sequence of local and global transactions. This has been fixed. | ||
| When an XA DataSource is configured and the XA transaction is enabled, if a delete operation fails, adapter may cause database deadlock. This has been fixed. | ||
| When there is an In/Out LOB parameter in stored procedure or stored function, Outbound operation will throw a 'Parameter Type Conflict' exception or 'Invalid column type' exception. This has been fixed. | ||
| When Adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw a NullPointerException. This has been fixed. | ||
| During Adapter inbound and outbound operations (standalone deployment), after the application is restarted, a NullPointerException is thrown when the adapter tries to query the ASI from cache. This has been fixed. | ||
| When ARM is enabled in WebSphere Process Server/WebSphere Application Server administrative console, but the ARM transaction Factory name is set to ""(empty string), ClassNotFound exception will be thrown when performing inbound/outbound operation. This has been fixed. | ||
| Currently the Adapter V6.2 only supports EMF, and does not support XCI. The adapter V6.2 has been made to comply with the new WebSphere Process Server V7.0 SDO implementation for XCI support. | ||
| The function in package of Oracle E-Business Suite which DB version is above 10.2.0.3 could not be imported by WebSphere Adapter for Oracle E-Business Suite successful. This has been fixed. | ||
| The WebSphere Adapter for Oracle E-Business Suite does not use bind variables and lead to reducing database performance in inbound service. . | ||
| When using "unordered" delivery and "maximumConnections" is greater than 1, connectionPool is not used to deliver events within the first poll cycle.This has been fixed. | ||
| The property "additional properties" could not work in WebSphere Adapter for Oracle E-Business Suite inbound. This has been fixed. | ||
| WebSphere Adapter for Oracle E-Business Suite maps the Date/Time/Timestamp SQL to SDO string by default. Now, OracleEBS adapter provides an optional check box to allow the user to change the default data type mapping. When the check box is checked OracleEBS adapter will map the Date/Time/Timestamp SQL type to Date/Time/DateTime SDO type by default. | ||
| The SQL statement input field for Query BO and Batch SQL BO is a single-line editor. OracleEBS adapter now provides a multi-line editor for the SQL statement input field. | ||
| For some special three or more level BO structure, the child BO may be updated unexpectedly. This has been fixed. | ||
| For some special three or more level BO structure, the child BO may be created unexpectedly. This has been fixed. | ||
| JR32227 | WebSphere Integration Developer (6.1.x and 6.2.x) Enterprise Metadata Discovery wizard for OracleEBS adapter generates incorrect SQL for batch SQL BO: 1. Uppercase is converted into lowercase incorrectly. 2. Special character is not escaped correctly. Both these have been fixed. | |
| When the foreign key value of BO is null, OracleEBS adapter returns a child object, but all attributes of this child object are null. This has been fixed. The child object will be unset. | ||
| OracleEBS adapter displays RecordNotFoundException error when it tries to update the foreign key value to another valid value. This has been fixed. | ||
| JR32553 | OracleEBS adapter displays exception when NULL is provided as parameter value for stored procedure that has a complex parameter data type (STRUCT, TABLE, VARRAY etc). Null values for complex data type parameters for stored procedures in now supported. | |
| Support for WebSphere Business Monitor | ||
| In a multiple card update operation delete the child when KeepRelationShip is true. This has been fixed. | ||
| RetrieveAll operation with multi-level child BOs does not return all the records. This has been fixed. | ||
| Only the last input data is returned when executing a stored procedure with nested array parameter. This has been fixed. | ||
| PeopleSoft V6.2.0.3 | PeopleSoft Adapter fails with JOAException when setting get keys during the second time for Update operations. This has been fixed. | |
| When Child BO has no primary key ASI, Update operation fails in some cases. This has been fixed. | ||
| When CI has no get keys or get() method is not available in EIS side, the response of a create operation fails with JOAException. This has been fixed. | ||
| When IgnoreEffectiveSequence and InsAtOldestEffDtPos are set to true and EIS has no child, if input data contains child, the operation fails. This has been fixed. | ||
| When KeepRelations is false, EIS has child/children and input data has no child, Update operation returns incorrect response that has a dummy child; it sometimes even returns a dummy child with a non dummy grand child. This has been fixed. | ||
| JR34574 | When Adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw a NullPointerException. This has been fixed. | |
| During Adapter inbound and outbound operations (standalone deployment), after the application is restarted, a NullPointerException is thrown when the adapter tries to query the ASI from cache. This has been fixed. | ||
| When ARM is enabled in WebSphere Process Server/WebSphere Application Server administrative console, but the ARM transaction Factory name is set to ""(empty string), ClassNotFound exception will be thrown when performing inbound/outbound operation. This has been fixed. | ||
| Currently the Adapter V6.2 only supports EMF, and does not support XCI. The adapter V6.2 has been made to comply with the new WebSphere Process Server V7.0 SDO implementation for XCI support. | ||
| Support has been added for generic fault BO to contain error message and error code for API call. | ||
| When using "unordered" delivery and "maximumConnections" is greater than 1, connectionPool is not used to deliver events within the first poll cycle.This has been fixed. | ||
| retrieveALL gives NPE when Set "unset" for the input fields and maxRecords value < record number in DB. This has been fixed. | ||
| Added support for WebSphere Business Monitor. | ||
| SAP V6.2.0.4 | JR29884 | When the Import or Export section of a BAPI (instead of the Tables section) contains tables then a BAPI fails with the error 'Cannot convert field CONFIG of type TABLE to JCO.Structure'. This has been fixed. |
| Receiving partner not found in EMD (Configure Composite Properties) for extension IDocs. This has been fixed. | ||
| JR33557 | The JCA SAP ALE Passthough adapter incorrectly posts IDoc control records multiple times for IDoc packets. The first IDoc's output is as expected. Then the second IDoc show IDoc_01's control record then IDoc_02's control record and so on. This has been fixed. | |
| JR32715 | JCA SAP Adapter contains unnecessary debug messages when using QISS functionality. These have been removed. | |
| JR32706 | The adapter will be up and processing as expected. Without warning the ABAP logic on the SAP host is updated and some global variables are changed. After the update the adapter does not retrieve the new values and continues to process using the old values. This has been fixed. | |
| Calling a BAPI (such as BAPI_USER_GET_DETAIL) on SAP using Adapter works fine, but gives misleading ERROR messages in the SystemOut.log. This has been fixed. | ||
| JR34330 | Inbound processing with extended idocs does not work when qrfc is configured. It produces this error - Basic type or extension does not exist. This has been fixed. | |
| JR34424 | When using a registered namespace on the SAP system for BAPI artifacts, the SAP adapter throws exceptions such as 'Business Object definition for SapStfcWriteToTopicWrapper in namespace ... not found'. This has been fixed. | |
| JR34365 | Empty tags are included in the message if the fields are followed by other populated fields, but all unpopulated fields at the end of a segment do not have empty tags outputted xml. This has been fixed. | |
| JR32699 | Sap ale outbound throws this error - exception while getting accessor. This has been fixed. | |
| JR33266 | JCA SAP Adapter fails to receive a passthrough idoc with czech characters. This has been fixed. | |
| JR30725 | When adapter finds that a received idoc is designated for one of the applications, it internally sends it to all the applications. This has been fixed. | |
| JCA SAP adapter is unable to find an accessor for bapi fields of type string. This has been fixed. | ||
| JR29813 | Data is not getting updated in sap even though BAPI_transcation_COMMIT is found in the logs. This has been fixed. | |
| JR31593 | Multiple applications deployed have the same thread id during inbound. This has been fixed. | |
| If set retryLimit a valid value (like 20), adapter will continue retrying connection even if it's stopped/undeployed, until it reaches the retryLimit times (20). This has been fixed. | ||
| Ability to split idoc packets using ALE pass through outbound. | ||
| Adapter does not poll the non-unicode transport files events. This has been fixed. | ||
| With the AEP interface Event data is being retuned as blank even though there is data available for the fields. | ||
| Whenever there is no value for a field being sent to an AEP inbound node, the value is being set to CxIgnore. This has been fixed. | ||
| AEP transports - delete archive events does not delete from correct archive table. This has been fixed. | ||
| SAP transports - when delete queue events operation is executed ,it does not delete from the correct event table. This has been fixed. | ||
| AEP transports - The logging is not being done correctly, it points to the old ABAP code. This has been fixed. | ||
| During AEP oubound, the IDoc Data present across second consecutive segments and their child segments is not processed by the adapter. This has been fixed. | ||
| All the consecutive requests followed by a SAP Adapter AEP Outbound request execution fail. This has been fixed. | ||
| JR35196 | During adapter startup, any pre-queued events existing in the event table are not getting processed. This has been fixed. | |
| As part of the SAP Adapter functionality provide the option to WAIT for a configured amount of time when executing the BAPI_TRANSACTION_COMMIT. This has been fixed. | ||
| BAPI module throws jco_error_null_handle while reusing pool connection (stale connection fix). This has been fixed. | ||
| All the BAPI runtime - detailed traces are changed to Trace.Finest level, earlier it was at Trace.Info level. This has been fixed. | ||
| Running a BAPI outbound scenario with a field of JCO BYTE type, adapter will fail while setting the value from adapter. This has been fixed. | ||
| JR29537 | Fix for the trfc/qrfc functionality. | |
| SAP Inbound Adapter to optionally output a configured hex-bin IDoc. This has been added. | ||
| JR31171 | When using QISS module to retrieve data from such a system BO gets filled wrong as soon as table contains multibyte chars. This has been fixed. | |
| JR31592 | The current BO framework cannot handle the anonymous data type. This has been fixed. | |
| No any address data returned in a single application with 3 BAPIs. This has been fixed. | ||
| When an IDoc is sent that is not properly constructed from WMB to SAP using SAP Adapter, the error handling is not correct. This has been fixed. | ||
| Adapter throws date parse exception when the JavaBean has java.util. This has been fixed. | ||
| JR29885 | Commit or rollback on BAPI transaction should be done as per the containers decision. This has been fixed. | |
| JR29531 | Integer fields have a value of 00010 in their input message.But, However when looked in SAP System, the values are being seen as zero. | |
| JR29879 | When decimal fields are present in BAPI, errors are seen in the return type. This has been fixed. | |
| JR34939 | The names for the Control Record and DataRecord are either 'Short SAP generated names in UPPERCASE or Camel case' or 'Long Names basedon SAP field descriptions'. This has been fixed. | |
| JR32384 | When building data types to be used with BAPI module, the field length testing policy is somewhat unclear. This has been clarified in the EMD screen. | |
| JR33598 | When importing an IDoc and selecting 'use SAP field names' the field names are now camel case, they were previously uppercase. | |
| The JCA SAP Adapter fails when invoking an outbound BAPI that contains a TIME files stored as a TABLE parameter. This has been fixed. | ||
| Time field value is passed to SAP in incorrect format. This has been fixed. | ||
| JR29741 | ESD wizard connects to SAP (Outbound Adapter, BAPI call), with a Filter of CRMXIF_IBASE_SAVE specified. This has been fixed. | |
| JR31614 | Problem when writing a BO into SAP using BAPI-Calls (Outbound). If there is a BO which has decimal datatypes and an attribute value is '0', then SAP receives useless content as '5=7.0000000'. This has been fixed. | |
| JR34494 | JCA SAP adapter fails to receive a passthrough idoc with Chinese characters. This has been fixed. | |
| Load balancing - not required connect properties are not disabled. This has been fixed. | ||
| When connecting to cwd31, the default value is sapgw00 in EMD, but the system Number is 02, user need to modify it manually to sapgw02 in the last panel of EMD. This has been fixed. | ||
| Empty tags are included in the message if the fields are followed by other populated fields, but all unpopulated fields at the end of a segment do not have empty tags outputted xml. This has been fixed. | ||
| JR33388 | CBE names are not unique and semantic equalized. This has been fixed. | |
| The bo definition sap adapter generates requires 'minoccurs=1' at least once. This has been fixed. | ||
| JR34178 | When an exception is thrown , the exception is not included as a part of the fault message. This has been fixed. | |
| Some informational messages are tagged asError (message type 'E'). This has been fixed. | ||
| JR32652 | The update by the first bapi is not effected to SAP DB but those by the second one is effected. This has been fixed. | |
| The errorCode only contains NUMBER, does not include ID. This has been fixed. | ||
| When a BAPI fault currently thrown does not display the right error code as returned on SAP Gui. This has been fixed. | ||
| When an invoke for a BAPI result set call with a query BO that has multiple entries is sent to adapter, just the first entry from queryBO is processed to the SAP system. This has been fixed. | ||
| When RuntimeException thrown in the endpoint (e.g. session bean), there are two ALEAUD iDocs generated. One is with success code, one is failed code. This has been fixed. | ||
| JR35118 | When the sap input node connects to the SAP Load balancing setup, it only gets IDocs or picks up events from the server specified in the Gateway Host. This has been fixed. | |
| JR34964 | JCA SAP Adapter corrupts bcd value in BAPI call when locale has a comma as decimal separator. This has been fixed. | |
| JR34652 | Error message is thrown when building a new sap request adapter connection. This has been fixed. | |
| The update operation fails with reset client in mutiple BAPI in one interface. This has been fixed. | ||
| The xsd schema generated by the JCA SAP ESD marks some control fields as required. However, the adapter treats these fields as optional and does not add those elements into an output message. This has been fixed. | ||
| The checkbox 'Use wait parameter before calling BAPI commit' exists in both 'Configure Composite Properties' panel and 'Service Generation and Deployment Configuration' panel whatever CWYAP_SAPAdapter_Tx.rar or CWYAP_SAPAdapter.rar build, but the checkbox is effective only in the 'Configure Composite Properties' panel. This has been fixed. | ||
| When a decimal value or negative value is entered for RetryLimit and RetryInterval properties, no error is reported. This has been fixed. | ||
| By default, connection RetryInterval is not disabled. It has now been disabled by default. | ||
| The bo definition sap adapter generates requires minoccurs=1, but it should generate minoccurs=0. This has been fixed. | ||
| JR33249 | When there are one or more DATE fields in the return BAPI, the adapter needs to be tuned for better performance. This has been fixed. | |
| For both Async and Sync mode, Adapter does not emit the corresponding CBEs during callback inbound because the aspectj script is not correct. This has been fixed. | ||
| When Adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw a NullPointerException. This has been fixed. | ||
| During Adapter inbound and outbound operations (standalone deployment), after the application is restarted, a NullPointerException is thrown when the adapter tries to query the ASI from cache. This has been fixed. | ||
| When ARM is enabled in WebSphere Process Server/WebSphere Application Server administrative console, but the ARM transaction Factory name is set to ""(empty string), ClassNotFound exception will be thrown when performing inbound/outbound operation. This has been fixed. | ||
| Currently the Adapter V6.2 only supports EMF, and does not support XCI. The adapter V6.2 has been made to comply with the new WebSphere Process Server V7.0 SDO implementation for XCI support. | ||
| JR32384 | The WA for SAP Software does not generate correct maxLength values for BAPI attributes. It gets defaulted to 0. This has been fixed. | |
| JR33557 | The JCA SAP ALE Passthough adapter incorrectly posts IDoc control records multiple times for IDoc packets. The first IDoc's output is as expected. Then the second IDoc show IDoc_01's control record then IDoc_02's control record. The number of duplicated control records increases by one for each subsequent IDoc. This is now fixed. | |
| JR33557 | The adapter coverts most Czech characters into question marks(?). This has been fixed. | |
| WBIA AEP inbound artifacts do not work with the JCA adapter. This is now fixed. | ||
| After running migration on an ALE outbound repository, request Business Objects with the Dummy_key field fails the request. This has been fixed. | ||
| When using "unordered" delivery and "maximumConnections" is greater than 1, connectionPool is not used to deliver events within the first poll cycle.This has been fixed. | ||
| JR33598 | The adapter Enterprise Metadata Discovery schema generation pattern for the ALE interface is not standardized and hence not backward compatible. This is fixed. | |
| The adapter does not support conditional generation of Common Base Events. This has been fixed. | ||
| The adapter does not support sending ALEAUD audits per packet. This has been fixed. | ||
| JR31171 | Adapter does not handle QISS retrieval on non-unicode machines correctly. This has been fixed. | |
| JR31759 | The adapter does not correctly parse out time fields. This has been fixed. | |
| JR31614 | The adapter does not correctly parse out decimal fields. This has been fixed. | |
| JR31250 | Multiple threads change status when a single thread begins processing an event. This has been fixed. | |
| JR32057 | The adapter uses the incorrect 'E' (error) tag for success messages. This has been fixed. | |
| Support for WebSphere Business Monitor | ||
| While using the ALE inbound-passthrough module, specific IDoc objects should not be available to be chosen from the "Discover IDoc from System/File" node in the Object Discover and Selection screen This has been fixed and only Generic IDoc object is available for selection. | ||
| Adapter fails to log an error if it is in standalone deployment mode and wrong listener type is used. This has been fixed. | ||
| Siebel V6.2.0.4 | When the name of Integration object (IO) and Integration Component (IC) are the same, the schema file for service binding will be overwritten. This has been fixed. | |
| If primary key field in WBIA adapter project is not the same as EIS side, runtime will have error after migration to JCA. This has been fixed. | ||
| During EMD, NullPointerException will occur if the same integration object (IO) has been chosen as input for several times. This has been fixed. | ||
| Some field value in child BOs are missed in runtime. Those child BOs have 'simplelink' relationship with their parent BOs. This has been fixed. | ||
| Some extra null BOs and fields are returned in the inbound processing of business service. This has been fixed. | ||
| When Adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw a NullPointerException. This has been fixed. | ||
| During Adapter inbound and outbound operations (standalone deployment), after the application is restarted, a NullPointerException is thrown when the adapter tries to query the ASI from cache. This has been fixed. | ||
| When ARM is enabled in WebSphere Process Server/WebSphere Application Server administrative console, but the ARM transaction Factory name is set to ""(empty string), ClassNotFound exception will be thrown when performing inbound/outbound operation. This has been fixed. | ||
| Currently the Adapter V6.2 only supports EMF, and does not support XCI. The adapter V6.2 has been made to comply with the new WebSphere Process Server V7.0 SDO implementation for XCI support. | ||
| JR32670 | View mode property in runtime setting does not work. This has been fixed. | |
| JR33660 | Siebel EMD does not list complete list of BOs from Siebel system. This has been fixed. | |
| When using "unordered" delivery and "maximumConnections" is greater than 1, connectionPool is not used to deliver events within the first poll cycle.This has been fixed. | ||
| JR31991 | Siebel EMD does not prompt the dialog to change the query method. This has been fixed. | |
| JR32073 | When processing EMD for BO,if there is special characters in BC's attributes and select short name, BaseException will be thrown. This has been fixed. | |
| JR32074 | When generating BO, the calculated fields cannot be generated. This has been fixed. | |
| JR31795 | During inbound, if the database crashes, the adapter can't resume polling after the database's recovery. This has been fixed. | |
| WebSphere adapter for Siebel can not properly handle the stale connections in the connection pool. This has been fixed. | ||
| Support for WebSphere Business Monitor |
[{"Product":{"code":"SSMKUK","label":"WebSphere Adapters Family"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Adapter \u2013 Non-specific","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"7.0;6.2","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27019757