IBM Support

IBM® WebSphere® Partner Gateway, Advanced Edition, V6.2 FixPack 5

Download


Abstract

This document is the readme for version 6.2 FixPack 5 IBM® WebSphere Partner Gateway, including installation-related instructions, prerequisites, and known issues.

Download Description

These notes describe the changes made in the FixPack for 6.2.0.5 of IBM
WebSphere Partner Gateway Advanced Edition.This FixPack includes and supersedes all previous FixPacks for the same version and edition of WebSphere Partner Gateway.

IMPORTANT: 6.2 FixPack 5 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. FixPack 6.2.0.5 can be installed with Administrative security enabled for only "Standalone LDAP registry" realm definition. For details on how to configure Update Installer for WebSphere Partner Gateway, refer to  IBM® WebSphere® Partner Gateway Update Installer.

WebSphere Partner Gateway 6.2 FixPack 5(6.2.0.5)
© Copyright International Business Machines Corporation 2010. All rights reserved.
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Note: The most current version of the readme can always be found online.

Prerequisites
Operating System, Server and Database support
Known problems and workarounds
Installation instructions
Uninstallation instructions
List of fixes
Copyrights and Trademarks

Prerequisites

  1. For applying 6.2 FixPack 5 when WebSphere Partner Gateway is installed on an existing cell, see the technote on Prerequisite steps to be followed before using Update Installer with WebSphere Partner Gateway v6.2 on existing cell.

  2. For customers who have already setup the Update Installer for WebSphere Partner Gateway, would need to apply APAR JR37556 as prerequisite before upgrading to 6.2 FixPack 5. The 6.2.0.0-WS-WPG-TFJR37556.pak can be downloaded along with the 6.2 FP5 pak file.


Operating System, Server and Database support

The Advanced Edition of WebSphere Partner Gateway Version 6.2.0.0 FixPack 5 extends support for the following Operating System, Server and Database, other than those available in the base release.


  1. WebSphere Application Server Network Deployment V6.1.0.31
  2. Oracle 10g Enterprise Edition Release 2 - 10.2.0.5
  3. IBM DB2 UDB V9.1 FixPack9


For more details, refer to WebSphere Partner Gateway, Version 6.2, detailed system requirements.

Known problems and workarounds

The following problems exist in this FixPack:



  1. For WebSphere Partner Gateway FixPack 5, all new additions related to console will be seen in English language only. No other languages are supported.

  2. The Partner Migration export on DB2 does not import on Oracle for EDI maps. This issue is found while importing a map using the console on Oracle and then importing some exported data from a DB2 system that has the same map ID. This corrupts the existing map on Oracle, and does not allow the same map to get imported in WebSphere Partner Gateway (using Import Utility and console).

  3. In this FixPack, when you upload a JKS certificate after uploading a PEM for SFTP server authentication, and when you restart the SFTP server, an error may get logged in the SFTP log file. The workaround to resolve this problem is to restart the SFTP server.

  4. After upgrading to WPG 6.2 FP5 from WPG 6.2 FP4a, the existing SFTP Receiver and SFTP Destination which were created using the Integrated SFTP Server will not be able to process the documents.For details on how to resolve this issue refer to SFTP Receiver and SFTP Destination do not work after upgrading to WPG 6.2 FP5

  5. The WebSphere Partner Gateway (WPG) Receiver Cluster/Server needs to be restarted after switching authentication type from "User/Password" to "Private Key" or after switching authentication type from "Private Key" to "User/Password". This has also been technoted at SFTP Receiver does not pick any documents after it is updated

  6. No validation is performed on certificates uploaded using the "Load SFTP keys" page.
    More information regarding the same is available at What kind of certificates can be uploaded using the "Load SFTP keys" page?

    The following specific workarounds would need to be applied:

  7. When you attempt to install WebSphere Partner Gateway v6.2 GA DBLoader directly on Oracle 11.1.0.7, then the "ORA-22996: NEXT extent size is smaller than LOB chunksize", error gets generated.

    Users intending to use Oracle 11.1.0.7 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2 FixPack 5 immediately after installation of WebSphere Partner Gateway 6.2 GA.

  8. When you attempt to install WebSphere Partner Gateway v6.2 GA DBLoader directly on Oracle 10.2.0.5, then the "ORA-22996: NEXT extent size is smaller than LOB chunksize" error gets generated.

    Users intending to use Oracle 10.2.0.5 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2 FixPack 5 immediately after installation of WebSphere Partner Gateway 6.2 GA.

  9. When you attempt to install WebSphere Partner Gateway v6.2 GA DBLoader directly on DB2 9.5 FP5, then the installation may fail on Base.



    Users intending to use DB2 9.5 FP5 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2 FixPack 5 immediately after installation of WebSphere Partner Gateway 6.2 GA.

  10. When you attempt to install WebSphere Partner Gateway v6.2 GA DBLoader directly on
    DB2 9.1 FP9, then the installation may fail on Base.

    Users intending to use DB2 9.1 FP9 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2 FixPack 5 immediately after installation of WebSphere Partner Gateway 6.2 GA.

  11. Certificate expiry related events and alerts were not getting triggered. From 6.2 FixPack 2 onwards, such events and alerts will be triggered. Users who want to use this fix, need to follow the additional steps, after applying the FixPack.

    Users who are upgrading from 6.2 Fixpack2 to current FixPack and have performed the additional steps as provided in the above technote, do not need to perform the additional steps again.



  12. When a customer uninstalls WebSphere Partner Gateway 6.2 Fixpack 5 to revert to 6.2 FP4a level, and then tries application of WebSphere Partner Gateway 6.2 Fixpack 5 again, an error message "Unsupported product" displays. To resolve this problem, go to: "<WPG Installed location>/properties/version" and edit the "WPG.product" file. Here, set the version from 6.2.0.4a to 6.2.0.4.


