Uninstall IBM HTTP Server silently
We can use Installation Manager to uninstall IBM® HTTP Server silently.
Before you begin
Optional: Complete or record the installation of Installation Manager and installation of IBM HTTP Server to a temporary installation registry on one of your systems so that we can use this temporary registry to record the uninstallation without using the standard registry where Installation Manager is installed.Read the following for more information:
Procedure
-
Record a response file to uninstall IBM HTTP Server:
On one of your systems, complete the following actions to record a response file that will
uninstall IBM HTTP Server:
- 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\uninstall_response_file.xml
- Administrator:
./IBMIM -skipInstall /var/temp/imRegistry -record /var/temp/uninstall_response_file.xml
- Non-administrator:
./IBMIM -skipInstall user_home/var/temp/imRegistry -record user_home/var/temp/uninstall_response_file.xml
Tip: If you choose to use the -skipInstall parameter with a temporary installation registry created as described in the Before you begin section. Installation Manager uses the temporary installation registry while recording the response file. It is important to note that when the -skipInstall parameter is specified, no packages are installed or uninstalled. All of the actions that you complete in Installation Manager simply update the installation data that is stored in the specified temporary registry. After the response file is generated, it can be used to uninstall IBM HTTP Server, removing IBM HTTP Server files and updating the standard 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 IBM Installation Manager documentation.
-
Administrator or
non-administrator:
- Click Uninstall.
-
In the Uninstall Packages window, complete the following actions.
- Select IBM HTTP Server for WebSphere Application Server and the appropriate version. Note: If you are uninstalling the trial version of this product, select IBM HTTP Server Trial and the appropriate version.
- Select IBM SDK Java Technology Edition.Avoid trouble: IBM SDK, Java™ Technology Edition must be uninstalled at the same time that you uninstall the IBM HTTP Server offering.
- Click Next.
- Review the summary information.
-
Click Uninstall.
- If the uninstallation is successful, the program displays a message that indicates success.
- If the uninstallation is not successful, click View log to troubleshoot the problem.
- Click Finish.
- Click File > Exit to close Installation Manager.
-
Use the response file to uninstall IBM HTTP Server
silently: From a command line on each of the systems from which you want to uninstall IBM HTTP Server, change to the eclipse/tools
subdirectory in the directory where you installed Installation Manager and use the response file
created to silently uninstall IBM HTTP Server.
For example:
- Administrator or
non-administrator:
imcl.exe -input C:\temp\uninstall_response_file.xml -log C:\temp\uninstall_log.xml
- Administrator:
./imcl -input /var/temp/uninstall_response_file.xml -log /var/temp/uninstall_log.xml
- Non-administrator:
./imcl -input user_home/var/temp/uninstall_response_file.xml -log user_home/var/temp/uninstall_log.xml
Go to the IBM Installation Manager documentation.
- Administrator or
non-administrator:
Example
The following is an example of a response file for silently uninstalling IBM HTTP Server and IBM SDK, Java Technology Edition, Version 8.Important: Because IBM SDK Java Technology Edition is a separate offering that must be
uninstalled when you uninstall IBM HTTP Server, your response
file must contain two <offering> elements: one for the IBM HTTP Server, and one for the Java
SDK.
<?xml version="1.0" encoding="UTF-8"?>
<!-- ##### Copyright ######################################################
# Licensed Materials - Property of IBM (c) Copyright IBM Corp. 2011.
# All Rights Reserved. US Government Users Restricted Rights-Use, duplication
# or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
####################################################################### -->
<!-- ##### Frequently Asked Questions #####################################
# The latest information about using Installation Manager is
# located in the online Information Center. There we can find
# information about the commands and attributes used in
# silent installation response files.
#
# Installation Manager Information Center can be found at:
# http://www.ibm.com/support/knowledgecenter/SSDV2W/im_family_welcome.html
#
# Question 1. How do I record a response file using Installation Manager?
# Answer 1. Start Installation Manager from the command line under the
# eclipse subdirectory with the record parameter and it will generate a
# response file containing actions it performed, repositories it used, and
# its preferences settings. Optionally use the -skipInstall parameter if
# you do not want the product to be installed to the machine. Specify a
# new agentDataLocation location value when doing a new installation. Do
# not use an existing agentDataLocation for an installation because it might
# damage the installation data and prevent you from modifying, updating,
# rolling back, or uninstalling the installed packages.
#
# Windows: IBMIM -record <responseFile> -skipInstall <agentDataLocation>
# Linux or UNIX: ./IBMIM -record <responseFile> -skipInstall <agentDataLocation>
#
# For example:
# Windows = IBMIM.exe -record c:\temp\responsefiles\WASv9.install.Win32.xml
# -skipInstall c:\temp\skipInstall\WebSphere_Temp_Registry
# Linux or UNIX = ./IBMIM -record /home/user/responsefiles/WASv9.install.RHEL64.xml
# -skipInstall c:\temp\skipInstall\WebSphere_Temp_Registry
#
# Question 2. How do I run Installation Manager silently using response file?
# Answer 2. Create a silent installation response file and run the following command
# from the eclipse\tools subdirectory in the directory where you installed
# Installation Manager:
#
# Windows = imcl.exe -acceptLicense -showProgress
# input <response_file_path_and_name> -log <log_file_path_and_name>
# Linux, UNIX, IBM i and z/OS = ./imcl -acceptLicense -showProgress
# input <response_file_path_and_name> -log <log_file_path_and_name>
#
# For example:
# Windows = imcl.exe -acceptLicense -showProgress
# input c:\temp\responsefile\WASv9.install.Win32.xml
# Linux, UNIX, IBM i and z/OS = ./imcl -acceptLicense -showProgress
# input /home/user/responsefile/WASv9.install.RHEL64.xml
#
# The -acceptLicense command must be included to indicate acceptance of all
# license agreements of all offerings being installed, updated or modified.
# The -showProgress command shows progress when running in silent mode.
# Additional commands can be displayed by requesting help: IBMIM -help
#
####################################################################### -->
<!-- ##### Agent Input #############################################
# The clean and temporary attributes specify the repositories and other
# preferences Installation Manager uses and whether those settings
# should persist after the uninstall finishes.
#
# Valid values for clean:
# true = only use the repositories and other preferences that are
# specified in the response file.
# false = use the repositories and other preferences that are
# specified in the response file and Installation Manager.
#
# Valid values for temporary:
# true = repositories and other preferences specified in the
# response file do not persist in Installation Manager.
# false = repositories and other preferences specified in the
# response file persist in Installation Manager.
#
####################################################################### -->
<agent-input clean='true' temporary='true'>
<!-- ##### Repositories ###################################################
# Repositories are locations that Installation Manager queries for
# installable packages. Repositories can be local (on the machine
# with Installation Manager) or remote (on a corporate intranet or
# hosted elsewhere on the internet).
#
# If the machine using this response file has access to the internet,
# then include the IBM WebSphere Live Update Repositories in the list
# of repository locations.
#
# If the machine using this response file cannot access the internet,
# then comment out the IBM WebSphere Live Update Repositories and
# specify the URL or UNC path to custom intranet repositories and
# directory paths to local repositories to use.
#
####################################################################### -->
<server>
<!-- ##### IBM WebSphere Live Update Repositories ####################
# These repositories contain IBM HTTP Server offerings,
# and updates for those offerings
#
# To use the secure repository (https), you must have an IBM ID,
# which can be obtained by registering at: http://www.ibm.com/account
# or your Passport Advantage account.
#
# And, you must use a key ring file with your response file.
################################################################## -->
<repository location="http://www.ibm.com/software/repositorymanager/com.ibm.websphere.IHS.v90" />
<!-- <repository location="https://www.ibm.com/software/rational/repositorymanager/repositories/websphere" /> -->
<!-- ##### Custom Repositories #######################################
# Uncomment and update the following repository location key
# to specify URLs or UNC paths to any intranet repositories
# and directory paths to local repositories to use.
################################################################## -->
<!-- <repository location='https:\\w3.mycompany.com\repositories\'/> -->
<!-- <repository location='/home/user/repositories/websphere/'/> -->
<!-- ##### Local Repositories ########################################
# Uncomment and update the following line when using a local
# repository located on your own machine to install a
# IBM HTTP Server offering.
############################################################# -->
<!-- <repository location='insert the full directory path inside single quotes'/> -->
</server>
<!-- ##### Uninstall Packages ############################################
#
# Uninstall Command
#
# Use the uninstall command to inform Installation Manager of the
# installation packages to uninstall.
#
# The modify attribute is optional and can be paired with an install
# command to add features or paired with an uninstall command to
# remove commands. If omitted, the default value is set to false.
# false = indicates not to modify an existing install by adding
# or removing features.
# true = indicates to modify an existing install by adding or
# removing features.
#
# The offering ID attribute is required because it specifies the
# offering to be uninstalled. The example command in the following section contains the
# offering ID for IBM HTTP Server.
#
# The version attribute is optional. If a version number is provided,
# then the offering will be uninstalled at the version level specified
# If the version attribute is not provided, then the default behavior is
# to uninstall the latest version. The version number can be found in
# the repository.xml file in the repositories.
# For example, <offering ... version='9.0.0.20160617_2222'>.
#
# The profile attribute is required and must match the package group
# name for the offering to be uninstalled.
#
# The features attribute is optional. If there is no feature attribute,
# then all features are uninstalled. If features are specified, then
# only those features will be uninstalled.
# Features must be comma delimited without spaces.
#
# Installation Manager supports uninstalling multiple offerings at once.
# Additional offerings can be included in the uninstall command,
# with each offering requiring its own offering ID, version, profile value,
# and feature values.
#
# Profile Command
#
# A separate profile command must be included for each offering listed
# in the install command. The profile command informs Installation
# Manager about offering specific properties or configuration values.
#
# The installLocation specifies where the offering will be installed.
# If the response file is used to modify or update an existing
# installation, then ensure the installLocation points to the
# location where the offering was installed previously.
#
# The eclipseLocation data key should use the same directory path to
# IBM HTTP Server as the installationLocation attribute.
#
# Include data keys for product specific profile properties.
#
####################################################################### -->
<uninstall modify='false'>
<offering id='com.ibm.websphere.IHS.v90'
profile='IBM HTTP Server V9.0'
features='core.feature'/>
<offering id='com.ibm.java.jdk.v8'
profile='IBM HTTP Server V9.0'
features='com.ibm.sdk.8'/>
</uninstall>
<profile id='IBM HTTP Server V9.0'
installLocation='C:\Program Files\IBM\HTTPServer'>
<data key='eclipseLocation' value='C:\Program Files\IBM\HTTPServer'/>
<data key='user.import.profile' value='false'/>
<data key='user.ihs.http.server.service.name' value='none'/>
<data key='user.ihs.httpPort' value='80'/>
<data key='user.ihs.installHttpService' value='false'/>
<data key='user.ihs.http.admin.service.name' value='none'/>
<data key='user.ihs.runSetupAdmin' value='false'/>
<data key='user.ihs.createAdminAuth' value='false'/>
<data key='user.ihs.installAdminService' value='false'/>
<data key='user.ihs.win.adminServiceLogOnAsLocalSystem' value='false'/>
<data key='user.ihs.createAdminUserGroup' value='false'/>
<data key='user.ihs.adminPort' value=''/>
<data key='cic.selector.nl' value='en'/>
</profile>
<!-- ##### Shared Data Location ###########################################
# Uncomment the preference for eclipseCache to set the shared data
# location the first time you use Installation Manager to do an
# installation.
#
# Eclipse cache location can be obtained from the installed.xml file found in
# Linux/Unix: /var/ibm/InstallationManager
# Windows: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager
# from the following property:
# <property name='cacheLocation' value='C:\Program Files\IBM\IMShared'/>
#
# Open the installed.xml file in a text editor because the style sheet
# might hide this value if opened in a web browser.
#
# After the shared data location is set, it cannot be changed
# using a response file or the graphical wizard.
#
# Ensure that the shared data location is a location that can be written
# to by all user accounts that are expected to use Installation Manager.
#
# By default, Installation Manager saves downloaded artifacts to
# the shared data location. This serves two purposes.
#
# First, if the same product is installed a more than once to the machine,
# then the files in the shared data location will be used rather than
# downloading them again.
#
# Second, during the rollback process, the saved artifacts are used.
# Otherwise, if the artifacts are not saved or are removed, then
# Installation Manager must have to access the repositories used to
# install the previous versions.
#
# Valid values for preserveDownloadedArtifacts:
# true = store downloaded artifacts in the shared data location
# false = remove downloaded artifacts from the shared data location
#
####################################################################### -->
<!--
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='C:\Program Files\IBM\IMShared'/>
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/>
-->
<!-- ##### Preferences Settings ###########################################
# Additional preferences for Installation Manager can be specified.
# These preference correspond to those that are located in the graphical
# interface under File / Preferences.
#
# If a preference command is omitted from or commented out of the response
# file, then Installation Manager uses the preference value that was
# previously set or the default value for the preference.
#
# Preference settings might be added or deprecated in new versions of
# Installation Manager. Consult the online Installation Manager
# documentation for the latest set of preferences and
# descriptions about how to use them.
#
# http://www.ibm.com/support/knowledgecenter/SSDV2W/im_family_welcome.html
#
####################################################################### -->
<!--
<preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.readTimeout' value='45'/>
<preference name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount' value='0'/>
<preference name='offering.service.repositories.areUsed' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication' value='false'/>
<preference name='http.ntlm.auth.kind' value='NTLM'/>
<preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles' value='false'/>
<preference name='PassportAdvantageIsEnabled' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/>
<preference name='com.ibm.cic.agent.ui.displayInternalVersion' value='false'/>
-->
</agent-input>
Related tasks