IBM® WebSphere® Partner Gateway, Enterprise Edition, V6.2 FixPack 2

Download Description

These notes describe the changes made in the Fixpack for 6.2.0.2 of IBM WebSphere Partner Gateway Enterprise Edition.

WebSphere Partner Gateway 6.2 FixPack 2(6.2.0.2)
© Copyright International Business Machines Corporation 2009. 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
Server and Database support
Known problems and workarounds
Installation instructions
Uninstallation instructions
List of fixes
Copyrights and Trademarks

Prerequisites

1. When using WebSphere Partner Gateway 6.2 FixPack 2 with WebSphere Application Server Network Deployment 6.1 Fixpack 23 and 25 (WAS ND FP23 and 25), following Null Pointer exceptions are seen in WebSphere Partner Gateway logs.
   
   The Null pointer exception seen is followed by a "DSRA9110E: Connection is closed" exception trace. The following exceptions are seen in the WebSphere Partner Gateway server logs:
   
   
E UOW=null source=com.ibm.ws.scheduler.SchedulerDaemonImpl org=IBM prod=WebSphere component=Application Server thread=
[java.lang.ThreadGroup[name=ArchiverWorkManager: WM Service Group,maxpri=10]]
SCHD0104E: The Scheduler poll daemon ArchiverScheduler (scheduler/ArchiverScheduler) failed to load tasks
from the database due to an exception: java.lang.NullPointerException
at java.util.Hashtable.getEntry(Hashtable.java:468)
at java.util.Hashtable.containsKey(Hashtable.java:354)
at com.ibm.db2.jcc.a.lg.setCursorName(lg.java:695)
......
......
E UOW=null source=com.ibm.ejs.j2c.MCWrapper org=IBM prod=WebSphere component=Application Server thread=
[java.lang.ThreadGroup[name=ArchiverWorkManager: WM Service Group,maxpri=10]]
J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection
WSRdbManagedConnectionImpl@4e904e90 from resource datasources/bcgArchiverDS. Caught exception:
com.ibm.ws.exception.WsException: DSRA9110E: Connection is closed.
at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>
(DataStoreAdapterException.java:241)
at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>
(DataStoreAdapterException.java:190)
at com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException
AdapterUtil.java:389)
at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.dissociate
(WSJdbcConnection.java:1383)

   
   This problem is identified to occur due to incorrect handling of closed database pooled connections in WebSphere Application Server. See the recommended link to download and apply the fix for WAS ND 6.1 FP23 and WAS ND FP 25.
   
   Also, see the WebSphere Application Server APAR PK86552 description
   
   
2. Make sure that value for -Wupdate.RunSQLFiles is set to "Yes" in the Update Installer response parameter file.
   
   
3. For applying 6.2 FixPack 2 on WebSphere Partner Gateway that is installed on an existing cell, see the technote link Prerequisite steps to be followed before using Update Installer with WebSphere Partner Gateway v6.2 on existing cell. You do not have to apply this FixPack on bcgapps location.

Operating System, Server and Database support

The Enterprise Edition of WebSphere Partner Gateway Version 6.2.0.0 FixPack 2 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.27
   
2. IBM DB2 UDB V9.5 FixPack4a
   
3. AIX 6.1 TL1, TL2, TL3 and TL4. The WebSphere Partner Gateway(WPG) 6.2 base installer does not launch on AIX 6.1 TL2, TL3 and TL4. Please click here for details regarding the work-around for details of installation.
   

For more details, refer to System Requirements.

Known problems and workarounds

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. Errors are observed in bcgmigration logs during the import of Certificate sets, which are associated to an already deleted partner. For the certificate set, deleted partner can be associated either as a “from” or “to” partner.

3. Client Authentication for FTPS mode may not work when an invalid primary and a valid secondary certificates are uploaded. When using client authentication for FTPS mode in case of an expired primary certificate and a properly configured valid secondary certificate, the document processing fails. The transition of secondary to primary certificate happens in WebSphere Partner Gateway configuration. The workaround solution is to perform a restart of WebSphere Partner Gateway Document Manager server.

4. When Secondary to primary transition of a certificate happens, events “BCG240027- Certificate Is Expired” and “BCG108011-Secondary Certificate changed to Primary Certificate” may not get logged.

