Readme for IBM^® WebSphere^®Partner Gateway, Enterprise and Advanced Editions, V6.1.0 fix pack 1

© Copyright International Business Machines Corporation 2005, 2007. 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 6.1.0.1 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions.

Prerequisites

New in fix pack

Product fix history

Known problems and workarounds

Installation instructions

Uninstalling the fix pack

Tracking Number

Description

JR26558

WebSphere Partner Gateway Linear Scaling Deployment Topology
The WebSphere Partner Gateway suggests a Linear Scaling Deployment
Topology to obtain linear scalability using multiple instances of WebSphere Partner Gateways.
The suggested configuration changes are optional. Carry out the configuration changes only if you want to implement this topology.

For this topology, two or more instances of WebSphere Partner Gateway are installed to improve the performance throughput, but are perceived by the user as a single WebSphere Partner Gateway.

If one WebSphere Partner Gateway instance provides throughput as x docs/sec, then two WebSphere Partner Gateway instances throughput is 2x docs/sec. All the WebSphere Partner Gateways share the same database, but have individual file systems that are in turn shared.

Refer to http://www.ibm.com/support/docview.wss?uid=swg27010147 for more information on the setup and configurations.

JR26559

The datahandler was not supporting the Interchange Server (ICS). This is required for supporting ebMS with attachments. In this fix pack, the existing datahandler has been modifed to support ICS.

Tracking Number

Description

JR26271

When MDN was received without message ID, header parsing failure occurred due to interoperability issue.

JR26272

When a case-insensitive header was received from the trading partner, WebSphere Partner Gateway fails the received AS2 document with header parsing failure exception.

JR26273

Whenever the WebSphere Partner Gateway received AS2 messages with "from" and "to" optional headers, the WebSphere Partner Gateway considered them as AS1 message, which resulted in failure during header parsing.

JR26308

In the active connection between the source and target, click "Destination" to edit the destination values. Alternatively, you must be able to edit these values using the migration tool, but the migration utility was unable to modify these values.

JR26424

WebSphere Partner Gateway did not place any limitation on the number of characters that can be entered in CBE Event Field. In this fix pack, you can not place more than 1024 characters.

JR26449

The Target document of an EDI > XML transformation was not displayed in the Document Viewer of the console; instead a "Message not found" error was displayed.

JR26461

When a new destination is created using a custom transport without the "TargetURL" attribute, WebSphere Partner Gateway console triggered "500" error.

JR26612

Whenever a partner sent ebMS document with XML signature that does not have the prefix “ds”, the WebSphere Partner Gateway failed to validate the signature.

JR26635

In the previous fix pack versions, JMS receivers did not have the capability to create more than one thread. In this fix pack, the JMS receiver has been enabled to spawn multiple threads depending on the receiver configuration.

JR26646

In WebSphere Partner Gateway 6.1, the inbound RNIF documents to the hub with mixed case headers were not identified correctly. For example, x-RN-Version.

JR26674

When ebMS outbound document flowed from None to ebMS, WebSphere Partner Gateway 6.1 placed empty manifest element in the ebMS soap message.In this fix pack, all the manifest element will contain data as per ebMS specifications.

JR26689

After unpackaging of inbound document, data written to the inbound non-repudiation location was same as that of data written to message store.This was because the inbound non repudiation data was being over written during inbound message store update calls. In this fix pack changes are done to store packaged data in inbound non repudiation location.

JR26795

The PIPs are modified in this fix pack. However, it is recommended not to upload these new set of PIP packages unless you experience issues with your existing PIP packages.

In this fix pack, the following set of PIP packages are rectified to adhere to RNIF specifications:

