IBM Security Access Manager for Enterprise Single Sign-On, fix pack 8.2.0-ISS-SAMESSO-IMS-FP0001 readme file

(C) Copyright International Business Machines Corporation 2012. All rights reserved. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM® Corp.
Note: Before using this information and the product it supports, read the general information under "NOTICES" in this document.

DATE: March 2012

-------------------------------------------------------------------------------------------------------------------------

CONTENTS

  • About this fix pack
  • APARS and defects fixed
  • Software limitations
  • Before installing this fix pack
  • Installing this fix pack (automatic)
  • Installing this fix pack (manual)
  • Post installation configurations
  • Other configurations
  • Before uninstalling this fix pack
  • Uninstalling this fix pack (automatic)
  • Uninstalling this fix pack (manual)
  • Verifying the IMS Server version after you install or uninstall the fix pack
  • Documentation updates
  • Notices
  • Trademarks

-------------------------------------------------------------------------------------------------------------------------

  • ABOUT THIS FIX PACK

    This fix pack package contains fixes for IBM Security Access Manager for Enterprise Single Sign-On IMS Server software. This fix pack requires that the IMS Server version 8.2 is installed successfully.

    • Fix pack contents
      This fix pack package contains:
      • This readme file
      • 8.2.0-ISS-SAMESSO-IMS-FP0001.pak

        This .PAK file is the Update Installer fix pack for IMS Server.

      • etc-ISS-SAMESSO-8.2.zip
      • deploymentPack_biometrics_8.2.0.0.543.zip

        Use this package if you are using the fingerprint authentication feature.

      • fix_IV15402_dbscripts.sql

        Use this script specifically to resolve APAR IV15402.

      • The following reports and scripts. Use these files to resolve the missing Delete user and Reset ISAM ESSO password events issue on Tivoli® Common Reporting (TCR) reports.
        • isamesso-reports-deployment-8.2.0.0.543.zip
        • db2_alter_view.sql
        • sqlserver_alter_view.sql
        • oracle_alter_view.sql
    • Dependencies
      This fix pack has the following dependencies:
      • IMS Server, version 8.2
      • IBM WebSphere® Application Server Update Installer, version 7.0.0.1 or later. See IBM Update Installer for WebSphere® Software for Windows®.
  • APARS AND DEFECTS FIXED
    This fix pack corrects the following issues and limitations found in IBM Security Access Manager for Enterprise Single Sign-On version 8.2 and 8.1 release:
    • APAR IV11101

      Symptom: A deadlock occurs when you delete a user through a provisioning system such as Tivoli Identity Manager.

    • APAR IV11556

      Symptom: The user is redirected to the AccessAssistant logon page after the user completes the unlock account page and clicks Next.

    • APAR IV15402

      Symptom: In the AccessAdmin non-English locale user interface, the secret questions are displayed in English. Users also cannot delete or add questions in the non-English locale interface of AccessAdmin. The changes are not saved.

    • APAR IV16928

      Symptom: The Enterprise user name is not correctly displayed in the AccessAdmin if the Search audit logs for Revoke users is done for deleted user.

    • APAR IV16905

      Symptom: Redirection of pre-configured web application link for AccessAssistant and Web Workplace does not work when log on to AccessAssistant and Web Workplace is required.

    • Defect

      Symptom: The user cannot log on to AccessAssistant and WebWorkplace by using a UPN name format. This issue occurs when The user must change the password at next logon option is not selected during user provisioning. The option is in AccessAdmin > System policies > Password Policies > Password Change Policies

    • Defect

      Symptom: There is no sentinel JSP page to check whether the IMS Server and database connection is running.

    • Defect

      Symptom: As the number of configured repositories increase, the IMS Server startup time also increases progressively.

    • Defect

      Symptom: An unexpected bind user DN validation warning message is displayed when you change the SSL connection setting in the IMS Configuration Wizard.

    • Defect

      Symptom: The error message displayed is not correct. This issue occurs during the 8.1 to 8.2 upgrade in the Upgrade Configuration Wizard, LDAP configuration page. When the user enters the wrong port or bind distinguished name, the error message "Specify the Domain Name and NetBios Name" is displayed.

    • Defect

      Symptom: User cannot log on with fingerprint to AccessAgent with only a username. This issue occurs on a newly installed IMS Server 8.2 that is configured with a Tivoli Directory Server or base connector. You need to run fixEnterpriseDirectoryConfig.bat to fix this issue.

    • Defect

      Symptom: You cannot upgrade the IMS Server from version 8.1 to version 8.2 if AccessAnywhere or AlwaysDeny Connector is configured in IMS Server 8.1.

    • Defect

      Symptom: The nameLdapAttribute is not found for a newly registered user. This issue occurs after upgrading the IMS Server from version 8.1 to version 8.2 with Tivoli Directory Server.

    • Defect

      Symptom: The bind user name is case sensitive in IMS Server 8.2, which might cause installation or upgrade to fail. The issue occurs if the bind user name in the Active Directory and the bind user name in the IMS Server have a different case.

    • Defect

      Symptom: Cannot search for Delete user and Reset ISAM ESSO password audit log events. These events are not displayed in the AccessAdmin user interface.

    • Defect

      Symptom: IMS Server can be configured to autostart when WebSphere Application Server is started up.

    • Limitation

      Symptom: If you are using a Tivoli Directory Server as your repository and you are enrolling a fingerprint for the first time or if you already have biometric support but your Wallet is not cached, you are prompted to enter your user name. Your user name must have a prefix. The prefix is the Tivoli Directory Server host name or IP that you specified during the Enterprise Directory configuration. For example, IBMTDSHost\user where <IBMTDSHost> is the Tivoli Directory Server host name or IP and <user> is the user name.

  • SOFTWARE LIMITATIONS

    You must use WebSphere Update Installer version 7.0.0.1 or later. WebSphere Update Installer version 7.0.0.0 does not support updating the IMS Server.

  • BEFORE INSTALLING THIS FIX PACK

    Copy the IMS Server installation folder to a backup directory.

  • INSTALLING THIS FIX PACK (AUTOMATIC)

    Before you begin

    Ensure that:
    • You have a copy of 8.2.0-ISS-SAMESSO-IMS-FP0001.zip. This fix pack contains 8.2.0-ISS-SAMESSO-IMS-FP0001.pak and etc-ISS-SAMESSO-8.2.zip.
    • WebSphere Application Server 7.0 is installed and running.
    • IBM HTTP Server 7.0 is installed and configured for the IMS Server.

    About this task

    Do an automatic installation of the fix pack if the IMS Server is already installed and deployed in the WebSphere Application Server 7.0. If it is not, go to INSTALLING THIS FIX PACK (MANUAL).
    1. Download the 8.2.0-ISS-SAMESSO-IMS-FP0001.zip file from IBM Support & downloads.
    2. Extract the contents of the 8.2.0-ISS-SAMESSO-IMS-FP0001.zip file into your local computer.
    3. Extract the etc-ISS-SAMESSO-8.2.zip file into your selected directory.
    4. Copy the extracted etc folder into the root of the <IMS Server installation directory>.

      For example: C:\Program Files\IBM\ISAM ESSO\IMS Server\etc

    5. From the <IMS Server installation directory>\etc\ folder, open the tamesso.ims.appserver.properties file with a text editor and edit the values of these variables.
      was.hostname=was_hostname
