Instructions for installing patches for InfoSphere™ Information Server 8.1. Document updated September 20, 2011.
Always refer to the latest version of the patch installation instructions. The instructions are periodically updated and contain critical information to ensure the successful installation of patches. Access the latest version of the instructions at http://www.ibm.com/support/docview.wss?uid=swg27012519.
© Copyright International Business Machines Corporation 2008. All rights reserved. US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM® Corp.
This information is the most current about the product on the date of publication.
Instructions in this document use the default installation paths. Your path varies if you installed IBM Information Server in a different location.
Operating system | Directory |
---|---|
Windows® | C:\IBM\InformationServer |
Linux®, UNIX® | /opt/IBM/InformationServer |
Viewing the log files that are created during installation is useful when you are troubleshooting installation problems. During the installation and uninstallation process, the log file is simultaneously updated in the following directories:
After a successful installation, the log file is named ISInstall.YYYY.MM.DD.HH.MM.SS.log where YYYY.MM.DD.HH.MM.SS is the date and time that the installation was started.
After an unsuccessful installation, the ISInstall.YYYY.MM.DD.HH.MM.SS.log file is included in the InformationServer/logs directory, and all logs that are used for troubleshooting are included in the InformationServer/isdump-operating_system-YYYY.MM.DD.HH.MM.SS.zip file.
Patch component | Description |
---|---|
README.txt | Contains important information specific to the patch. |
*.ispkg | Patch package installed with the Update Installer. |
IBM Information Server Update Installer Version 8.1.0.160
On IBM AIX®, Microsoft Windows, and Red Hat Linux, the script might not exist. If the script does not exist, you do not have the latest version of the Update Installer. When you install a patch with Update Installer Version 8.1.0.160 or later, the script is created automatically for future use.
Patches are installed with the Update Installer that is part of the IBM InfoSphere Information Server installation. Updated versions of the Update Installer are located at http://www.ibm.com/support/docview.wss?uid=swg27012519.
Ensure that the following requirements are met before you install patches.
The patch name patch_JR000000_type_os.ispkg in the following commands is an example. Use the correct name of the patch that you are installing.
The user name and password shown in the following commands are examples. Use the same user name and password that you used to install IBM InfoSphere Information Server.
The Update Installer supports two installation modes on all operating systems: installation wizard mode and console mode. You can use command line parameters in both installation modes.
The following command line parameters are available for the patch installation. If you do not specify values for an optional parameter, the Update Installer prompts you to enter the values during the patch installation.
Parameter | Description |
---|---|
-p | Optional. The file name of the patch installation package. |
-user | Optional. IBM InfoSphere Information Server administrator user name. |
-password | IBM InfoSphere Information Server administrator password, required when the -user parameter is provided. |
-wasadmin | Optional. IBM WebSphere Application Server administrator (server ID) user name. Applies only when installing a patch on computers with the services tier installed. |
-waspassword | IBM WebSphere Application Server administrator (server ID) password, required when the -wasadmin parameter is provided. |
-console | Optional. Install without opening the installation wizard. |
-force | Forces reinstallation of a patch. To ensure a consistent installation, reinstall all patches and fix packs that were initially installed after you originally installed this patch. |
-verbose | Optional. Include detailed information in the console output. |
-version | Display the version number of the Update Installer. |
. /opt/IBM/InformationServer/Server/DSEngine/dsenv
unset LDR_CNTRL
/opt/IBM/WebSphere/AppServer/java/bin/java -jar updater.jar other arguments
./InstallUpdate.sh -console
./InstallUpdate.sh –p patch_JR000000_type_os.ispkg -user admin -password AdminPassword -wasadmin wasadmin -waspassword WebSpherePassword –console
export DISPLAY=myhost.mydomain.com:0.0
Where myhost.mydomain is
the full name of the computer that the patch is being installed on.xtermA message confirms that the X11 DISPLAY environment variable is configured properly. You cannot use the wizard to install patches without the correct DISPLAY environment variable.
. /opt/IBM/InformationServer/Server/DSEngine/dsenv
unset LDR_CNTRL
./InstallUpdate.sh
InstallUpdate -console
InstallUpdate -p patch_JR000000_type_os.ispkg -user admin -password AdminPassword -wasadmin wasadmin -waspassword WebSpherePassword -console
InstallUpdate
After you install the patch, verify the installation.
... <History> ... <Sequence description="Description of the patch" id="1" installLocation="" lastUpdateDate="Thu Feb 14 13:13:52 EST 2008" patch="patch_JR000000" rollback="/opt/IBM/InformationServer/Updates/patch_JR000000" status="Success" version=""/> </History> ...
Perform a complete backup of the IBM InfoSphere Information Server installation. See http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.found.admin.common.doc/topics/t_admin_backup_infsrv.html for more information.
Not all patches can be uninstalled. The README.txt file included with each patch indicates whether the patch can be uninstalled. Only the last patch installed can be uninstalled. To uninstall a patch that is not the last installed patch, you must first uninstall the latest installed patch and then uninstall all later patches. Installing a patch that cannot be uninstalled prevents all previously installed patches from being uninstalled because patches must be uninstalled in reverse order of their installation. To determine which patches have been installed, locate the Version.xml file:
In the Version.xml file, the entry for the last patch installed is at the end of the history section and is similar to the following example:
... <History> ... <Sequence description="Description of the patch" id="1" installLocation="" lastUpdateDate="Thu Feb 14 13:13:52 EST 2008" patch="patch_JR000000" rollback="/opt/IBM/InformationServer/Updates/patch_JR000000" status="Success" version=""/> </History> ...
You must use the Update Installer in console mode when you uninstall patches.
Parameter | Description |
---|---|
-rollback | The name of the latest installed patch. |
-verbose | Optional. Include detailed information in the console output. |
Follow these steps to uninstall the latest patch installed on Linux or UNIX operating systems:
. /opt/IBM/InformationServer/Server/DSEngine/dsenv
unset LDR_CNTRL
./InstallUpdate.sh -rollback patch_JR000000
Follow these steps to uninstall the latest patch installed on a Windows operating system:
InstallUpdate -rollback patch_JR000000
At the time of publication, the following problems are known for patch installations.
If IBM InfoSphere Information Server Pack for SAP BW or the IBM InfoSphere Information Server Pack for SAP R/3 is installed on your computer, before installing a patch, shut down SAP and BW listeners to avoid a possible installation failure.
Workaround
Command line options that are passed to the Update Installer are ignored when you use the InstallUpdate.sh or InstallUpdate.bat script. This issue exists only on some installations.
Workaround
Modify the InstallUpdate script to pass through command line options to the Update Installer.
Windows: Edit the C:\IBM\InformationServer\Updates\bin\InstallUpdate.bat script and add %* to the end of the command line as shown in the following example:
"C:\IBM\InformationServer\ASBNode\apps\jre\bin\java.exe" -jar updater.jar -i "C:\IBM\InformationServer" %*
AIX, Linux: Edit the /opt/IBM/InformationServer/Updates/bin/InstallUpdate.sh script and add “$@” to the end of the command line as shown in the following example:
"/opt/IBM/InformationServer/ASBNode/apps/jre/bin/java" -jar updater.jar -i "/opt/IBM/InformationServer" "$@"
If the port for the InfoSphere Information Server services was modified in IBM WebSphere Application Server after the original installation, the patch installation fails with an authentication error. The following error message appears in the log file:
SEVERE: com.ibm.is.install.update.installer.ConsoleUpdateDriver Failed to authenticate username/password, please ensure your application server is running, and ensure you have entered valid Information server administrator user name/password. Return message is: null
Workaround
Before installing the patch, confirm that the ASBPort value in the Version.xml file matches the actual port used for InfoSphere Information Server.
http://hostname:9080/index.jsp
<Property name="AsbHostName" value=localhost.localdomain/> <Property name="AsbPortNumber" value=9080/>localhost.localdomain is your system hostname. In the AsbPortNumber value, enter the application server port number that you use to connect to the InfoSphere Information Server Web console.
During patch installation, the IBM WebSphere Application Server and the IBM InfoSphere Information Server are automatically shut down and restarted. The patch installation fails when the ASBAgent service fails to stop the ASBAgent process after a shutdown request times out. When this occurs, the following entry is found in the installation log file:
taskkill.exe -Unable to Locate Component Window appears with the message. This application failed to start because framedyn.dll was not found. Re-installing the application may fix the problem.ISinstalltimestamp.txt log file locations:
Workaround
Restart your computer, and then restart the patch installation. If the issue is not resolved, contact IBM customer support. To resolve issues with the taskkill.exe process, contact Microsoft Corporation.
Patch installation might fail if the maximum heap size is not sufficient for that system, resulting in an OutOfMemory exception in IBM WebSphere Application Server. Some systems runningIBM WebSphere Application Server might require increasing the heap size to successfully install a patch. The default maximum heap size allocation of IBM WebSphere Application Server process is automatically set to 768 MB during IBM InfoSphere Information Server installation.
Workaround
Set the maximum heap size property to 1280 MB before installing the patch.
SEVERE: Exit Code: 0, Info: Stopping JobMonApp JobMonApp has been shut down. DataStage Engine 8.0.1.0 instance "801" has been brought down., Error: DeadLock Daemon shutdown
IBM has several methods for you to learn about products and services.
You can find the latest information about IBM InfoSphere Information Server on the Web at http://www.ibm.com/software/data/integration/info_server/. To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/planetwide.
You can contact IBM by telephone for customer support, software services, and general information.
To contact IBM customer service for IBM InfoSphere Information Server in the United States or Canada, call 1-866-INFO-NOW (1-866-463-6669).
To find general information in the United States, call 1-800-IBM-CALL (1-800-426-2255).
Go to http://www.ibm.com for a list of numbers outside of the United States.
Please send any comments that you have about this information or other documentation.
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 Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, 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 may 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.
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003 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 measurements 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.
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.
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
IBM and the IBM logo are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A complete and current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.
The following terms are trademarks or registered trademarks of other companies:
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product or service names may be trademarks or service marks of others.