Product Readmes
Abstract
WebSphere® Partner Gateway provides periodic fixes for release V6.2.0.5. The following is a complete listing of fixes for V6.2.0.5.
Content
WebSphere Partner Gateway V 6.2.0 Fix Pack 5 |
| Fix release date: 22/10/2010 V6.2 Fixpack5 Advanced Download V6.2 Fixpack5 Enterprise Download |
| Component | Tracking Number | Description |
AS | JR36114 | With this FixPack, the “Resend” works as expected. |
Archiver | JR35684 | While purging DB table data, WebSphere Partner Gateway Archiver displayed "SQL error: SQLCODE: -532, SQLSTATE: 23504" an exception for DB foreign key constraint violation. |
| JR36757 | WebSphere Partner Gateway Archiver has been improved to delete WebSphere Partner Gateway created temp files. | |
BPE | JR35132 | This FixPack resolves the problem encountered in handling documents in process during WebSphere Partner Gateway shutdown. It includes stage recovery in reliable fashion, which ultimately resolves BPE's cyclic document processing problem. |
| JR36116 | With this FixPack, the problem of signature verification failure, which encountered inappropriately during WebShpere Partner Gateway shutdown is resolved. | |
BPE/Console | JR37676 | With this FixPack, you have an option to change the duplicate field declaration in the System Administration properties. |
BPE/ebMS | JR35429 | During secure ebMS message flows, it was noticed that the security operations failed when the BCGBPE application was restarted. |
| JR37687 | This FixPack has resolved the problem of failing security operations upon restarting the BCGBPE application during ebMS secure message flow. | |
Console | JR35330 | When using WebSphere Partner Gateway Console to edit partner with large number of business IDs (more than 200), the edit and save operation takes long time to display the page. With this FixPack, the performance is considerably improved. |
| JR35603 | While deleting one version of a PIP, the information pertaining to other versions (for example, shared attributes and validation maps) was deleted. With this FixPack, dependency check happens before deleting the associated attributes and maps so that the other PIP definitions are not affected. | |
| JR35647 | The "Destination Queue" page in the WebSphere Partner Gateway console takes a long time to display the page, if the number of destinations configured for the partner are large (more than 600). | |
| JR35717 | Associated handlers for any POP3 type receivers were seen missing from the configuration XML data that was exported using the Partner Migration utility. | |
| JR35736 | With this FixPack, you can successfully create a custom SFTP destination. | |
| JR35745 | The hub’s default internal partner was set to wrong partner after importing the partner migration data. | |
| JR35990 | While starting the DocMgr application, the "NumberFormatExceptions" exception, which was thrown in the scheduler, was causing the "DeliverySchedulerBean" to stop and report errors. These exceptions were thrown because the FTPScripting destination configurations having POLLINTERVAL displayed 0.0 seconds. With this FixPack, the POLLINTERVAL value is validated to have a non-zero positive integer while creating the destination. | |
| JR36069 | The "Password" field was not masked while creating a destination or a receiver using custom transport. Some additional configuration would be needed. Please refer to http://www.ibm.com/support/docview.wss?rs=2311&uid=swg21448337 for more details. | |
| JR36402 | When a custom user, who is not a member of "hubadmin" group, login to the WebSphere Partner Gateway console, this user was not able to view or configure handler and its attribute for receivers or destinations even when the user had read/write permission for the receiver and destination modules. | |
| JR36916 | When the WebSphere Partner Gateway configuration data was exported using the Partner Migration utility, the Folder Name attribute, and its value set for web mailbox type destinations was seen missing. | |
| JR37255 | Deleting of a user in the WebSphere Partner Gateway happened without prompting for any confirmation. With this FixPack, a confirmation dialogue box appears before deleting the user from database to avoid any unintentional delete of user. | |
| JR37692 | The Time zone setting option drop down list for the user confirmation was listing only important time zone regions without listing all sub-regions with different DST scheme for that region. | |
Console/ebMS | JR34693 | In Websphere Partner Gateway console, the Document Viewer or the ebMS Viewer did not display the document timestamp of the outbound ebMS document. |
| JR35911 | In the current implementation, the WebSphere Partner Gateway uses fixed key length for the defined encryption algorighthms, and hence the Encryption Key Length attribute, which is provided as the ebMS connection attribute is redundant, so it has been removed from the console. | |
| JR37690 | In the current Websphere Partner Gateway implementation, the supported "syncReplyMode" values for ebMS are none and mshSignals only. This FixPack removes the other redundant options listed in the "SyncReplyMode" drop down from the connection attributes for ebMS. | |
Console/FTP Configuration | JR35234 | With this FixPack, you can now edit the "The bcg.config.ftpmanagement.allowedIPs" property of the Integrated FTP Server by navigating to: System Administration -> FTP Administration page in the WebSphere Partner Gateway console. |
CPA Editor | JR35411 | When opening the CPA using the CPA Editor, the following error was seen "java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck (UnknownSource)". |
| JR35542 | When the CPA was edited in the CPA Editor, the user was unable to upload the edited CAP in the WebSphere Partner Gateway console. This error occurred because the CPA editor incorrectly adds the element Persist Duration to the CPA. Nevertheless, the Persist Duration is not a mandatory element, so it is wrong to add it without the other dependencies being present. | |
Database | JR36742 | While updating WebSphere Partner Gateway to any latest fix pack, channel attribute “EXCLUDEDCONTENTTYPESFORCANONICALIZATION” was getting reset. |
Destination - FTP scripting destination | JR37055 | When the APPEND command was used, the FTPScripting destination used to throw null pointer exception in SystemErr.log. This exception was seen when the FTP server was returning a warning code '000'. |
Destination/HTTP | JR29147 | By using the "bcg.http.requestSizeForChunking" parameter from the System Properties, you can set this value as number of bytes. Note that you can retain the default value 2147483647, unless it is required to change. |
Document Manager | JR35606 | Errors relating to "java.lang.ArrayIndexOutOfBoundsException" were logged as MDNs did not generate. With this FixPack, all such problems seen on a multi-machine setup have been resolved. |
| JR35716 | When a certificate is uploaded using WebSphere Partner Gateway console, an error -"com.ibm.bcg.server.cache.docmgr.DocMgrConfigCache refreshDocMgr Error in refreshing the cache java.lang.NullPointerException" was seen in the “SystemOut” log files because there were Docmgrconfig cache updates happening for the Archiver EAR. | |
| JR35897 | Earlier, the checking of the AS2 duplicate documents happened frequently. With this FixPack, the checking of the AS2 duplicate documents happen only when the channel attribute is set to “No”. | |
| JR37807 | The removal of the oldest entry in the channel cache and cache refresh were not synchronized, which could lead to unexpected results/entries in the channel cache. | |
Document Manager/AS | JR34571 | For the ebMS document, the retry count is updated in the database only when the retried message is processed by the BPE. This exceeded the maximum retry count of unwanted retries, when the messages are stuck in the MAIN_INBOUNDQ. |
| JR36527 | With this FixPack, logging of duplicate AS documents is handled efficiently. | |
| JR37675 | With this FixPack, now if the "PartyID" has a type other than "urn:duns", and if it is configured in the connection attribute for that partner, then that value is used during the packaging of the ebMS acknowledgement. | |
| JR37684 | According to an interop consensus line item, "SOAPAction" header is not mandatory for synchronous ebMS response. This FixPack allows processing of a synchronous response message even if the SOAPAction header is absent. | |
| JR37685 | During ebMS message flows, it was observed that the "MessageId element" value was not setting up correctly on the ebMS Ping message that was sent outbound. This resulted in having an incorrect RefToMessageId in the ebMS PONG message, and "a B2B capability not found" error message for the received EBMS Pong message. This problem is resolved in this FixPack. | |
| JR37688 | With this FixPack, as per the ebMS specification, the "Timestamp" element in the StatusResponse displays the time when the request message, whose status is being queried was received. | |
| JR37689 | The WebSphere Partner Gateway rejects the stray acknowledgement received for an ebMS request document that is not in the WebSphere Partner Gateway system without logging any error messages in the log files. | |
| JR37691 | With this FixPack, the "PersistDuration" is correctly inserted or updated as currentTimeStamp + PersistDuration set in the "BP_RM_STATE_DTL" table. | |
| JR37693 | The way the Persist Duration value for an ebMS document is calculated has been changed as follows: a) If the "x-aux-TimeToLive" attribute is not present, then the source side attribute value of Persist Duration is used as the message TimeToLive. b) If the PersistDuration is set to an incorrect value that results in NumberFormatException, then a value of RetryInterval * (Retry Count +1) is used as the PersistDuration. c) If the PersistDuration attribute is set as 0 or -1, then the PersistDuration defaults to 7 days. | |
Document Manager/EDI | JR34071 | The FA generated during EDI Interchange Validation action did not contain FA for each of the transaction present in the EDI document being validated. |
| JR35640 | When the action EDI Validate Interchange was used, duplicate EDI transaction was not rejected. | |
| JR36013 | Earlier, Functional Acknowledgement (FA) for an EDI document did not get associated with the document for which it was generated. | |
| JR36031 | During the validation of an EDI Interchange, the validation events generated using the action EDI Validate Interchange were not shown in the document viewer details. | |
| JR36068 | With this FixPack, the RE-ENVELOPED EDI-X12 Document’s transaction segment count remains the same and does not increment by 2. | |
| JR36078 | Earlier, the RE-ENVELOPED EDI-X12 Document's transaction segment count was expected to remain the same, but it incremented by 2. With this FixPack, the RE-ENVELOPED EDI-X12 Document's transaction segment count remains the same. | |
| JR36243 | While using EDI interchange validation, BCGEDIVA0011 related errors were issued. The failure happened because SV504 and SV505 erroneously reported as missing. | |
| JR36395 | While processing a 40 MB document of type-837 edi having HL Loops, out of memory problem used to occur. | |
| JR36537 | Earlier, when the action was "EDIValidateInterchange", the EDI X12 997 FA document was not getting processed. | |
| JR36560 | Earlier, the EDI ReEnveloper was setting the UNT01 (TRANSACTION SEGMENT COUNT) with a wrong number. Additionally, the UNT01 (TRANSACTION SEGMENT COUNT) of the incoming document and the outgoing document should be the same, but was different. | |
| JR37076 | With this FixPack, the redundant logging of the "FileNotFound" exception has been removed. | |
| JR37181 | While using EDISplitter, if any failures were seen, WebSphere Partner Gateway would not move the files from the receiver directory to reject the directory if any failures were seen while using th eEDISplitter. | |
| JR37412 | Earlier, during reenveloping with deenveloping, large messages failed due to the validation of the documents, which was not required. | |
ebMS | JR36989 | If an ebMS document fails with unsupported ebMS version event, then all subsequent ebMS documents failed, even if they were supported ebMS versions. |
| JR37062 | With this FixPack, the document is marked as failed for any unsupported version of ebMS. | |
| JR37686 | With this FixPack, the problem in having the "Syncreply" element, when the "MessageOrder" element is present is corrected. Now, as per the specifications, when the the "MessageOrder" element is present, only "DuplicateElimination" element will be present in the ebMS document, but the "Syncreply" element will not be present. | |
Event Engine | JR34907 | With this FixPack, event 'BCG250008', 'Document delivery to Partner Destination failed' gets logged appropriately. |
FTP Scripting / FTP Client | JR37694 | With this FixPack, support for passive mode has been provided for the FTP Client. |
Installation/FTP Server | JR31636 | When an integrated FTP server was installed as a Windows service, it could not be started as Windows services. |
Integrated SFTP server | JR36766 | While using with WebSphere Partner Gateway Integrated SFTP Server, the posting of a document delivery to a SFTP destination failed and displayed "com.ibm.j2ca.ftp.exception.FTPOperationsException: 2: No such file: <directory_name>" error message. |
| JR37476 | While accessing the WebSphere Partner Gateway integrated SFTP server, the absolute path for example - "remote directory is /opt/IBM/PG62/Ftpserver/data/config/ftpadmin" of user directory was being exposed to SFTP client. | |
| JR37753 | When WebSphere Partner Gateway was installed on DB2 9.5 on Windows 32 bit environment, the "startsftpmgmtserver" script displayed "Warning: No host key defined for the server" warning message while starting the sftpmanagement server. | |
| JR37932 | For public key verification for the integrated SFTP user, WebSphere Partner Gateway needed the private key of the user for uploading along with the passphrase. | |
Receiver | JR36241 | With this FixPack, the POP3 User Exit Receiver Handler works with the WebSphere Partner Gateway without any problem. |
Receiver/FTP Directory | JR35549 | Earlier, an unhandled exception in the "FTPDirectoryReceiver" resulted in the ObjectFIFO object growing continuously. This resulted in logging of OutOfMemory exceptions in the log files. |
Receiver/FTP receiver | JR36077 | After creation or deletion of any folders from the FTP Root Directory when the polling of WebSphere Partner Gateway FTP receiver was on, the FTP Directory receiver - 'FTP Receiver' used to hang. As a result of this, the files were not picked up from any of the FTP receivers created. |
Receiver/HTTP | JR35521 | Earlier, an HTTP 401 response was sent back without the required "WWW-Authenticate" HTTP header, when a partner sent a message to the HTTP receiver without having the user ID and or password authentication. With this FixPack, the "WWW-Authenticate" header will be present in the HTTP 401 response as per the information specified at http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html. |
Receiver/JMS | JR37683 | With this FixPack, additional trace statements are introduced for finding the cause of jms receiver failures. |
RNIF | JR36844 | The 0A1 mandates the presence of the “GlobalSupplyChainCode” and “GlobalPartnerClassificationCode” elements. The incoming 4A5 V11.00.00 needs to supply this information. There is no place in the 4A5 ,3B2,7C7 , 7C8 RNIF PIP Packages to handle this. |
Security | JR37328 | Earlier, while performing Client Authentication for FTPS destination using chain certificates, the SSL Client authentication would fail in WebSphere Partner Gateway, if only leaf certificates were uploaded. In an ideal scenario, the user was required to upload the entire chain of certificates at the FTP server end. |
| JR37695 | When an invalid primary, and a valid secondary certificates were uploaded, Client Authentication for FTPS mode did not work. | |
| JR37806 | When the Private Key was being read from the Database, extraneous data was being written to the internal output buffer when the Private Key was large in size. | |
Server-AS2 | JR35698 | Earlier, when the value of the Content-Disposition was set to "Attachment", the positive MDN was received in the WebSphere Partner Gateway console displaying "MDN Disposition Errors" error message. |
Server performance | JR36701 | With this FixPack, the temp files will be written in the rolling directories in a tmp folder, which will be created at the location defined under “bcg.bpe_temp_directory.main” directory. This has also substantially improved the performance. |
Server resend | JR37442 | Earlier, resending of the target document failed and displayed "File does not exist" error message. |
[{"Product":{"code":"SSDKKW","label":"WebSphere Partner Gateway Advanced Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.2.0.5","Edition":"Advanced;Enterprise","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27019782