was.connector.port=was_connector_port
was.security.enabled=true
was.admin.user.id=was_admin_id
was.admin.user.pwd=was_admin_pw
was.truststore.file=truststore_file
was.truststore.pwd=truststore_pwd
was.keystore.file=
was.keystore.pwd=
      1. Replace was_hostname with the name of your computer.
      2. Replace was_connector_port with the SOAP connector port. For example, 8880.

        Retrieve the SOAP connector port value from: C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\logs\AboutThisProfile.txt

        Note: If you are using WebSphere Application Server Network Deployment, <profile_name> is the deployment manager profile name.
      3. Take one of the following actions, if WebSphere Application Server security:
        • Is enabled, replace was_admin_id and was_admin_pw with your WebSphere Application Server user name and password.
        • Is not enabled, set the value of was.security.enabled to false.
      4. Set the truststore_file and truststore_pwd.
        Note: Use any of these valid formats when you specify the path for the truststore file: 
        C:/.../...
C:\\...\\...
        truststore_file

        Replace truststore_file with the path where the truststore file is located.

        Follow the format in the tamesso.ims.appserver.properties file.

        • For WebSphere Application Server stand-alone:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\nodes\<node_name>\trust.p12

          See the following example:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\ibmusvr1Node01Cell\nodes\ibmusvr1Node01\trust.p12

        • For WebSphere Application Server Network Deployment:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\<Dmgr_profilename>\config\cells\<cell_name>\trust.p12

          See the following example:

          C:\Program Files\IBM\WebSphere\AppServer\Profiles\Dmgr01\config\cells\ibm-svr1Cell01\trust.p12

        truststore_pwd

        Replace truststore_pwd with your WebSphere Application Server trust store password.

        The default password for WebSphere Application Server trust store is WebAS.

      5. If two-way SSL is enabled, set the was.keystore.file and was.keystore.pwd.
        Note: Use any of these valid formats when you specify the path for the keystore file: 
        C:/.../...