5. When SSL client authentication is configured for FTP scripting destination with FTPS mode enabled, and a revoked CA certificate is uploaded at the hub operator profile, the events "BCG240024 -CertPath validation failed" and "BCG240033 -No valid SSL client certificate found" may not get logged.

6. When you upgrade to 6.2 FixPack 2, “Error 404: Cannot load application resources bundle console” error might occur. This problem is observed intermittently on HP-UX platform. Workaround for this problem:
   
   
   • Run the Update Installer and uninstall the WebSphere Partner Gateway 6.2 FixPack 2.
     
   • Do NOT restore the DB.
     
   • Run the Update Installer and Install WebSphere Partner Gateway 6.2 FixPack 2 again.

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 during the creation of the following WebSphere Partner Gateway tables:
   
   
   • BP_RNSTATEDTL
     
   • BP_RNSTATEDTL_HIST
     
   • CF_BUSINESSLOGO
     
   • CF_CRL
     
   • CF_GUIDELINEMAP
     
   • CF_TRANSFORMMAP
     
   • PR_CERT
     
   • EDICSTX

Problem Symptom
Oracle Error "ORA-22996: NEXT extent size is smaller than LOB chunksize" This error is seen to be occuring during the execution of WebSphere Partner Gateway v6.2 GA DBLoader installation.

Resolving the problem
This problem has been resolved with WebSphere Partner Gateway 6.2 FixPack 2. 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 2 immediately after installation of WebSphere Partner Gateway 6.2 GA, so as to get these tables created.

Only users who intend to have WebSphere Partner Gateway 6.2 GA installed on Oracle 11.1.0.7 are affected by this error. WebSphere Partner Gateway v6.2 GA is supported on Oracle 11.1.0.6. From WebSphere Partner Gateway v6.2 FixPack 2 onwards, support is also provided for Oracle version 11.1.0.7.

Installation instructions

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

Step A - Setup the IBM Update Installer environment.
Step B - Take the backup of WebSphere Partner Gateway application Database.
Step C - Install the FixPack.

Step A - Setup the IBM Update Installer environment.

1. Download the IBM® Update Installer for WebSphere Software from http://www.ibm.com/support/docview.wss?rs=180&uid=swg24020212.
   Note : Please update UPDI with WPG 6.2 Fix Pack 2 specific UPDI version before applying WPG Fix Pack 2.
   
2. Follow the instructions at http://www.ibm.com/support/docview.wss?uid=swg27015150 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.

Now, IBM Update Installer is ready to install WebSphere Partner Gateway fixes and FixPacks on your environment.

Step B - Take the backup of WebSphere Partner Gateway application Database.

Take the backup of the existing WebSphere Partner Gateway Application database. This 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 2. 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 2 is uninstalled.

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

Step C - Install the FixPack.

1. In case of applying the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); the 6.2 FixPack 2 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. 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 2 file using update installer.

3. Following are the prerequisites for 6.2 FixPack 2 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.

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

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

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

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

8. 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 will start and after it completes, an appropriate message, that is, Success or Failed will be displayed. Verify the logs <updateconfig.log> present under <DMGR installed path>/logs/update/<6.2 FP2 pak name>.install for more information on the FixPack installation.

9. Perform these steps on all machines where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed.

Note: For applying 6.2 FixPack 2 on WebSphere Partner Gateway that is installed on an existing cell, see the technote link Prerequisite steps to be followed before using Update Installer with WebSphere Partner Gateway v6.2 on existing cell. You do not have to apply this FixPack on bcgapps location.

Uninstallation instructions

IBM WebSphere Partner Gateway Version 6.2 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 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 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 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 FixPack 2 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 will start and once it is complete the appropriate message i.e., Success or Failed will be displayed. Please verify the logs <.updateconfig.log> present under <DMGR installed path>/logs/update/<6.2 FixPack 2 pak name>.uninstall for more information on the FixPack uninstallation.

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

Step B - Restore the WebSphere Partner Gateway application Database.

Once the uninstallation is successfully completed, 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.2 FixPack:
http://www.ibm.com/support/docview.wss?uid=swg27017465

Copyrights and Trademarks

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