File:   4.5.1-TIV-TIM-WAS-IF0089.README For ITIM 4.5.1 using IBM WebSphere Application Server.
Date:   April 29, 2009
                                                   
Interim fix 4.5.1-TIV-TIM-WAS-IF0089 for APARs IZ18189, IZ21263, IZ29890, IZ31646, IZ39676, and IZ47949.

Components:
       enrole.ear for all supported platforms for WebSphere AppServer.
      
General Description:

This Interim fix provides fixes for APARs IZ18189, IZ21263, IZ29890, IZ31646, and IZ39676.
NOTE:  This interim fix contains the fixes as 4.5.1-TIV-TIM-WAS-IF0088, except it has been compiled using JDK 1.3 to work with WebSphere 5.0.2.

  Problems Fixed:
    
    APAR:    IZ47949
    Symptom: AE Fix Completion for Interim Fix 4.5.1-TIV-TIM-WAS-IF0088.
    		 Unable to start ITIM after installing Interim Fix 4.5.1-TIV-TIM-WAS-IF0088 in ITIM 4.5.1 when running on WebSphere 5.0.2.
    
    APAR:    IZ18189
    Symptom: Specifying search filers for contextual List Boxes when specifying locations as the base do not 
    		 work consistently.
   
    APAR:    IZ21263
    Symptom: ITIM Message, "Role Change Not Allowed" is always displayed in English even when the Browser is 
    		 set to another language. 
  
    APAR:    IZ29890
    Symptom: Email constraint fails with valid domains such as abc@x.ibm.com if one of the expressions contains
             only one character.
  
    APAR:    IZ31646
    Symptom: HumanResourceMO.getAssignments() returns no results.
  
    APAR:    IZ39676      32580
    Symptom: Authentication may occur when an empty challengesAndResponses Map is passed.
  
  Old Problems Fixed from prior Interim Fixes:
  
    APAR:    IZ09946
    Symptom: ITIM throws "java.util.ConcurrentModificationException" while refreshing the 
             internal ACI cache under some conditions.
     
Architecture(s): Windows, Solaris, AIX, HPUX and Linux.

Fixes Superseded: Interim fix 4.5.1-TIV-TIM-IF0087 and Interim fix 4.5.1-TIV-TIM-IF0088.

Dependencies: ITIM 4.5.1-TIV-TIM-FP0086 Fixpack.

Database Changes: NONE.

JMS (Java Messaging Service) Changes: NONE

LDAP Changes: NONE.

Files Replaced or Added or Modified by this Interim fix :

    <ITIM_HOME>/enrole.ear
    
Patch Contents:
  - This README file
  - enrole.ear 

MD5 Checksums:
59710bb45cc6dfe2d8754674ae44b208 - 4.5.1-TIV-TIM-WAS-IF0089.zip

MD5 Checksums:
bc2d56a5ee87f5b07df9084f56ced6bf - enrole.ear


Applying the Patch:

   1) Extract the Interim Fix zip file to a temporary directory on your hard drive:
     
         # jar xvf 4.5.1-TIV-TIM-WAS-IF0089.zip  

      NOTE:  You may also use any unzip equivalent to unpack the zip file.
             Back-level versions of jar, FastJar or PKZIP may report errors. 
             Use the jar executable supplied with java or another zip utility 
             to uncompress the file.
      
   2) Copy the file(s) to the appropriate directory.

      You will now need to copy the files to the appropriate directories.
NOTE: *************************************************************************       
      Always BACKUP your old files in a safe place in case an unforseen 
      event occurs.  It is recommended to backup ITIM_HOME/data directory.
      Especially, be sure to backup any configuration files you 
      may have modified  such as properties or xml files.
NOTE: *************************************************************************       
      IF YOU ARE USING JAVA 2 SECURITY:
      Backup up your was.policy file to a temporary holding directory.  During 
      the fix application you will be re-deploying enrole.ear, which removes the
      $WAS_HOME/config/cells/$CELL_NAME/applications/enRole.ear/deployments/enRole/META-INF
      directory and its contents. During the deployment, the was.policy is not 
      replaced and will need to be copied back during the COMMON TASKS section 
      of this document.  On a Cluster this needs to be done on the NDM as well.
      $WAS_HOME/DeploymentManager/config/cells/$CELL_NAME/applications/enRole.ear/deployments/enRole/META-INF
NOTE: *************************************************************************       
      IF YOU HAVE INSTALLED A CUSTOM LOGO:
      The logo is copied to:
      $WAS_HOME/installedApps/<machine_name>/enRole.ear/app_web.war/images
      The Fixpack and Interim fix process removes the enRole.ear and all subdirectories.  
      To make it easier to restore the custom logo, copy it to a backup directory of your 
      choosing to facilitate copying it back after the Interim fix is applied.
      The ui.properties is preserved so it will not need to be updated.
      After the Interim fix is installed copy the custom logo to:
         $WAS_HOME/installedApps/<machine_name>/enRole.ear/app_web.war/images
