IBM® WebSphere® Partner Gateway, Advanced Edition, v6.2.1 Fixpack 2

Download Description

These Fixpack Readme notes describe the changes made in the WPG Fixpack v6.2.1.2 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.1 Fixpack 2 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. Fixpack 6.2.1.2 can be installed with Administrative security enabled for only "Stand-alone LDAP registry" realm definition.

WebSphere Partner Gateway 6.2.1 Fixpack 2 (6.2.1.2)
© Copyright International Business Machines Corporation 2012. 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 on-line.

For details on how to configure Update Installer for WebSphere Partner Gateway, refer to IBM® WebSphere® Partner Gateway Update Installer.

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.1 Fixpack 2 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 IBM® Update Installer for WebSphere Partner Gateway, would need to apply APAR JR38213 ( If not applied already )as prerequisite before upgrading to 6.2.1 Fixpack 2. The 6.2.0.0-WS-WPG-TFJR38213.pak can be downloaded along with 6.2.1-WS-WPG-FP2_Advanced.pak file.
   
   
3. Make sure WPG integrated FTP and SFTP management servers are stopped when you apply Fixpack on hub location.
   
   
4. With this Fixpack onwards SFTP receiver and destination do not depend on WebSphere FTP adapter. Users who are using or planning to use SFTP client must follow the instructions in this link
   
   
5. Customers who are using WPG 6.2.1.2 with Oracle 11.2.0.x , its mandatory to follow instructions give in link after applying WPG 6.2.1 FP2
   
   
6. WPG 621 Fixpack 2 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. If user is applying database scripts manually these ^M characters should be mandatorily be removed before performing manual steps

Operating System, Server and Database support

The Advanced Edition of WebSphere Partner Gateway Version 6.2.1 Fixpack 2 extends support for the following WebSphere Application Server , WebSphere MQ and Database versions, other than those available in the base release:

1. WebSphere Application Server Network Deployment V6.1.0.45
   
2. WebSphere Application Server Network Deployment V7.0.0.23
   
3. IBM DB2 UDB V9.1 Fixpack 11
   
4. IBM DB2 UDB V9.5 Fixpack 9
   
5. IBM DB2 UDB V9.7 Fixpack 5
   
6. Oracle 11.2.0.3
   
7. IBM WebSphere MQ 7.0.1.8
   
8. IBM WebSphere MQ 7.1.0.1
   ( For more information on default security settings in MQ 7.1 please visit link http://www-01.ibm.com/support/docview.wss?uid=swg21577137 )
   
   

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

Known problems and workarounds

The following problems exist in this Fixpack :

1. 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).
   
   
2. 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.
   
   
3. No validation is performed on certificates uploaded using the "Load SFTP keys" page.
   More information is available in the What kind of certificates can be uploaded using the "Load SFTP keys" page? technote.
   
   
4. When WPG MAS DB is hosted on DB2 and DB2 is upgraded from any version to DB2 v9.1 FP5 , when you start MAS cluster ,messaging engine does not start . To resolve this issue refer to link http://www-304.ibm.com/support/docview.wss?uid=swg21590281
   
   
5. WebSphere Partner Gateway 6.2 GA installation fails on Oracle 11.2.x
   Following specific workaround would need to be applied for using Oracle 11.2.x with WPG 6.2.1.2
   http://www-01.ibm.com/support/docview.wss?rs=2310&uid=swg21598385
   
   
6. 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 Fixpack 2 to current Fixpack , and have performed the additional steps as provided in the fix Readme, need not perform the additional steps again.

   
   
   
7. When a customer uninstalls WebSphere Partner Gateway 6.2.1 Fixpack 2 to revert to 6.2 Fixpack 4a level, and then tries application of WebSphere Partner Gateway 6.2.1 Fixpack 2 again, an error stating - "Unsupported product" displays. To resolve this, go to: "<WPG Installed location>/properties/version" location 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.1 Fixpack 2 can be installed ONLY by using IBM® Update Installer for WebSphere Software (7.0.0.1 and above).

Along with this Fix Pack, we are introducing a tool - WPG Update Installer (UPDI) Validator.
This tool can setup the UPDI, deploy the UPDI Validator console changes, and validate the UPDI response file values. This tool is provided to ease the WebSphere Partner Gateway UPDI setup and validate response file values. For more information, see http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27022133

Note : The following steps are applicable, when WebSphere Partner Gateway customer has already migrated the WebSphere Partner Gateway profiles to WebSphere Application Server 7.

Installing the Fixpack is a five step operation:

Step A – Setting up 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 – Setting up 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 response file - bcgupdate_<locale>.txt is present under <DMGR Installed Path>/responsefiles/ and <Hub Installed Path>/responsefiles/ are performed.
   
   
3. Apply APAR JR38213 prerequisite (if not applied already) before upgrading to 6.2.1 Fixpack 2. 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 Fixpack s on your environment.

