Readme for IBM® WebSphere®Partner Gateway, Enterprise and Advanced Editions, V6.0.0 fix pack 7




© Copyright International Business Machines Corporation 2005, 2008. 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.7 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

Product fix history

WebSphere Application Server and JDK Versions

Known problems and workarounds

Overview of schema-based PIP support in WebSphere Partner Gateway V6.0.0.1

Migration

Installation instructions

Uninstalling the fix pack





Product fix history

The following problems were fixed in this fix pack.

Tracking Number

Description

JR26022 Earlier, after resending a failed document, when the user tried to delete the corresponding entry in the console gateway queue, the console removed the entry temporarily. But it appeared again when the refresh link was used.
JR26148 WebSphere Partner Gateway did not limit the number of characters that can be entered in CBE Event field. This fix pack restricts the number of characters to 1024.
JR26342 WebSphere Partner Gateway reported errors while processing documents that got routed through many proxy servers. In this fix pack, IP address of the originating partner is fetched from the headers to avoid errors.
JR26354 The JMS Correation ID of an incoming message is now set on the outbound JMS message. The JMS message ID of a message delivered by JMS gateway can be read through user exit using the SenderResult.getAttribute("JMSMessageID") API.
JR26391 As part of this fix pack, an inbound binary document can be routed through a custom channel.
JR26399 In this fix pack onwards, WebSphere Partner Gateway has enabled the global security to provide JMS security support for external event delivery.
JR26447 The outbound encoding in the XML translation was incorrect.The outbound encoding is propagated and is used while creating the XML in the translation step.
JR26583 Earlier, when the stop process was initiated, a document posted over a gateway with Auto queue set to "ON" remained in "Document stop process submitted" state forever. Also, the gateway was moved to offline state. In this fix, the document is moved to failed state when the stop process is initiated.
JR26693 In case of an inbound AS document, when the incoming AS message was unsigned while the receiving hub expects a signed message, an "insufficient Message Security" error event was logged. Despite this, the message was successfully sent. In this fix pack, the document is failed if "Insufficient Message Security" error event is logged.
JR26859 From this fix pack onwards, Validation Maps for PIP can be updated without getting "File not found" error message.
JR26907 Earlier, the timer for the AS retry was starting as soon as an entry was made in the AS state tables. In this fix pack, the timer for AS Retry will start only after all the attempts by the gateway to deliver is completed.
JR26910 In earlier fix packs, "OutOfMemoryException" used to occur while routing several 8 MB documents simultaneously over AS2. This has been rectified such that you can route several 16 MB documents together.
JR27086 For RNIF transactions, non-repudiation of late acknowledgements were failing in WebSphere Partner Gateway due to message digest mismatch.In case of late acknowledgement scenario, the request acknowledgement that ensues the response message was failing digest verification.
JR27131 An error "java.sql.SQLException: ORA-01873: the leading precision of the interval is too small" that occured during resend has been rectified in this fix pack.
JR27184 In this fix pack, return code 334 has been added as a valid return code for FTPS.
JR27186 Community Participant Simulator used to fail for a single action PIP. In addition, there was failure with respect to 4A4 R02.00A.
JR27217 When large number of transactions were enveloped, extraneous calls to database for fetching the routing object attributes led to performance degradation. For more details, refer to http://www.ibm.com/support/docview.wss?uid=swg21271778  technote.
JR27248 While moving from Calendar Based Scheduling to Interval Based Scheduling in FTP Scripting gateway, the default value for Interval was set to zero, which caused the Gateway failure to transfer files. In this fix pack, the default value is set to 60 seconds.
JR27332 FTP Scripting gateway failed to schedule the tasks even when specific days were specified in the configuration. Instead the task was scheduled daily.
JR27359 In this fix pack, the original filename attribute is retrieved from the Compressed MIME bodypart for AS2 protocol.
JR27378 The customer could not get Event alerts as the Resource Property files were missing for locale en_us in the Router.These files have now been added.
JR27413 While writing files, the AS engine sequenced incorrectly. This sometimes resulted in errors during MDN generation. This fix pack has corrected the sequencing problem.
JR27474 In the gateway detail screen of console, for the FTP Scripting gateway, the lengths of the RETRY INTERVAL and RETRY COUNT fields were restricted to 3 and 2 respectively. In this fix pack it has been corrected to 5 for both the fields, so as to make it consistent with the similar fields of other gateway detail screens.
JR27506 The time stamp for enveloped and transformed data was UTC. In this fix pack you can specify the time zone that should be used while creating an envelope or transformed data. To specify the time zone/CPU-Time, you need to do the following steps:
  1. Go to <installed_path>/bcghub/router/lib/config.
  2. Open the ediparms.properties file.
  3. Add a new property "timezone=<Zone ID>"
    The accepted values of <Zone ID> are:
    • <Zone ID> can be time zone ID.
      Example : timezone=Europe/Rome
    • <Zone ID> can be specified in the format GMT+HHMM
      Where HH can take values from 00 to 23
      and MM can take values from 00 to 59.
      GMT is the GMT time and the value HHMM specifies the difference in the CPU-time and GMT.
      Example : timezone=GMT+0530
      Note : If the value specified for <Zone ID> is not acceptable, then the time used will be GMT.
  4. Re-start Document Manager.
