Readme for IBM® WebSphere®Partner Gateway, Enterprise and Advanced Editions, V6.0.0 fix pack 5 |
|
© Copyright International Business Machines Corporation 2005, 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. |
|
These notes describe the changes made in fix pack V6.0.0.5 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. This fix pack is cumulative and includes all fixes released in earlier fix packs for the V6.0.0 release. |
This document contains the following sections:
|
Overview of schema-based PIP support in WebSphere Partner Gateway V6.0.0.1 |
This fix pack includes the following new features and improvements.
|
Tracking Number |
Description |
|
JR23886 |
Support and inclusion of embedded WAS 6.0.2.13 and JAVA SDK 1.4.2 SR5 in IBM WebSphere Partner Gateway Fix Pack 5. The prerequisites for applying WAS 6.0.2.13 are given below. If the prerequisites are not present, WAS 6.0.2.13 will not be correctly applied. Hardware prerequisites : http://www.ibm.com/support/docview.wss?rs=180&uid=swg27007250 Software prerequisites : http://www.ibm.com/support/docview.wss?rs=180&uid=swg27007251 After the this fix pack is installed, the WAS level and the JAVA SDK level can be determined by the following commands respectively.
Determine JAVA SDK level Determine WAS level |
|
JR24570 |
In WebSphere Partner Gateway Fix Pack 5, support has been provided to connect to MQ queues enabled with global security. This applies to both JMS receivers and gateways. The Console provides additional entry fields to capture the authentication details for connecting to MQ. |
|
JR25355 |
Support for DB2 8.1 fix pack 13. |
The following problems were fixed in this fix pack.
|
Tracking Number |
Description |
|
JR24029 |
In WebSphere Business Integration Connect V4.2.x, certificates could be set for multiple uses, such as digital signatures, encryption, and SSL client. The primary/secondary designation that was added in WebSphere Partner Gateway V6.0.0 can be set only for applicable certificate uses. For some configurations of a certificate in V4.2.x, when migrated to V6.0.0, primary/secondary designation was not applicable for all the selected certificate uses. However, when migrated from V4.2.x to V6.0.0, the certificates stayed listed in the certificates viewer with the V4.2.x value, even if the values were not valid for V6.0.0. This lead to confusion as to which certificates were valid for which functions. Once you have migrated from WebSphere Business Integration Connect V4.2.x to WebSphere Partner Gateway V6.0.0, pr_multicertu.sql script must be run. This script will change the usage settings based on the certificate type. A technote on this topic has been published here: link. |
|
JR24083 |
The optional domain node is added in the RNIF messages under the PartnerIdentification element. The node value is defaulted to DUNS. |
|
JR24118 |
The 3B12, 4B3 and 3A8 PIP packages had missing XSD files and were incomplete. The missing XSD files are added in Fix Pack 5. |
|
JR24138 |
WebSphere Partner Gateway was not enclosing the file names in double quotes in the Content-Disposition header for AS2 transactions. This has been corrected. |
|
JR24177 |
The Resend engine may stop when the resend for any document fails because of an unexpected error. This behavior has been rectified. |
|
JR24204 |
3B11 PIP package had incorrect enumeration value of "Delivery Noter" for the element "GlobalDocumentReferenceTypeCode". The element has been modified to contain "Delivery Note" as the element value. |
|
JR24266 |
WebSphere Partner Gateway was not appending the trailing slash '/' to HTTP URL if HTTP URL did not contain the URI. |
|
JR24272 |
Event BCGEDIFT0120 is triggered when the FTP Open command fails. This event text, apart from including the ftp server hostname and user id, also had the password as clear text. As a fix to the problem the password now does not appear in the event BCGEDIFT0120. |
|
JR24273 |
The 4A5 PIP package had the incorrect enumeration value of "Forecast Reply" for the element "GlobalPartnerRoleClassificationCode". This is modified to "Forecast Reply Recipient" in this fix pack. |
|
JR24281 |
Outbound AS1 messages are now encoded in base64. |
|
JR24333 |
4C1 PIP package had reverse metadata information for "ToService/FromService" and "ToRole/FromRole". This has been corrected. |
|
JR24355 |
When the enveloper-scheduling interval is set to less than 5 seconds via the console, the Enveloper is invoked at every 10 seconds instead of the actual interval configured. This has been corrected in this fix pack. |
|
JR24372 |
Failure of any FTP command after the OPEN command had succeeded, was causing the FTP script execution to stop. Once the execution stopped the QUIT command would not get invoked to terminate the FTP session. The QUIT command will now always get invoked regardless of error during the script processing. This will ensure the connection will be closed correctly. |
|
JR24440 |
When the length of the sender/receiver IDs in the ROD document were less than their defined length in the ROD definition, the partner IDs were not recognized and the channel lookup failed. This is corrected in this fix pack. |
|
JR24457 |
The Receipt Acknowledgement data for RNIF 1.1 contains incorrect information. The element "receivedDocumentDateTime/DateTimeStamp" should contain the exact time-stamp when the document was received. Previously, it contained the value parsed from the RNSC part of the received document. This is rectified. |
|
JR24499 |
WebSphere Partner Gateway successfully decodes plain AS1 message (encoded in base64) and sent by the Cyclone trading partner |
|
JR24501 |
The RN STATE Engine retry counter was started after the First Delivery Attempt failed, but before all the gateway-level tries were exhausted. With this fix, the RN State Engine retry counter now starts after all the gateway level retries are exhausted. |
|
JR24559 |
DB Maintenance procedure AR_StateEngine_Maintenance has been enhanced to purge data from BP_Sponsor_State table. |
|
JR24642 |
This problem occurs during SSLHandShake between a partner and WebSphere Partner Gateway (WPG). If the partner A does not send the list of certifying authority certificates, the SSL client in WPG will not send the client certificate. This causes the handshake failure. However, a change needs to be made for this fix to work properly if the WebSphere Partner Gateway installation has been done using Base WAS. The java.security file on Base WAS installations needs to be modified for this change. Please note again that if you have installed WPG using embedded WAS the fix will work fine. However if you are running this on Base WAS, you will have to do the below mentioned change to the java.security configuration file. java.security file is located in <Base WAS installation directory>\java\jre\lib\security directory. In Unix systems, use forward slash ("/") instead of back slash ("\"). The default order of providers is as follows: security.provider.1=com.ibm.crypto.provider.IBMJCE It should be modified as follows to place IBMJSSE2 provider before IBMJSSE provider: security.provider.1=com.ibm.crypto.provider.IBMJCE The WebSphere Partner Gateway servers (bcgconsole, bcgreceiver and bcgdocmgr) need to be restarted after the java.security file is changed. |
|
JR24653 |
Starting in 2007, the United States Daylight Saving Time will be extended by four weeks, starting three weeks earlier on the second Sunday in March and ending one week later on the first Sunday in November. Canada, Mexico, and Bermuda also plan to make the corresponding changes to their Daylight Saving Time rules, in order to stay in sync with the United States. ICU4J v3.6 takes into consideration these daylight savings. This fix pack installer replaces the older version of icu4j with ICU4J v3.6. Due to this upgrade of ICU4J, a corresponding NOTICES.TXT file is included in the delivery image. This NOTICES.TXT has additional terms for the usage of the icu4j_3_6.jar package. It will be copied under the root installation path. |
|
JR24677 |
The execution of Document Viewer Search, for "IN PROCESS DOCUMENTS", was slow. The search functionality has been made efficient. |
|
JR24680 |
WebSphere Partner Gateway fix Pack 5 includes "From" and "To" headers in the outbound AS1 document. |
|
JR24706 |
On upgrading from WebSphere Business Integration Connect V4.2.1 to WebSphere Partner Gateway V6.0.0, in some cases the JMS Gateway configuration was not showing all entry fields in the console. The missing fields include -JMS Factory Name, JMS Message Class, JMS Message Type, Provider URL Packages, JMS Queue Name and JMS JNDI Factory Name. This is rectified. |
|
JR24717 |
With this fix pack, the following privileges have been revoked for better security.
CONNECT and RESOURCE roles were revoked from bcgapps, bcgcon, bcgrecv and bcgdoc users. |
|
JR24738 |
In some cases during normal operation, the summary engine was throwing the following error ORA-20999: 20000 LG_UNP_SUMMARY_RN_PR error while running summary engine. This has been rectified. |
|
JR24741 |
In case of an invalid RNIF document, document validation errors are now displayed in proper format in the document viewer. |
|
JR24762 |
On WebSphere Partner Gateway installations with Oracle, normal file locking conflicts in the gateway directories would intermittently cause .tmp files to remain in these gateway folders, which caused document sending errors. These symptoms have corrected. |
|
JR24763 |
WebSphere Partner Gateway was unable to load more than one CRL file from the location under <installed_path>/<common shared folder >/security/crl folder. This is rectified. |
|
JR24795 |
Inbound RNIF documents, which do not contain double quotes around the boundary element of the MIME document, were failing. WebSphere Partner Gateway Fix Pack 5 now allows MIME messages to have boundary elements without the quotes. |
|
JR24815 |
The update of validation.jar, BCGConsole.ear and BCGReceiver.ear files do not take place correctly when WebSphere Partner Gateway Fix pack 3 or Fix pack 4 is applied to an existing WebSphere Partner Gateway installation (v6.0.0.x), installed on top of IBM WebSphere Application Server (Base WAS). As a result, WebSphere Partner Gateway would not correctly process documents, after applying either of the above fix pack installations. The installation of these packages has been corrected. |
|
JR24821 |
Maps in use within WebSphere Partner Gateway could not be deleted from WebSphere Partner Gateway, using DIS Client over an ODBC connection. This is rectified. |
|
JR24830 |
For any AS1 message, WebSphere Partner Gateway mandated that the subject header contained the business IDs of the partners exchanging documents. With this fix pack , this restriction has been eliminated. Mapping between the email IDs and business ID is provided to retrieve Business IDs. The Partners email ID is configurable as part of the partner profile definition. |
|
JR24838 |
Production systems involving large number of gateways and a having high document transaction rates take longer to get the results of queued documents on a gateway. The "Gateway Queue" screen has been improved to handle high production data in more efficient manner. |
|
JR24883 |
This fix pack enables the console to properly display a list box having over 500 entries. |
|
JR24915 |
During heavy document transaction scenarios, the end-state of some transactions do not get logged and they remain in “In progress” state. This has been corrected in this fix pack. |
|
JR24923 |
Documents encoded in GB18030 do not get displayed properly in the raw document viewer. The GB18030 encoding has been added in the raw document viewer. The raw content will now be shown with the encoding specified in the document. |
|
JR25047 |
WebSphere Partner Gateway has been modified to use the file extension of ".p7z" instead of ".p7m" for compressed data. This is in adherence to the RFC 3851. |
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. 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 the process state and the 'Stop Process' link from the console is clicked for any such document, the document processing may not be stopped since it is already processed and delivered. For such a document that was 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 the '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. |
|
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. |
|
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 Connect 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. |
|
There are separate fix packs for the Advanced and Enterprise Editions. Each fix pack has two major parts, the DBLoader and the Hub. There is a separate launcher for each operating system. The WebSphere Partner Gateway V6.0.0 fix packs are located at http://www.ibm.com/software/integration/wspartnergateway/support/ Note: If you are on WebSphere Partner Gateway 6.0.0 fix pack 3 or below and if you have WebSphere Partner Gateway - EDI Wizards installed, make sure to uninstall the EDI Wizards console component before installing this fix pack. After you have installed this fix pack, please install the EDI Wizards console component again from http://www.ibm.com/support/docview.wss?uid=swg24011593. The EDI Wizards database component does not need to be uninstalled or reinstalled. Note that you must install the EDI Wizards console component, from the latest version of the EDI Wizards, which is applicable for WebSphere Partner Gateway 6.0.0 fix pack 4 and above. WARNING: Installation of this fix pack cannot be easily reversed. It is very important that you shut down WebSphere Partner Gateway and create a backup of the current installation before proceeding with the fix pack installation. Failure to do so may result in loss of data or prevent you from properly performing the fix pack uninstallation procedure. 1. Shut down WebSphere Partner Gateway servers in the following order:
3. Run the DBLoader setup launcher for your operating system. 4. EDI protocols must be migrated for WebSphere Partner Gateway V6.0.0.1. The DBLoader install wizard installs cf_edi_protocoltypeu.bat, cf_edi_protocoltypeu.sh and cf_edi_protocoltypeu.sql files into <WPG INSTALL DIR>/bcgdbloader/scripts/<DB2/Oracle> directory. You will have to execute the script once for each EDI protocol you have created. Note that EDI protocols are created by importing them via the Data Interchange Services Client (DIS Client) or bcgDISImport scripts. On DB2
cf_edi_protocoltypeu bcgapps db2admin pa55word EDI_Protocol
su - db2inst1 On Oracle
cf_edi_protocoltypeu bcgapps bcgapps victoria EDI_Protocol
su - oracle Note: There are no specific database migration scripts from WebSphere Business Integration Connect V4.2.2.5 and above to WebSphere Partner Gateway V6.0.0. The user should follow the procedure to migrate from V4.2.2 to V6.0.0 (that is, run the <6.0.0 install>/bcgdbloader/scripts/.../BCGUpgrade_422FP4_600.sql script) and then apply V6.0.0 fix packs. Note: If you choose not to have the DBLoader run the SQL files automatically, you can run them manually at the completion of the DBLoader. To do this: On DB2 a. UNIX: su - db2inst1 WINDOWS: Start the DB2CLP and make sure you are logged in as the user that owns the DB2 database. b. db2start (if the database is not started) c. db2 connect to bcgapps d. cd <WPG INSTALL DIR>/bcgdbloader/scripts/DB2 e. Run the applicable scripts from below. Determine the level you are starting from. (That is from V6.0.0.0, run all five scripts, from V6.0.0.1, only the last four, from V6.0.0.2, only the last three, from V6.0.0.3, only the last two and from V6.0.0.4, only the last one.) db2 -td! -f BCGUpgrade_600_600FP1.sql -z /tmp/bcgdbloader/logs/BCGUpgrade_600_600FP1.log Note: The BCGUpgrade_600FP1_600FP2.sql script mentioned in bullet-e above had a migration related issue, which was corrected in V6.0.0.3 onwards. On Oracle
WINDOWS: Make sure you are logged in as the owner of the Oracle database. b. Run the applicable scripts from below. Determine the level you are starting from. (That is from V6.0.0.0, run all five scripts, from V6.0.0.1, only the last four, from V6.0.0.2, only the last three, from V6.0.0.3, only the last two and from V6.0.0.4, only the last one.) cd <WPG INSTALL DIR>/bcgdbloader/scripts/Oracle 5. Run the hub setup launcher for your operating system. 6. Start the console, receiver and router. Consult the WebSphere Partner Gateway Installation guide. |
|
To uninstall the fix pack, WebSphere Partner Gateway must be restored to its original state (prior to the fix pack installation). Restore the system to its original state using the database backup that was created before the fix pack was installed. Failure to do so may result in lost data or prevent you from properly performing the following fix pack uninstallation procedure. Any changes to configuration files must be manually saved and restored. Note: It is recommended to uninstall the hub before uninstalling the DBLoader. 1. Uninstall hub version 6.0.0.5. a. Shut down WebSphere Partner Gateway servers in the following order: Navigate to the ProductDir/bin directory and execute the following On Unix : i. bcgStopServer.sh bcgconsole ii. bcgStopServer.sh bcgreceiver iii. bcgStopServer.sh bcgdocmgr iv. bcgStopHelp.sh (If using the Help Server) On Windows : v. bcgStopServer.bat bcgconsole vi. bcgStopServer.bat bcgreceiver vii. bcgStopServer.bat bcgdocmgr viii. bcgStopHelp.bat (If using the Help Server) b. Save any hub configuration that may have been done by manually copying the bcghub/console/lib/config and /was/profiles/bcgconsole/config directories to a safe location. The hub configuration settings that are not stored in the database are located in the following directories: ProductDir/console/lib/config
ProductDir/receiver/lib/config
ProductDir/router/lib/config
c. Save the ProductDir/common tree to the backup location. d. Uninstall the version 6.0.0.5 hub, removing all components. e. Delete all remaining files and remove the following directories: Note: Do not delete the ProductDir/DBLoader and ProductDir/common directories. ProductDir/console
2. Revert the bcgapps database and DBLoader back to the previously installed version. This will restore the database and customer data. a. Run the DBLoader Uninstall. Do not drop the database. b. Restore the bcgapps database using the backup created before the fix pack was installed. c. Run the DBLoader for V6.0.0.0. Do not run SQL. If reverting to V6.0.0.4, the DBLoader for V6.0.0.4 must also be run. 3. Re-install Hub
Note: Be sure to specify the same installation information that was used during the previous installation. b. Start WebSphere Partner Gateway servers in the following order: Navigate to the ProductDir/bin directory and execute the following On Unix : i. bcgStartServer.sh bcgconsole ii. bcgStartServer.sh bcgreceiver iii. bcgStartServer.sh bcgdocmgr iv. bcgStartHelp.sh (If using the Help Server) On Windows : v. bcgStartServer.bat bcgconsole vi. bcgStartServer.bat bcgreceiver vii. bcgStartServer.bat bcgdocmgr viii. bcgStartHelp.bat (If using the Help Server) c. Restore
the previous configuration by copying and replacing the following
directories:
|
Trademarks and service marks:
For trademark attribution, visit the IBM Terms of Use Web site.