Installation instructions

IBM WebSphere Partner Gateway Version 6.2 FixPack 5 can be installed, ONLY by using IBM® Update Installer for WebSphere Software (7.0.0.1 and above).
Installing the FixPack is a five step operation:

Step A - Setup the IBM Update Installer environment.
Step B - Performing the backup of WPG Application Database.
Step C - Apply needed prerequisites.
Step D or Step E can be performed next based on whether you need to manually upgrade the DB or if the DB has to be upgraded automatically through UPDI.
Step D - Applying the FixPack - Upgrade WPG Application database automatically through UPDI.
Step E - Applying the FixPack - Manually upgrade WPG Application database.

Step A - Setup the IBM Update Installer environment.

  1. Download the IBM® Update Installer for WebSphere Software.

  2. Follow the instructions to download and apply the WebSphere Partner Gateway specific Update Installer changes. Ensure that the necessary updates to the responsefile bcgupdate_<locale>.txt present under <DMGR Installed Path>/responsefiles/, <Hub Installed Path>/responsefiles/ are performed.

  3. Apply APAR JR37556 prerequisite before upgrading to 6.2 Fixpack 5. This APAR will update the WPG UPDI related jars and upgrade these to the latest levels.

For customers who have already setup UPDI as per step 1 and 2 only need to follow step 3. Now, IBM Update Installer is ready to install WebSphere Partner Gateway fixes and FixPacks on your environment.

Note: See the technotes for applying 6.2 FixPack 5 when WebSphere Partner Gateway is installed on an existing cell.

Step B - Performing the backup of WPG Application Database.

Performing the backup of WPG Application Database is a mandatory step, and the database backup taken at this point is to be retained and used, as necessary, during uninstallation of WebSphere Partner Gateway 6.2 FixPack 5. The backup step is required as uninstallation of the FixPack using IBM Update Installer does not restore the database to its previous version of WebSphere Partner Gateway. The database restoration step is to be performed manually, and it is mandatory whenever WebSphere Partner Gateway 6.2 FixPack 5 is uninstalled.

For more information on data back up and restore, see "Migrating the database" of WebSphere Partner Gateway Installation Guide.

Step C - Apply needed prerequisites.

Refer to the section at the beginning of this page to know about the prerequisites that need to be applied.

Step D - Applying the FixPack - Upgrade WPG Application Database automatically through UPDI.