JR27619 On Database restart, WebSphere Partner Gateway failed to process the documents that were routed while the database was down.
JR27666 When the file names received from an FTP server was less than 3 characters, the FTP Scripting receiver using MGET * failed to retrieve them.
JR27676 The System.out logs were getting bulkier while printing the entire RNIF document. The logging is removed in this fix pack.
JR27771 In case of a backend integration with AS Channel, if a blank value was specified for x-aux-process-instance-id, the outbound AS2 message had a blank MessageID. From this fix pack onwards,WebSphere Partner Gateway will generate a MessageID during such instances.
JR27875 In the FTP Gateway configuration page, the value for the attribute "Use Unique File Name"" was not saved properly.
JR27910 When WebSphere Partner Gateway received RNIF document with the Mime Header "Content-Location" having quoted values, it was unable to handle it and failed the document.
JR27941 When a document is routed in FTPScripting gateway and the gateway is offline, the delivery of the document fails. If the Receiver and Router are restarted after such an event, ClassCastException occured.
JR27956 In this fix pack, a FTP gateway having auto queue attribute set to "True", will go offline in the event of the unavailability of target FTP Server.
JR27960 RosettaNet viewer displayed the Target partner's Business ID rather than the label "Target ID".
JR28014 While transacting an AS2 document with requested MDN, the event 240038 "AS STATE ENGINE ERROR, TRYING TO GENERATE MDN FOR AN MDN" was getting generated incorrectly in WebSphere Partner Gateway.
JR28121 Earlier, the generic search for MessageID did not work for AS2 Viewer. In this fix pack, to search for MessageIDs starting with EDI12, you can enter either EDI12* or EdI12 in the MessageID keyword field.
JR28126 Even though EDI events were marked as "Alertable", they were not generating alert notification.
JR28220 WebSphere Partner Gateway 6.0 Fix Pack 6 returned SQL0532N error while calling AR_PURGEHEADERS stored procedures:
  • call AR_PURGE_HEADERS('2007-08-15')
  • SQL0532N A parent row cannot be deleted because the relationship "BCGUSER.LG_A
    ACTIVITY_DTL.FK_ACTIVITY_DTL_1" restricts the deletion.SQLSTATE=23504
    KEYWORD: WPG, 600, DTL.FK_ACTIVITY_DTL_1, parent, row, deleted,SQLSTATE=23504, SQL0532N.