• 0A1 - Notification of failure
• 3A4 - Request Purchase Order V02.00 - 2 Way Action
• 3A4 - Request Purchase Order V02.02 - 2 Way Action
• 3A7 - Notify of Purchase Order Update V02.02 - 1 Way Action
• 3A8 - Request Purchase Order Change V01.02 - 2 Way Action
• 3A8 - Request Purchase Order Change V01.03 - 2 Way Action
• 3B11- Notify Of Shipping Order R01.00 - 1 Way Action
• 3B12- Request Shipping Order V01.01 - 2 Way action
• 3B13- Notify of Shipping Order Confirmation V01.01 - 1 Way Action
• 3B2 - Notify of Advance Shipment V01.01 - 1 Way Action
• 3B3 - Distribute Shipment Status R01.00 - 1 Way Action
• 3C3 - Notify of Invoice V01.00 - 1 Way Action
• 3C6 - Notify of Remittance Advice V01.00 - 1 Way Action
• 3C7 - Notify of Self-Billing Invoice V01.00 - 1 Way Action
• 4A1 - Notify of Strategic Forecast V02.00 - 1 Way Action
• 4A3 - Notify of Threshold Release Forecast V02.00 - 1 Way Action
• 4A4 - Planning Release Forecast Notification R02.00A- 1 Way Action
• 4A5 - Notify of Forecast Reply V02.00 - 1 Way Action
• 4B2 - Notify of Shipment Receipt V01.00 - 1 Way Action
• 4B3 - Notify of Consumption V01.00 - 1 Way Action
• 4C1 - Distribute Inventory Report V02.01 - 1 Way Action
• 4C1 - Distribute Inventory Report V02.03 - 1 Way Action

The date/time format of the following PIP packages are corrected in this fix pack:

• 2A1 - Product Catalog Information Notification V02.00 - 1 Way Action
• 2A12- Product Master Notification V01.03 - 1 Way Action
• 3A1 - Quote Request V02.00 - 2 Way Action
• 3A2 - Price And Availability Request R02.01 - 2 Way Action
• 3A5 - Purchase Order Status Query R02.00 - 2 Way Action
• 3A6 - Purchase Order Status Notification V02.02 - 1 Way Action
• 3A9 - Purchase Order Cancellation Request V01.01 - 2 Way Action
• 3B14- Shipping Order Cancellation Request V01.00 - 2 Way Action
• 3B18- Shipping Documentation Notification V01.00 - 1 Way Action
• 3C4 - Invoice Reject Notification V01.00 - 1 Way Action
• 3D8 - Distribute Work In Process Notification V01.00 - 1 Way Action
• 5C1 - Product List Notification V01.00 - 1 Way Action
• 5C2 - Design Registration Request V01.00 - 2 Way Action
• 5C4 - Registration Status Notification V01.02 - 1 Way Action
• 5D1 - Ship From Stock And Debit Authorization Request V01.00 - 2 Way Action
• 6C1 - Service Entitlement Query V01.00 - 2 Way Action
• 7B1 - Work in Process Notification V01.00 - 1 Way Action
• 7B5 - Notify of Manufactuting Work Order V01.00 - 1 Way Action
• 7B6 - Notify of manufacturing Work Order Reply V01.00 - 1 Way Action

JR26796

Sometimes, the logs in WebSphere Partner Gateway displayed fatal error even though the messages were getting processed properly.

JR26797

In the previous versions, WebSphere Partner Gateway did not allow the suppression of 0A1 generation. From this fix pack onwards, 0A1 generation and XML Event generation can be suppressed at the participant level.

JR26798

When a partner sends an encrypted document in AS2 and WebSphere Partner Gateway fails in the decryption stage, an MDN is sent back to the partner with the error disposition status. Subsequently, if the partner tries to resend the document, the WebSphere Partner Gateway should recognize the message duplicity, but instead a message stating that the channel could not be found was displayed.

JR26799

RNIF Exception messages were not getting generated at the receiver end of the trading partner. Due to this, the sender would continue to send erroneous messages till timeout. This fix sends back an Exception Acknowledgement.

JR26800

This fix resolved the non-mapped shared drives problem, which was occurring in the archiver on windows operating system.

JR26803