Note: Customers upgrading to 6.2 FixPack 5 on DB2 8.1/8.2, please refer to upgrade the DB.

  1. In case of applying the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); the 6.2 FixPack 5 pak file needs to be applied using update installer on all machines that host the following WebSphere Partner Gateway components in the specified order:

    • WebSphere Partner Gateway Deployment Manager
    • WebSphere Partner Gateway Hub
    • WebSphere Partner Gateway Application Database
    • WebSphere Partner Gateway MAS Database
    • WebSphere Partner Gateway Integrated FTP Server

    The following steps need to be performed on the nodes where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed.


  2. Make sure that value for -Wupdate.RunSQLFiles is set to "Yes" in the Update Installer response parameter file.

  3. In case of applying the FixPack on WebSphere Partner Gateway simple mode installation, provide the product location corresponding to the WebSphere Partner Gateway Hub location to apply the 6.2 FixPack 5 file using update installer.

  4. Following are the prerequisites for 6.2 FixPack 5 installation:



    • While applying the FixPack on simple mode deployment, make sure that the server is up and running.
    • Make sure that the Deployment Manager (DMGR) and all node agents are up and running for simple distributed and fully distributed deployments.
    • Stop all WebSphere Partner Gateway clusters in case of simple distributed and fully distributed deployment before applying the FixPack.

  5. Execute the script update.bat for Windows and update.sh for non-Windows to launch Update Installer.
  6. In the Product Selection window, enter the DMGR installed location as the value for Directory Path.
  7. In the Maintenance Operation Selection window, select Install maintenance package.
  8. In the Maintenance Package Directory Selection window, provide the location of the 6.2 FixPack 5 pak file.
  9. In the Available Maintenance Package to Install window, ensure that the check box for FixPack pak file is selected. Note that when using the IBM Update Installer for WebSphere Partner Gateway, select only one pak file for installation. Else it may give unexpected results.

    Installation Summary window will list the details about the pak file to be installed on selected location. Installation begins, and when the installation completes, an appropriate installation success or failure message displays. Verify the logs <updateconfig.log> present under <DMGR installed path>/logs/update/<6.2 FP5 pak name>.install for more information on the FixPack installation.

  10. Perform all the above steps on all machines where Receiver hub, Console hub, and DocMgr and Integrated FTP server (WebSphere Partner Gateway components) are installed.

Step E - Applying the FixPack - Manually upgrade WPG Application database.