The keyword "EXISTS" in the procedure has been replaced with the keyword "IN".
JR28230 In this fix pack the Restore Utility restores the .txt file extensions also.
JR28246 New Zealand has extended Daylight Saving Time (DST) effective from September 2007. See the New Zealand Department of Internal Affairs official announcement link http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Index?OpenDocument
ICU4J v3.6 takes into consideration these daylight savings.
JR28303 Sometimes, during high volume scenarios, event BCG240415 was generated due to multiple threads accessing the certificate repository.
When two documents were processed simultaneously, the user had to re-start processing of one document.
JR28366 In the installation of WebSphere Partner Gateway with multiple common file systems, if the .gw directory under the gateways directory contained any files, then the resend from the console failed.
JR28386 DocMgr restart was required for RosettaNet PIP Activity name changes to take into effect. In this fix pack, you need not restart DocMgr.
JR28442 UCI04 Element with value 8 in an inbound EDIFACT FA, but was treated as reject status. From this fix pack onwards it will be treated as accept status.
JR28499 When receiving a binary payload, Document Viewer did not show the DocIDs of the successfully processed documents that were delivered to the trading partner.
JR28690 Earlier, the password in the Event Publishing Properties of Event Delivery Information was readable text. In this fix pack, it has been rectified to hold password characters as non readable text.
JR28791 For any partner, if there are multiple FTP Scripting gateways with all configuration attributes, but the User Options exactly the same, the documents got delivered to wrong gateways.
JR29318 For RNIF transactions, in a late acknowledgement scenario, the response acknowledgement that came in after the request acknowledgement was sent out, failed sequence check.







WebSphere Application Server and JDK Versions

Currently as part of WebSphere Partner Gateway 6.0 FP7, the IBM JDK version is 1.4.2 SR5.
There are few security issues that have been fixed as a part of IBM JDK version 1.4.2 SR7.
The known issues which are seen in WebSphere Partner Gateway too are listed below:
  1. PK33715: SUPPORT VERISIGN CERTIFICATES THAT HAVE NO AKI EXTENSION"
  2. PK34657: MULTIPLE THREADS ARE TRYING TO ACCESS THE SIGNER INFORMATION OF
    THE SIGNERDATA OBJECT CORRUPTS ISSUERNAME FIELD.
We recommend upgrading the IBM JDK to 1.4.2 SR7.
The SR7 installer is available at http://www-1.ibm.com/support/docview.wss?uid=swg24015638.
We also support WAS 6.0.2.25(FixPack 25) and IBM JDK 1.4.2 SR9.




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. 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.






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 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.





Installation instructions

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:

Navigate to the ProductDir/bin directory and execute the following

On Unix :

  1. bcgStopServer.sh bcgconsole
  2. bcgStopServer.sh bcgreceiver
  3. bcgStopServer.sh bcgdocmgr


On Windows :

  1. bcgStopServer.bat bcgconsole
  2. bcgStopServer.bat bcgreceiver
  3. bcgStopServer.bat bcgdocmgr


2. Back up the database before running the installer. Use the appropriate database utility to perform this step. For example, DB2 and Oracle provide an export utility. Consult your database server documentation for instructions. Do not continue with the fix pack installation without first backing up your database.

3. Run the DBLoader setup launcher for your operating system.

Note: If you receive warnings stating that certain directories will be overwritten, for example: _jvm, press yes to continue with the fix pack installation.

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

  1. For Windows platform: Open DB2 command prompt and execute cf_edi_protocoltypeu.bat file. The DB2 command prompt on Windows can be launched by the "db2cmd" command. The following example assumes that database name is bcgapps, database username is db2admin, password ispa55word and EDI protocol name is EDI_Protocol.

cf_edi_protocoltypeu bcgapps db2admin pa55word EDI_Protocol

  1. For UNIX platform: Open console and execute cf_edi_protocoltypeu.sh file. The following example assumes that user name is bcgapps, database username is db2inst1, password is pa55word and EDI protocol name is EDI_Protocol.

su - db2inst1
cf_edi_protocoltypeu.sh bcgapps db2inst1 pa55word "EDI_Protocol"

On Oracle

  1. a. For Windows platform: Open command prompt and execute cf_edi_protocoltypeu.bat file. The following example assumes that user name is bcgapps, password is bcgapps, SID is victoria and EDI protocol name is EDI_Protocol.

cf_edi_protocoltypeu bcgapps bcgapps victoria EDI_Protocol

  1. For UNIX platform: Open console and execute cf_edi_protocoltypeu.sh file. The following example assumes that user name is bcgapps, password is bcgapps, SID is victoria and EDI protocol name is EDI_Protocol.

su - oracle
cf_edi_protocoltypeu.sh bcgapps bcgapps victoria "EDI_Protocol"

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

Run the following commands

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 seven scripts, from V6.0.0.1, only the last six, from V6.0.0.2, only the last five, from V6.0.0.3, only the last four and from V6.0.0.4, only the last three.)