When the record identifier in a ROD data of type CSV is enclosed in double quotes, the ROD splitter fails with ROD Parser Exception.

JR26804

Whenever WebSphere Partner Gateway sent an EDI document over the Binary-Binary channel, connection lookup failed error occurred.

JR26808

This fix pack has modified RNIF 1.1 3B3 PIP package as it earlier contained 3B11 PIP package definition.

JR26809

Sometimes WebSphere Partner Gateway did not generate acknowledgements for RNIF requests.

JR26811

During inbound RNIF transaction, the receipt acknowledgement for request was referring to the Document ID of the confirmation. This occurred during instances wherein the Request Ack was received after the Response Acknowledgement was generated.

JR26812

Valid UNA segment was not getting created while mapping XML to EDIFACT V3.

JR26813

When an EDIFACT V3 document was received and the UNA segment was not mentioned, the repeating element separator was always defaulted to space (default of version 4). Any field values which had spaces in them were considered as repeating elements. This fix pack solved the WebSphere Partner Gateway handling of EDIFACT V3 documents.

JR26814

When a file was received through JMS receiver, the original file name information remained nonexistent. During such instances, when the original file name option was chosen for the FTP Scripting Gateway, ‘NULL’ was prefixed to the file name.

JR26815

The bcgconsole logs showed DB2 SQL error -514 (java.sql.SQLException: DB2 SQL error: SQLCODE: -514, SQLSTATE: 26501,SQLERRMC: SQL_CURSN200C1).

JR26816

WebSphere Partner Gateway triggered exceptions when any of the Global Transport attributes were changed on the console.

JR26817

When an event was configured to generate alerts was published, alerts were sent to configure e-mail addresses with NULL values for some fields.

JR26818

7B1 PIP package had incorrect enumeration, that is, "Solution Requestor" was present instead of "Solution Requester" for the element "GlobalPartnerRoleClassification".

JR26819

This fix has rectified the SSL handshake failures that were occurring when chained certificates were used via FTPS.

JR26820

Previously, the response message did not have "Document Delivered" description for the event BCG250004.

JR26821

The error page that was getting displayed for non-hubadmin users while viewing the AS1/AS2 viewer has been rectified in this fix pack.

JR26822

The bcgconsole Admin API generated “500 internal error” instead of an XML document with the element BCGPublicAPIException.

JR26823

When mapping command assignment mapped the target element, the target element contained spaces instead of NULL. This fix removes the extra spaces that replaced the empty element in the XML output.

Inbound RNIF messages having boundary element without quotes and terminating spaces were getting rejected because of parseException. These MIME messages were sent by TIBCO.

JR26825

In this fix the procedure AR_PURGE_HEADERS has been modified to delete 1000 records at a time.

JR26826

WebSphere Partner Gateway has enabled the global security to provide JMS Security Support for external event delivery.

JR26827

To improve the performance, JMS Session objects and JMS Connections must be reused. In the earlier fixes, a new JMS connection was obtained from the WebSphere Application Server pool and a new session was created by all the producing threads every time an object was required to be placed in a queue.

JR26828

When business ID associated with a partner was deleted, the connection continued to refer the business ID.

JR26829

JMS gateways were not able to release threads after delivering the documents. As a result, other gateways were unable to deliver documents. In this fix pack these gateways have been modified to release threads back to the pool.

JR26830

The WebSphere Partner Gateway was unable to parse the chunked data received as a response from the trading partner.

JR26831

The throughput for AS2 synchronous case was very low and this fix pack increased the throughput for AS2 synchronous scenario. This has been handled by initiating the MDN generation process immediately after the logging step of the received AS2 document.

JR26832

Performance tests indicated that direct communication with Remote Messaging Engine increased the throughput of WebSphere Partner Gateway. This fix pack has enabled the direct communication to improve the yield of performance bypassing the Local Messaging Engine.

JR26833

The "Test Partner Connection" feature helps partners to test the connection. When connection with http gateway of partner was tested with POST, it was treated as a document with failed status though the test succeeded.

