WebSphere Partner Gateway 6.0.0 Advanced Edition Fix Pack 4

Download Description

This fix pack is cumulative and includes all fixes released in earlier fix packs for the V6.0.0 release of WebSphere Partner Gateway.



NEW IN THIS FIX PACK
=====================

JR23409:
The second action (response) of the two way PIP can not be sent based on the PIP-instance-ID. The response document can be co-related only by using the document ID contained in the request. With this fix pack, it is possible to co-relate the second action (response) based on either the request document ID or based on the PIP instance ID.

The following property has been added in bcg.properties file.

"bcg.rnif.pip.twoaction.correlation" with default value of "documentid".The possible values are "documentid" or "pipinstanceid", The values are case sensitive.

If "bcg.rnif.pip.twoaction.correlation" is set to "pipinstanceid" and the PIP instance ID is not available in the response document, the document ID of the response will be used.



PRODUCT FIX HISTORY
======================

The following problems were fixed in this fix pack.


JR22742:
To allow specifying the syntax for the ROD documents in the custom handlers, following attributes have been made public.

- BCG_TPA_PREFIX_FROM
- BCG_DOCSYNTAX

The following constant has been made available to be set as the syntax.
- BCG_ROD


JR22974:
While sending a document from WebSphere Partner Gateway to WebSphere Process Server (WPS), If the protocol header name is not present in the "packagingHeaders" business object, the following error message is displayed in the SystemOut.log file of WPS. This issue has been resolved with this fix pack.

warning : Error in the element JMS-IBM-MsgTypeMsg :Class 'BCGPackagingHeaders' does not have a feature named JMS-IBM-MsgTypeMsg.


JR23067:
The console raw document viewer does not show a xml end tag when displaying an xml document with no space after the end tag. This has been corrected in this fix pack.


JR23092:
In some cases, the summary data shown in the summary pages was incorrect. With this fix pack, the summary counts now show correct data.


JR23161:
WebSphere Partner Gateway v6 provides support for an additional XSD-based PIP, 7C7. With this fix pack, the 7C7 PIP packages (Notify of Semiconductor Test Data) are included.


JR23218:
As the amount of non_rep numbered subdirectories increased, in some instances, the non_rep data was being written to an older archived number rather than the latest numbered subdirectory. With this fix pack, the behavior is corrected.


JR23240:
The receiver overwrites the "content-length" header with the content length that was read. With this fix pack, the receiver maintains the incoming content-length that is associated with the request.


JR23241:
During heavy load transactions, the end state of the transactions does not get logged because of lack of logger objects. The values for these properties can be increased in case of a large number of gateway threads.

With this fix pack, the logger objects have been made configurable by adding two new properties in the router’s bcg.properties :

- bcg.delivery.numberOfLoggers : This property defines number of logger objects with default value of 10.
- bcg.delivery.loggerTimeOut : This property defines the timeout period (in milli second) while waiting for a logger object with default value of 10000.


JR23268:
When the number of gateways in WebSphere Partner Gateway is configured to more than 100, at times the Document Manager may encounter a NullPointerException during the start up. With this fix pack, sequence tags are introduced in the "router-cacheEngine.xml" file located under <installed_path>/<bcghub>/router/lib/config to load the cache based on the sequence number.


JR23285:
An xml document is shown with incorrect indentation in the raw document viewer, if the document has self closing tags. This is corrected with this fix pack and the raw document viewer displays the xml document with correct indentation.


JR23287:
WebSphere Partner Gateway fails to process RNIF documents encoded in "Quoted-printable". This is fixed in this fix pack.


JR23331:
Database connection leak occurred during the startup of the Document Manager when loading the Gateway Cache. With this fix pack, database resources were released appropriately in order to avoid database connection leak.


JR23339:
File descriptor handles were not getting closed when message was posted to WebSphere Partner Gateway over the JMS target. With this fix pack, the File descriptor handles are appropriately closed.


JR23374:
An incomplete message (having incorrect Content-Length) is consumed by the receiver. With this fix pack, an incomplete message will be rejected by sending an appropriate HTTP message.


JR23408:
A ROD document containing messages destined for multiple partners does not get successfully processed. Only the first message gets consumed, while the other messages remain in "InProcess" state. This behavior is corrected in this fix pack.


JR23452:
In multiple router setups, during heavy loads, a few documents get delivered twice. This behavior has been corrected with this fix pack.


JR23484:
After successive RNIF transactions, the average transaction time increases, resulting in performance degradation. With this fix pack, the processing time is tuned to be consistent even during heavy RNIF transactions.