db2 -td! -f BCGUpgrade_600_600FP1.sql -z /tmp/bcgdbloader/logs/BCGUpgrade_600_600FP1.log

db2 -td! -f BCGUpgrade_600FP1_600FP2.sql -z /tmp/bcgdbloader/logs/BCGUpgrade_600FP1_600FP2.log

db2 -td! -f BCGUpgrade_600FP2_600FP3.sql -z /tmp/bcgdbloader/logs/BCGUpgrade_600FP2_600FP3.log

db2 -td! -f BCGUpgrade_600FP3_600FP4.sql -z /tmp/bcgdbloader/logs/BCGUpgrade_600FP3_600FP4.log

db2 -td! -f BCGUpgrade_600FP4_600FP5.sql -z /tmp/bcgdbloader/logs/BCGUpgrade_600FP4_600FP5.log

db2 -td! -f BCGUpgrade_600FP5_600FP6.sql -z /tmp/bcgdbloader/logs/BCGUpgrade_600FP5_600FP6.log

db2 -td! -f BCGUpgrade_600FP6_600FP7.sql -z /tmp/bcgdbloader/logs/BCGUpgrade_600FP6_600FP7.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

Run the following commands

  1. UNIX: su - 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 seven scripts, from V6.0.0.1, only the last six, from V6.0.0.2, only the last five, from V6.0.0.3, only the last four and from V6.0.0.4, only the last three.)

cd <WPG INSTALL DIR>/bcgdbloader/scripts/Oracle

sqlplus -L bcgapps/<password> @BCGUpgrade_600_600FP1.sql >/tmp/bcgdbloader/logs/BCGUpgrade_600_600FP1.log

sqlplus -L bcgapps/<password> @BCGUpgrade_600FP1_600FP2.sql >/tmp/bcgdbloader/logs/BCGUpgrade_600FP1_600FP2.log

sqlplus -L bcgapps/<password> @BCGUpgrade_600FP2_600FP3.sql >/tmp/bcgdbloader/logs/BCGUpgrade_600FP2_600FP3.log

sqlplus -L bcgapps/<password> @BCGUpgrade_600FP3_600FP4.sql >/tmp/bcgdbloader/logs/BCGUpgrade_600FP3_600FP4.log

sqlplus -L bcgapps/<password> @BCGUpgrade_600FP4_600FP5.sql >/tmp/bcgdbloader/logs/BCGUpgrade_600FP4_600FP5.log

sqlplus -L bcgapps/<password> @BCGUpgrade_600FP5_600FP6.sql >/tmp/bcgdbloader/logs/BCGUpgrade_600FP5_600FP6.log

sqlplus -L bcgapps/<password> @BCGUpgrade_600FP6_600FP7.sql >/tmp/bcgdbloader/logs/BCGUpgrade_600FP6_600FP7.log

5. Run the hub setup launcher for your operating system.

6. If you are migrating from version 6.0.0.4 (WPG 6.0 Fix Pack 4) or below, then refer to the following link to verify the successful upgration of WAS:
http://www.ibm.com/support/docview.wss?uid=swg21304460.

7. Start the console, receiver and router. Consult the WebSphere Partner Gateway Installation guide.





Uninstalling the fix pack

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.7.

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/was/profile/bcgconsole/config

ProductDir/receiver/lib/config
ProductDir/was/profile/bcgreceiver/config

ProductDir/router/lib/config
ProductDir/was/profile/bcgdocmgr/config

c.       Save the ProductDir/common tree to the backup location.

d.      Uninstall the version 6.0.0.7 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
ProductDir/receiver
ProductDir/router

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.6, the DBLoader for V6.0.0.6 must also be run.

3. Re-install Hub

  1. Install hub version 6.0.0.0 to the same location ProductDir. If reverting to V6.0.0.6, the Hub install for V6.0.0.6 must also be run.

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:

ProductDir/console/lib/config
ProductDir/receiver/lib/config
ProductDir/router/lib/config

  1. Restore the ProductDir/common tree using the backup copy if it was deleted from this computer.





Trademarks and service marks:

For trademark attribution, visit the IBM Terms of Use Web site.