C:\\...\\...
        was.keystore.file

        Specify the path where the keystore file is located.

        Follow the format indicated in the tamesso.ims.appserver.properties file. For example,
        • For WebSphere Application Server stand-alone:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\nodes\<node_name>\key.p12

          See the following example:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\ibmusvr1Node01Cell\nodes\ibmusvr1Node01\key.p12

        • For WebSphere Application Server Network Deployment:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\<Dmgr_profilename>\config\cells\<cell_name>\key.p12

          See the following example:

          C:\Program Files\IBM\WebSphere\AppServer\Profiles\Dmgr01\config\cells\ibm-svr1Cell01\key.p12

        was.keystore.pwd
        Specify the WebSphere Application Server keystore password.
        Note: Remove the value after the installation to avoid compromising security.
      6. Click Save and close the file.
    6. Launch the IBM Update Installer for WebSphere Software.
      1. On your Microsoft Windows Desktop, select Start > All Programs > IBM WebSphere > Update Installer for WebSphere V7.0 Software. The IBM Update Installer for WebSphere Software wizard is displayed.
      2. Click Next. The Product Selection page is displayed.
      3. Click Browse to select the location of the <IMS Server installation directory> and click Open. For example: C:\Program Files\IBM\ISAM ESSO\IMS Server
      4. Click Next. The Maintenance Operation Selection page is displayed.
      5. Select Install maintenance package.
      6. Click Next. The Maintenance Package Directory Selection page is displayed.
      7. Click Browse to select the location of the 8.2.0-ISS-SAMESSO-IMS-FP0001.pak file and click Open.
      8. Click Next.
      9. Select the 8.2.0-ISS-SAMESSO-IMS-FP0001.pak file.
      10. Click Next. The Installation Summary page is displayed.
      11. Click Next. There are two possible messages that can be displayed:
        Success: The following maintenance package was successfully installed.

        Displays if you provided the correct connection properties.

        Success: The following maintenance package was partially installed.

        Displays if you provided the wrong connection properties. See INSTALLING THIS FIX PACK (MANUAL).

      12. Click Finish. The IMS Server version is updated with the latest fix pack and deployed in the WebSphere Application Server.
    7. Remapping the ISAMESSOIMS module.
      1. Log on to the IBM Integrated Solutions Console.
      2. On the Integrated Solutions Console left navigation pane, select Applications > Application Types > WebSphere enterprise applications.
      3. Click ISAMESSOIMS.
      4. Under Modules, click Manage Modules.
      5. Click Select All.
      6. Select all entries in the Clusters and servers field.
      7. Click Apply. The list is updated.
      8. Click OK.
      9. Click Save.
      10. Restart the IBM HTTP Server.
    What to do next
    1. Do the post installation configurations.
    2. Verify the IMS Server version.
  • INSTALLING THIS FIX PACK (MANUAL)

    Before you begin

    Ensure that:
    • You have a copy of 8.2.0-ISS-SAMESSO-IMS-FP0001.zip. This fix pack contains 8.2.0-ISS-SAMESSO-IMS-FP0001.pak and etc-ISS-SAMESSO-8.2.zip.
    • WebSphere Application Server 7.0 is installed and running.
    • IBM HTTP Server 7.0 is installed and configured for the IMS Server.

    About this task

    This manual installation of the fix pack involves the uninstallation and reinstallation of the IMS Server in the WebSphere Application Server.

    Installing the fix pack
    1. Download the 8.2.0-ISS-SAMESSO-IMS-FP0001.zip file from IBM Support & downloads.
    2. Extract the contents of the 8.2.0-ISS-SAMESSO-IMS-FP0001.zip file into your local computer.
    3. Extract the etc-ISS-SAMESSO-8.2.zip file into your selected directory.
    4. Launch the IBM Update Installer for WebSphere Software.
      1. On your Microsoft Windows Desktop, select Start > All Programs > IBM WebSphere > Update Installer for WebSphere V7.0 Software. The IBM Update Installer for WebSphere Software wizard is displayed.
      2. Click Next. The Product Selection page is displayed.
      3. Click Browse to select the location of the <IMS Server installation directory> and click Open. For example: C:\Program Files\IBM\ISAM ESSO\IMS Server
      4. Click Next. The Maintenance Operation Selection page is displayed.
      5. Select Install Maintenance package.
      6. Click Next. The Maintenance Package Directory Selection page is displayed.
      7. Click Browse to select the location of the 8.2.0-ISS-SAMESSO-IMS-FP0001.pak file and click Open.
      8. Click Next.
      9. Select the 8.2.0-ISS-SAMESSO-IMS-FP0001.pak file.
      10. Click Next. The Installation Summary page is displayed.
      11. Click Next. The message Success: The following maintenance package was partially installed is displayed.
      12. Click Finish.
    5. Log on to the IBM Integrated Solutions Console.
    Uninstalling the IMS Server
    1. On the Integrated Solutions Console left navigation pane, select Applications > Application Types > WebSphere enterprise applications.
    2. Select the ISAMESSOIMS and ISAMESSOIMSConfig check box.
    3. Click Uninstall.
    4. Click OK.
    5. Click Save.
    Installing the ISAMESSOIMSConfig application
    1. On the Start menu, click Run.
    2. In Open, type cmd.
    3. In the command prompt window, browse to the <ims_home>\bin directory. For example: C:\Program Files\IBM\ISAM ESSO\IMS Server\bin.
    4. Run deployIsamessoConfig.bat. For example:

      deployIsamessoConfig.bat <WAS Admin user ID><password>

    Installing the ISAMESSOIMS application
    1. On the Integrated Solutions Console left navigation pane, select Applications > Application Types > WebSphere enterprise applications.
    2. Click Install.
    3. Under Path to the new application, select between Local file system and Remote file system.
    4. Under Path, click Browse. The com.ibm.tamesso.ims-delhi.deploy.isamessoIms.ear file is located by default in C:\Program Files\IBM\ISAM ESSO\IMS Server\.
    5. Click Next.

      The Preparing for the application installation page is displayed.

    6. Select Fast Path - Prompt only when additional information is required.
    7. Click Next.

      The Install New Application page is displayed.

    8. Retain the default values under Select installation options.
    9. Click Next.
    10. Click Select All.
    11. Select all entries in the Clusters and servers field.
    12. Click Apply.

      The list is updated with the selected clusters and servers.

    13. Click Next.
    14. Click Finish.

      The installation is successful.

    15. Click Save.
  • What to do next
    1. Do the post installation configurations.
    2. Verify the IMS Server version.
  • POST INSTALLATION CONFIGURATION
    If you are using WebSphere Application Server Network Deployment, override session management.
    1. In the WebSphere administrative console navigation pane, click Applications > Application types > WebSphere enterprise applications.
    2. Click ISAMESSOIMS.
    3. Under Web Module Properties, click Session management.
    4. Under General Properties, select the Override session management check box.
    5. Click Apply.
    6. In the Messages box, click Save. The ISAMESSOIMS application is stopped.
    7. Resynchronize the nodes.
      1. Click System administration > Nodes.
      2. Select the check box for each corresponding node.
      3. Click Full Resynchronize.
    8. Start the cluster.
    If you are using WebSphere Application Server Stand-alone, start the IMS Server.
    1. On the Integrated Solutions Console left navigation pane, select Applications > Application Types > WebSphere enterprise applications.
    2. Select the ISAMESSOIMS check box.
    3. Click Start.
  • OTHER CONFIGURATIONS
    • If you are using LDAP enterprise directory, run fixEnterpriseDirectoryConfig.bat.
      1. Back up the IMS Server database.
      2. Open the command prompt.
      3. Enter fixEnterpriseDirectoryConfig.bat <wasadmin> <password>.
      4. Restart the IMS Server.
    • If the IMS Server 8.2 GA release is already configured with base connector:
      1. Open <WAS_HOME>/profiles/<profile_name>/config/tamesso/config/EnterpriseDirectory.xml.
      2. Search for <EnterpriseDirectoryMetaConfiguration>.
      3. Add the following segment between <EnterpriseDirectoryMetaConfiguration> </EnterpriseDirectoryMetaConfiguration>
      <dummyRepositories class="list">
 <DummyRepository>
  <id>edir_BaseConnector</id>
  <enabled>true</enabled>
  <userNameAttributeNames>
   <string>cn</string>
  </userNameAttributeNames>
  <aliasBaseDNs>
    <AliasBaseDN>
     <dN serialization="custom">
      <LdapName>
       <default/>
       <string>dc=edir_BaseConnector</string>
      </LdapName>
     </dN>
    </AliasBaseDN>
  </aliasBaseDNs>
 </DummyRepository>