JR26834

When multiple Document Managers were running, AS state engine intermittently stopped working. Sometimes, it resumed the processing after few minutes or at other times, it waited for all the processing of normal documents, that is, till the MAIN_INBOUND queue was empty. This problem occurred while using DB2 and was more pronounced when DB2 was hosted on a Linux server.

JR26835

In handler type screen, question marks were getting displayed in place of the actual description.

JR26836

In the earlier fixes, WebSphere Partner Gateway was unable to build the cert path if the certificate had serial number as part of the subject field.

JR26837

The uninstaller is modified to check if Deployment Manager is running before starting the uninstallation of Hub application. If the Deployment Manager is not running, the following message gets displayed: "Stop! Could not connect to the Deployment Manager. Please verify the information specified before proceeding or the WebSphere Partner Gateway installation will not be successful". This is applicable only for SimpleDistributed and FullyDistributed modes, as there is no Deployment Manager for Simple mode.

JR26838

Calendar-based scheduling for an FTP Scripting receiver was incorrect for time zones other than Universal Time Coordinated (UTC).

JR26839

Certain valid certificates were incorrectly marked as invalid. The certificate date handling has been corrected.

JR26840

In the earlier fix packs the customized values of event delivery information attributes were overwritten with default values.

JR26841

EDIX12TransTypeBusinessProcess user exits sample will allow searching of EDI documents with EDI transaction type using the User Defined Search Fields in Doc Viewer.

JR26842

When CPA contained more than one business process, WebSphere Partner Gateway was able to upload ebXML CPA, but it was unable to configure the connections for all the business processes.

JR26843

The archive program was looking for .vmd, .vhd files, which are no longer relevant. The restoration logic is modified in this fix pack. Now, it is sufficient if you just provide the restoration directory alone and not the DBOutput.txt parameter.

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 no fix pack installer for MAS Database and Deployment Manager. There is a separate launcher for each operating system. The WebSphere Partner Gateway V6.1.0 fix packs are located at http://www.ibm.com/software/integration/wspartnergateway/support/
WARNING: You cannot reverse the installation of this fix pack. 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:
Navigate to the ProductDir/bcghub-distrib/bin directory for SimpleDistributed and FullyDistributed mode and execute the following. For Simple mode, navigate to ProductDir/bcghub-simple/bin directory. Make sure that the Deployment Manager and NodeAgent are running in case of both SimpleDistributed and FullyDistributed modes.
SimpleDistributed and FullyDistributed mode on Unix:

a.        bcgStopserver.sh console

b.       bcgStopServer.sh receiver

c.    bcgStopServer.sh router

d.    bcgStopServer.sh MAS

       Simple mode on Unix:

bcgStopServer.sh

       SimpleDistributed and FullyDistributed mode on Windows:

a.    bcgStopserver.bat console

b.    bcgStopServer.bat receiver

c.    bcgStopServer.bat router

d.    bcgStopServer.bat MAS

       Simple mode on Windows:

bcgStopServer.bat

2.      Take a backup of 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 taking a backup of 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, then select Yes to continue with the fix pack installation.

4.        Run the Hub setup launcher for your operating system. In the component selection panel, select only the applicable components. The "Messaging Application Server" or "Common Shared Files" do not have any updates in Fix Pack 1 and should never be selected.

5.        Start WebSphere Partner Gateway servers:
Navigate to the ProductDir/bcghub-distrib/bin directory for SimpleDistributed and FullyDistributed mode and execute the following. For Simple mode, navigate to ProductDir/bcghub-simple/bin directory. Make sure that the Deployment Manager and NodeAgent are running in case of both SimpleDistributed and FullyDistributed modes.
SimpleDistributed and FullyDistributed mode on Unix:

a. bcgStartServer.sh console

b. bcgStartServer.sh receiver

c. bcgStartServer.sh router

d. bcgStartServer.sh MAS

Simple mode on Unix:

