© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
The launchpad does not support Mozilla Firefox V1.6; the supported range is V1.7 or higher.
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'll have to specify the jar as a repository in your server command.
The best way to get started with this is to use 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.
The string ".map." in a filename can cause the Apache Web server to perform a translation on the file contents before sending 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.
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 reposotory.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.
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.
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 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.
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.
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 previously 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.
When you click File > View Log in Installation Manager, the following error appears if you are running Firefox V1.0.7 (which is standard in Red Hat Linux 4 Desktop):
Error loading stylesheet: (null) file:///var/ibm/InstallationManager/logs/log.xsl
Workaround: Upgrade to a newer version of Firefox such as V1.5.
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:
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.