NOTE: *************************************************************************       
      IF YOU HAVE INSTALLED A LANGUAGE PACK:
         Symptom - Fixpacks and Interim fixes partially overwrite Language Pack installation.
         Note - Before Fixpack or Interim fix installation, take a back-up of the following
         files/folder related to the language pack, located in the directory:
          $WAS_HOME/installedApps/<machine_name>/enRole.ear/app_web.war
            - AppletErrorMessages_<language code>.properties
            - AppletLabels_<language code>.properties
            - AppletMessages_<language code>.properties
            - The folder along with it's contents by the name as <language code>.
        
      The <language code> is generally a two letter word representing the language. 
      For example for English, the language code is 'en'.
        
      After applying the Fixpack or Interim Fix, restore all the language pack related files
      and folders, that were backed up, to their respective locations in the directory: 
      $WAS_HOME/installedApps/<machine_name>/enRole.ear/app_web.war
        
      Note that for WAS Cluster installation, the same steps will have to be followed on 
      each of the nodes. This procedure is needed only on the cluster member, not on the 
      Deployment Manager node.
      
	  The file, enrole.ear, is used for single server and regular cluster.
      For all instances of <server_name> below we are referring to the AppServer name in
      WebSphere, usually referred to as server1 in a single server environment.
    
      NOTE***  SINGLE SERVER INSTRUCTIONS:
      Please use the following instructions for a Single Server environment.  
      If this is a single server environment, only the enrole.ear is needed.         
          
      1. Log in to the App Server Administrator.
      
       a. Example:
               http://localhost:9090/admin .
      
      2. Uninstall enrole application       
      
       a. Select the enRole application
       
       b. Stop the enRole application
       
       c. Uninstall the enRole application
       
       d. Above this box, click on save the configuration...another panel will 
          come up and you will need to confirm this by pressing the save configuration
          button.
          
       e. You are now finished with the App Server Administrator
       
      3. Restart WAS.
      
       a. Stop the AppServer (stopServer.sh)
       
       b. Start the AppServer (startServer.sh)  
      
      4. In the <ITIM_HOME>/bin directory run 
               SetupEnrole install server:<server_name>  (e.g. server1)
               
          If you have WAS Security setup then:
         
               SetupEnrole install server:<server_name> user:<userid> password:<password>
               
      5. Perform the COMMON TASKS listed below these instructions.
      
      6. After you are done with the COMMON TASKS, then:
      
      7. Restart WAS and you are done.
             
       a. Stop the AppServer (stopServer.sh)
              
       b. Start the AppServer (startServer.sh)
               
         
      NOTE***  CLUSTER INSTRUCTIONS:
      Please use the following instructions for a Cluster environment.  
      If this is a regular cluster, only the enrole.ear is needed.         
      
      1C. Ensure all node agents are up and can communicate with the NDM.
      
      2C. Uninstall the ITIM Application from WebSphere.
      
       a. Stop the cluster. Use "ssCluster.sh stop" or from NDM admin console, 
          navigate to Servers -> Clusters. Select the cluster (s) where ITIM 
          is installed, and stop. 
       
       b. Uninstall the enrole enterprise app. 
       
       c. Save the config ensuring that it is synched with all the nodes. 
       
       d. Logout from the NDM admin console.       
       
      3C. Re-Install ITIM.
      
       a. From NDM, run <ITIM_HOME>/bin/setupEnrole install. This is same as 
          in single server case, except, you don't need the "server" argument 
          here because the app will be deployed onto a cluster.
      
          If you have WAS Security setup then:
         
               SetupEnrole install user:<userid> password:<password>
               
      4C. Perform the COMMON TASKS listed below these instructions.
               
      5C. Start the cluster. Use "ssCluster.sh start" or do it from the NDM 
          admin console. 
          
NOTE: *****************************************************************************
       The following are COMMON TASKS that you may need to perform prior to restarting 
       the AppServer or Cluster. 
NOTE: *****************************************************************************

      1. Copy the itim_api.jar, itim_server.jar and the api_ejb.jar from:
         $WAS_HOME/installedApps/$MACHINE_NAME/enrole.ear  directory to
         $ITIM_HOME/lib  directory.
          
      2. If you are using the JAVA 2 Security, replace the was.policy file you saved
         earlier.  Copy it back to:
         $WAS_HOME/config/cells/$CELL_NAME/applications/enRole.ear/deployments/enRole/META-INF
         For Cluster in the NDM:
         $WAS_HOME/DeploymentManager/config/cells/$CELL_NAME/applications/enRole.ear/deployments/enRole/META-INF
         Where $CELL_NAME is either the $MACHINE_NAME or $CLUSTER_NAME.
         For additional information on using JAVA 2 Security with ITIM, please review the ITIM
         Installation Guide, Appendix C.
 
       END OF COMMON TASKS

End of Readme