Note: The FixPack.pak file should be transferred in Binary mode on Non-Windows systems. In case of performing ASCII transfers or using Binary transfers with some FTP clients, the ^M characters may get introduced in the transferred contents of the .pak file. These ^M characters would mandatorily need to be removed, before performing manual steps.



  1. In case of applying the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); the 6.2 FixPack 5 pak file needs to be applied using update installer on all machines that host the following WebSphere Partner Gateway components in the specified order:
    • WebSphere Partner Gateway Deployment Manager
    • WebSphere Partner Gateway Hub

  2. WebSphere Partner Gateway Application Database
  3. WebSphere Partner Gateway MAS Database
  4. WebSphere Partner Gateway Integrated FTP Server


  5. Make sure that value for -Wupdate.RunSQLFiles is set to "No" in the Update Installer response parameter file.

  6. In case of applying the FixPack on WebSphere Partner Gateway simple mode installation, provide the product location corresponding to the WebSphere Partner Gateway Hub location to apply the 6.2 FixPack 5 file using update installer.

  7. Following are the prerequisites for 6.2 FixPack 5 installation:



    • While applying the FixPack on simple mode deployment, make sure that the server is up and running.
    • Make sure that the Deployment Manager (DMGR) and all node agents are up and running for simple distributed and fully distributed deployments.
    • Stop all WebSphere Partner Gateway clusters in case of simple distributed and fully distributed deployment before applying FixPack.

  8. Execute the script update.bat for Windows and update.sh for non-Windows to launch Update Installer.

  9. In the Product Selection window, enter the DMGR installed location as the value for Directory Path.

  10. In the Maintenance Operation Selection window, select Install maintenance package.

  11. In the Maintenance Package Directory Selection window, provide the location of the 6.2 FixPack 5 pak file.

  12. In the Available Maintenance Package to Install window, ensure that the check box for FixPack pak file is selected. Note that when using the IBM Update Installer for WebSphere Partner Gateway, select only one pak file for installation. Else it may give unexpected results.

    Installation Summary window will list the details about the pak file to be installed on selected location. Installation begins. When the installation completes, an appropriate installation success or failure message displays. Verify the logs <updateconfig.log> present under <DMGR installed path>/logs/update/<6.2 FP5 pak name>.install for more information on the FixPack installation.

  13. Perform all the above steps on all machines where Receiver hub, Console hub, DocMgr hub and Integrated FTP Server (WebSphere Partner Gateway components) are installed.

  14. Stop all WPG servers before performing the next few steps to upgrade the database.



  15. To manually upgrade the DB now follow the below listed steps:

    Run the following commands

    On DB2



    Note: Customers upgrading to 6.2 FixPack 5 on DB2 8.1/8.2, please refer to upgrading to 6.2 FixPack 5 on DB2 8.1/8.2 to upgrade the DB.

    • UNIX: su - db2inst1
      WINDOWS: Start the DB2CLP and make sure you are logged in as the user that owns
      the DB2 database.

      Steps required to upgrade WPG Application Database:

    • start the database if it is not already started

    • db2 connect to bcgapps

    • cd <DMGR installed location>/WPGUpdate/6.2.0-WS-WPG-FP5_Advanced/database/db2



    • Run the following applicable scripts. Determine the level you are starting from. (That is from V6.2.0.0, run all five scripts, from V6.2.0.1, only the last four, from V6.2.0.2, only the last three scripts and so on.)

      db2 -td! -f 6.2.0.0_to_6.2.0.1/BCGUpgrade_620_620FP1.sql -z /home/db2inst1/BCGUpgrade_620_620FP1.log

      db2 -td! -f 6.2.0.1_to_6.2.0.2/BCGUpgrade_620FP1_620FP2.sql -z /home/db2inst1/BCGUpgrade_620FP1_620FP2.log

      db2 -td! -f 6.2.0.2_to_6.2.0.3/BCGUpgrade_620FP2_620FP3.sql -z /home/db2inst1/BCGUpgrade_620FP2_620FP3.log

      db2 -td! -f 6.2.0.3_to_6.2.0.4/BCGUpgrade_620FP3_620FP4.sql -z /home/db2inst1/BCGUpgrade_620FP3_620FP4.log

      db2 -td! -f 6.2.0.4_to_6.2.0.5/BCGUpgrade_620FP4_620FP5.sql -z /home/db2inst1/BCGUpgrade_620FP4_620FP5.log

    • Then run the Set_Grants script using the following command:
      db2 -td! -f <WPG APPSDB INSTALL DIR>/ scripts/DB2/Set_Grants.sql -z /home/db2inst1/Set_Grants.log

      Steps required to upgrade WPG MAS DATABASE. Not applicable for Simple Mode installation. The next set of commands need to be run only if you are upgrading from 6.2.0.0 to 6.2.0.5. If you are upgrading from 6.2.0.1 or 6.2.0.2 to 6.2.0.5, do not execute the following steps:

    • Run the following command to disconnect from application database:
      db2 connect reset

    • Run the following command to log on to the WPG mas database:
      db2 connect to <WPG mas database>
      For example, db2 connect to bcgmas

    • Run the following command to fetch the configuration parameters of MAS database:
      db2 get db cfg for <WPG mas database> >> "<PATH>/mascfg.log"
      For example, db2 get db cfg for bcgmas >> "/home/db2inst1/mascfg.log"

    • Open file mascfg.log and search for "LOGFILSIZ" parameter. If the value for this is more than 10000 then do not execute the next step.

    • Run the following command: db2 "UPDATE DATABASE CONFIGURATION FOR < WPG mas database > USING logfilsiz 10000 immediate"


    On Oracle:

    Run the following commands:
    • UNIX: su - oracle
      WINDOWS: Make sure you are logged in as the owner of the Oracle database.

    • Go to the following location: cd <DMGR installed location>/WPGUpdate/6.2.0-WS-WPG-FP5_Advanced/database/oracle

    • Run the following applicable scripts. Determine the level you are starting from (that is from V6.2.0.0, run all five scripts, from V6.2.0.1, only the last four, from V6.2.0.2, only the last three scripts and so on). The spool commands need to be run irrespective of the FixPack you are upgrading from.
      spool /home/oracle/FPUpgrade.log

      sqlplus -L bcgapps/<password> @6.2.0.0_to_6.2.0.1/BCGUpgrade_620_620FP1.sql

      sqlplus -L bcgapps/<password> @6.2.0.1_to_6.2.0.2/BCGUpgrade_620FP1_620FP2.sql

      sqlplus -L bcgapps/<password> @6.2.0.2_to_6.2.0.3/BCGUpgrade_620FP2_620FP3.sql

      sqlplus -L bcgapps/<password> @6.2.0.3_to_6.2.0.4/BCGUpgrade_620FP3_620FP4.sql

      sqlplus -L bcgapps/<password> @6.2.0.4_to_6.2.0.5/BCGUpgrade_620FP4_620FP5.sql

      spool off

    • Then run the Grants_Syns script using the following command:

      sqlplus -L bcgapps/<password> @<WPG INSTALL DIR>/bcgdbloader/scripts/Oracle/Grants_Syns.sql >/home/oracle/Grants_Syns.log


    Uninstallation instructions

    IBM WebSphere Partner Gateway Version 6.2 FixPack 5 can be uninstalled using IBM® Update Installer for WebSphere Software (7.0.0.1 and above).

    Note: Uninstallation of the FixPack using Update Installer does not restore the database to its previous version of WebSphere Partner Gateway. The database restoration step is to be performed manually, and is mandatory whenever WebSphere Partner Gateway 6.2 FixPack 5 is uninstalled.

    Uninstalling the FixPack is a two step operation:

    Step A - Uninstall the FixPack using IBM Update Installer.
    Step B - Restore the WebSphere Partner Gateway Application Database.

    Step A - Uninstall the FixPack using IBM Update Installer.

    Note: In case of uninstalling the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed), the FixPack .pak file needs to be uninstalled using IBM Update Installer on all machines that host the following WebSphere Partner Gateway components in the specified order:

    1. WebSphere Partner Gateway Hub,
    2. WebSphere Partner Gateway Deployment Manager


    In case of uninstalling the FixPack on WebSphere Partner Gateway simple mode installation, the FixPack .pak file needs to be uninstalled using IBM Update Installer providing the product location as corresponding to the location of WebSphere Partner Gateway Hub.

    Following are the prerequisites for 6.2 FixPack 5 uninstallation:

    1. Stop the WebSphere Partner Gateway servers.

    2. Go to the IBM® Update Installer installed location and launch the same by executing the script update.bat for Windows and update.sh for non-Windows.

    3. Provide the Directory Path in the Product Selection window as the DMGR installed location.

    4. In the Maintenance Operation Selection window, select Uninstall maintenance package.

    5. Select the maintenance package to uninstall, here, the 6.2 FixPack 5 pak file. Note that when using the IBM Update Installer for WebSphere Partner Gateway, only one pak file should be selected for uninstallation. Else it may give unexpected results.

    6. Uninstallation Summary window will list the details about the pak file to be uninstalled on which location.

    7. After this the uninstallation begins, and when it completes, an appropriate uninstallation success or failure message displays. Please verify the logs <.updateconfig.log> present under <DMGR installed path>/logs/update/<6.2 FixPack 5 pak name>.uninstall for more information on the FixPack uninstallation.


    Note: These steps should be performed on all machines, where WebSphere Partner Gateway components are installed.

    Step B - Restore the WebSphere Partner Gateway Application Database.

    Once the uninstallation completes successfully, restore the database using the backup taken before applying the FixPack.

    List of fixes

    Refer to the link below for the list of fixes included in WebSphere Partner Gateway 6.2.0.5 FixPack:
    http://www.ibm.com/support/docview.wss?uid=swg27019782

    Copyrights and Trademarks

    Notices and trademarks: http://www.ibm.com/legal/copytrade.shtml
    Terms of use: http://www.ibm.com/legal/us/en/

On
[{"DNLabel":"Download Package for 6.2.0.5","DNDate":"10/22/2010","DNLang":"English","DNSize":"110025582","DNPlat":{"label":"AIX","code":"PF002"},"DNURL":"http://www.ibm.com/support/fixcentral/quickorder?fixids=6.2.0-WPG-Advanced-FixPack-05&product=ibm%2FWebSphere%2FWebSphere+Partner+Gateway+Advanced+Edition&source=dbluesearch","DNURL_FTP":" ","DDURL":null}]
[{"Product":{"code":"SSDKKW","label":"WebSphere Partner Gateway Advanced Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.2.0.5","Edition":"Advanced","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Product Synonym

WebSphere Partner Gateway;version 6.2;FixPack 6.2.0.5

Document Information

Modified date:
15 June 2018

UID

swg24027947