</dummyRepositories>
    • To resolve the missing Delete user and Reset ISAM ESSO password events in AccessAdmin:
      Edit the ims.xml and add these two event codes as the value for the <encentuate.ims.log.UserAdminLog.SearchableEventCodes> tag in the ims.xml file:
      • 43011004
      • 43005077
      For example:
      <encentuate.ims.log.UserAdminLog.SearchableEventCodes>
<value xml:lang="en">42000007,42000002,..............43011004,43005077</value>
</encentuate.ims.log.UserAdminLog.SearchableEventCodes>
    • To resolve the missing Delete user and Reset ISAM ESSO password events in TCR reports:
      1. Run the SQL script that corresponds to the database in used.
      2. Import the isamesso-reports-deployment-8.2.0.0.543.zip package.

    • To resolve APAR IV15402:
      1. Ensure that all ISAMESSOIMS applications are stopped to prevent the applications from overwriting the IMS database with cached data.
      2. Run this script on the ISAMESSO IMS database.
        Important:
        • Do this step only if you configured IMS Server version 8.2, logged on to AccessAdmin with any non-English locale, and updated some policies.
        • This script will delete all the existing user defined text listed under Access Admin \ System Policies \, which are not saved correctly because of the issue mentioned in APAR IV15402.
        DELETE FROM IMSTemplatedSyncRepo WHERE attrName='policy_object' 
	AND 
	(
			keyValue LIKE '%unlock%_text</id>'
		OR	keyValue LIKE '%engina_%_text</id>'
		OR	keyValue='<id>pid_bind_secret_question_list</id>'
		OR	keyValue='<id>pid_audit_custom_events_list</id>'
		OR 	keyValue='<id>pid_logon_credentials_text</id>'
		OR	keyValue='<id>pid_bind_display_template</id>'
	);
	COMMIT;
      3. Start all ISAMESSOIMS applications.
  • BEFORE UNINSTALLING THIS FIX PACK

    If you want to uninstall the fix pack and revert to IMS Server version 8.2, you must have access to the IMS Server version 8.2 installation files.

  • UNINSTALLING THIS FIX PACK (AUTOMATIC)

    Before you begin

    Ensure that:
    • You have extracted the etc-ISS-SAMESSO-8.2.zip file into your selected directory and copied the extracted etc folder into the root of the IMS Server 8.2 installation directory.
    • IMS Server 8.2 fix pack 1 is installed.
    • WebSphere Application Server 7.0 is installed and running.
    • IBM HTTP Server 7.0 is installed and configured for the IMS Server.

    About this task

    Follow these steps to uninstall the IMS Server 8.2 fix pack 1 and automatically redeploy the IMS Server in the WebSphere Application Server 7.0.

    Procedure
    1. From the <IMS Server installation directory>\etc\ folder, open the tamesso.ims.appserver.properties file with a text editor and edit the values of these variables.
      was.hostname=was_hostname
