The release notes cover release information for IBM(R) WebSphere(R) Partner Gateway, Enterprise and Advanced Editions, Version 6.0. It contains the following sections:
Note: Important information about this product may be available in Technical Support Flashes issued after these release notes were published. These can be found on the WebSphere Partner Gateway support web site at http://www.ibm.com/software/integration/wspartnergateway/support. Select the component area of interest and search the flashes section.
This section lists the new features and improvements made in this release.
The following problems, based on customer-reported cases for WebSphere Business Integration Connect, Version 4.2.2, fix packs 1, 2, 3, and 4, are fixed in WebSphere Partner Gateway, Enterprise and Advanced Editions, Version 6.0:
APAR |
Description |
JR20152 | The Raw Document Viewer did not display different encoding documents correctly. |
JR20266: | Receiver problems returned code 500 to the partner while starting. |
JR20300 | When user exit sample code was used, object errors could not be serialized. |
JR20332 | A null pointer exception was returned when a SOAP synchronous call failed the connection lookup. |
JR20335 | A NonRepudiationPKIProcess error was returned in the LG_MSG_ARCHIVEU_AH1 procedure. |
JR20336 | User-defined actions did not work. |
JR20371 | The BusinessDocumentInterface class referred to the old file. |
JR20394 | The addEvent method in the SenderResult class was inconsistent. |
JR20414 | The Community Console did not allow more than one active SSL certificate. |
JR20415: | An error occurred when uploading the XML file with UTF-8 or UTF-16 encoding. |
JR20419 | The ToPartnerBusinessId was hardcoded to the hub manager's ID. |
JR20446 | A WSDL with soap:header in the binding element could not be uploaded. |
JR20587 | A null pointer exception was returned when the Event Delivery option was enabled. |
JR20784 | Oracle version 9.2.0.4 was not supported. |
JR20954 | An error occurred while the schema name was retrieved. |
JR21021 | A partner name was restricted to 25 characters. |
JR21128 | A deleted community console partner ID could not be reused. |
JR21253 | Successfully sent MDNs showed as in-process in the AS1/AS2 viewer. |
JR21277 | The document viewer was unable to show Japanese characters. SJIS encoding support was added. |
JR21278 | The console showed negative numbers in the In Progress column of the document analysis report. |
JR21279 | The console did not save changes to the Gateway configuration if a custom transport was used. |
JR21318 | While processing a document, if the target URI was changed, messages continued to be sent to the old URI. |
JR21319 | The console showed the incorrect Doc Time Stamp for XMLEvent. |
JR21328 |
Using 4A4 packages alone was generating data validation errors. |
JR21341 |
If MDN was received in multiple chunks, an error occurred while processing. |
JR21342 |
A null pointer exception was returned if the attachment encoding was not specified. |
JR21373 |
For 7B5, there was an incorrect channel ID in processing 0A1. |
JR21658 |
Document were lost if there was a database deadlock. |
JR21680 |
Document Manager status was incorrect or unclear when when it was started as a service in WebSphere Business Integration Connect, Enterprise and Advanced Editions, Versions 4.2.1 and 4.2.2. |
WebSphere Partner Gateway, Enterprise and Advanced Editions, Version 6.0, is functionally backward compatible with its predecessor, WebSphere Business Integration Connect, Enterprise and Advanced Editions, Version 4.2.2
Hardware and software requirements are included in the product documentation. See Installation, upgrade, and configuration information for links to those guides.
Whether you are installing the software from the CD or downloading it from Passport Advantage and installing it from a local directory, refer to the following documentation:
The following notes provide additional installation, upgrade, and configuration information:
GRANT Schema_Name_DEL TO DocMgr_Name;
GRANT Schema_Name_INS TO DocMgr_Name;
GRANT Schema_Name_SEL TO DocMgr_Name;
GRANT Schema_Name_UPD TO DocMgr_Name;
ALTER USER DocMgr_Name DEFAULT ROLE CONNECT, RESOURCE
, Schema_Name_DEL
, Schema_Name_INS
, Schema_Name_SEL
, Schema_Name_UPD;
GRANT Schema_Name_DEL TO Receiver_Name;
GRANT Schema_Name_INS TO Receiver_Name;
GRANT Schema_Name_SEL TO Receiver_Name;
GRANT Schema_Name_UPD TO Receiver_Name;
ALTER USER Receiver_Name DEFAULT ROLE CONNECT, RESOURCE
, Schema_Name_DEL
, Schema_Name_INS
, Schema_Name_SEL
, Schema_Name_UPD;
Example 1
A Participant-initiated, one-way synchronous PIP with the following connection attributes:
Digital Signature Required = Yes
Non-Repudiation of Receipt = Yes (the receipt acknowledgement contains the original message digest)
Sync Supported = Yes
Sync Ack Required = No (a synchronous receipt acknowledgment is required for Non-Repudiation of Receipt)
In this example, the Sync Ack Required has priority and WebSphere Partner Gateway returns an "http 200" to the Participant and does not generate a receipt acknowledgement, even though the Non-Repudiation of Receipt attribute is set to Yes. Similarly, if the Community Manager initiates a one-way PIP to a Participant, WebSphere Partner Gateway expects only an "http 200" status and no receipt acknowledgement.
Example 2
A Participant-initiated, one-way synchronous PIP with the following connection attributes:
Digital Signature Required = Yes
Non-Repudiation of Receipt = Yes (the receipt acknowledgement contains the original message digest)
Sync Supported = Yes
Sync Ack Required = Yes (a synchronous receipt acknowledgment is required for Non-Repudiation of Receipt)
In this example, WebSphere Partner Gateway generates a receipt acknowledgement with the correct message digest and signature. Similarly, if the Community Manager initiates a one-way PIP to a Participant, WebSphere Partner Gateway expects a receipt acknowledgement with the correct message digest and signature.
The following problems have been found in this release:
cscript //NoLogo %WAS_HOME%\bin\GetGSKITInstallPath.vbsRefer to the problem fix page for more information.
to
cscript //NoLogo "%WAS_HOME%\bin\GetGSKITInstallPath.vbs"
To install unlimited jurisdiction policy files in WebSphere Partner Gateway, follow these steps:
local_policy.jar
US_export_policy.jar
to
local_policy.jar.bak
US_export_policy.jar.bak
For using the keystore with weaker cryptography, the keystore must be saved with the permitted cryptography strength, as listed in the default jurisdiction policy files. IBM KeyMan supports configuring the cryptographic strength. IBM KeyMan software is available from http://www.alphaworks.ibm.com. Information about the cryptography strength permitted by default can be found in the Java Cryptography Extension Reference Guide for JDK 1.4.2.
If "common folders" and "document manager" are installed on different machines and if "document manager" is installed as a service, the "document manager" service may not start properly. To avoid this, always use the same user ID and password for bcguser during the installations.
Product documentation is not included as part of the product package, either by CD or electronic product distribution. The documentation for this product can be found in the following information center:
http://www.ibm.com/software/integration/wspartnergateway/library/infocenter/
To obtain the product documentation, visit the Web site and download the current documentation set for the release that you are using. Follow the instructions provided on the information center page to complete the installation.