These notes describe the changes made in patch 6.0.0.1 of IBM WebSphere Partner Gateway – Express. This readme contains the following sections:
|
Tracking # |
Description |
JR22306
|
Support for forward proxy for HTTP and HTTPS and proxy authentication With this fix pack, support for forward proxy for HTTP and HTTPS and proxy authentication is provided. To enable forward proxy
support, append the statements below to the bcg.properties
file : # HTTP Proxy Servers. bcg.http.proxyHost= bcg.http.proxyPort= bcg.http.nonProxyHosts= # HTTP Proxy authentication Details bcg.http.proxyUserName= bcg.http.proxyUserPassword=
Where: bcg.http.proxyHost=<Proxy server name/IP> bcg.http.proxyPort=<Proxy server port>
The property “bcg.http.nonProxyHosts” must include a list of the IP addresses or hostnames separated by a pipe (‘|’). The wild character(*) can also be specified.
For example : bcg.http.nonProxyHosts=localhost|9.182.12.103|9.182.14.*
If the partner’s IP address exists in the non-proxy list, then all the outbound messages to it will bypass the proxy server when they are routed. For partner IP addresses not in the list, the outgoing message will be routed through the proxy server.
To enable a different proxy server for HTTPS, append
the statements below to the bcg.properties file : #In case a different proxy is to be used for SSL bcg.https.proxyHost= bcg.https.proxyPort= bcg.https.nonProxyHosts= # HTTPS Proxy authentication Details bcg.https.proxyUserName= bcg.https.proxyUserPassword=
Where: bcg.https.proxyHost=<Proxy server name/IP> bcg.https.proxyPort=<Proxy server port>
The property “bcg.https.nonProxyHosts” must include a list of the IP addresses or hostnames separated by a pipe ( ‘|’). The wild character (*) can also be specified. For example: bcg.https.nonProxyHosts=localhost|9.182.12.103|9.182.14.*
If the partner’s IP address exists in the non-proxy list, then all the outbound messages to it will bypass the proxy server when they are routed. For partner IP addresses not in the list, the outgoing message will be routed through the proxy server.
Note : The hostname or the IP address of the system
running the receiver should be mentioned in the bcg.http.nonProxyHosts
or bcg.https.nonProxyHosts. |
|
JR22307 |
WebSphere Partner Gateway - Express console does not
correctly display the pending MDN status for all the partners. Previously, the WebSphere Partner Gateway - Express 6.0 console was displaying the same status for all the partners, even though only one trading partner had been requested for an MDN. This has been corrected. |
|
JR22308 |
WebSphere Partner Gateway - Express console displays
a failed document in an always “Pending state”. Sometimes when WebSphere Partner Gateway - Express failed to transmit a document to a trading partner, it had copied the file into a directory location from where WebSphere Partner Gateway - Express neither attempted to resend the document nor failed the document. Thus the document remained perpetually in the “Pending Transmission” state. Even after stopping and restarting Express, this state remained unaltered. This erratic behavior confuses the end-user, making it appear that there still are a few documents which need to be sent. This typically would happen when the document was directly copied inside the <send> folder more than once before getting picked up by WebSphere Partner Gateway - Express. This has been corrected. With this fix pack, if the document is not delivered, then the failure gets logged and the document is moved to the <error> folder. |
|
JR22724 |
Encryption properties are not being read from the partner.properties (properties file). With this fix pack, this issue
is resolved. Currently supported values are 3DES i.e. DESede and 168 bit key
size. This addresses the limitation
specified in the WebSphere Partner Gateway - Express 6.0 Release notes. |
|
JR22725 |
If revocation status of a certificate is undetermined, an exception should be thrown. Now WebSphere Partner Gateway - Express will throw an exception while verifying the
certificate’s CertPath validity against
revocation, if the revocation status of the certificate is undetermined.
Along with the above, now CertPath validation is
made configurable by adding the “bcg.checkRevocationStatus”
property with a default value of “true” in the bcg.properties file. This addresses the known
issue on certificate revocation status mentioned in the WebSphere
Partner Gateway - Express 6.0 Release notes. |
|
JR22726 |
Verification of a self-signed certificate is not being done completely. An extra check has been added to
check the certificate’s public key against its corresponding private
key. This check will ensure that the signature of the certificate matches
against its public key. A runtime exception will occur and be logged
if the signature does not match, and customers will need to delete the
invalid certificate identified by the exception via console and correct the
problem by uploading valid certificates. |
|
JR22727 |
Revocation check for self-signed certificates is not complete With this fix pack, revocation
status of self-signed certificates will not be checked. |
WebSphere Partner Gateway - Express has separate launchers for each supported
operating system. The fix packs are located at http://www.ibm.com/software/integration/wspartnergateway/express/support
.
It is recommended that you backup the
‘data’ and ‘config’ folders
before installing this fix pack. These folders are located in the WebSphere Partner Gateway - Express installation directory.
WARNING: Installation of this fix pack cannot be easily reversed. It is very important that you shut down WebSphere Partner Gateway - Express server before starting the installation. Failure to do so may result in loss of data or prevent you from properly performing the fix pack uninstallation procedure.
It is not possible to uninstall only just the fix pack. WebSphere Partner Gateway - Express needs to be uninstalled completely in case of any problems. To restore the system to the original state, use the backup taken during installation of this fix pack. Install the complete product and then overwrite the backed up “config” and “data” directories in the installation directory.
© Copyright IBM Corporation 2005. All rights reserved.