Product Documentation
Abstract
WebSphere Adapters provide periodic fixes for editions of release version 7.0. The following is a listing of those fixes alongwith the corresponding Websphere Integration Developer versions with which they are packaged.
Content
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Integration Developer versions 7.0.0.4 (Linux, Windows) and 7.0.0.5 (Linux, Windows)
| Adapter | APAR | Description |
| Email V7.0.0.4 | JR36457 | When the adapter waits for response from the mail server, the CPU utilization goes up. This has been resolved. As a part of the fix, a new property called 'Response Timeout' has been introduced so that the adapter waits only for the number of milliseconds mentioned in the timeout. |
| Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | ||
| Flat File V7.0.0.4 | Flat File adapter does not print the value of the property on which a failure has occurred when it throws an error message. This has been fixed. | |
| If you specify the output directory in the Interaction Spec in zOS/Linux/Unix, Flat File Adapter is not able to find the directory. This has been fixed. | ||
| JR39427 | After mounting the Samba shared folder onto the local directory, the adapter is reading the file repeatedly. This has been fixed. | |
| The generate unique file feature does not allow the user to set a prefix and suffix. This feature has been enhanced to allow the user to specify the prefix and suffix for the unique file. The prefix and suffix values can be specified either at the managed connection factory, interaction specification or the wrapper business object.If no values are specified, the previous predefined values will be used as default. | ||
| The value of staging directory is getting ignored when specified together with generateUniqueFile option. This has been fixed. | ||
| When Outbound Create module is configured with Sequence file option and deployed on a clustered environment, there is a duplicate record exception under high load. This has been fixed. | ||
| JR38019 | Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | |
| JR39129 | During Adapter Inbound operation, after several unplanned database outages during event processing, duplicate messages can be observed. This is due to the fact that the event is delivered but the overall transaction is marked failure and no rollback is called by the transaction manager. This has been fixed. | |
| The largest value for sequence number is the highest integer value, which is 2^31-1, after which the sequence number restarts from 1. This has been changed and the sequence number is now of long type and can take upto 2^63-1 before it restarts. | ||
| No warning message is displayed in the trace file when the adapter resets the sequence number in the sequence file. This has been fixed. | ||
| FTP V7.0.0.4 | FTP adapter does not support chmod,chgrp,chown commands in ExecuteFTPScript operation for SFTP protocol. The support has now been added. | |
| FTP adapter throws exception while performing list operation on an empty directory with certain SFTP servers. The problem occurs due to the JSch thirdparty library used to provided SFTP functionality. The issue is fixed in JSch 0.1.42 version. The Adapter now ships JSch v0.1.42. | ||
| The FTP Adapter currently creates unique files based on the "STOU" FTP command. If the "STOU" command is not supported by the FTP server, Adapter creates file starting with prefix "FTP" followed by a random number. The user does not have an option to configure the prefix string or a suffix for the unique file that is generated. The feature has been enhanced whereby the user can specify the prefix and suffix strings for the unique file. These properties can be set through the External Service wizard at Interaction Specification properties. If no values are provided for both these properties, the Adapter creates an unique file using the previous behaviour. | ||
| FTP adapter throws exception while checking for the permission of the output directory when user is locked in home directory. The user is not allowed to execute commands like CDUP and throws InvalidPropertyException. An option is provided in EMD to disable the checking for permission of output directory. When the property is unchecked, the Adapter does not check for the permissions of the directory before performing the operation. When the property is enabled, ensure that the listing permission is available on the parent directory to perform the permission check. | ||
| SFTP servers like WinSSHd server provides options to authenticate users using both password and public key authentication. FTP Adapter does not support using both public key and password authentication simultaneously for authentication with SFTP protocol. FTP Adapter now supports providing both public key and password authentication to be used simultaneously for authentication with SFTP servers. | ||
| Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | ||
| JDBC V7.0.0.4 | JR38018 | The JDBC Adapter runtime is not compatible with the v6.1 of the wrapper business. This backward compatibility has been added now. |
| JR38387 | When processing large and deep hierarchy BOs, there is a performance issue accompanied by high CPU utility, the performance issue caused the low efficiency on processing BO. The performance issue has been fixed. | |
| JR37501 | When JCA JDBC adapter runs in heavy workload multiple threaded environment, it returns a 'Cannot call cleanup on a ManagedConnection while it is still in a transaction' error message. This has been fixed by ensuring that the WAS datasource connection is closed after JCA JDBC adapter cleanup method is invoked. | |
| Transaction related errors are thrown when the JBBC adapter application is run in a sequence of local and global transaction. This has been fixed. | ||
| JR38019 | Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | |
| A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log. | ||
| JR39129 | During Adapter Inbound operation, after several unplanned database outages during event processing, duplicate messages can be observed. This is due to the fact that the event is delivered but the overall transaction is marked failure and no rollback is called by the transaction manager. This has been fixed. | |
| OracleEBS V7.0.0.4 | JR39584 | If the complex type contained in Record/Table/Array/Object has a different owner from the current user's schema, it will result in an error as the adapter retreives the metadata using the same schema as the current user's schema. This has been fixed. |
| JR39285 | When a procedure is being bound and this procedure does not have input and output parameters a null exception is shown and EMD process can't be completed. This has been fixed. | |
| JR39341 | When generating wrapper with the adapter on procedures with similar name, a new wrapper procedure name will overwrite the old wrapper procedure name. This has been fixed by adding a suffix in the new package name. | |
| JR39340 | When reading a procedure schema from Oracle package, if there is a record or table which is typed as %rowtype, the adapter does not build the record business object fields and schema correctly. This has been fixed. | |
| JR38594 | 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. This has been fixed. | |
| JR38019 | Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | |
| JR38671 | When using Oracle EBS adapter to connect to the EIS with customer's username and passoword, and customer tries to discover the stored procedure with PL/SQL Record type related parameters in other user's schema, the adapter generates the wrapper procedure in current user's schema, which will cause 'datatype missing' problem. This has been fixed. | |
| A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log. | ||
| PeopleSoft V7.0.0.4 | JR38869 | Adapter fails to generate decimal attribute for properties of type NUMBER/SIGNED NUMBER with decimal positions. This has been fixed. |
| JR38019 | Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | |
| A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log. | ||
| JR39773 | Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException during the call to BootStrapContext.createTimer(). This has been fixed. | |
| SAP V7.0.0.4 | Added support for Single RFC Program ID. | |
| For BAPI Result Set, the schema is generated incorrectly - SAPReturn is not created for the added BAPI. This has been fixed. | ||
| Adapter EMD cannot load msvcrt.dll in the PATH on Windows2008 R2 Enterprise. This has been fixed. | ||
| In Case of SAP ALEPT Inbound/Outbound. An additional "sap" text will be added to the BO name when moving back and forth between screens in EMD. This has been fixed. | ||
| JR37948 | The BAPI Result Set does not run the Detail-RFC although many entries from the Search-RFC are returned. This has been fixed. | |
| JR34964 | Adapter corrupts BCD Value in BAPI calls when locale has a comma as decimal seperator. This has been fixed. | |
| Second EMD run with the same RAR in same workspace will fail if missing msvcr71.dll. This has been fixed. | ||
| QISS Iterative: The Configuration Properties panel is not correct. This has been fixed. | ||
| JR37643 | ALE inbound with namespace syntax throws exceptions.This has been fixed. | |
| API_BANK_GetList: Adapter will display one more bank info with non-set value. This has been fixed. | ||
| Optional changing parameters not listed in the Optional parameters list. This has been fixed. | ||
| JR37652 | Unable to find the field - about bapi table fields built using field names. This has been fixed. | |
| JR36753 | Event not found error logged in the websphere bi connector log: aep inbound. This has been fixed. | |
| Property "waitOnCommit" should not be applicable for for ALEPT/ALE outbound EMD. This has been fixed. | ||
| JR39274 | ALE AUD Packet update dosent work correctly. This has been fixed. | |
| There are few defects fixed for the BAPI interface 1- MaxLength was incorrectly set for BAPI fields.Internal length was set instead of proper length. 2- Field Type was not set correctly for table types.WhiteSpace was padded in the type returned by adapter 3- Support was added for field types like: NUMC,DEC, TIMS, INT4 etc. This has been fixed. | ||
| User trace of the adapter does not state that the file SapBusinessObjectMetadata.xsd is missing in the deployed BAR file. This has been fixed. | ||
| QISS iterative development failure. This has been fixed. | ||
| JR38117 | JCA SAP adapter v7 fails to load logon group members because sap 4.6 is missing a required structure in a lookup bapi. This has been fixed. | |
| JR33249 | The adapter does not perform the its best when there are one or more DATE fields in the return when BAPI interface is used. This has been fixed. | |
| When event is resubmitted from sap, its moved to the mqout,but not cleared from mq system queue. This has been fixed. | ||
| BaseException: A resource exists with a different case: when discovering BAPIs. This has been fixed. | ||
| ASI business object definition for SAP Adapter to be changed to have CHANGING PARAM enumeration. This has been fixed. | ||
| Submitted sapparse record fails at runtime- EXPRESS field accessor not found. This has been fixed. | ||
| Inbound retry connection only used JCo retry mechanism. This has been fixed. | ||
| Fetching metadataobject based on location ID for BOR does not work. This has been fixed. | ||
| Sap adapter throws npe with ale inbound when exception occurs. This has been fixed. | ||
| JCA SAP Sync inbound bapi returns the union of input and output table rows if the output table rows were modified. This has been fixed. | ||
| JR38060 | Easy way to retrieve the client value e.g. through connection factory without having to hardcode it. This has been fixed. | |
| IDoc field Value are getting trimmed. This has been fixed. | ||
| BAPI: Integer field inside Structure is not created in SAP. This has been fixed. | ||
| Deploy fails after using mqsicreateconfig/ adding setter/getter for rfctracePath. This has been fixed. | ||
| QISS editBO error : editBO is erroneous when we select 2 or more BOs in QISS. This has been fixed. | ||
| Changing exception.printstacktrace to throw exception to stop adapter processing further. This has been fixed. | ||
| JR39129 | During AEP Inbound operation, after several unplanned SAP outages during event processing duplicate messages can be observed. This is due to the fact that the event is delivered but the overall transaction is marked failure and no rollback is called by the transaction manager. This is the fix: If the event is already delivered to the downstream components but the overall transaction is marked failure due to issues in downstream component, the event is deleted if no rollback is issued. | |
| JR39474 | The JCA SAP Adapter on V7 was failing if the segmenents that are not mandatory having maxoccurs =1 are not sent in the input xml during outbound. This has been fixed. | |
| JR38885 | Adapter thows exception while fetching value for accessor EXPRESS. Adapter was incorrectly trying to fetch the value for EXPRESS, correct field is EXPRSS , This has been fixed. | |
| JR37643 | ALE inbound with namespace syntax "//" is throwing exception using extension IDOCs, where the extended IDOC is having a linked IDOC who's name includes namespace in it. This has been fixed. | |
| JR38640 | Adapter throws nullpointer exception if non-mandatory level 1 idoc segments are omitted when sending idoc to sap. This has been fixed. | |
| JR38223 | Adapter unable to process IDocs via qRFC when the IDoc contains unreleased segments. This has been fixed. | |
| JR38356 | When using the SAP Adapter as inbound adapter, receiving following misleading error message: SAPRA001 E SAPtRFCServerDataBinding getDataObject CWYBS0499E: An invalid key was encountered while the adapter was using Resource Bundle com.ibm.j2ca.sap.LogMessages with Locale en_US. The key is either null or an empty string. Though it does not have any functional impact. This has been fixed. | |
| JR38359 | If XSTRING is defined field type of the business object SAP Adapter throws an exception at runtime. ABAP data type XSTRING cannot be parsed correctly from SAP adapter at runtime. This has been fixed. | |
| If msvcr71.dll is missing in the PATH then 2nd EMD run with the same RAR in the same workspace fails with the exception Array Out of Bounds. This has been fixed. | ||
| JR37644 | JCA SAP sync inbound bapi returns the union of input and output table rows if the output table rows were modified. This has been fixed. | |
| WBI adapter did not contain the prefix sap_ which is being set by default while creating business object definitions using SAPODA. JCA adapter expecting sap_ as prefix in BO definition throws error. New Parameter "Default BO Prefix" is introduced in Activation Spec at runtime as part of the fix. | ||
| JR36754 | Even when the trace is not enabled i.e, with just *=info,detailed logging is logged into the systemout log. This is now fixed. | |
| JR33249 | When there are one or more DATE fields in the return BAPI, the adapter needs to be tuned for better performance. This is now fixed. | |
| Connections to SAP are not closed when BAPI calls fail. This is now fixed. | ||
| Concurrent requests to SAP Adpater fail with JCO_ERROR_CONCURRENT_CALL. This is now fixed. | ||
| JR37070 | Message flow does not stop on HP-UX. This is now fixed. | |
| JR37493 | Detailed errors not written to syslog. This is now fixed. | |
| JR37494 | SAP adapter throws npe with alein when exception occurs thus masking the original exception. This is now fixed. | |
| JR37349 | IDOC datarecord values are getting truncated on non-unicode systems. This is now fixed. | |
| SAP outbound ale/bapi connection lost and transaction goes stateless mode. This is now fixed. | ||
| JR36874 | IllegalStateException is thrown as AFTER_DELIVERY was called but message delivery didnt started with BEGAN_DELIVERY. This is now fixed. | |
| Connections to SAP are not reset if JCoReset Connection is checked and rollback happens. This is now fixed. | ||
| No address data returned with an application containing 3 BAPIs or more. This is now fixed. | ||
| SAP Adapter throws ClassCastException when reading annotation in Synchronous BAPI Inbound with Lazy BO parsing mode, when the Adapter RAR is deployed at Node level. During Node level deployment, the default BO parsing for runtime is Eager parsing. Hence, properties generated in Lazy parsing mode will encounter issue while reading annotations. The issue is resolved by reading the annotations accordingly. | ||
| JR39773 | Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException will be thrown during the call to BootStrapContext.createTimer(). This has been fixed. | |
| JR38019 | Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | |
| A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log. | ||
| Siebel V7.0.0.4 | In WPS, adapter doesn't handle business error from Siebel server as fault. User cannot use BPEL to handle these business errors. This has been addressed by adding a new fault "InvalidRequestFault" for Siebel Exception. | |
| JR39485 | Some field values in child BOs having "association" relationship with their parent BOs are missed during runtime. This has been fixed. | |
| Siebel adapter ignores fields which contains string 'SBL-DAT' in repsonse message. This has been fixed. | ||
| XML character filter set properties in EMD will not take effect, if either of option B or C is selected; it will always be A at the end of the EMD run. The code has been fixed to preserve the selection in EMD. | ||
| JR39417 | When multiple/array requests are sent in business service, the adapter only returns one response. This has been fixed. | |
| JR38016 | Siebel Adapter creates null as data type for some arguments of business services after metadata discovery. This issue is caused due to "Inactive" integration objects(IOs). The "inactive" IOs are now filtered out during the metadata discovery to fix this problem. | |
| JR36907 | Adapter ignores fields with empty string value in both request and response of business services calls. This has been fixed. Added empty string value handling in business services request part. Added a property includeEmptyFields in MCF to determine whether adapter returns empty string fields in response BO. Activate this feature by setting the property to true. | |
| JR38003 | If Siebel adapter is active and is idle for a long time (resonateSupport = true), then an error will be thrown in the next attempt to connect to the EIS. This has been fixed. | |
| JR38019 | Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | |
| JR39773 | Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException during the call to BootStrapContext.createTimer(). This has been fixed. | |
| Lotus Domino V7.0.0.4 | RetrieveAll Outbound operation currently uses search() function on the Domino Client API. This is much slower when compared to the indexed search approach that Domino API provides. The search during RetrieveAll has been enhanced by providing an additional option to the customer to use indexed search so that they can benefit from the speed. This additional option 'Use Indexed Search' will be available as part of the External Service Discovery wizard. | |
| A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log. | ||
| JR38019 | Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | |
| JR39129 | During Adapter Inbound operation, after several unplanned database outages during event processing, duplicate messages can be observed. This is due to the fact that the event is delivered but the overall transaction is marked failure and no rollback is called by the transaction manager. This has been fixed. | |
| JDE V7.0.0.4 | A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log. | |
| JR38019 | Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. | |
| JR39773 | Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException during the call to BootStrapContext.createTimer(). This has been fixed. | |
| JR38857 | When using JDE adapter to pull data into WPS with special characters, a ResourceException is thrown. For an accent on the E in HELLO, the string in the XML reads H\u00C9LLO. This has been fixed by encoding the input xml using "UTF-8" by default. | |
| "Folder of failed events", the whole BO schema and data will be put into the folder. This assumes application having privilege to read and write local file of the broker. This has security risks. To address this, the "Folder of failed events" has been removed, and the event data is saved to the Event Data column of the persistent event store. | ||
| Timeout and MaxRecord are interaction specification properties only valid for XML List RetrieveAll operations. However they are shown when no XML List BO is selected. This has been fixed by hiding these properties when no XML list BO is selected. | ||
| JDE adapter does not acknowledge and delete processed event from event store on adapter restart. This has been fixed. | ||
| Added support for WebSphere Message Broker. | ||
| JR37204 | JDE Adapter does not support a container type Real-Time event with only one child. This has been fixed. | |
| JR37670 | The migration code does not migrate JDE key references from first method call in a batched group to the rest of the group. This has been fixed. | |
| JR36794 | Migration tool throws StringIndexOutOfBound exception when doing migration. This has been fixed. | |
| JR38754 | When migrating from WICS environment to WPS 7.0 the JDE Adapter failed to generate some of attributes. The migration code path has been fixed. | |
| When migrating from version 6.2 to 7.0, migration tool throws MigrationException. This has been fixed. | ||
| IBMi V7.0.0.4 | JR38713 | When a customer uses an array of structures inside a nested structure and runs a simple outbound operation, the adapter fails. This has been fixed. |
| JR38393 | When a customer uses an array of simple data types inside structures and runs a simple outbound operation, the adapter fails. This has been fixed. | |
| Currently the adapter does not support encoding for the parameters of RPG and COBOL programs. This has been fixed. The adapter takes the CCSID from the data tag attribute of the PCML. For DBCS graphic-only field, the user need to provide the pure DBCS CCSID in the EMD for the Data CCSID field. | ||
| A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log. | ||
| JR37522 | When a customer uses BOPrefix and runs a simple Inbound operation, the adapter fails with exception com.ibm.websphere.sca.ServiceRuntimeException: Did not find method for native method 'emit(DataQueueName)'. This has been fixed. | |
| JR38285 | The adapter throws an exception when relative reference of variables inside structures is used during Outbound operation. This has been fixed. | |
| JR37664 | The adapter throws an exception when dynamic variable length array is used during Outbound operation. This has been fixed. | |
| JR39653 | The adapter throws an exception when structure inside array of nested structures is used during Outbound operation. This has been fixed. | |
| When the user selects two objects with same name in the EMD, the discovery cannot be completed and will result in NPE. This has been fixed. | ||
| When the user selects a BOPrefix value for RPG, COBOL, Service Program, the BO name is not prefixed with that BOPrefix. This has been fixed. | ||
| When the user does a "getQueue" operation and if no data is present in the Data queue, an exception is thrown by the adapter. This has been fixed. | ||
| Currently, the user has to add elements to the structure explicitly otherwise the adapter throws an exception. This has been fixed. | ||
| When the user unsets the attributes inside the structures or arrays and calls pgm operation then adapter throws an exception. This has been fixed. | ||
| When the user selects the pcml having the attribute (length) of the variable referring to the other variable in the same structure or different structure, the adapter throws an exception. This has been fixed. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Integration Developer version 7.0.0.3
| Adapter | APAR | Description |
| Email V7.0.0.3 | If the deliveryType is set to UNORDERED during inbound EMD, a null pointer exception will be thrown at the end of the EMD run. This has been fixed. | |
| Flat File V7.0.0.3 | During Outbound operation for Flat File, if generateUniqueFile = true, and stagingDirectory is set, new file has no content. This has been fixed. | |
| The following properties in the FlatFileResourceAdapter class are used internally: flatFileUtil, verifier, bridge, endpointActivationCompleted. However, set methods, which are not used, are created for them, which is causing these properties to show up in the administrative console. Hence the set methods for these properties have been removed. | ||
| During inbound operation for Flat File, when filePassByReference=True, the same file cannot be polled for the second time. This has been fixed. | ||
| During inbound operation for Flat File, using splitting and pollquantity=n, BO number=n+m, m can not be transacted correctly. This has been fixed. | ||
| If the deliveryType is set to UNORDERED during inbound EMD, a null pointer exception will be thrown at the end of the EMD run. This has been fixed. | ||
| FTP V7.0.0.3 | Null pointer exception is thrown with ftps or sftp protocol for ServerToSeverFileTransfer operation. The issue has been resolved; it now throws InvalidPropertyException. | |
| Incorrect exception message throw when SecondServerDirectory value is incorrectly set on the wrapper. This has been fixed and the correct exception is thrown now. | ||
| A word "properties" not been translated for RootNameFunctionSelector option. Translation been invoked for the same. | ||
| The word "Advanced" in the error info is not translated when Truststore is not selected. Translation has been invoked for the same. | ||
| FTPS connection fails for PKCS12 key store type. This has been fixed. | ||
| If the deliveryType is set to UNORDERED during inbound EMD, a null pointer exception will be thrown at the end of the EMD run. This has been fixed. | ||
| JDBC V7.0.0.3 | When there is a column with an identity (auto-increased value), after the EMD wizard is run, users need to manually edit UID ASI in business object definition in order to support the column. This has been fixed. JDBC Adapter is now able to support a column with an identity without need to edit UID ASI manually. | |
| OracleEBS V7.0.0.3 | While editing binding for Stored Procedure/Function during iterative discovery, exception pops up and the process cannot go through. This has been fixed. | |
| PeopleSoft V7.0.0.3 | JR35982 | JCA PeopleSoft Adapter fails with JOAException to set get keys during the second run when doing Update operation. This has been fixed. |
| JR35830 | When Child BO has no primary key ASI, Update operation can not succeed in some cases. This has been fixed. | |
| JR35978 | 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. Adapter does not call get() method to generate response for Create operation when CI has no get keys or get() method is not available in EIS side. | |
| When IgnoreEffectiveSequence and InsAtOldestEffDtPos are set to true and EIS has no child, if input data contains child, it will do child create and it fails due to insert at invalid position (-1). This has been fixed. Adapter will insert at position 0 in this case to avoid error. | ||
| When KeepRelations is false, EIS has some child and input data has no child, Update operation returns incorrect response that has a dummy child, sometimes even returns a dummy child with a non dummy grand child. This has been fixed. Adapter will call get() to get the EIS data to generate correct response for Update operation if get() method is available in EIS side. | ||
| JR36715 | If a property is not getkey, but is key, after running ESD, PrimaryKey ASI will be set to true for this property. This leads to runtime error when calling set method for this property. This has been fixed. Adapter will not set PrimaryKey ASI to true for the property that is not getkey. | |
| When doing update for some specific CI, update will take no effect. This has been fixed. A flag has been added to differentiate whether Peoplesoft record is used in producing command or generating response. The extra get operation is supposed to be performed when generating response. | ||
| SAP V7.0.0.3 | The xsd schema generated by the JCA SAP ESD marks some control fields as required. However, the adapter treats these fields as optional. This problem is now fixed. | |
| JR36038 | Even when the message flow is stopped i.e., adapter is stopped, connections are still active when tested using SM59. This problem is now fixed. | |
| JR36606 | When client tries to create a SAP-Outbound-Adapter From WebSphere Message Broker Toolkit Adapter V7 Wizard they get error message: com.ibm.adapter.framework.BaseException. This problem is now fixed. | |
| SAP Adapter V7 fails connecting to non-unicode SAP Systems when the password is entered in lower case. This problem is now fixed. | ||
| JR34424 | When using a registered namespace on the SAP system for BAPI artifacts, the SAP adapter throws the following exception: "Business Object definition for 'SapStfcWriteToTopicWrapper' in namespace ...not found" This problem is now fixed. | |
| JR36123 | SAP Adapter Outbound QISS interface: only the first of several child tables is retrieved. The other child table remain null. This problem is now fixed. | |
| JR36095 | Using ALE Passthrough for outbound messages going to SAP, not all the fields are set SAP throws an error and the SAP request node gets the error about those missing values. This problem is now fixed. | |
| JR36223 | The client is using the JCA SAP Adapter V7 and is not able to extend or add to their existing EIS artifacts using the WebSphere Adapter's 'Iterative Development' feature. This problem is now fixed. | |
| JR35371 | IDocs sent from SAP EIS from AEP custom handler contain only CxIgnore values. This problem is now fixed. | |
| BOR discovery for all filter patterns not containing asterisk does not work. This problem is now fixed. | ||
| In SAP Adapter, BAPI ZPM_TEST_RFC outbound generates the following FFDC entry: Field NUMBER not a member of BAPIRETURN. This problem is now fixed. | ||
| Iterative discovery does not work for BOR. This problem is now fixed. | ||
| Set "*Cross" as BOR filter, BAPI which begin with Cross, such as "Cross-System command", will be listed. This problem is now fixed. | ||
| The description of BAPI in "Find Objects in Enterprise System" should be divided by "/" or something else. This problem is now fixed. | ||
| SAP Adapter to provide an optional feature for preserving leading spaces in the IDoc fields. This support has now been added. | ||
| In EMD, the panel's progress bar information is not translated accordingly. This problem is now fixed. | ||
| No CBE 'delivery.entry' event for SAP Inbound event delivery. This problem is now fixed. | ||
| SAP Adapter CBEs must have correlation in order to track the events in a flow. This support has now been added. | ||
| Dummykey behavior is different from basic IDoc to extension IDoc. This problem is now fixed. | ||
| When selecting one basic IDoc and one extension IDoc or two basic IDocs to generate artifacts, the generated method bindings are not the expected ones. This problem is now fixed. | ||
| For multi-IDocs, in top level BO the generated methodname attribute belonged to operation element does not reflect the value, which fills during EMD process in Specify Composite Property panel. This problem is now fixed. | ||
| When load balancing is enabled - can not deploy the sapinput note if number of listeners is set to 1. This problem is now fixed. | ||
| JR36754 | Even when the trace is not enabled i.e, with just *=info, detailed logging is logged into the systemout log. This problem is now fixed. | |
| JCO_ERROR_SESSION_REF_NOT_VALID error happens when testing ALE inbound. This problem is now fixed. | ||
| Event not found error logged in the WebSphere bi connector logs -aep module. This problem is now fixed. | ||
| JR33249 | Performance fixes along with the stringoutofbounds exception fix. | |
| Sending out the BAPI request to SAP server with default MaxRows value, when the request is sent out, then un-deploying this app from WebSphere Process Server runtime, but the log messages still are printed. This problem is now fixed. | ||
| JR35842 | With WMB Toolkit V6.1 and SAP Adapter V6.1, the ESD Wizard shows the option to receive an individual message per IDoc sent but it cannot be changed. This problem is now fixed. | |
| With some certain steps, AEP inbound EMD fails with a "java.lang.RuntimeException: Unable to create definitions null" error. This problem is now fixed. | ||
| The finish button in the last panel of ALEPT iterative does not work correctly. This problem is now fixed. | ||
| If the first run of the discovery wizard contains a File, Folder or Schema type property, subsequent iterative discovery wizard runs fail to launch and an error message is displayed to the user. This problem is now fixed. | ||
| Siebel V7.0.0.3 | Some extra null BOs and fields are returned in the inbound processing of business service. Fixed the conversion problem between SiebelPropertySet, which is returned by business service, and BO. | |
| JR35750 | Some field value in child BOs are missed during runtime for child BOs that have "simplelink" relationship with their parent BOs. This has been fixed by activating all fields in child BOs before all field values are retrieved. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Integration Developer version 7.0.0.2
| Adapter | APAR | Description |
| Email V7.0.0.1 | 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. | |
| 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, a 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. | ||
| 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. | ||
| When the email id mentioned in the 'to' field is wrong, the adapter does not have the capability of sending a bounce email. This has been fixed. The adapter now has the capability of sending bounced emails to an alternate email id. | ||
| Flat File V7.0.0.1 | FFDC recorded BO related Exception, although the operations were done correctly. 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, a 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. | ||
| The description of RootNameFunctionSelector is missing from EMD.properties file causing an exception when getting the display name in External service wizard. 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. | ||
| System out for "O isGloable element=== false/true" shows up in the trace. 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. | ||
| EIS binding using BOXMLSerializer to serialize events when the adapter is configured to use default data binding with no data handler. It seems no notification is sent to adapter when exception is encountered. This is fixed from Adapter end. | ||
| FTP V7.0.0.1 | 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. | |
| 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 from cache This has been fixed. . | ||
| The description of RootNameFunctionSelector is missing from EMD.properties file causing an exception when getting the display name in External service wizard. This has been fixed. | ||
| Adapter throws a FFDC with NumberFormatException during Inbound when splitting is not enabled.The Adapter doesnt throw any FFDC when the splitting is not enabled in Inbound. 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. | ||
| FTP adapter throws IOException during create operation when both "FileInLocalDirectory" and "Local archival after create" properties are enabled. This has been fixed. | ||
| IBMi V7.0.0.1 | Certain strings in adapter are hard-coded. This has been fixed. | |
| EmptyGetQueueBO is getting generated for the Keyed Data Queue and will be set as input for the GetQueue operation. So there is no way to input the "key value" for the query. This has been fixed. | ||
| During running migration script for IBMi stand-alone module, exception message showed up, and migration process stopped. 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 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. | ||
| 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. | ||
| JDBC V7.0.0.1 | In inbound process, adapter can not support the element type of ARRAY type is a complex type (STRUCT/ARRAY) for table business object. Adapter add support for nested complex type for ARRAY type in table business object. This has been fixed. | |
| In the database selection screen of enterprise service discovery, the port number shown as 50000 is not the default value of db2 iSeries.This has been fixed. | ||
| On JDBC inbound endpoint configuration in WebSphere Integration Developer edit environment, the value of "event query type for processing events" gets back to default "Standard" even if you change to "User-Defined(Dynamic)" and save it. The value of "event query type for processing events" is changed to the desired value after saving changes. | ||
| WebSphere Application Server private API is deprecated and they should be removed. This has been fixed. | ||
| 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.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. | ||
| 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. The BO's namespace and name has been preserved as BO instance's fields. After the application is restarted, adapter can still get them from those instance's field rather than the stale data cache. | ||
| 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 used for it, which need to be replaced with public interfaces. This has been fixed. | ||
| 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. | ||
| LotusDomino V7.0.0.1 | The message "All fields of the form are already included!" is hard-coded. Make the message support globalization. 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. The BO's namespace and name has been preserved as BO instance's fields. After the application is restarted, adapter can still get them from those instance's field rather than the stale data cache. | ||
| 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. | ||
| 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 Printed AFC version in the trace.This has been fixed. | ||
| Currently the version of the bundled NCSO.jar is 8.5. Updated the bundled NCSO.jar to the 8.5.1 version of the Domino server. | ||
| 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 doesnt 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 ocurr 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. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Integration Developer version 7.0.0.1iFix001
| Adapter | APAR | Description |
| Flat File V7.0.0.0_IF02 | The description of RootNameFunctionSelector was missed from EMD properties file causing an exception when getting the display name in Inbound pattern wizard flow. This has been fixed. | |
| FTP V7.0.0.0_IF03 | The description of RootNameFunctionSelector was missed from EMD properties file causing an exception when getting the display name in Inbound pattern wizard flow. This has been fixed. | |
| IBMi V7.0.0.0_IF02 | 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 information from cache. This has been fixed. | |
| JDBC V7.0.0.0_IF02 | 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 information from cache. This has been fixed. | |
| JDE V7.0.0.0_IF02 | 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 information from cache. This has been fixed. | |
| OracleEBS V7.0.0.0_IF02 | 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 information from cache. This has been fixed. | |
| PeopleSoft V7.0.0.0_IF03 | 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 information from cache. This has been fixed. | |
| SAP V7.0.0.0_IF04 | 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 information from cache. This has been fixed. | |
| Siebel V7.0.0.0_IF03 | 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 information from cache. This has been fixed. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Integration Developer version 7.0.0.1
| Adapter | APAR | Description |
| Email V7.0.0.0_IF01 | When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | |
| Flat File V7.0.0.0_IF01 | When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | |
| FTP V7.0.0.0_IF02 | When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | |
| IBMi V7.0.0.0_IF01 | Adapter throws NullPointerException when complex COBOL structured data having multi level BO -- struct nested within an array of structures further nested. This has been fixed. | |
| When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | ||
| JDBC V7.0.0.0_IF01 | The method of "getMaxLength" does not work fine for the XSMetaData as it can not be resolved by the newer 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 is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | ||
| JDE V7.0.0.0_IF01 | When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | |
| Lotus Domino V7.0.0.0_IF01 | When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | |
| OracleEBS V7.0.0.0_IF01 | The method of "getMaxLength" does not work fine for the XSMetaData as it can not be resolved by the newer 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 is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | ||
| PeopleSoft V7.0.0.0_IF02 | When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | |
| SAP V7.0.0.0_IF03 | During deployment and redeployment, the SAP Healthchecker is not cleaned up properly leading to memory leaks over a long period of time. This has been fixed. | |
| When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. | ||
| The method of "getMaxLength" does not work fine for the XSMetaData as it can not be resolved by the newer 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. | ||
| Siebel V7.0.0.0_IF02 | When adapter is used to creates two or more different modules with two business object having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed. |
[{"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":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"7.0.0.4;7.0.0.3;7.0.0.2;7.0.0.1;7.0","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27017803