was.connector.port=was_connector_port
was.security.enabled=true
was.admin.user.id=was_admin_id
was.admin.user.pwd=was_admin_pw
was.truststore.file=truststore_file
was.truststore.pwd=truststore_pwd
was.keystore.file=
was.keystore.pwd=
      1. Replace was_hostname with the name of your computer.
      2. Replace was_connector_port with the SOAP connector port. For example, 8880.

        Retrieve the SOAP connector port value from: C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\logs\AboutThisProfile.txt

        Note: If you are using WebSphere Application Server Network Deployment, <profile_name> is the deployment manager profile name.
      3. Take one of the following actions, if WebSphere Application Server security:
        • Is enabled, replace was_admin_id and was_admin_pw with your WebSphere Application Server user name and password.
        • Is not enabled, set the value of was.security.enabled to false.
      4. Set the truststore_file and truststore_pwd.
        Note: Use any of these valid formats when you specify the path for the truststore file: 
        C:/.../...
C:\\...\\...
        truststore_file

        Replace truststore_file with the path where the truststore file is located.

        Follow the format in the tamesso.ims.appserver.properties file.

        • For WebSphere Application Server stand-alone:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\nodes\<node_name>\trust.p12

          See the following example:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\ibmusvr1Node01Cell\nodes\ibmusvr1Node01\trust.p12

        • For WebSphere Application Server Network Deployment:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\<Dmgr_profilename>\config\cells\<cell_name>\trust.p12

          See the following example:

          C:\Program Files\IBM\WebSphere\AppServer\Profiles\Dmgr01\config\cells\ibm-svr1Cell01\trust.p12

        truststore_pwd

        Replace truststore_pwd with your WebSphere Application Server trust store password.

        The default password for WebSphere Application Server trust store is WebAS.

      5. If two-way SSL is enabled, set the was.keystore.file and was.keystore.pwd.
        Note: Use any of these valid formats when you specify the path for the keystore file: 
        C:/.../...