JR23491:
In the case of exceptions during the end state logging, the end state events were lost. With this fix pack, in such cases, the event is logged into the DataLogErrorQ. These events can be processed offline using the reprocessDbLoggingErrors script located under <installed_path>/<bcghub>/bin


JR23497:
The FTPScripting Gateway was not setting the document state to "delivered" even after delivering the document to the FTP server causing the document to be resubmitted for delivery during every retry configured. This was happening only in case of ROD to EDI conversion. This has been fixed in this fix pack.


JR23541:
Sometimes, during heavy loads, event logging procedures could cause database deadlocks. With this fix pack, the event logging procedures have been modified to avoid deadlock situations.


JR23565:
If the document sent from WPG to WPS does not contain namespace value set, the data binding is not able to create a business object. This has been corrected with this fix pack.


JR23570:
During RNIF transactions, the data validation error pop up screen does not display the error description in proper format. The display is corrected with this fix pack and the error description is displayed in correct format.


JR23608:
Incorrect format of 3B2 PIP caused Data Validation errors. In the enumerations for "GlobalPartnerRoleClassificationCode", the "fromRole" was set to "Receiver" and the "toRole" was set to "Shipper". In this fix pack, the assignments are corrected. Now the "fromRole" is set to "Shipper" and the "toRole" is set to "Receiver".


JR23621:
When a document is routed to FTP scripting gateway and the document transaction fails for any reason (for example, wrong username or password), the event "Document Failed" does not appear on the console document viewers. The document viewer displays the red mark indicating document failure, but the events for failure are not getting displayed. With this fix pack, the events for failure are also displayed.


JR23726:
The decimal value defined in the ROD input data is not being handled as per the definition of the data type. If the decimal data value is 0 or not mentioned, the resultant field after mapping would have missing data or unrecognizable characters. This has been corrected with this fix pack.


JR23743:
When the source partner is unknown and the user tries to navigate to the details pop up in document analysis screen, the popup text displayed was null. This issue has been corrected in this fix pack.


JR23752:
The namespace mapping is stored in the DIS tables. In Oracle, the namespace lookup based on the dictionary name was returning NULL and causing error in the output. This has been corrected with this fix pack.


JR23757:
When creating a target, if the "Poll Interval" is set to a value more than 32 seconds, the target does not get created and returns with SQLCODE: -413 error. This problem is applicable only on DB2 systems and has been corrected with this fix pack.


JR23765:
In multiple router setups, during heavy loads, a few documents get processed twice, which leads to processing failure.


JR23766:
When a document transaction is rolled back automatically because of any processing issues, the router logs still indicate that the stop process had been initiated by the user. With this fix pack, this message gets logged only in scenarios where the stop process is initiated by the user.


JR23806:
In the event of HTTP session expiry, the Event Viewer and Document Viewer pages throw HTTP 500 error. With this fix pack, the user is directed to the login page.


JR23811:
With Oracle 10.1.0.4, RNIF flow throws exception for non-English locales. This has been corrected with this fix pack.


JR23839:
The "Proxy Host" field in console was limited to 30 characters. With this fix pack, it can contain upto 90 characters.


JR23845:
Enveloper throws database deadlock errors while processing ROD documents having a large number of transactions. With this fix pack, the transaction processing flow has been modified to avoid deadlock situations.


JR23850:
RNIF Acks were not getting generated on systems with Oracle 10.1.0.4. This problem occurred only when the document was received the first time. This behavior is corrected with this fix pack.


JR23866:
The Archiver looks for the presence of .vcm files. This makes the deletion operation slow, as .vcm files do not exist in the msg_store directory. With this fix pack, the Archiver does not check for .vcm files in the msg_store directory, thus making the search faster.


JR23885:
POP3 Target continuously polls the Mail Server irrespective of the poll interval set in the POP3 target configuration. With this fix pack, the polling schedule is based on interval or calendar.


JR23887:
Document Manager was unable to send back the synchronous MDN for a request within the timeout period of receiver. With this fix pack, the following changes have been done to correct this problem.

Caching is enabled for the channel parse and destination parse. A new property bcg.destinationCache.expiry is added in "bcg.properties" located under <installed_path>/router/lib/config for the expiry interval for the destination cache.

A new port 57081 (default setting) has been opened on the receiver profile. This port will be used for sending back the synchronous MDN from Document Manager to receiver. If the user wants to use a different port, the port can be changed by executing the bcgModifyPortsV6.jacl script located under <installed_path>/bcghub/scripts

