Installing Edge Components with IBM Installation Manager
IBM Installation Manager is a common installer for many IBM software
products that you use to install this version of Edge Components.
New Feature: Edge Components Version 8.0 is the
first full version of the product to be installed by Installation
Manager rather than the programs that are based on InstallShield MultiPlatform
(ISMP) or native packages that are used to install, update, and uninstall
previous versions. Installation Manager is a single installation program
that can use remote or local software flat-file repositories to install,
modify, or update the products. It determines and shows available
packages -- including products, fix packs, interim fixes, etc. --
checks prerequisites and interdependencies, and installs the selected
packages. You also use Installation Manager to easily uninstall the
packages that it installed.
- Overview of IBM Installation Manager
- IBM Installation Manager is a general-purpose software installation
and update tool that runs on a range of computer systems. Installation
Manager can be invoked through a graphical user interface (GUI) or
a command-line interface. You can also create response files in XML
and use them to direct the performance of Installation Manager tasks
in silent mode. For more information on using Installation Manager,
read the Installation Manager Information
Center.
- Packages and package groups
- Each software product that can be installed with Installation
Manager is referred to as a "package." An installed package has a
product level and an installation location. A package group consists
of all of the products that are installed at a single location.
- Installation Manager modes
- IBM Installation Manager can be installed in one of the following
three modes:
- In admin mode, the Installation Manager is installed from an administrator
or a root ID and can be invoked by any administrator or root user. Load Balancer for IPv4 requires
you to install and run the program in admin or root mode for the processes
to run.
- In nonAdmin mode (also called "user mode"), only the user that
installed Installation Manager can invoke it.
- How many Installation Managers do you need
- You only need to run Installation Manager on those systems on
which you install or update product code. You normally need only one
Installation Manager on a system because one Installation Manager
can keep track of any number of product installations.
- Getting the Installation Manager installation kit
- IBM Installation Manager comes in the form of an installation
kit, which contains a set of Installation Manager binaries and a flat-file
repository for the Installation Manager product. The installation
kit is only used for setup and maintenance of the Installation Manager.
- Installing Installation Manager
- When the installation kit is available on your system, you can
install Installation Manager. Installation Manager consists of a set
of binaries that are copied from the installation kit and a set of
runtime data that describe the products that have been installed by
this particular Installation Manager. Before installing Installation
Manager, you must decide in which mode the Installation Manager will
run as well as where the binaries and runtime data -- called
"agent data" or "appdata" -- will reside. Then, you issue the
Installation Manager installc, userinstc, or groupinstc command from
the appropriate user ID to install Installation Manager.
- Accessing product repositories
- All software materials that will be installed with IBM Installation
Manager are stored in flat-file repositories. Each repository contains
program objects and metadata for one or more packages--that
is, software products at a particular level. Repositories can also
contain product maintenance, such as fix packs and ifixes. Whenever
you install a new product, you can choose from any of the available
product levels in any accessible repository.
- Installing the product
- After you have installed Installation Manager and have access
to all necessary product repositories, you can use Installation Manager
command-line commands or response files to perform the actual product
installations. When you install a product, you provide the package
name, optionally the product level to be installed, the product location,
and any other optional properties. For example, some products have
optional features that you can select at installation time or a list
of optional supported language packs from which you can select.
- Working with installed products
- You can use Installation Manager commands to list installed
products and product levels. You can also obtain this information
for installed copies of the products by issuing the versionInfo command
from the product file system. You can use Installation Manager commands
or response files to install a new product level, roll back to a previous
level, or modify the product by adding or removing optional features
or language packs.
- Using the IBM Packaging Utility
- With the Packaging Utility, you can create and manage packages
for installation repositories. You can copy multiple packages into
one repository or copy multiple disks for one product into a repository.
You can copy packages from Passport Advantage into a repository, for
example. For more information on the Packaging Utility, go to the IBM Installation Manager Version 1.4 Information
Center or the IBM Installation Manager
Version 1.5 Information Center.
- Restrictions
-
- Do not use the same response files that are used with other versions
of the product to install or uninstall Version 8.0 silently. Use response
files that are based on Installation Manager to install, update, or
uninstall Version 8.0 and later.
-
The Installation Manager GUI is not supported on Solaris
10 x64 systems. Perform the following actions to install or uninstall
the product on these systems:
- Use the Installation Manager GUI on a supported system to record
a response file that will allow you to install or uninstall the product
silently.
- Edit the recorded response file if necessary.
- Use the response file to install or uninstall the product silently
on your system.
-
For any Linux system that is enabled for Security Enhanced
Linux (SELinux), such as Red Hat Enterprise Linux Version 5 or SUSE
Linux Enterprise Server Version 11, you must identify the Java shared
libraries in the Installation Manager 1.4.2 or later installation
image to the system. Also, you must identify the Java shared libraries
in the Installation Manager 1.4.2 or later installation after it has
been installed. For example:
chcon -R -t texrel_shlib_t ${IM_Image}/jre_5.0.3.sr8a_20080811b/jre/bin
chcon -R -t texrel_shlib_t
${IM_Install_root}/eclipse/jre_5.0.3.sr8a_20080811b/jre/bin
-
If a non-administrator installs the product on a Windows
Vista, Windows 7, or Windows Server 2008 operating system into the
Program Files or Program Files (x86) directory with User Account Control
(UAC) enabled, the product might not function correctly.
UAC is
an access-control mechanism that allows non-administrative users to
install a software product into the Program Files or Program Files
(x86) directory; but it then prohibits any write access to that directory
after the installation has completed. The product requires write access
in the main installation directory to function correctly.
To
resolve this issue, perform one of the following actions:
- Install the product into a directory other than Program Files
or Program Files (x86). For example:
C:\IBM\Edge
- Disable UAC.
- When you install the product using Installation Manager with local
repositories, the installation takes a significantly longer amount
of time if you use the repository.zip file directly without extracting
it.
Before you install the product using Installation Manager
local repositories, extract the repository.zip file to a location
on your local system and add that location to your Installation Manager
preferences.
Note:
Do not transfer the content of a repository
in non-binary mode and do not convert any content on extraction.
New Feature: In addition to the GUI and silent
methods described in this information, you can also use Installation
Manager to manage installation using the Installation Manager imcl
installation command. For information on using Installation Manager
using this method, read the Installation
Manager Information Center.
Perform the following tasks:
- Ensure that any previous versions of the product are uninstalled.
You must uninstall previous versions of Edge Components through the native
installation program or system package tools.
Read Uninstalling previous versions of Edge Components for instructions.
- Perform the tasks in Installing IBM Installation Manager,
which includes adding the product repositories for the Edge Components products.
- Install the product:
- To update your products, read Installing fix packs to Edge Components.
If you need to uninstall the product through IBM Installation
Manager, perform one of the following tasks:
After installing the product, be aware of the following notes for
logging, tracing, and troubleshooting:
- Notes on logging and tracing
-
- Notes on troubleshooting
-
- Set permissions of files that are installed into the /usr directory as 755. Files in the install_home directory depend on the system umask.
You can change permissions of files that are installed into the /usr directory to 700 to match the permissions in Version 7.0 or lower. When you install a fix pack, the file permissions revert to the original 755 permissions. You can change the permissions again after you install the fix pack.
-
By default, some HP-UX systems are configured to not use
DNS to resolve host names. This could result in Installation Manager
not being able to connect to an external repository. You can ping
the repository, but nslookup does not return anything.
Work with
your system administrator to configure your machine to use DNS, or
use the IP address of the repository.
- In some cases, you might need to bypass existing checking mechanisms
in Installation Manager.
- On some network file systems, disk space might not be reported
correctly at times, and you might need to bypass disk-space checking
and proceed with your installation.
To disable disk-space checking,
specify the following system property in the config.ini file in IM_install_root/eclipse/configuration and restart
Installation Manager:
cic.override.disk.space=sizeunit
where size is a positive integer and unit is blank for
bytes, k for kilo, m for megabytes, or g for gigabytes. For example:
cic.override.disk.space=120 (120 bytes)
cic.override.disk.space=130k (130 kilobytes)
cic.override.disk.space=140m (140 megabytes)
cic.override.disk.space=150g (150 gigabytes)
cic.override.disk.space=true
Installation Manager will report
a disk-space size of Long.MAX_VALUE. Instead of displaying a very
large amount of available disk space, N/A is displayed.
- To bypass operating-system prerequisite checking, add the following
line to the to the config.ini file in IM_install_root/eclipse/configuration
directory:
disableOSPrereqChecking=true
Then restart Installation
Manager.
If you need to use any of these bypass methods, contact IBM Support
for assistance in developing a solution that does not involve bypassing
the Installation Manager checking mechanisms.
- Installation Manager might display a warning message during the
uninstallation process.
Uninstalling the product using Installation
Manager requires that the data repositories remain valid and available.
- For more information on using Installation Manager, read the IBM Installation Manager Information Center.
Read the release notes to learn more about the latest version of Installation
Manager.
To access the release notes, complete the following task:
-
Click Start > Programs > IBM Installation
Manager > Release Notes.
-
Go to the documentation subdirectory
in the directory where Installation Manager is installed, and open
the readme.html file.
- Note on version and history information
- The versionInfo and historyInfo commands return version and
history information based on all of the installation, uninstallation,
update, and roll back activities performed on the system.
Installing IBM Installation Manager
Before you install any Edge Components products, you need to install IBM
Installation Manager.
- Obtain the necessary files from the physical media or the web.
There are three basic options for obtaining and installing Installation
Manager and the product.
- Access the physical media, and use local installation:
You can access Installation Manager and the product repositories on
the product media. Install Installation Manager on your system, and
use it to install the product from the product repositories on the
media.
- Download the files from the IBM Passport Advantage
site, and use local installation: Licensed customers can download
Installation Manager as well as the necessary product repositories
from the Passport Advantage site. You can then install Installation
Manager on your system and use it to install the product from the
repositories.
- Download a file from the Installation Manager
website, and use web-based installation: You can download and
unpack a compressed file containing Installation Manager from the IBM Installation Manager website.
You can then install Installation Manager on your local system and
use it to install the product from the web-based repository.
- Install the product through the GUI or silently.
- To install through the GUI:
- Change to the location containing the Installation Manager installation
files, and run one of the following commands:
- Administrative installation
-
- Non-administrative installation
-
- Make sure that the Installation Manager package is selected, and
click Next.
- Accept the terms in the license agreements, and click Next.
The program creates the directory for your
installation.
- Click Next.
- Review the summary information, and click Install.
- If the installation is successful, the program displays a message
indicating that installation is successful.
- If the installation is not successful, click View
Log File to troubleshoot the problem.
- To install silently:
- Administrative installation
-
- Non-administrative installation
-
- Add the product repository to your Installation Manager preferences.
There are three ways to access repositories for your product:
- Access the physical media, and use local installation
You
can access the product repositories on the product media. Use your
existing Installation Manager to install the product from the product
repositories on the media.
- Download the files from the Passport Advantage
site, and use local installation
Licensed customers can download
the necessary product repositories from the Passport Advantage site.
You can then use your existing Installation Manager to install the
product from the repositories.
- Access the live repositories, and use web-based
installation
You can install Installation Manager on your
local system and use it to install the product from the web-based
repositories.
Note:
This live repository is accessed
by using Passport Advantage authentication. After you install Installation
Manager, you can set the Passport Advantage preference to connect
to the live repositories. To set Passport Advantage preferences, follow
this procedure:
- Open Installation Manager.
- Open the Passport Advantage preferences page by selecting File > Preferences > Passport Advantage.
- Select Connect to Passport Advantage to
connect to the Passport Advantage repository. The Password Required
dialog box opens.
- Enter a user name and password for Passport Advantage.
- Optional: Select Save password to
save the user name and password credentials. If you do not save the
user name and password credentials, you are prompted for these credentials
each time you access Passport Advantage.
- Click OK to close the Password Required
dialog box.
- Click OK to close the Preferences window.
For more information on setting your Installation Manager preferences,
see the
Installation Manager Information
Center.
To add the repository:
- Start Installation Manager.
- In the top menu, click File > Preferences.
- Select Repositories.
- Click Add Repository.
- Enter the path to the repository.config file in the location containing
the repository files.
- This is a sample path for a local repository:
C:\repositories\product_name\local-repositories
/var/repositories/product_name/local-repositories
- This is the path for the remote repository:
http://www.ibm.com/software/repositorymanager/V8WASNDEdge
Note:
Be aware of the following conditions:
- Click OK.
- Deselect any locations listed in the Repositories window that
you will not be using.
- Click Apply.
- Click OK.
- Click File > Exit to close Installation
Manager.
- Install the Edge Components product:
Installing Edge Components with the IBM Installation Manager GUI
Use the Installation Manager GUI to install Edge Components products.
Note:
Be aware of the following conditions when you install this
product:
- You must have Administrator or root access to install and use Load Balancer for IPv4 and Caching Proxy.
-
Do not install Caching Proxy on 64-bit operating systems.
-
Load Balancer for IPv4 is not supported on Windows 7 or Windows Vista.
- Installing IBM Installation Manager if it is not installed.
These instructions also include steps to add repository information
for the Edge Components products.
- Start Installation Manager.
- Click Install.
Note:
If you are
prompted to authenticate, use the Passport Advantage credentials that
you registered with on the program website. Installation Manager
searches its defined repositories for available packages.
- Select the product you want to install. For example, select IBM WebSphere Edge Components: Caching Proxy or IBM
WebSphere Edge Components: Load Balancer for IPv4.
If you already have the
product installed on your system, a message displays indicating that
the product is already installed.
- Click Next.
Note:
If you try to
install a newer level of the product with a previous version of Installation
Manager, Installation Manager might prompt you to update to the latest
level of Installation Manager when it connects to the repository.
Update to the newer version before you continue if you are prompted
to do so. Read the
Installation Manager
Information Center for information about automatic updates.
- Accept the terms in the license agreements, and click Next.
- Specify the installation root directory for the product binaries,
which are also referred to as the core product files or system files.
The
panel also displays the shared resources directory and disk-space
information.
Note:
The first time that you install a package
using Installation Manager, specify the shared resources directory.
The shared resources directory is where installation artifacts are
located that can be used by one or more package groups. Use your largest
drive for this installation. You cannot change the directory location
until after you uninstall all packages.
Restrictions:
- Installation manager requires that you install the product to
an empty directory. The default installation paths are:
- Caching Proxy
-
- Load Balancer for IPv4
-
- Deleting the default target location and leaving an installation-directory
field empty prevents you from continuing.
- Do not use symbolic links as the destination directory. Symbolic
links are not supported.
- Do not use a semicolon in the directory name. The product cannot
install properly if the target directory includes a semicolon.
-
A semicolon is the character used to construct the class
path on Windows systems.
-
The maximum path length on the Windows Server 2008, Windows
Vista, and Windows 7 operating systems is 60 characters.
-
Before you install Load Balancer for IPv4 on Windows 2003 64-bit machines,
you must install the required Microsoft hotfix. If you do not install
the Microsoft hotfix prior to installing Load Balancer for IPv4, Load
Balancer does not run correctly.
To correct this problem, you must
install the required Microsoft hotfix for KB942589.
After you apply the Microsoft hotfix, restart your system. You must
restart your system before you install Load Balancer for IPv4 on Windows
2003 64-bit machines. You will need to restart your system again after
completing the installation of Load Balancer for IPv4.
If you
do not install the Microsoft hotfix before you install Load Balancer
for IPv4 and you encounter this problem, you must uninstall Load Balancer
for IPv4, install the Microsoft hotfix, and then reinstall Load Balancer
for IPv4.
- Click Next.
- Select the languages for which translated content should be installed.
English is always selected.
- Click Next.
- Select the features that you want to install.
- Click Next.
- Review the summary information, and click Install.
- If the installation is successful, the program displays a message
indicating that installation is successful.
Note:
The program
might also display important post-installation instructions as well.
- If the installation is not successful, click View
Log File to troubleshoot the problem.
- Click Finish.
- Click File > Exit to close Installation
Manager.
-
Optional: If you are migrating from
a previous version of Caching Proxy, update the configuration files with the
new installation path. The default paths for Caching Proxy Version 7 and earlier
are different than the default paths for the current version.
Tip: Installation Manager optionally can
search for updates to itself whenever the Install Packages, Modify
Packages, or Update Packages page is opened from the Start page as
well as when clicking Check for Other Versions and
Extensions on the Install Packages page. To enable this option,
perform the following actions:
- Start Installation Manager.
- In the top menu, click File > Preferences.
- Select Updates.
- Select Search for Installation Manager updates.
- Click Apply.
- Click OK.
Do not enable this option if you do not have access to the service
repository.
Installing Edge Components silently with IBM Installation Manager
Note:
Be aware of the following conditions when you install
this product:
- You must have Administrator or root access to install and use Load Balancer for IPv4 and Caching Proxy.
- Do not install Caching Proxy on 64-bit operating systems.
-
Load Balancer for IPv4 is not supported on Windows 7 or Windows Vista.
- Installing IBM Installation Manager if it is not installed.
These instructions also include steps to add repository information
for the Edge Components products.
- Optional: Record a response file to install
the product. If you already have a response file, proceed directly
to Step Use the response files to install the product silently..
On one of your systems, perform
the following actions to record a response file that will install
the product:
- From a command line, change to the eclipse subdirectory in the
directory where you installed Installation Manager.
- Start Installation Manager from the command line using the -record
option. For example:
-
Administrator or non-administrator:
IBMIM.exe -skipInstall "C:\temp\imRegistry"
-record C:\temp\install_response_file.xml
-
Administrator:
./IBMIM -skipInstall /var/temp/imRegistry
-record /var/temp/install_response_file.xml
-
Non-administrator:
./IBMIM -skipInstall user_home/var/temp/imRegistry
-record user_home/var/temp/install_response_file.xml
Tip: When you record a new response
file, you can specify the -skipInstall parameter. Using this parameter
has the following benefits:
- No files are actually installed, and this speeds up the recording.
- If you use a temporary data location with the -skipInstall parameter,
Installation Manager writes the installation registry to the specified
data location while recording. When you start Installation Manager
again without the -skipInstall parameter, you then can use your response
file to install against the real installation registry.
- The -skipInstall operation should not be used on the actual agent
data location used by Installation Manager. This is unsupported. Use
a clean writable location, and re-use that location for future recording
sessions
For more information, read the Installation
Manager Information Center.
- Ensure that you added the repository information for your product
in Step 1.
- Click Install.
Note:
If you are
prompted to authenticate, use the Passport Advantage credentials that
you registered with on the program website. Installation Manager
searches its defined repositories for available packages.
Installation Manager searches its defined repositories for
available packages.
- Select your product and the appropriate version. For example,
select IBM WebSphere Edge Components: Caching Proxy or IBM WebSphere Edge Components: Load Balancer for IPv4.
If you
already have the product installed on a WebSphere Application Server
installation on your system, a message displays indicating that the
product is already installed. To create another installation of the
product in another location, click Continue.
- Click Next.
- Accept the terms in the license agreements, and click Next.
- Specify the installation root directory for the product binaries,
which are also referred to as the core product files or system files.
The
panel also displays the shared resources directory and disk-space
information.
Note:
The first time that you install a package
using Installation Manager, specify the shared resources directory.
The shared resources directory is where installation artifacts are
located that can be used by one or more package groups. Use your largest
drive for this installation. You cannot change the directory location
until after you uninstall all packages.
Restrictions:
- Installation manager requires that you install the product to
an empty directory. The default installation paths are:
- Caching Proxy
-
- Load Balancer for IPv4
-
- Deleting the default target location and leaving an installation-directory
field empty prevents you from continuing.
- Do not use symbolic links as the destination directory. Symbolic
links are not supported.
- Do not use a semicolon in the directory name. The product cannot
install properly if the target directory includes a semicolon.
-
A semicolon is the character used to construct the class
path on Windows systems.
-
The maximum path length on the Windows Server 2008, Windows
Vista, and Windows 7 operating systems is 60 characters.
-
Before you install Load Balancer for IPv4 on Windows 2003 64-bit machines,
you must install the required Microsoft hotfix. If you do not install
the Microsoft hotfix prior to installing Load Balancer for IPv4, Load
Balancer does not run correctly.
To correct this problem, you must
install the required Microsoft hotfix for KB942589.
After you apply the Microsoft hotfix, restart your system. You must
restart your system before you install Load Balancer for IPv4 on Windows
2003 64-bit machines. You will need to restart your system again after
completing the installation of Load Balancer for IPv4.
If you
do not install the Microsoft hotfix before you install Load Balancer
for IPv4 and you encounter this problem, you must uninstall Load Balancer
for IPv4, install the Microsoft hotfix, and then reinstall Load Balancer
for IPv4.
- Click Next.
- Select the languages for which translated content should be installed.
English is always selected.
- Click Next.
- Select the features that you want to install.
- Click Next.
- Review the summary information, and click Install.
- If the installation is successful, the program displays a message
indicating that installation is successful.
Note:
The program
might also display important post-installation instructions as well.
- If the installation is not successful, click View
Log File to troubleshoot the problem.
- Click Finish.
- Click File > Exit to close Installation
Manager.
- Optional: If you are using an authenticated
remote repository, create a keyring file for silent installation.
Note:
In a keyring file, you can store credentials for URLs that
require authentication, such as your remote repositories.
- From a command line, change to the eclipse subdirectory in the
directory where you installed Installation Manager.
- Start Installation Manager from the command line using the -record
option.
For example:
-
Administrator or non-administrator:
IBMIM.exe -skipInstall "C:\temp\imRegistry"
-keyring C:\IM\im.keyring
-record C:\temp\keyring_response_file.xml
-
Administrator:
./IBMIM -skipInstall /var/temp/imRegistry
-keyring /var/IM/im.keyring
-record /var/temp/keyring_response_file.xml
-
Non-administrator:
./IBMIM -skipInstall user_home/var/temp/imRegistry
-keyring user_home/var/IM/im.keyring
-record user_home/var/temp/keyring_response_file.xml
- When a window opens that requests your credentials for the authenticated
remote repository, enter the correct credentials and save them.
- Click File > Exit to close Installation
Manager.
For more information, read the Installation
Manager Information Center.
- Use
the response files to install the product silently.
- Optional: Use the response file to install
the keyring file silently: Go to a command line on each of the systems
on which you want to install the product, change to the eclipse/tools
subdirectory in the directory where you installed Installation Manager,
and install the keyring file silently.
For example:
-
Administrator or non-administrator:
imcl.exe -acceptLicense
input C:\temp\keyring_response_file.xml
-log C:\temp\keyring_log.xml
-
Administrator:
./imcl -acceptLicense
input /var/temp/keyring_response_file.xml
-log /var/temp/keyring_log.xml
-
Non-administrator:
./imcl -acceptLicense
input user_home/var/temp/keyring_response_file.xml
-log user_home/var/temp/keyring_log.xml
For more information on keyring files, read the Installation Manager Information Center.
- Use the response file to install the product silently. Go to a
command line on each of the systems on which you want to install the
product, change to the eclipse/tools subdirectory in the directory
where you installed Installation Manager, and install the product
silently.
For example:
-
Administrator or non-administrator:
imcl.exe -acceptLicense
input C:\temp\install_response_file.xml
-log C:\temp\install_log.xml
-keyring C:\IM\im.keyring
-
Administrator:
./imcl -acceptLicense
input /var/temp/install_response_file.xml
-log /var/temp/install_log.xml
-keyring /var/IM/im.keyring
-
Non-administrator:
./imcl -acceptLicense
input user_home/var/temp/install_response_file.xml
-log user_home/var/temp/install_log.xml
-keyring user_home/var/IM/im.keyring
Notes:
- The relevant terms and conditions, notices, and other information
are provided in the license-agreement files in the lafiles or product_name/lafiles subdirectory of the installation
image or repository for this product.
- The program might write important post-installation instructions
to standard output.
-
Optional: If you are migrating from
a previous version of Caching Proxy, update the configuration files with the
new installation path. The default paths for Caching Proxy Version 7 and earlier
are different than the default paths for the current version.
Example: The following is a sample
response file for installing Load Balancer for IPv4:
<?xml version="1.0" encoding="UTF-8"?>
<agent-input acceptLicense='true'>
<server>
<repository location='C:\repositories\edge80\local-repositories'/>
</server>
<profile id='Load Balancer for IPV4 v8.0'
installLocation='c:\program files\loadbalancer\ibm\edge\lb'>
<data key='eclipseLocation' value=c:\program files\loadbalancer\ibm\edge\lb'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='cs,ja,es,zh_HK,en,zh_TW,pt_BR,it'/>
</profile>
<install modify='false'>
<offering id='com.ibm.websphere.EDGELBIPV4.v80' version='8.0.0.0'
profile='IBM WebSphere Edge Components: Load Balancer for IPV4 V8.0'
features='Dispatcher,Load Balancer,Metric Server'/>
</install>
<preference name='com.ibm.cic.common.core.preferences.eclipseCache'
value='C:\Program Files\IBM\IMShared'/>
<preference value='30' name='com.ibm.cic.common.core.preferences.connectTimeout'/>
<preference value='30' name='com.ibm.cic.common.core.preferences.readTimeout'/>
<preference value='0' name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount'/>
<preference value='false' name='offering.service.repositories.areUsed'/>
<preference value='false' name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode'/>
<preference value='false'
name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication'/>
<preference value='true'
name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'/>
<preference value='false' name='PassportAdvantageIsEnabled'/>
<preference value='false'
name='com.ibm.cic.common.core.preferences.searchForUpdates'/>
</agent-input>
Tips:
- To disable remote searches for updates in the response file, set
the following preferences to false:
- offering.service.repositories.areUsed
- Used for searching remote repositories for updates to installed
offerings.
- com.ibm.cic.common.core.preferences.searchForUpdates
- Used for searching for updates to Installation Manager.
For example:
<preference value='false' name='offering.service.repositories.areUsed'/>
<preference value='false' name='com.ibm.cic.common.core.preferences.searchForUpdates'/>
- Installation Manager can save earlier versions of a package to
roll back to if you experience issues later. When Installation Manager
rolls back a package to a previous version, the current version of
the files are uninstalled and the earlier versions are reinstalled.
If
you choose not to save the files for rollback, you can prevent the
files from being saved by changing the following preference in your
response file:
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'
value='true'/>
to this:
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'
value='false'/>