Product Readmes
Abstract
IBM® WebSphere® Partner Gateway provides periodic fixes for release V6.1.1. The following is a complete listing of fixes for V6.1.1.
Content
WebSphere Partner Gateway V 6.1.1 Fix Pack 2 |
| Fix release date: 16/07/2010 V6.1.1 Fixpack2 Advanced Download V6.1.1 Fixpack2 Enterprise Download |
| Component | Tracking Number | Description |
AS | JR31380 | Earlier, some bytes of data were present in the compressed data, which did not allow the document flow in WebSphere Partner Gateway to complete successfully. |
| JR31807 | The exception – "com.ibm.websphere.ce.cm.DuplicateKeyException" was getting logged for some AS2 messages. This FixPack avoids duplicate attempts for logging the same header data. | |
Archiver | JR32834 | When DB2 was installed in Swedish locale, the archiver failed to archive data. |
| JR34518 | With this FixPack, the entire "msg_store" directory does not get deleted when you run archiver on a system that was migrated from 6.0. | |
| JR37038 | Previously, the BCGDBNONREPEXPORT.bat script did not work for all months of a year. It displayed error message "The input date format is not right. It should be YYYYMMDD". | |
Certificate Management | JR32212 | Previously, the error message "No valid signing certificate found" displayed once out of 400 messages in a transaction. However, the transaction, displaying this error message was processed successfully on resend. This problem is resolved in the database processing to avoid any timing issues in getting the certificate from the database. |
Console | JR29947 | In this FixPack, WebSphere Partner Gateway Viewers are enhanced to support systems with Russian locale. |
| JR30846 | With this FixPack, in the Create XML page of WebSphere Partner Gateway console, the values in document type drop down list are sorted as unique values along with the code. | |
| JR31723 | In this FixPack, the PIP Code for Rosettanet PIP messages display in the document details screen of the document viewer. | |
| JR31832 | Previously, the event description for BCG210013 - 'Connection not fully configured' displayed incorrect values for the event. | |
| JR32207 | In this Fix Pack, FA Overdue report is enhanced to support pagination. | |
| JR32275 | Prior to this fix, download of CPA from Oracle database through Partner Gateway Console resulted in a 0KB file. This is corrected with this FixPack. | |
| JR32276 | Previously, RosettaNet viewer did not display the PIP code in the process details screen, but displayed the Operation Mode instead. Also, in the RosettaNetviewer search result screen, Operation Mode was shown twice. | |
| JR32386 | Previously, the console HTTP requests were trapped and injected with the SQL code, which lead to a security hole. The problem of SQL injection threat is resolved in this FixPack. | |
| JR32387 | Prior to this fix, when a CPA was downloaded from the EBMS CPA list screen and the search link was clicked, it inappropriately displayed the dialog window for CPA download. | |
| JR32399 | In this FixPack, a user can be created with the same name as that of a deleted partner's user name. | |
| JR34373 | While uploading new chain certificates in WebSphere Partner Gateway console, the 'Cert path is not valid' error message was displayed on click of "Validate" button. However, this error message did not display after restarting the WebSphere Partner Gateway servers. This problem occurred because the cache refresh was not happening, and so the new certificates were not getting loaded in the cache. | |
| JR36089 | Previously, in the console of WebSphere Partner Gateway, setting the time to "Central Time (GMT -6:00 DST)" did not work because the time shown was exactly the same as "Central Time (GMT -6:00)" time. Moreover, the Daylight Saving Time (DST) did not make any difference. | |
| JR32946 | When the user tried to create an alert using the following procedure, an error message "An Alert with this name already exists. Alerts must be unique." was displayed. 1. Save this alert without navigating to the "Notify" page. 2. Click on Notify page. Subscribe any contact and save this page. | |
| JR34555 | The volume alert create page did not save the correct frequency whenever the defined frequency was more than 7 days. | |
Console/EBMS | JR33933 | From this FixPack onwards, the EBMS Viewer in WebSphere Partner Gateway console displays the retried documents under a conversation. |
| JR34530 | The EBMS Viewer and the document viewer displayed incorrect timestamps. The timestamp of the retried document was same as that of the original received document. The timestamp problem is resolved in this Fix Pack. | |
Console/EDI | JR36863 | Previously, when the data was imported from an EIF using the EIF Import wizard, all translational tables were not successfully imported. Additionally, after running the import wizard, the translation table entries were seen missing. The problem in the EIF import wizard is resolved. |
Console/EDI-Reports | JR33507 | SQL exception occurred when the user selected Functional Acknowledgment overdue reports using multiple From and To partners. Now, users can retrieve reports for large number of partners at once. |
Console/Resend | JR34815 | The target resend for Rosettanet document from the WebSphere Partner Gateway console failed. |
| JR35176 | The target resend for AS document from the WebSphere Partner Gateway console failed. | |
| JR35177 | The target resend for EBMS document from the WebSphere Partner Gateway console failed. | |
Database | JR37222 | The DB2 database instance ID which is used for executing the Archiver scripts is now corrected. |
| JR36896 | When a duplicate insert was done to the LG_AS_HDR table, it resulted in an incorrect error message. The message, "LG_AS_HDRI_ah1 failed with error code = 2. Error msg = RAN SUCCESSFULLY!” was logged in the System.out file. From this FixPack onwards, it displays "LG_AS_HDRI_ah1 failed with error code = 2. Error msg = DUP_VAL_ON_INDEX " error message. | |
| JR37037 | In this FixPack, the tablespace quota is correctly assigned to MAS database of WepSphere Partner Gateway. | |
| JR34769 | In this FixPack, the MAS database script does not fail while creating the required indexes on the MAS database tables. | |
| JR37222 | The mirroring problem of LOB DB2 data for certificates to enable DB2 HADR usage is resolved. Now, all LOB columns are logged and can be mirrored. To enable DB2 HADR usage, the mirroring problem of LOB DB2 data for certificates is resolved. Now, all LOB columns are logged and can be mirrored. | |
Destination/File Directory | JR33901 | Previously, while using a File Directory Gateway configured to a physical location on a Unix platform, it was observed that the file permissions set on the transferred files were inconsistent. Additionally, some of the files had rw-r-r permission and few other files had rw-rw-rw permission. This inconsistency is corrected in this FixPack. Now, all the files have the intended permission of rw-rw-rw on the files transferred using the File Directory Gateway. |
Destination/HTTP | JR29147 | With this FixPack, you can configure a value, which will use the transfer encoding as chunked while sending the HTTP document. Using the "bcg.http.requestSizeForChunking" parameter from the System Properties, this value can be set as number of bytes. Note that you can retain the default value 2147483647 unless it is required to change. |
Destination/JMS | JR36869 | When there were no transport headers attached to the response document, the custom destination PostProcess handler failed to introduce the response document into the WebSphere Partner Gateway flow. |
Destinations/Console | JR31355 | In WebSphere Partner Gateway console, the results of destinations "Where User" displayed all connections instead of displaying specific participant connections on which the destination was configured. |
Document Manager | JR30376 | In this FixPack, DB2 CPU utilization is substantially improved. |
| JR30558 | The default threshold for storing messages is increased to 1 MB. This facilitates storing of documents below 1 MB in the message store. A threshold value of 0 or -1 overrides the restriction of message threshold and stores all the messages into the message store. | |
| JR32901 | When WebSphere Partner Gateway was installed in distributed mode with multiple routers, it intermittently displayed "*_PROT.TMP DOES NOT EXIST" error message. This triggered the "BCG250002" event while routing the documents. | |
| JR34498 | On Oracle, WebSphere Partner Gateway intermittently logged "SQLException ORA-00001: unique constraint violated" error while processing customer XML transactions. | |
| JR36898 | For a signed document, the payload content type did not contain any information about the payload encoding. This caused the UTF-8 data to be saved as ASCII, resulting in corruption of data for partners, who used non – WebSphere Partner Gateway software to receive AS Message. In this fix pack, a channel attribute is used to set the encoding over the channel that sets it on the payload. | |
| JR36902 | The reprocessDbLogging script is not successful if the ws_runtime.jar is not found in "<WAS_HOME>\deploytool\itp\plugins\com.ibm.websphere. <Version>" directory. However, while applying WebSphere Application Server FixPacks, the <version> part changes caused the failure of a batch file. In this FixPack, if the script fails, a warning message displays so that the user can change the ws_runtime.jar location. | |
| JR36903 | Previously, when an external trading partner repeatedly sent the same AS2 document with same message-id in HTTP header, WebSphere Partner Gateway did not reject the AS2 document as a duplicate message instead processed the document successfully. | |
| JR36906 | In this Fixpack, using the FTP scripting, target can process "mput" command with wildcard expression. For example, mput *.doc. | |
| JR37008 | 3A4 v2.00 PIP package was not in accordance with its corresponding message guideline, it caused a validation error while routing a valid 3A4 v2.00 RN document. The problem is resolved in this FixPack by correcting the PIP package. | |
Document Manager/AS | JR33552 | When a synchronous response with just a "LF" and not "CRLF" was appended to the header, WebSphere Partner Gateway failed to parse the content-type field, which caused the document to fail. |
| JR36904 | When "Allow AS Documents with Duplicate Message ID channel" attribute was set to Yes, the AS2 dupcheck procedure (PR_AS_DUP_CHECK) was called, which resulted in performance problems. | |
Document Manager/BPE | JR32679 | Previously, in a deployment topology that had a network firewall in front of the database, it was observed that on firewall timeout, some of the poll engines of WebSphere Partner Gateway had long running transactions that were severed. This resulted in a lot of StaleConnection exceptions and the connections from the pool were exhausted. This eventually led to ConnectionWaitTimeout exceptions. In this FixPack, the poll engine logic is corrected to use UserTransactions instead of shareable connections under LTC boundary. |
| JR33284 | Previously, some resent documents remained in the "in-process" state, and issued many BCG210022 "Process transaction rolled back" events. | |
Document Manager/EBMS | JR32225 | WebSphere Partner Gateway did not put the RefMessageID element in the packaged ebXML document, even though the backend header "x-aux-request-msg-id" was present in the document from the backend. |
| JR32404 | Previously, while performing transactions with EBMS documents having Oracle as a backend database, it was observed that the WebSphere Partner Gateway logged "ORA-01000: maximum open cursors exceeded error" SQLException. In this FixPack, some of the EBMS related classes were corrected to explicitly close the ResultsSet objects, which in turn mitigated the occurrence of the ORA-01000 problem. | |
| JR32817 | Although the "ConversationConstraints" element in the CPA was optional, the console of WebSphere Partner Gateway prevented the upload of a CPA that did not have the "ConversationConstraints" element. | |
| JR32895 | WebSphere Partner Gateway did not place the RefMessageID element in the packaged ebXML document, even though the document from backend had the x_aux_request_msg_id" header. | |
| JR33990 | For EBMS conversation, the "acknowledgment" and the "Message error" for EBMS document were under the conversation constraint check. With this fixPack, these have been taken out of the conversation constraint check. | |
| JR34051 | During activity logging, some errors prevented the completion of EBMS state logging, so during EBMS logging, some transactions were seen in the "in process" state even though they had reached their end state. | |
| JR34133 | Many duplicate key exceptions were seen in the log files while performing EBMS documents transactions. These exceptions occurred while logging the retried documents. | |
| JR34521 | Under load, when EBMS retries and outbound acknowledgements were posted to the internal queue of MAIN_INBOUNDQ, the messages piled up in the MAIN_INBOUNDQ. As a result, inbound acknowledgements were processed after a significant delay, which generated in unwanted EBMS retries. | |
| JR34571 | During EBMS retries, the retry count of EBMS documents were updated only after the retried document was processed in BPE. When the retries were stuck in the MAIN_INBOUNDQ, and when the retry interval was of less duration, it lead to retries more than configured value. | |
| JR34693 | With this FixPack, if the "x-aux-create-datetime" header is present, then its value should be set as the document's timestamp for the EBMS document. If the "x-aux-create-datetime" header is missing, then the system time when the document was received, should be set as the document's timestamp, and the same timestamp should be displayed in the viewers. | |
| JR34718 | EBMS performance is substantially improved in this FixPack. | |
| JR34923 | In this FixPack, when multiple verification certificates are uploaded on the receiver hub, the XML Signature verification process does not fail for signed EBMS document. | |
| JR36894 | If the document failed at the gateway, EBMS retries did not work at the EBMS protocol level. | |
Document Manager/EDI | JR33035 | A precision problem in double arithmetic resulted in an unexpected result, when the "NumFormat" function was used in the transformation map. |
| JR34401 | As the inbound document did not display the associated 997 when there was a syntactical error prior to EDI transformation, failed inbound message displayed when the user viewed the document using document viewer. | |
| JR33539 | In this FixPack, the problem of the null pointer exception accompanied with "Unexpected Exception Occurred" events (BCGEDICM0001) during inbound 997 processing is resolved. | |
| JR35028 | Due to the locking of an Enveloper problem, some EDI Documents indefinitely got stuck in the "In-Progress" state. | |
| JR36870 | With this FixPack, you can produce the desired output by using the "ROUND" and "TRUNCATE" map functions in transformation maps. | |
| JR36912 | Unhandled exceptions resulted in losing the FTP error events without being displayed to the user. | |
Document Manager/FTP | JR32934 | In the WebSphere Partner Gateway console, while delivering an EDI interchange having multiple transactions over FTP scripting gateway by having unique file name option de-selected, all de-enveloped transactions are shown as "in process". |
Document Manager/FTP Scripting | JR36910 | The scheduler stopped when the thread for polling FTP Gateway folder was run having the FTP Scripting Gateway disabled. During such instances, even after the FTP Scripting was enabled, there was no polling of the FTP gateway for delivering the document. |
| JR36914 | In case of FTP Scripting Gateway, the MetaData.sql had two configuration point ID entries for the gateway preprocess handler. When the available handlers were loaded in the Scripting Gateway configuration screen, it displayed erratic behavior. | |
Document Manager/JMS Gateway | JR36905 | In this FixPack, the document delivery does not fail when the user sends enveloped document through a JMS Gateway. |
Document Manager/RNIF | JR30201 | In this FixPack, the Content-Transfer-Encoding header is set during RNIF packaging. |
| JR32229 | Routing a 4B2 PIP document using Rosettanet Participant Simulator failed due to incorrect PIP version mentioned in the contents of the PIP package. When the simulator failed, "B2B Capability not found" error event was displayed. | |
EDI | JR32039 | When there was a double quote within the ROD data fields, WebSphere Partner Gateway displayed "Missing Record Delimiter" BCGEDIUP0038 error message. |
| JR32457 | Whenever batch of acknowledgments were processed, WebSphere Partner Gateway displayed "an unexpected exception occurred in component: EDIAckProcessor.Exception text: java.lang.IllegalArgumentException: Unmatched braces in the pattern" error message. This error message was displayed because the character "{" present in EDI document was treated as a special character. | |
| JR33448 | Duplicate documents were generated by WebSphere Partner Gateway due to the locking mechanism used by the Enveloper. | |
| JR34275 | During multiple router setups, Enveloper was processing documents without acquiring locks which resulted in duplicate Envelopes. | |
| JR36899 | The ALC loop in table number 3 of EDI99b dictionary is now getting detected during transformation. | |
| JR36913 | An error message “ArrayIndexOutOfBounds Failed inbound” was displayed when viewed using document viewer. The inbound document did not show the associated 997, when there was a syntactical error prior to EDI transformation. This exception occurred during transformation when locale was set to Chinese. However, the same exception did not occur when locale was set to en_us. The problem relating to the locale is resolved in this FixPack. | |
Event Engine | JR31549 | The BCG250004 event alert now works for both, inbound and outbound documents. |
| JR34907 | In this FixPack, the event 'BCG250008', 'Document delivery to Partner Destination failed' is correctly logged. | |
Event Processing | JR33576 | During WebSphere Partner Gateway document processing on Oracle, the logging of WebSphere Partner Gateway generated events that produced unique constraint violated log statements. These statements were misleading as the events were logged properly. |
Infrastructure | JR31016 | When a failover (HACMP) occurred for MQ, the connections to MQ were not picked up again. Instead, WebSphere Partner Gateway displayed "BCG103203 - Receiver 'JMS:TO.WPG.EXT,JMS' failed to processing document" error message in the Event Viewer. |
| JR31749 | uring the following conditions, high volumes of document transaction caused the document processing to stop abruptly. The following errors were seen in the log file: 1. JMSQueueSende E com.ibm.bcg.util.JMSQueueSender sendMessage JMS Exception occurred for queue: jms/bcg/queue/main_InboundQ javax.jms.JMSException: CWSIA0067E: An exception was received during the call to the method 2. JmsMsgProducerImpl.sendMessage (#4): com.ibm.websphere.sib.exception.SIResourceException: CWSIC8007E: An exception was caught from the remote server with Probe Id 3-008-0007. 3. Exception: com.ibm.websphere.sib.exception.SIResourceException: CWSIP0002E: An internal messaging error occurred in com.ibm.ws.sib.processor.impl.ConsumerDispatcher, 1:692:1.282,com.ibm.ws.sib.msgstore.RollbackException: 4. CWSIS1002E: An unexpected exception was caught during transaction completion. 5. Exception: com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1500E: The dispatcher cannot accept work. | |
| JR32160 | In this FixPack, the classes that deal with Native Library are moved to server level class loader. Henceforth, when an application is restarted, it does not display the "UnsatisfiedLinkError" error. | |
| JR33357 | When JMS destination was configured on WAS SIBUS other than where WebSphere Partner Gateway was hosted and the corresponding messaging engine was unavailable, WPG issues retired on JMS destination. However, events for the retry attempts were not seen from event viewer. With this FixPack, for this specific scenario, the retry events are logged and can be viewed from WPG event viewer. | |
Installer | JR32660 | From this Fixpack onwards, if any user or group other than bcguser or bcggroup is provided, the FixPack Installer installs successfully. |
Partner Migration | JR30754 | With this FixPack, XML Formats can be migrated from any previous versions of WebSphere Partner Gateway. |
| JR31241 | While using BCGMigration import utility, null pointer exceptions were seen in "processConnectionList" attribute. These exceptions occurred in the code where imported envelop profile names were not looked up properly in later references. The null pointer exception related problems are resolved in this FixPack. | |
| JR32149 | With this FixPack, while importing WebSphere Partner Gateway configuration using partner migration, partner not found related error messages will not be displayed for a particular connection. | |
| JR36901 | While exporting routing objects, the partner migration utility failed and displayed "Exception in getRoutingObjectListXML():com.ibm.bcg.shared.VCBaseException" exception message. | |
Receiver | JR36263 | The FTP Scripting Receiver with lock User turned ON, stopped polling after a prolonged run and it needed a server restart to get it to poll again. This problem is resolved in this FixPack. |
| JR36868 | DB connections were left open during Receiver startup. This happened when there were a number of Receivers of different transport types. Also, most of these receivers had custom handlers defined for them. | |
Receivers/Console | JR31356 | If the file receiver existed, the "operation mode" for receivers did not work. Additionally, an error message stating that the directory cannot be created was displayed. |
Receiver/FTP Scripting | JR34653 | Previously, in case of FTP Scripting receivers with LOCK USER set to Yes, stray locks in the "LG_LOCK_FTPSCRIPT" table resulted in indefinite wait time for a lock. As a result, the FTP Scripting receivers were not polling. This is corrected in this FixPack. |
| JR36915 | FTP Scripting target failed with an unhandled exception while receiving files having numeric filenames for example 22.txt, 33.txt, 12.txt or 1.txt. | |
Receiver/JMS | JR36225 | In this FixPack, Trace statements are added to log JMS Receiver to track JMS Receiver failures. |
| JR36911 | From this FixPack onwards, JMS receiver does not fail to receive a document if the "topic://" attribute is specified in the header <Destination> tags. | |
Security | JR30564 | With this FixPack, when an existing Primary certificate expires, the secondary certificate displays as a primary certificate for the same security function. |
| JR32566 | The length calculated of encoded data of "EncapslatedContentInfo" did not include the length of the identifier, which was causing the length of CompressedData content to be less by one. This was causing the exception to occur and hence decompression was failing. | |
| JR32617 | The expired primary certificate is now automatically replaced by a secondary certificate in case of EBMS flows. |
[{"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.1.1.2","Edition":"Advanced;Enterprise","Line of Business":{"code":"LOB59","label":"Sustainability Software"}},{"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.1.1.2","Edition":"Enterprise","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27019161