© Copyright International Business Machines Corporation 2006, 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
1.0 About this release
2.0 Installation information
3.0 Limitations
4.0 Known problems and workarounds
5.0 IBM Rational Software Support
6.0 Notices and trademarks
The latest version of this document is available at http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/im/1002/docs/readme/readme.html.
IBM® Installation Manager is a program that helps you install, update, modify, and uninstall packages on your workstation. This update contains fixes to the version 1.0 release of IBM Installation Manager. You can use Installation Manager to perform the following tasks:
- Keep track of what you are about to install, as well as what you have already installed and what is available for you to install
- Install, update, and uninstall packages silently
- Search for updates so you know that you are installing the latest version of a package
- Manage licenses for the packages it installs, and to update and modify packages
- Uninstall packages
For information about installing IBM Installation Manager, refer to the installation guide for a product that is part of the IBM Rational® Software Development Platform.
This section describes limitations specific to this release.
3.1 Launchpad: nonsupported browser error
The launchpad does not support Mozilla Firefox V1.6; the supported range is V1.7 or higher.
This section describes known problems specific to this release and any workarounds that are available.
4.1 Silent Install; silently installing the LUM license 4.2 MD5 errors when Apache configuration file contains AddHandler imap-file map 4.3 Repository inaccessible due to repository.config file configuration issue on Web servers 4.4 Removal of installed content during uninstallation 4.5 Missing shortcut allowing View Installed Packages on Linux 4.6 Non-IBM eclipse plugin management and the -clean option 4.7 Starting a product as non-admin generates log file errors and may cause workspace issues 4.8 Installing and uninstalling Installation Manager Silently 4.9 Package Enablement Kit must be a jar file (rather than a zip file) 4.10 The rollback feature is not supported in Installation Manager Version 1.0.0.2 4.11 Adding content to a file without using link files 4.12 IM from Aux CD on Windows and Linux 4.13 Error message during session finalization
4.1 Silent Install; silently installing the LUM license
The LUM Kit is a compressed repository containing an offering. You can silently install a LUM Kit just as you install an offering. The only difference is that a LUM Kit is a jar repository, so you must specify the jar as a repository in your server command.
Begin by using the record mode to generate a response file for silent install.
- Start Installation Manager using the following command: -record <path to generated response file>
- Import a LUM kit using the license wizard.
After exiting Installation Manager, a response file is created.
4.2 MD5 errors when Apache configuration file contains AddHandler imap-file map
The string ".map." in a filename can cause the Apache web server to perform a translation on the file contents before sending it to the client.
For example, in Apache 2.2, this can happen by adding the line:
AddHandler imap-file map
into an .htaccess file in a directory served. The default configuration for some Apache installations is for AddHandler to be applied generally.
Workaround: Comment out the "AddHandler imap-file map" line in the configuration files that affect the repositories used by Installation Manager and Packaging Utility.
This incorrect configuration will cause a message that looks similar to the following error message:
Downloading plugin com.ibm.etools.sfm.mft.uri.map.nl1_7.0.0.v200610130814.
Downloading http://server.name.com/ccb/Offerings/wdz70/20061013_1017/repository/plugins/com.ibm.etools.sfm.mft.uri.map.nl1_7.0.0.v200610130814.jar to "D:\SDP70Shared\tmp\cicdip\v\md5\2aa842bc2558c018304a60446ddb2d3a".
Table of contents digests differs from digest of downloaded file.
4.3 Repository inaccessible due to repository.config file configuration issue on Web servers
Some Web servers may not serve the file named "repository.config" without configuration of the Web server.
When you attempt to add a repository using the File > Preferences > Repositories window with a repository.config file, an error will appear indicating that it is not possible to connect to a repository with the given URL. The error message looks like this, "Failed to connect to repository http://..."
Workaround: You must configure the Web server to allow the repository.config file to be served. Refer to the Web server documentation for configuration details. You can use a browser such as Firefox or Internet Explorer to verify the existence and and correct working of the server by browsing directly to the fully qualified repository URL and opening the repository.config file. A repository.config file is a text file that indicates a file-based repository.
4.4 Removal of installed content during uninstallation
Some artifacts generated during the normal usage of a package are not uninstalled when the package is uninstalled. These files, which vary by the package being uninstalled, must be manually deleted. You should only delete these files located within a package group install directory rather than the shared install directory. Once the last package has been uninstalled from the package group directory, any remaining files may be removed.
4.5 Missing shortcut allowing View Installed Packages on Linux
IBM Installation Manager requires administrative access to install packages; however, you do not need administrative access to run packages installed through Installation Manager. This setup allows an administrator to perform the installation and a non-administrator to use the installed packages.
Non-Administrators can view installed packages by opening the installed.xml file directly. On Microsoft® Windows®, there is a shortcut to the installed.xml file via the Start > IBM Installation Manager > View installed Packages. However, this kind of shortcut is not supported on Linux®.
Workaround: Navigate directly to the installed.xml file and open the file using a Web browser. The installed.xml file resides in the administrator's Application Data area which by default resides in /var/ibm/InstallationManager. The Application Data area can be set to a non-default value when you install Installation Manager.
4.6 Non-IBM Eclipse plug-in management and the -clean option
This note describes advanced Eclipse plug-in installation information for Eclipse-based packages. This note only applies when the installed package is Eclipse-based and when the installed package needs to be extended with non-IBM Eclipse plug-ins.
An empty Eclipse installation location (also known as an Eclipse site) is created during installation to manage Eclipse plug-ins not contained within IBM Rational products; IBM Installation Manager never uses this Eclipse site. This empty Eclipse installation location is created to simplify the experience of advanced Eclipse users when using the Eclipse Update Manager found on Help > Software Updates. The Eclipse update should not be used for the normal updates and fixes of IBM Rational packages because Installation Manager is used to manage the fixes and updates for IBM Rational packages. The Eclipse update should only be used for non-IBM plug-ins and only used with extreme caution by advanced Eclipse users.
The Eclipse installation location that has been created for non-IBM software is in the installation location where the IBM Rational Packages were originally installed. In Eclipse, the Help > Software Updates > Manage Configurations displays the installation locations when you select the Show Install Locations button. There will be two sites and by default their directory names will be SDP70 and SDP70Shared. The SDP70Shared installation location is managed by Installation Manager and should never be used by the Eclipse Update Manager. The SDP70 installation location is an empty installation location that can be used by the Update Manager when installing Eclipse software from Eclipse sites.
It is also possible to copy Eclipse plug-ins into the SDP70 empty plug-ins directory and start Eclipse with the -clean option; this triggers Eclipse to recognize the new plug-ins.
4.7 Starting a product as non-admin generates log file errors and may cause workspace issues
If you start an IBM Rational product with a non-admin user id in a Windows XP environment, you might see the following error messages:
Caused by: java.io.FileNotFoundException:
<install>\configuration\org.eclipse.core.runtime\.manager\.fileTableLock (The handle is invalid.)In addition, settings for "workspace launcher" point to the previous admin user's workspace.
This problem only happens when products are installed in an NTFS file system because products store configuration information in the <install>\configuration\org.eclipse.core.runtime\.manager directory; however, non-administrators do not have permission for this directory.
Workaround: You must remove the write permission of the non-admin user in <install>\configuration directory. This action forces the configuration to be stored in the %userprofile% directory instead.
To force the configuration to use the %userprofile% directory:
- Log in as admin user.
- Browse to <install>.
- Right click on "configuration" folder and display the properties of the directory.
- Click the Security tab, and then click Advanced.
- Ensure that the non-admin user does not have permission to create file and create folder under the "configuration" directory.
4.8 Installing and uninstalling Installation Manager Silently
To silently install Installation Manager onto a default install location on Windows:
If you want to change the install location, you can add INSTALLDIR property inside the /v option. For example:
setup.exe /S /v"/qn INSTALLDIR=\"C:\InstallationManager\""To silently uninstall Installation Manager on windows, run this command in the command prompt:
msiexec /x {DBD90D51-BD46-41AF-A1F5-B74CEA24365B}To silently install Installation Manager onto a default install location on Linux:
- Change directory to InstallerImage_linux folder on the first installation disk.
- Run setupLinux.bin -silent -V licenseAccepted=true.
"-V licenseAccepted=true" option is used to state that you accept the license agreement on the use of Installation Manager.
If you want to change the install location, you can add -P installLocation="<new dir>" flag. For example:
setupLinux.bin -silent -P installLocation="/opt/myIM" -V licenseAccepted=trueTo silently uninstall Installation Manager on Linux:
4.9 Package Enablement Kit must be a jar file (rather than a zip file)
The Package Enablement Kit is a jar file that is typically obtained through Passport Advantage Online; it may contain a name such as RADlic.jar. When you download this file using Internet Explorer's Save As or click to download commands, Internet Explorer stores this file as a .zip file (rather than a .jar file). You must save this file as a jar file or change the zip extension back to jar after the download is complete. Installation Manager only accepts jar files through the Manage Licenses wizard.
4.10 The rollback feature is not supported in Installation Manager Version 1.0.0.2
Contrary to the Installation Manager online help and the 7.0.0.1 product Installation Guide documents, you cannot use the Uninstall Packages wizard rollback feature; the rollback feature is not supported in Installation Manager Version 1.0.0.2.
The Rolling back updates online help topic indicates that you can use the Uninstall Packages wizard to revert to a previously installed version of a package. For example, if you install Rational Application Developer Version 7.0 and then update to version 7.0.0.1, the help topic states that you can use the rollback feature to revert to 7.0; this is not possible. Also, the Silent Install Commands online help topic indicates that you can use the rollback command during silent install; this command is not supported.
Workaround: To revert to an earlier version of a package, you must uninstall the entire package. In the example, a single uninstallation procedure removes the version 7.0 package and the upgraded 7.0.0.1 package. After uninstalling, you would need to reinstall the 7.0 package.4.11 Adding content to a file without using link files
In this release, using link files no longer works; if you want to add content to a product, you have a couple of options described below.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=166852 (Update Configurator reconciles platform.xml with newer features even for sites that have USER-INCLUDE Policy and have explicit inclusion plugin lists)
Due to the defect referenced above, Installation Manager is setting the transient flag in the platform.xml. Setting this flag ensures Eclipse ignores link files while working around the defect.
Workaround: Use the Eclipse standalone update commands (addSite and removeSite) to add an extension directory. For details, see http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/doc/working/documentation/standalone_update.html
Alternatively, you can use the Add extension option in manage configuration or put plugins/feature into the <installdir>/feature and <installdir>/plugins directory; then, execute -clean.4.12 Installing Installation Manager from the Aux CD on Windows and Linux
The auxilary CD was packaged with zip files for Installation Manager.
To install Installation Manager from the Windows Aux CD:
To install Installation Manager from the Linux Aux CD:
- Navigate to AuxCD-Windows\InstallationManager.
- Unzip agent.installer.win32.zip.
- Run install.exe to install Installation Manager.
- Navigate to AuxCD-Linux/InstallationManager.
- Unzip agent.installer.linux.zip.
- Run install.bin to install the Installation Manager.
4.13 Error message during session finalization
If two or more packages have been installed into the same package group and one of those package versions is 7.0.0.0 while the other package version is 7.0.0.1, the installation may complete with a dialog that states:
"Problem during session finalization, and Validation of Eclipse installation configuration failed because it has unsatisfied bundle constraints."
Workaround: You can resolve this problem by updating all of the packages in the package group to version 7.0.0.1.
IBM Rational Software Support provides you with technical assistance.
For contact information and guidelines or reference materials that you will need when you require support, read the IBM Software Support Handbook.
For FAQs, lists of know problems and fixes, and other support information, visit the IBM Rational Software Support Web site.
For Rational software product news, events, and other information, visit the IBM Rational Software Web site.
Before you contact IBM Rational Software Support, gather the background information that you will need to describe your problem. When describing a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
- What software versions were you running when the problem occurred?
- Do you have logs, traces, or messages that are related to the problem?
- Can you reproduce the problem? If so, what steps do you take to reproduce it?
- Is there a workaround for the problem? If so, be prepared to describe the workaround.
© Copyright IBM Corporation 2006, 2007. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
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 documentation 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 documentation. The furnishing of this documentation 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:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, 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 OR CONDITIONS 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.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:
Intellectual Property Dept. for Rational Software
IBM Corporation
20 Maguire Road
Lexington, Massachusetts 02421-3112
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 documentation 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.
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.Trademarks and service marks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
- developerWorks
- IBM
- Passport Advantage
- Rational
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.