PK98282: WAI URL HANDLING FIX

APAR status

• Closed as program error.

Error description

• Portal navigation not available when integrating external web
  application via WebSphere Application Integrator (WAI).
  The original WAI code appended query parameters as ?a=b; these
  parameters get lost when redirects occur. The new (fixed) code
  encodes the parameters needed directly in the URL.
  

Local fix

Problem summary

• Portal navigation not available when integrating external web
  application via WAI.
  

Problem conclusion

• The original WAI code appended query parameters as ?a=b; these
  parameters get lost when redirects occur.
  The new (fixed) code encodes the parameters needed directly in
  the URL.
  
  Manual Steps (optional):
  
  Manual steps are only required if Web Application Integrator for
  IBM WebSphere Portal (WAI) is actually installed and used in
  WebSphere Portal. Otherwise the following steps can be omitted.
  
  WARNING: This fix will extract the current wps.ear file, modify
  it and redeploy it. You should be certain that all the previous
  changes you have made to the wps.ear directory have been
  properly redeployed PRIOR to installing this iFix. See
  'Redeploying the portal EAR file' in the InfoCenter for
  directions on how to do this. So, for example, if you have
  implemented custom themes but have not yet redeployed them to
  the wps.ear file, then your custom themes will be lost. Hence,
  this warning.
  
  WARNING: Any modifications you have made to the out of the box
  themes may be overwritten by this fix. If you have made
  modifications you should back up these files PRIOR to installing
  this fix and then merge your changes back in. Please note that
  it is recommended that you NOT modify these files for this very
  reason.
  
  --- Manual steps for single node installation ---
  Applicable for single node or the primary node of a cluster.
  Execute the following:
     <wp_profile>/ConfigEngine/ConfigEngine.[bat|sh] PK98282
  -DWasPassword=<was pwd> -DPortalAdminPwd=<wps pwd>
  The installation process will take a couple of minutes.
  
  --- Manual steps for a clustered Portal deployment ---
  Applicable for a clustered Portal deployment
  
  1. Enable automatic synchronization on all nodes in the cluster.
  2. Apply the single node install directions above to the Primary
  Node in the Portal cluster.
  3. After the Primary Node installation completes, execute the
  following task to active the portlet
     <wp_profile>/ConfigEngine/ConfigEngine.[bat|sh]
  activate-portlets -DWasPassword=<was pwd>
  
  --- Troubleshooting: ---
  Exported and modified wps.ear file is stored at
  <wp_profile>/ConfigEngine/config/PK98282
  
  Failing Module(s):
     Engine: URL Generation
  
  Affected Users:
     all users
  
  Version Information:
      Portal Version(s): 6.1.0.1
       Pre-Requisite(s): PK90578
        Co-Requisite(s): ---
  
      Portal Version(s): 6.1.0.2
       Pre-Requisite(s): PK90578
        Co-Requisite(s): ---
  
  Platform Specific:
     This fix applies to all platforms.
  
  A fix is available from Fix Central:
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?apar=PK98282&productid=WebSphere%20Portal&brandid=5
  
  You may need to type or paste the complete address into your Web
  browser.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R61A PSY

     UP

• R61B PSY

     UP