bcgStartServer.sh

SimpleDistributed and FullyDistributed mode on Windows:

a. bcgStartServer.bat console

b. bcgStartServer.bat receiver

c. bcgStartServer.bat router

d. bcgStartServer.bat MAS

Simple mode on Windows:

bcgStartServer.bat

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 loss of 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. Also, uninstall hub apps before uninstalling hub Deployment Manager.

1.      Uninstall hub apps version 6.1.0.1.

1.      Shut down WebSphere Partner Gateway servers. Make sure that the Deployment Manager and NodeAgent are running in case of both SimpleDistributed and FullyDistributed modes.

2.      Navigate to the ProductDir/bcghub-distrib/bin directory for SimpleDistributed and FullyDistributed mode and execute the following. For Simple mode, navigate to ProductDir/bcghub-simple/bin directory. 

SimpleDistributed and FullyDistributed mode on Unix:

1.        bcgStopserver.sh console

2.        bcgStopServer.sh receiver

3.    bcgStopServer.sh router

4.    bcgStopServer.sh MAS

Simple mode on Unix:

bcgStopServer.sh

      SimpleDistributed and FullyDistributed mode on Windows:

a.    bcgStopserver.bat console

b.    bcgStopServer.bat receiver

c.    bcgStopServer.bat docmgr

d.    bcgStopServer.bat MAS

             Simple mode on Windows:

bcgStopServer.bat

3.    Save any hub configuration using backupConfig.bat/.sh.(under ProductDir/bcghub-distrib /wasND/Profiles/bcgprofile/bin) This will create a zip file name with current timestamp. For example, WebSphereConfig_2007-06-05.zip. This will create backup for all servers ( bcgconsole, bcgreceiver, bcgdocmgr, bcgmas and nodeagent). Log file (backupConfig.log) will be created under deployment manager profile logs. The hub configuration settings that are not stored in the database are located in the following directory:  ProductDir/bcghub-distrib/wasND/Profiles/bcgprofile/config

4.    Save the ProductDir/bcghub-distrib/common tree to the backup location.

5.      Uninstall the version 6.1.0.1 hub, removing all components.
Note: Do not delete the ProductDir/DBLoader and ProductDir/common directories.

2.      Revert the bcgapps database and DBLoader to the previously installed version. This will restore the database and customer data.

1.      Run the DBLoader Uninstall. Do not drop the database.

2.      Restore the bcgapps database using the backup created before the fix pack was installed.

3.      Run the DBLoader for V6.1.0.0. Do not run SQL. If you revert to V6.1.0.1, make sure that you run the DBLoader for V6.1.0.1.

3.      Reinstall Hub

1.      Install hub version 6.1.0.0 to the same location ProductDir. If revert to V6.1.0.1, make sure that you run the Hub install for V6.1.0.1.
Note: Be sure to specify the same installation information that was used during the previous installation.

2.      Start WebSphere Partner Gateway servers.

3.      Navigate to the ProductDir/bcghub-distrib/bin directory and execute the following:

SimpleDistributed and FullyDistributed mode on Unix:

·         bcgStartserver.sh console

·         bcgStartServer.sh receiver

·         bcgStartServer.sh router

·         bcgStartServer.sh MAS

Simple mode on Unix:

bcgStartServer.sh

      SimpleDistributed and FullyDistributed mode on Windows:

1.    bcgStartserver.bat console

2.    bcgStartServer.bat receiver

3.    bcgStartServer.bat router

4.    bcgStartServer.bat MAS

            Simple mode on Windows:

bcgStartServer.bat

4.      Restore the previous configuration by executing restoreConfig.bat/.sh backup_file command under ProductDir/bcghub-distrib/wasND/Profiles/bcgprofile/bin. This will restore configuration for all servers ( bcgconsole, bcgreceiver, bcgdocmgr, bcgmas and nodeagent) in the following directory: ProductDir/bcghub-distrib/wasND/Profiles/bcgprofile/config

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