The syntax for executing this script is :

./wsadmin.sh -f <installed_path>/bcghub/scripts/bcgModifyPortsV6.jacl <cellName> <nodeName> <serverName> <hostName> <PortType> <NewPortNumber>

For example,
./wsadmin.sh -f <installed_path>/bcghub/scripts/bcgModifyPortsV6.jacl DefaultNode DefaultNode bcgreceiver wpgblade HTTP3 57082

Make sure the receiver is restarted and the new port number is reflected in "bcg.receiver.sync.responseURL.port" property in the bcg_receiver.properties file located under <installed_path>/receiver/lib/config.



JR23889:
Certificate expiry alerts were generated for disabled certificates. With this fix pack, certificate expiry alerts are generated only for the enabled certificates.


JR23895:
A signed document sent from the WebSphere Partner Gateway to Cyclone product fails with "Unexpected-Processing" errors. This has been corrected in this fix pack.


JR23989:
POP3 Receiver throws ArrayIndexOutOfBoundsException for messages having more than 2000 characters in content header. This has been corrected in this fix pack to handle a large content header.


JR23996:
The WebSphere Partner Gateway v6 generates UNA segment only when the EDIFACT delimiters used were the non default delimiters. In certain versions of EDIFACT, the UNA segment has to be generated even with the default delimiters. The product has been updated to handle the generation of the UNA segment based on UNB01 element value in addition to the delimiters. If the value of UNB01 element is not UNAOA and default EDIFACT delimiters are used, the UNA segment will be generated.


JR24016:
When WebSphere Partner Gateway sends a signed and compressed document, the AS2 headers do not contain "Content-Disposition". With this fix pack, this header is included.


JR24027:
In the SenderFramework, there were MQ connection leaks while logging events to queue. With this fix pack, the MQ resources are handled appropriately to avoid connection leaks.


JR24049:
SenderFrameWork throws an exception when unable to rename the tmp file in the response directory. This has been corrected with this fix pack.



KNOWN PROBLEMS AND WORKAROUNDS
=======================================

The following problems have been found in this fix pack:


1). When a document is sent to WebSphere Partner Gateway via AS2 and if AS2 Package IDs and Content IDs differ, the document fails in WebSphere Partner Gateway. Even though the document fails, the event information is not very clear explaining the reason for document failure. In the event text, "From Partner ID" should read "From Content Partner ID" and "To Partner ID" should read "To Content Partner ID".

2). When a large number of documents are in process state and the 'Stop Process' link from console is clicked for any such document, the document processing may not get stopped since it is already processed and delivered. For such a document that got delivered during the time 'Stop Process' was invoked, the event 'Failed to stop the processing' might not get published on the console.

3). The server does not do any further processing of the document once the document is in the gateway queue if the gateway is either disabled or offline. If 'Stop Process' link from console is clicked for any such document, the document processing will not stop until the gateway becomes online or enabled. The user can use the feature of removing the document from the gateway queue from the console itself.

4). When an in-process document's processing is stopped using the "Stop Process" link from the console, it is required that the router must be running. Otherwise, the processing of the document will not be stopped.



OVERVIEW OF SCHEMA-BASED PIP SUPPORT IN WEBSPHERE PARTNER GATEWAY V6.0.0.1
====================================================================================

Refer to the technote http://www.ibm.com/support/docview.wss?uid=swg21242286 for details of schema-based PIP support in WebSphere Partner Gateway V6.0.0.1 or later.



MIGRATION
===========

Migrating certificates from WebSphere Business Integration Connect, V4.2.x to WebSphere Partner Gateway V6.0.0 :

If you are migrating from WebSphere Business Integration V4.2.x to WebSphere Partner Gateway V6.0.0, you must refer to the technote http://www.ibm.com/support/docview.wss?uid=swg21219514 before migration.




IBM COPYRIGHT INFORMATION:
______________________________

International Business Machines Corporation 2005, 2006 Licensed program - Property of IBM . All rights reserved. IBM and WebSphere are trademarks of International Business Machines Corporation in the United States and/or other countries. Java is a trademark of Sun Microsystems, Incorporated. U.S. Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP. Schedule Contract with IBM Corp.

LIMIT OF LIABILITY:
________________________

License to the contained APAR fixes is conditioned upon the recipient holding a license to the prerequisite product. The license terms and conditions of the APAR fixes are the same as those for the prerequisite product. Please see the product license for specifics.