C:\\...\\...
        was.keystore.file

        Specify the path where the keystore file is located.

        Follow the format indicated in the tamesso.ims.appserver.properties file. For example,
        • For WebSphere Application Server stand-alone:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\nodes\<node_name>\key.p12

          See the following example:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\ibmusvr1Node01Cell\nodes\ibmusvr1Node01\key.p12

        • For WebSphere Application Server Network Deployment:

          C:\Program Files\IBM\WebSphere\AppServer\profiles\<Dmgr_profilename>\config\cells\<cell_name>\key.p12

          See the following example:

          C:\Program Files\IBM\WebSphere\AppServer\Profiles\Dmgr01\config\cells\ibm-svr1Cell01\key.p12

        was.keystore.pwd
        Specify the WebSphere Application Server keystore password.
        Note: Remove the value after the installation to avoid compromising security.
      6. Click Save and close the file.
    2. Launch the IBM Update Installer for WebSphere Software.
      1. On your Microsoft Windows Desktop, select Start > All Programs > IBM WebSphere > Update Installer for WebSphere V7.0 Software. The IBM Update Installer for WebSphere Software wizard is displayed.
      2. Click Next. The Product Selection page is displayed.
      3. Click Browse to select the location of the <IMS Server installation directory> and click Open. For example: C:\Program Files\IBM\ISAM ESSO\IMS Server
      4. Click Next. The Maintenance Operation Selection page is displayed.
      5. Select Uninstall Maintenance package.
      6. Click Next. The Maintenance Package Directory Selection page is displayed.
      7. Click Next.
      8. Select the 8.2.0-ISS-SAMESSO-IMS-FP0001.pak file.
      9. Click Next. The Installation Summary page is displayed.
      10. Click Next. There are two possible messages that can be displayed:
        Success: The following maintenance package was successfully uninstalled.

        Displays if you provided the correct connection properties.

        Success: The following maintenance package was partially uninstalled.

        Displays if you provided the wrong connection properties. See UNINSTALLING THIS FIX PACK (MANUAL)

    3. Click Finish.
    What to do next
    1. Map the ISAMESSOIMS module.
    2. Do the post installation configurations.
    3. Verify that the IMS Server version was changed to the previously installed version.
  • UNINSTALLING THIS FIX PACK (MANUAL)

    Before you begin

    Ensure that:
    • IMS Server 8.2 fix pack 1 is installed.
    • IBM HTTP Server 7.0 is configured for the IMS Server.

    About this task

    Follow these steps to uninstall the IMS Server 8.2 fix pack 1 and to manually redeploy the IMS Server in the WebSphere Application Server 7.0.

    Procedure
    1. On your Microsoft Windows Desktop, select Start > All Programs > IBM WebSphere > Update Installer for WebSphere V7.0 Software. The IBM Update Installer for WebSphere Software wizard is displayed.
    2. Click Next. The Product Selection page is displayed.
    3. Click Browse to select the location of the <IMS Server installation directory> and click Open. For example: C:\Program Files\IBM\ISAM ESSO\IMS Server
    4. Click Next. The Maintenance Operation Selection page is displayed.
    5. Select Uninstall Maintenance package.
    6. Click Next. The Maintenance Package Directory Selection page is displayed.
    7. Click Next.
    8. Select the 8.2.0-ISS-SAMESSO-IMS-FP0001.pak file
    9. Click Next. TheUninstallation Summary page is displayed.
    10. Click Next. The message Success: The following maintenance package was uninstalled is displayed.
    11. Click Finish.
    What to do next
    1. Manually uninstall the IMS Server.
    2. Install the ISAMESSOIMSConfig application.
    3. Install the ISAMESSOIMS application.
    4. Map the ISAMESSOIMS module.
    5. Do the post installation configurations.
    6. Verify that the IMS Server version was changed to the previously installed version.
  • VERIFYING THE IMS SERVER VERSION AFTER YOU INSTALL OR UNINSTALL THE FIX PACK

    Verify the IMS Server version to determine whether the fix pack installation or uninstallation was successful.

    About this task

    After you apply the fix pack, see these steps to verify that the IMS Server version was updated. If the fix pack installation failed, manually uninstall the IMS Server and install the IMS Server in the WebSphere Application Server 7.0.

    Procedure
    1. Log on to AccessAdmin (https://<Web server name>/admin).
    2. Select System > Status > IMS Server version.
      • If you successfully installed IMS Server 8.2 fix pack 1, the IMS Server version is updated to 8.2.0.0.543 and the IMS maintenance level is FP0001.
      • If you successfully uninstalled IMS Server 8.2 fix pack 1, the IMS Server version is changed back to the previous version you installed.
  • DOCUMENTATION UPDATES

    The product documentation for Security Access Manager for Enterprise Single Sign-On, version 8.2, can be found at the following Web address (entered as one line):http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itamesso.doc/ic-homepage.html

  • NOTICES

    This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

    IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

    IBM Director of Licensing
    IBM Corporation
    North Castle Drive
    Armonk, NY 10504-1785 U.S.A.

    For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

    Intellectual Property Licensing
    Legal and Intellectual Property Law
    IBM Japan, Ltd.
    1623-14, Shimotsuruma, Yamato-shi
    Kanagawa 242-8502 Japan

    The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law :

    INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

    Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you.

    This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

    Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

    IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

    Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

    IBM Corporation
    2Z4A/101
    11400 Burnet Road
    Austin, TX  78758 U.S.A.

    Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.

    The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

    Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

    Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

    All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

    All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

    This information is for planning purposes only. The information herein is subject to change before the products described become available.

    This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

    COPYRIGHT LICENSE:

    This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

    If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed.

  • Trademarks

    IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information; at www.ibm.com/legal/copytrade.shtml.

    Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

    IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.

    Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

    Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

    Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

    ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.

    UNIX is a registered trademark of The Open Group in the United States and other countries.

    Java logo
    		 Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

    Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.

    Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

    Other company, product, and service names may be trademarks or service marks of others.

End of IBM Security Access Manager for Enterprise Single Sign-On, fix pack 8.2-ISAMESSO-IMS-FP0001 readme file.