Note: For applying 6.2.1 Fixpack 2 when WebSphere Partner Gateway is installed on an existing cell, see applying 6.2.1 Fixpack 2 when WebSphere Partner Gateway is installed on an existing cell technote.

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 should be retained and used, as necessary, during uninstallation of WebSphere Partner Gateway 6.2.1 Fixpack 2. The backup step is required because the 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.1 Fixpack 2 is uninstalled.

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

Step C - Apply needed prerequisites.

Refer to the section at the beginning of this page to know and apply the needed prerequisites.

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

1. In case of applying the Fixpack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); 6.2.1-WS-WPG-FP2_Advanced.pak file should 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 should be performed on the nodes where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed.

   
   
2. Make sure that the value for -W update.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 6.2.1-WS-WPG-FP2_Advanced.pak file using update installer.

4. Following are the prerequisites for 6.2.1 Fixpack 2 installation:
   • While applying the Fixpack on simple mode deployment, make sure that the server is running and Integrated FTP/SFTP management servers are stopped.

   • 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. Make sure WPG integrated FTP and SFTP management servers are stopped.
   
6. Execute the script "update.bat" for Windows and "update.sh" for non-Windows to launch Update Installer.
   
7. In the Product Selection window, enter the DMGR installed location as the value for directory path.
   
8. In the Maintenance Operation Selection window, select Install maintenance package.
   
9. In the Maintenance Package Directory Selection window, provide the location of 6.2.1-WS-WPG-FP2_Advanced.pak file.
   
10. 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. 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.1-WS-WPG-FP2_Advanced.install for more information on the Fixpack installation.

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

1. In case of applying the Fixpack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed);6.2.1-WS-WPG-FP2_Advanced.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

2. Make sure that value for -W update.RunSQLFiles is set to "No" 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.1 Fixpack 2 file using update installer.

4. Following are the prerequisites for 6.2.1 Fixpack 2 installation:
   
   
   
   
   • While applying the Fixpack on simple mode deployment, make sure that the server is running and Integrated FTP/SFTP management servers are stopped.
     
   • Make sure that the Deployment Manager (DMGR) and all node agents are up and running for simple distributed and fully distributed deployments.
     
   • Make sure WPG integrated FTP and SFTP management servers are stopped.
   • Stop all WebSphere Partner Gateway clusters in case of simple distributed and fully distributed deployment before applying 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.1 Fixpack 2 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. 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.1-WS-WPG-FP2_Advanced.install for more information on the Fixpack installation.

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

11. Stop all WebSphere Partner Gateway servers before performing the next few steps to upgrade the database.
    
    
    
12. To manually upgrade the DB, follow the steps given below:

    Run the following commands:

    On DB2

    
    
    • 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.1-WS-WPG-FP2_Advanced/database/db2
      
      
      
    • Run the following applicable scripts. Determine the level you are starting from (that is, from
      V6.2.0.0, run all eight scripts, from V6.2.0.1, only the last seven, from V6.2.0.2, only last six 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
      
      db2 -td! -f 6.2.0.5_to_6.2.1.0/BCGUpgrade_620FP5_621.sql -z /home/db2inst1/BCGUpgrade_620FP5_621.log
      
      db2 -td! -f 6.2.1.0_to_6.2.1.1/BCGUpgrade_621_621FP1.sql -z /home/db2inst1/BCGUpgrade_621_621FP1.log
      
      db2 -td! -f 6.2.1.1_to_6.2.1.2/BCGUpgrade_621FP1_621FP2.sql -z /home/db2inst1/BCGUpgrade_621FP1_621FP2.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. Note that these steps are not applicable for Simple Mode installation. The next set of commands should be run only if you are upgrading from 6.2.0.0 to 6.2.0.1.
      
      Note: If you are upgrading from 6.2.0.1 or higher to 6.2.1.2, 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 WebSphere Partner Gateway 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.1-WS-WPG-FP2_Advanced/database/oracle
      
      
    • Run the following applicable scripts. Determine the level you are starting from (that is from V6.2.0.0, run all eight scripts, from V6.2.0.1, only the last seven, from V6.2.0.2, only the last six 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
      
      sqlplus -L bcgapps/<password> @6.2.0.5_to_6.2.1.0/BCGUpgrade_620FP5_621.sql
      
      sqlplus -L bcgapps/<password> @6.2.1.0_to_6.2.1.1/BCGUpgrade_621_621FP1.sql
      
      sqlplus -L bcgapps/<password> @6.2.1.1_to_6.2.1.2/BCGUpgrade_621FP1_621FP2.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
    
    
    

    Uninstallation instructions

    
    IBM WebSphere Partner Gateway Version 6.2.1 Fixpack 2 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.1 Fixpack 2 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 should 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.1 Fixpack 2 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.1-WS-WPG-FP2_Advanced.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.

    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.1-WS-WPG-FP2_Advanced.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.1.2 Fixpack :
    

    http://www.ibm.com/support/docview.wss?uid=swg27028306

    
    
    
    

    Copyrights and Trademarks

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