Installing Edge Components silently with IBM Installation Manager
- 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.
- 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
-
-
/opt/ibm/edge/
This cannot be modified. -
C:\Program Files\IBM\edge\cachingproxy\
-
- Load Balancer for IPv4
-
-
/opt/ibm/edge/lb/
This cannot be modified. -
C:\Program Files\loadbalancer\IBM\edge\lb\
The beginning of this installation path can be changed, but be aware that Installation Manager requires you to install the product into an empty directory - in the default path it is C:\Program Files\loadbalancer. The IBM\edge\lb portion of the path is hard coded and cannot be modified.
-
- 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.
- Installation manager requires that you install the product to
an empty directory. The default installation paths are:
- 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.
- If the installation is successful, the program displays a message
indicating that installation is successful.
- 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: 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.
-
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.
<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'/>