Name: PK33379
=============
 
Summary:
   Enable schema support for the WMM database on DB2 for z/OS.
 
Problem Description:
   The tables of the WMM database are created implicetely in the schema
   of the database user. It is not possible to define a different schema name.
 
Problem Solution:
   This APAR enables schema support for the WMM database on DB2 for z/OS.
   Configuration scripts are extended. The WMM tables can be created within
   a given schema. For each WMM table an equally named SYNONYM is added for
   the user that created the WMM database. The synonyms allow an unchanged
   runtime code, which does not specify schema names for the WMM table related
   SQL queries.
   
   Note: A schema name for the tables in the WMM database on DB2 for z/OS can
         be specified by adding the following property to the
         wpconfig_dbdomain.properties file located in the PortalServer/config directory:
         wmm.DbSchema=<SCHEMA_NAME>
 
Failing Module(s):
   Database
   Configuration
 
Affected Users:
   All users
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): 
      Co-Requisite(s): ---
 
Platform Specific:
   This fix applies to all platforms.
 
Installation:
   NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
          The Portal Update Installer can be downloaded from the following link:
          http://www.ibm.com/software/genservers/portal/support
 
   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   4. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install the fix.
   5. Restart WebSphere Portal.
   6. The temporary directory may be removed.
 
Un-Installation:
   NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE
          A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
          YOU MAY REAPPLY ANY REMOVED FIX.
 
   1. Shutdown WebSphere Portal.
   2. Follow the instructions that are packaged with the
      Portal Update Installer on how to uninstall the fix.
   3. Restart WebSphere Portal.