WSTE 10272011 BestPracticesInstallingWASV7FeaturePacks

®
IBM Software Group
Best Practices for Installing WebSphere

Application Server V7 Feature Packs
Joseph Mertzlufft (mertzluf@us.ibm.com)
Vishavpal Shergill (vishavs@us.ibm.com)
WebSphere Application Server L2 Support
27 October 2011
WebSphere® Support Technical Exchange

IBM Software Group
Agenda
 Introduction
 Repositories
 Import
 Graphical Interface
 Silent Install
 Important Directories
 Best Practices
WebSphere® Support Technical Exchange 2 of 58

IBM Software Group
INTRODUCTION

IBM Software Group
Introduction to Installation Manager

 IBM® Installation Manager (IM) is an application that
simplifies downloading, installing, updating, and
uninstalling many IBM software products from a single
user interface
 Starting with WebSphere Application Server v7.0,

Feature Pack install and update is performed using
Installation Manager
 V7.0 Application Server and JavaTM SDK updates
continue to be performed with Update Installer

IBM Software Group
ISMP vs. Installation Manager

 ISMP – former installation technology
 Install, Uninstall and Update processes required different programs
 Each Feature Pack required separate install program
 Fix pack in .pak format
 Obtaining Feature Pack or fix pack downloads is separate process
 IBM Installation Manager (IM)

 Single interface to install, update, uninstall many IBM software products
 Use local or Web repositories
 Ability to download packages integrated into IM
 Single IM instance can manage multiple products
 Replaces dedicated installers and uninstallers and maintenance tools
 Simplifies product maintenance

IBM Software Group
REPOSITORIES

IBM Software Group
Repositories

Repositories are locations that Installation Manager queries for
installable packages

Web Repositories – Internet access required
 Feature Pack
https://www.ibm.com/software/rational/repositorymanager/repositories/websphere
 Fix pack for Feature Packs
http://public.dhe.ibm.com/software/websphere/repositories
 Note that those URLs are input into IM, not your web browser
 Local Repositories – download from IBM.com and store locally
 Download from Support Site as .zip format
Feature Fix Pack

Pack

IBM Software Group
IMPORT

IBM Software Group
Import
 Must use Import feature for Installation Manager to

recognize WebSphere Application Server V7.0
 Must do this before installing a feature pack for the first time
 The Import button is only visible after a WebSphere

repository has been added to the repository list
 Application Server fix pack and Java SDK fix pack
level must match before performing Import
 Example: Application Server has been updated with Fix Pack 17
(V7.0.0.17), so Java SDK must also be updated with Fix Pack 17.

IBM Software Group
NOTE: You can only select the shared resources directory the first time you install a
package with the IBM Installation Manager. All other installations of WSAS 7.0.0.X on
the same system will use the same Shared Resources directory.

IBM Software Group
GRAPHICAL INTERFACE:
INSTALL, UPDATE,
UNINSTALL, and ROLLBACK

IBM Software Group
Installation Manager graphical options

IBM Software Group

IBM Software Group
Install
With Web
With Local
Repositories
Repositories
If checked will list all available offerings

IBM Software Group
Update
With Web With Local
Repositories Repositories
Select recommended is checked in both cases above.

IBM Software Group
Rollback
Example: XML 1.0.0.5 is installed and Rollback
option is chosen.
Install Sequence was:

XML 1.0.0.0  XML 1.0.0.3  XML 1.0.0.5
Will Roll back to 1.0.0.3

(last installed)

(GA version)

IBM Software Group
Uninstall
Example: XML 1.0.0.5 was previously installed. Choosing Uninstall option
and selecting XML 1.0.0.5 option will uninstall entire Feature Pack.
If checked will uninstall Application Server
Will uninstall complete Feature Pack

IBM Software Group
PERFORMING SILENT
OPERATIONS

IBM Software Group
Silent Install
 Silent install is performed using a response file
 Sample response file from Information Center are available
 Response file can also be recorded
 Response file is xml format
 Same command (such as “imcl”) is used for installing,
uninstalling, updating, or rolling back
 Only need to change options in the response file in order to perform
different operations
 A single response file can perform multiple operations; i.e.,

Import WSAS, install two feature packs, install fix packs on
feature packs – all in a single session

IBM Software Group
Silent Install
 Sample command (v1.4.4) from
INSTALL_LOCATION\eclipse\tools
 UNIX®:
./imcl -input /temp/install.xml -acceptLicense -showProgress
 WINDOWS®:
imcl -input C:\install.xml -acceptLicense -showProgress
 imcl -help will list options available with imcl command

 An “interactive console mode” is available in Installation
Manager; however, it is not supported WSAS V7 Feature
Packs
Learn to use response files with WSAS V7 Feature Packs

IBM Software Group
Recording mode and skipInstall mode

 Recording mode allows you to generate a response file by
recording the actions taking place in the graphical interface
 skipInstall mode allows IM to operate in a mode where it does

not actually install, update, or uninstall packages
 This mode maintains a dummy set of IM data (known as “agent data”)
which persists – you can use the dummy data again later
 Does require an actual WSAS V7.0 install to be present, but Feature
Packs are not actually installed or uninstalled
 Both modes can be combined

 Example command-line (Windows):
IBMIM.exe -skipInstall C:\dummyIMdata -record C:\project\installXML.xml

IBM Software Group
Recording a response file

 IM graphical interface will indicate that it is recording response file
Installation Manager In
Record Mode
 Don’t specify IM's true agent data directory with skipInstall –

recommend using a dummy repository instead
 Once response file is recorded, you can use it on another system
 Be sure to edit the response file so paths match those on the system
where the install is taking place
 Keep the same dummy agent data directory to allow you to record
response files for future updates, installs, or uninstalls for the same
environment when using -skipInstall
 Sample response file on next page

IBM Software Group
Application Server Details
IMPORT
Repository Details
Shared Resource
Directory
Install Options

IBM Software Group
<agent-input> section

Purpose: Set global options for this IM session

Example: Recommended for most circumstances
 <agent-input clean=‘true’ temporary=‘true’>

clean – determines whether other preferences in response file are used
 true – only use the repositories and other preferences specified in this response file
false – use the repositories and other preferences that are specified in this response file
and Installation Manager's preferences
 temporary – determines if settings are saved to persistent preferences
 true – repositories and other preferences specified in the response file do not persist in
false – repositories and other preferences specified in the response file persist in
 Versions prior to IM 1.4.3 also used a required option named

acceptLicense='true'. This option is deprecated as of IM 1.4.3 and higher.
 Use command-line option “-acceptLicense” instead

IBM Software Group
<server> section
 Purpose: Provide locations for respositories
 Example: Local repositories for XML feature pack
 <server>
<repository location='C:\IMAIX\xml_and_import_repositories\local-repositories'/>
<repository location='C:\IMAIX\xml.1.0.0.1.fp\xml.1.0.0.1.fp'/>
<repository location='C:\IMAIX\was.7.0.import'/>
</server>
 When using same response file on different system,

ensure the repository location specified in response file is
correct

IBM Software Group
<profile> section
 Purpose: Provide details about product to be modified
 Example: Application server product installed on Linux®
 <profile installLocation='/home/user/IBM/WebSphere/AppServer' id='IBM WebSphere
Application Server - ND'>
<data key='eclipseLocation' value='/home/user/IBM/WebSphere/AppServer'/>
<data key='user.import.profile' value='true'/>
<data key='user.cic.imported,com.ibm.websphere.ND.v70' value='WAS'/>
</profile>
 InstallationLocation – specifies the directory path to an existing installation of
WebSphere Application Server V7.0.
 Id – package group name assigned to the imported installation of WebSphere Application

Server. If the product is already imported, then use the same name that has been used
previously.
 The installed.xml file under the agent data directory tracks which profile ID names
are in use. Consult that file to determine which name is associated with an already-
imported product. (More details about the agent data later.)

IBM Software Group
Data keys in <profile> section

 Example: Application server product installed on Linux
</profile>
 eclipseLocation – must set this to same value used for installLocation
 user.import.profile – set to 'true' to perform Import of WebSphere product

 It is okay to set this to 'true' even if product has already been imported.
 user.cic.imported – Set value to the offering ID key that matches the product edition:
 com.ibm.websphere.EXPRESS.v70
com.ibm.websphere.EXPRESSTRIAL.v70
com.ibm.websphere.BASE.v70
com.ibm.websphere.BASETRIAL.v70
com.ibm.websphere.ND.v70

IBM Software Group
<import> section
 Purpose: Provide additional information for import process
 Example: Importing a Network Deployment installation
 <import profile='IBM WebSphere Application Server - ND' type='WAS'/>
 This data is required if performing an import, and has no effect (can be omitted) if not
performing an import
 profile – specifies the name of the package group you will associate with this product
installation. Must set this to the same value used in the <profile> section. If the product
has already been imported before, then this value must match the value used previously.
(More details about this later – this value can be retrieved from 'installed.xml'.)
 type – always set to 'WAS'.

IBM Software Group
<install> section
 Purpose: Declare which packages to install or update
 Example: Install or update XML to V1.0.0.5
 <install modify='false'>
<offering id='com.ibm.websphere.XML.v10' version='1.0.5.20100406_1332'
profile='IBM WebSphere Application Server - ND' features='fep.xml.core.feature' />
</install>
 modify option – determines whether you are adding a sub-feature to an already-installed

product; e.g., adding the “SDO” feature to an already-installed SCA feature pack. Note
that feature packs themselves (CEA, SCA, XML, etc.) are not sub-features. Most of the
time, you will use modify='false'.
 offering section – each offering section instructs IM to install a package. The “offerings”
determine which repositories (or parts of repositories) are installed. You can use these to
install a new feature pack or upgrade an existing feature pack with a fix pack.
 Multiple offerings can be listed in an <install> section in order to install or update
multiple feature packs in a single IM session.

IBM Software Group
<offering> section in <install>

 Purpose: Declare a single package to install
</install>
 id – required parameter – specifies the name of a package to be installed. The package

needs to be part of at least one of the repositories declared in the <server> section. (How
to determine the “id” of a package is explained later.)
 version – optional parameter – determines which version of the package is installed. If

you have several repositories that all use the same ID (such as the XML Feature Pack
offering, XML Fix Pack 3, XML Fix Pack 5, and XML Fix Pack 7), then specifying the
version determines which of the packages get installed.
 If this parameter is omitted, then the newest (highest) version package (available
from the repository list) is installed.

IBM Software Group

profile='IBM WebSphere Application Server - ND' features='fep.xml.core.feature'/>
</install>
 features – optional parameter – specifies the name of a feature to be installed from the
offering. All feature pack offerings have at least one feature (the “core” feature), and
some have additional features (such as the SDO feature in the SCA feature pack).
 If you specify this option, be sure to at least specify the “core” feature. If you omit
this option, all features are installed.
 profile – required parameter – specifies the profile ID of a product to be updated. This

must match the profile ID specified in the <profile> section.

IBM Software Group
<preferences> - Shared resources location

 Purpose: Sets the location of shared resources directory
 Example: Setting shared resources directory on Windows
 <preference value='C:\IBM\WebSphere\AppServer-Shared'
name='com.ibm.cic.common.core.preferences.eclipseCache'/>
 name – there are many <preferences>. The name of this particular setting is
“com.ibm.cic.common.core.preferences.eclipseCache”. You must use that value when
setting the shared resources directory.
 value – specify the full path of the shared resources directory here
 Same rules apply for shared directory as discussed earlier – shared directory can
only be set for IM the first time a product is imported, and must be the same for all
products afterward.
 All other <preference> values should remain at the default values recorded in response
file or copied from sample response file, unless there is a specific need to change an
option

IBM Software Group
Finding data for response file

 To verify which profile ID was used for a previous import, consult
the installed.xml in the agent data directory – open in browser
 A feature pack's Offering ID and fix pack version number are

listed in repository.xml in a feature pack's main or
“local-repositories” directory

IBM Software Group
Sample: Updating XML to 1.0.0.5


In this example, we have obtained the XML Feature Pack repository, the WAS
Import Repository, and XML Fix Pack 5 repository

This will either install a fresh copy of XML Feature Pack and update it to V1.0.0.5,
or it will update an existing XML Feature Pack to Fix Pack 5. It does this because
Fix Pack 5 is the highest level repository in the repository location list.

Specify necessary repositories in <server> section
<server>
<repository location='C:\IBM\silentrep\xml_and_import_repositories\local-repositories\xml'/>
<repository location='C:\IBM\silentrep\was.7.0.import'/>
<repository location='C:\IBM\silentrep\xml.1.0.0.5.fp'/>
</server>

Then, specify the feature pack to be updated in <install> section
<install modify='false'>
<offering id='com.ibm.websphere.XML.v10'
profile='IBM WebSphere Application Server - ND' />
</install>

IBM Software Group


Alternative example: We happen to have Fix Packs 3, 5, and 7, but we really want
to update XML to fix pack 5

<server>
</server>

Then, specify the feature pack to be updated in <install> section, being sure to
specify the exact version number to install 1.0.0.5
</install>

IBM Software Group
Sample: ifix install

 Updating product with interim fix generally follows the same pattern
in the <install> section
<offering id='PM12345_FEATUREPACK'
profile='IBM WebSphere Application Server - ND'/>

Generally, ID of interim fix is provided in readme file bundled with fix, or
the ID matches the name of the interim fix repository .zip file provided by
IBM

Review repository.xml associated with fix for exact details

IBM Software Group
Sample: Uninstall of XML Feature Pack part 1


In this example, assume that XML Feature Pack 1.0.0.5 is installed

Update the <profile> section with a data key to indicate that profiles should
be automatically unaugmented, removing data from a specific feature pack
<profile id='IBM WebSphere Application Server – ND'>
<data key='user.confirm.unaugment,com.ibm.websphere.XML.v10' value='true'/>

Note: If more than one feature pack is being uninstalled, then include a separate
unaugment <data> key for each feature pack. Some feature pack offering ID values are:
com.ibm.websphere.SCA.v10
com.ibm.websphere.XML.v10
com.ibm.websphere.CEA.v10
com.ibm.websphere.ARIESJPA.v10
For example:
<data key='user.confirm.unaugment,com.ibm.websphere.SCA.v10' value='true'/>

IBM Software Group


Update the <uninstall> section with the offering ID of the feature packs to be
uninstalled. The feature pack and all its fix packs will be uninstalled.
<uninstall modify='false'>
</uninstall>
 The id and profile attributes are required.
 Alternatively, specify a version and/or feature attribute to uninstall a specific

fix pack or sub-feature instead of uninstalling the entire feature pack. This
sample uninstalls Fix Pack 5:
profile='IBM WebSphere Application Server - ND'
version='1.0.5.20100406_1332'/>
</uninstall>

IBM Software Group


Another alternative: Use rollback instead of uninstall. Works similarly to
rollback described earlier.
<rollback>
profile='IBM WebSphere Application Server - ND' features=''/>
</rollback>

IBM Software Group
Important Directories

IBM Software Group
Directories (Shared Resources Directory)

 This location acts as a cache for data retrieved from local repositories or web
repositories. Improves performance on systems where frequent installs /
uninstalls take place.
 Location is selected the first time a package is installed by Install Manager, or
during Import
 Multiple products share this same directory
 Choose location with reasonable disk space free
 Deleting this directory is not recommended
 Cannot be changed or moved once selected
Sample Shared Resource directory from Windows

IBM Software Group
Directories (appDataLocation)
 appDataLocation: also called Installation Manager Agent Data Directory or
IM_DATA directory
 IBM Installation Manager uses this to track data associated with packages it has
installed on the system
 This data is very important and should be backed-up regularly along with
WebSphere products
 Location of data can be changed using -dataLocation (or -dL ), but make sure to
use -dataLocation option every time Installation Manager programs are used
 Table of default
locations for
IM_DATA:

IBM Software Group
 The default appDataLocation is set by the cic.appDataLocation
property in the config.ini file – location depends on OS
 Windows: install_dir\IBM\Installation Manager\eclipse\configuration
 Linux and UNIX: install_dir/IBM/InstallationManager/eclipse/configuration
 IBM does not recommend changing this value in config.ini file
 To determine the location of Installation Manager, check in these

locations:
 Windows Registry key: HKLM\SOFTWARE\IBM\Installation Manager\location
 Linux and UNIX:
• Open the /etc/.ibm/registry/InstallationManager.dat file
• Look at the location entry. Example: location=/var/ibm/InstallationManager

IBM Software Group
Viewing logs from


IBM Software Group
Install Manager GUI can be used to view Installed packages, Installation history
and logs.

IBM Software Group
From the Logs folder under Data directory open index.xml in a browser

IBM Software Group
Best Practices and

Common Problems

IBM Software Group
Best Practices
 Each of the following should have unique path
 Installation Manager Install Directory
 Shared Resources Directory
 Install Manager Data Directory
 IM can be installed and run as non-root user

 Highly recommended to use WSAS as non-root
 Use same user to install and update Feature Packs

 When installing multiple feature packs using silent mode,
prepare the response file using record mode

IBM Software Group
Best Practices
 Repositories can be stored on a networked resource and
accessed through a networked filesystem (or a UNC path on
Windows)
 Multiple systems can access the same collection of local repositories
simultaneously
 Augmentation
 Must augment profiles once a feature pack is installed
 Must unagument profiles if uninstalling a feature pack
 Keep copies of all local repositories

 Maintain a copy of the appDataLocation data used with
“-skipInstall”

IBM Software Group
Problem: Synchronization Error

 When trying to install XML Feature pack on WSAS 7.0.0.15
using Local Repositories, and getting the following error:
Repositories in preferences
Error
On GUI

IBM Software Group

 XML Feature Pack Repository has Sync repositories for Application Server
fix pack 7. WSAS v7.0.0.7 should synchronize fine, but if the product is
upgraded to higher fix pack (like 7.0.0.15) then latest WSAS Import
Repositories are needed for product to synchronize with IM
WSAS Sync repository with Latest WSAS Import repository

XML Feature Pack Repository
NOTE: Always keep a copy of the latest WSAS import repositories.

IBM Software Group
Problem: Java SDK fixpack version not same

as WSAS fixpack
 Application Server is at 7.0.0.19 but Java SDK is at 7.0.0.15

 Both fix packs have to be at same level for Import to succeed

IBM Software Group
Problem: What do I download to install latest

version of XML feature pack ?
 Base Code of Feature pack can be downloaded from
Support page (requires IBM web site ID)
 Will download as <featurepack_name>_and_import_repositories.zip
 For XML, xml_and_import_repositories.zip
 Example from Fixpack 1.0.0.9 download page:
XML fixpack 1.0.0.9

WSAS Import
Repository
XML Import or Mini
XML only used if XML
1.0.0.0 (GA) is installed
and is being updated to
1.0.0.9

IBM Software Group
Mustgather data required by support

 Agent data directory (IM_DATA)
 Using Graphical Installation Manager
 Using Command line navigate to eclipse/tools subdirectory in the

location where you installed Installation Manager
• Windows:
imcl.exe exportInstallData outputFileName
• Unix and Linux: ./imcl exportInstallData outputFileName

• z/OS:
./imcl exportInstallData outputFileName
 Send the zip file created to support along with files listed on next slide

IBM Software Group
 In addition to this, we need

Logs directory from Application Server
All XML files from Application Server's
properties/version/nif/backup directory
Response file used for installation
• Only needed if performing a silent install
Screenshot of error if using Graphical Interface
• If you are installing IM and the graphical interface does not
appear, or if it appears but prints errors to the console, please
copy and paste the console errors to us

IBM Software Group
Additional WebSphere Product Resources

 Learn about upcoming WebSphere Support Technical Exchange webcasts, and access
previously recorded presentations at:
http://www.ibm.com/software/websphere/support/supp_tech.html
 Discover the latest trends in WebSphere Technology and implementation, participate in

technically-focused briefings, webcasts and podcasts at:
http://www.ibm.com/developerworks/websphere/community/
 Join the Global WebSphere Community:
http://www.websphereusergroup.org
 Access key product show-me demos and tutorials by visiting IBM Education Assistant:
http://www.ibm.com/software/info/education/assistant
 View a webcast replay with step-by-step instructions for using the Service Request (SR)
tool for submitting problems electronically:
http://www.ibm.com/software/websphere/support/d2w.html
 Sign up to receive weekly technical My Notifications emails:
http://www.ibm.com/software/support/einfo.html

IBM Software Group
Connect with us!
1. Get notified on upcoming webcasts

Send an e-mail to wsehelp@us.ibm.com with subject line “wste
subscribe” to get a list of mailing lists and to subscribe
2. Tell us what you want to learn

Send us suggestions for future topics or improvements about our
webcasts to wsehelp@us.ibm.com
3. Be connected!
Connect with us on Facebook
Connect with us on Twitter

IBM Software Group
Questions and Answers

®
IBM Software Group
Best Practices for Installing WebSphere

Application Server V7 Feature Packs
Joseph Mertzlufft (mertzluf@us.ibm.com)
Vishavpal Shergill (vishavs@us.ibm.com)
WebSphere Application Server L2 Support
27 October 2011
WebSphere® Support Technical Exchange
Welcome to Best Practices for Installation of Feature Packs for WebSphere

Application Server V7.0. This presentation is brought to you by the
WebSphere Support Technical Exchange program.
This material has been prepared and presented by Joe Mertzlufft and
Visavpal Shergill of the WebSphere Application Server Level 2 support team.
1
IBM Software Group
Agenda
 Introduction
 Repositories
 Import
 Graphical Interface
 Silent Install
 Important Directories
 Best Practices
This presentation will cover the general process and outline best practices
associated with the installation and upgrade process for Feature Packs
available for WebSphere Application Server V7.0 on “distributed” operating
systems: AIX, HP-UX, Linux, Solaris, and Windows. This process uses IBM
Installation Manager, which has previously not been used with WebSphere
Application Server V7.0.
2
IBM Software Group
INTRODUCTION

IBM Software Group
Introduction to Installation Manager

 IBM® Installation Manager (IM) is an application that
simplifies downloading, installing, updating, and
uninstalling many IBM software products from a single
user interface
 Starting with WebSphere Application Server v7.0,

Feature Pack install and update is performed using
 V7.0 Application Server and JavaTM SDK updates
continue to be performed with Update Installer
Installation Manager is a single installation program that can use remote

(“web”) or local software repositories to install, modify, or update new
WebSphere Application Server (WSAS) products. Starting with WSAS
version 7.0, feature packs must be installed by Installation Manager, rather
than by programs based on InstallShield MultiPlatform (ISMP). ISMP-based
programs are used to install, update, and uninstall previous versions of
WebSphere Application Server.
Fix pack updates to Application Server and the Java SDK should continue to
be installed using the UpdateInstaller utility.
IBM Software Group
ISMP vs. Installation Manager

 ISMP – former installation technology
 Install, Uninstall and Update processes required different programs
 Each Feature Pack required separate install program
 Fix pack in .pak format
 Obtaining Feature Pack or fix pack downloads is separate process
 IBM Installation Manager (IM)

 Single interface to install, update, uninstall many IBM software products
 Use local or Web repositories
 Ability to download packages integrated into IM
 Single IM instance can manage multiple products
 Replaces dedicated installers and uninstallers and maintenance tools
 Simplifies product maintenance
Earlier installation methods (in V6.1) for installing feature packs for
WebSphere Application Server used ISMP-based tools. To install these
feature packs, you had to locate and download the feature pack installation
package and install each feature pack separately. For each feature pack, the
required prerequisite WebSphere Application Server fix pack is bundled with
the feature pack, even if the fix pack has already been applied to the existing
installation. Also, the installation utilities could only install packages which
were downloaded before the installation took place.
The feature packs in v7.0 uses the new IBM Installation Manager solution.
Installation Manager can use local or web repositories. Web repositories
allow Installation Manager to connect directly to ibm.com (or another web
server) and download necessary repositories automatically.
One Installation Manager interface can handle installation, uninstallation, and

updates for multiple products, and it can perform several operations from a
single set of input.
IBM Software Group
REPOSITORIES
Here are supplemental details for speaker notes on Slide 7.
1
4
2
To add a repository:
3 Go to File > Preferences > Repositories menu
Click the “Add Repository...” button.
For local repositories, provide the repository path up to and including the
repository.config file. For Web repositories, provide the URL.
This is equivalent to the <server> section in a response file.
IBM Software Group
Repositories

Repositories are locations that Installation Manager queries for
installable packages

Web Repositories – Internet access required
 Feature Pack
https://www.ibm.com/software/rational/repositorymanager/repositories/websphere
 Fix pack for Feature Packs
http://public.dhe.ibm.com/software/websphere/repositories
 Note that those URLs are input into IM, not your web browser
 Local Repositories – download from IBM.com and store locally
 Download from Support Site as .zip format
Feature Fix Pack

Pack
Repositories are locations that Installation Manager queries for installable

packages.
There are two types of repositories available for feature packs:
Web repositories, and Local repositories.
Web repositories are available if the system has access to internet.
Installation Manager can connect to IBM.com directly and retrieve feature
pack repositories. IM needs to be supplied with URLs to connect to, but the
IM version available on the WebSphere support site are pre-configured with
these URLs. An IBM ID is required for authentication and can be stored in
Installation manager preferences.
If direct internet access is not available, then local copies of repositories are
available to download from the ibm.com support site separately. The same
repositories can be used to install the feature pack or fix packs for all sites.
Before installing a feature pack fix pack, you need to have the feature pack's
initial repository.
Best practice: If you are using local repositories, keep a copy of each
repository that you have downloaded. IM may require data from the base
install repository and fix pack repositories for subsequent upgrades and
uninstall operations.
For details on how to add a repository to the list, refer to the speaker notes on
Slide 6.
IBM Software Group
IMPORT

IBM Software Group
Import
 Must use Import feature for Installation Manager to

recognize WebSphere Application Server V7.0
 Must do this before installing a feature pack for the first time
 The Import button is only visible after a WebSphere

repository has been added to the repository list
 Application Server fix pack and Java SDK fix pack
level must match before performing Import
 Example: Application Server has been updated with Fix Pack 17
(V7.0.0.17), so Java SDK must also be updated with Fix Pack 17.
Before you can use Installation Manager to install any packages on top of
WebSphere Application Server V7, you need to import the application server
into the Installation Manager.
Click the Import button to open the import wizard. Note that the Import button
is only visible after a WebSphere repository has been added to the repository
list. So, if you do not see the Import button on the main Installation Manager,
check your repository configuration to be sure you are pointing to a
WebSphere repository.
Note that there is an additional requirement imposed on the WSAS V7
product in order to use feature packs. The application server fix pack level
and SDK fix pack level must be the same; i.e., if you install WSAS Fix Pack
17, then you must also install SDK Fix Pack 17 before importing WSAS into
Installation Manager.
IBM Software Group
NOTE: You can only select the shared resources directory the first time you install a
package with the IBM Installation Manager. All other installations of WSAS 7.0.0.X on
the same system will use the same Shared Resources directory.
To import an application server installation, you need to provide the

installation directory for that instance of the application server. The screenshot
on the left shows how this question is presented by the Import wizard. You
can either browse to the location using a standard file selection window or
type the full path into the Installation Directory field. After providing the path,
click Next.
The next panel, shown on the right, allows you to choose the Shared
Resources directory for the Installation Manager. The Shared Resources
directory contains files that can be shared by multiple packages. You can only
select the shared resources directory the first time you install a package with
the IBM Installation Manager. This directory caches data retrieved from
repositories. It is a good practice to use the recommended shared resources
directory. Click Next to proceed through through the import wizard. We will
discuss more details for this directory later in the presentation.
IBM Software Group
GRAPHICAL INTERFACE:
INSTALL, UPDATE,
UNINSTALL, and ROLLBACK

IBM Software Group
So far, we have discussed repositories and the import function. Let's give an
overview of the other functions as they are represented on the main
Installation Manager window.
The Installation Manager includes several wizards that guide you through
installing, updating, and uninstalling products.
The Install wizard is the starting place for installing new software packages,
including the first time you install a particular Feature Pack. The Install
function will access the repositories you have configured, allow you to select
specific packages to install from a list of packages available for installation,
and step you through the installation process.
The Update wizard discovers and installs updates and fixes to your software
packages. This is the interface you use to apply software maintenance or
update your products to a newer version. This wizard displays and
recommends fixes and maintenance packages that are targeted to your
operating system and set of installed products. You can also apply refresh
packs to update your software to the latest version.
Some products have optional sub-features which you can choose not to install
when the product is initially installed. But, you can choose to install them
Later. The Modify function allows you to select sub-features to add to an
already-installed product or feature pack.
IBM Software Group
The Import wizard allows you to point to an existing product installation on

your system and link it to Installation Manager. In this presentation, we're
concentrating on the WebSphere Application Server V7 product. As
discussed earlier, before installing a feature pack, you need to import an
installation of WebSphere Application Server V7. Note that the Import button
is not present until you add a WebSphere repository to the list of available
repositories.
The Roll Back wizard allows you to move your product back to a previous
version of service – for example, moving a product from Fix Pack Y to lower
Fix Pack X. This function lets you choose which version of the product you
want to roll back to.
The Uninstall wizard allows you to remove software packages from your
system and remove links to products that you have imported. This function
uninstalls a feature pack entirely.
(Note that the Manage Licenses wizard is not used by WebSphere products at
this time.)
Import operations are only available with WebSphere Application Server V7.
Do not try to use Installation Manager to import other products, like Rational
Application Developer.
IBM Software Group
Install
With Web
With Local
Repositories
Repositories
If checked will list all available offerings
Here are some sample screenshots of what you see when using the Install
function.
When using Web Repositories, represented on the left, you will see a list of all
available Feature Packs for the product. If the “Show all versions” option is
selected, then you will also see all the possible fix pack levels. Otherwise,
only the latest version of each feature pack is displayed. Note that you can
use this function to initially install a specific version of a feature pack, instead
of installing whatever the latest version is.
When using local repositories, represented on the right, only the feature packs
and fix packs represented in IM's repository list are displayed.
IBM Software Group
Update
With Web With Local
Repositories Repositories
Select recommended is checked in both cases above.
Similarly, here are some screenshots of what you see when using the Update
function.
Use the Update option to apply fix packs to existing, already-installed Feature
packs. This option will only list available fix packs for feature packs which are
installed.
The list of fix packs available when using Web repositories is represented on
the left. All available fixpacks for that feature pack will be listed.
The list of fix packs available when using Local repositories is represented on
the right. Only fix packs represented in IM's repository list which are eligible to
be installed will be shown.
If “Show recommended Only” is selected, then only the highest available fix
pack for each feature pack is displayed.
Note that if a feature pack is not yet installed, and only feature pack fix packs
are available in the IM Repository List, then these views will show that no
updates are available. The base Code of feature pack must be installed
before a feature pack fix pack is installed. Note that when installing the base
code, you can choose to install a fix pack as part of that initial installation
process.
IBM Software Group
Rollback
Example: XML 1.0.0.5 is installed and Rollback
option is chosen.
Install Sequence was:

XML 1.0.0.0  XML 1.0.0.3  XML 1.0.0.5

(last installed)

(GA version)
Here we have an example screenshot from the Roll Back wizard.
The Roll Back wizard allows you to move your product back to a previous
version of service – for example, moving a product from Fix Pack Y to lower
Fix Pack X.
The options presented to you allow you to choose which version you want to
have when the roll back is complete. For example, consider a scenario where
you have the XML base package along with XML Fix Packs 3 and 5. The Roll
Back wizard will present you with options to roll back to either XML Fix Pack 3
or the base XML version. If you choose to roll back to XML Fix Pack 3, then
XML Fix Pack 5 is uninstalled. If you choose to roll back to XML version
1.0.0.0, then both Fix Packs 3 and 5 are uninstalled.
Note that you can only roll back to remove fix pack levels delivered by the
“Update” function. if you chose to initially install a feature pack and fix pack in
a single session without using the “Update” function, then you cannot roll back
to an earlier level. For example, if you initially installed XML at version 1.0.0.5
and you have not installed any other fix packs, then you cannot roll back to an
earlier fix pack level nor can you roll back to version 1.0.0.0.
IBM Software Group
Uninstall
Example: XML 1.0.0.5 was previously installed. Choosing Uninstall option
and selecting XML 1.0.0.5 option will uninstall entire Feature Pack.
If checked will uninstall Application Server
Will uninstall complete Feature Pack
This is an example of using the Uninstall function.
The Uninstall wizard allows you to remove software packages from your
computer and remove links to products that you have imported.
Take care when using this option. If the main WebSphere product option is
selected, such as “WebSphere Application Server – ND”, then the entire
WebSphere Application Server product will be uninstalled.
Using the Uninstall wizard, you can choose which feature packs are
uninstalled.
IMPORTANT: Once WebSphere Application Server V7.0 is Imported to IM,
you should not use the product's standard “uninstall” program located in the
WAS_HOME/uninstall directory. When you eventually decide to uninstall the
product, please use the Uninstall function here in IM in order to remove the
product from the system. If you do not do this, then IM may continue to
indicate that the product is installed even when it has been uninstalled.
IBM Software Group
PERFORMING SILENT
OPERATIONS

IBM Software Group
Silent Install
 Silent install is performed using a response file
 Sample response file from Information Center are available
 Response file can also be recorded
 Response file is xml format
 Same command (such as “imcl”) is used for installing,
uninstalling, updating, or rolling back
 Only need to change options in the response file in order to perform
different operations
 A single response file can perform multiple operations; i.e.,

Import WSAS, install two feature packs, install fix packs on
feature packs – all in a single session
If Graphical capabilities are not available on the system, then the silent mode
can be used to install and maintain feature packs.
Note that Installation Manager itself can be installed in silent mode, and then
subsequent operations (such as installing feature packs) can also be
performed in silent mode.
Silent mode uses XML-formatted response files as input. Sample response
files for various activities are available in the WSAS V7 Information Center.
Also, it is possible to record your own response file, customized to whatever
operations you want to perform.
A single Installation Manager program takes the response file as input, and
that response file drives all activity. A single response file can instruct
Installation Manager to perform multiple actions.
IBM Software Group
Silent Install
 Sample command (v1.4.4) from
INSTALL_LOCATION\eclipse\tools
 UNIX®:
./imcl -input /temp/install.xml -acceptLicense -showProgress
 WINDOWS®:
imcl -input C:\install.xml -acceptLicense -showProgress
 imcl -help will list options available with imcl command

 An “interactive console mode” is available in Installation
Manager; however, it is not supported WSAS V7 Feature
Packs
Learn to use response files with WSAS V7 Feature Packs
Example commands for invoking Installation Manager to use a response file

are listed on this slide.
The “-input” parameter indicates which response file should be used. The
“-acceptLicense” parameter indicates that you accept the license agreements
associated with the products being installed, and is a required parameter for
Installation Manager to proceed.
The “-showProgress” parameter gives a progress indicator on the console to
show operations in progress. This is an optional parameter.
Note that newer version of Installation Manager, introduced after Feature
Packs came to WSAS V7.0, have features that can be used as an alternative
to silent mode. However, those features are only available to new IBM
products, and not to WSAS V7.0 feature packs. So, please familiarize
yourself with silent mode for use with WSAS V7 Feature Packs.
IBM Software Group
Recording mode and skipInstall mode

 Recording mode allows you to generate a response file by
recording the actions taking place in the graphical interface
 skipInstall mode allows IM to operate in a mode where it does

not actually install, update, or uninstall packages
 This mode maintains a dummy set of IM data (known as “agent data”)
which persists – you can use the dummy data again later
 Does require an actual WSAS V7.0 install to be present, but Feature
Packs are not actually installed or uninstalled
 Both modes can be combined

 Example command-line (Windows):
IBMIM.exe -skipInstall C:\dummyIMdata -record C:\project\installXML.xml
IM has two modes which are useful for preparing silent mode response files:
Recording Mode and skipInstall Mode.
Recording mode runs IM in graphical mode, and it records the actions that
take place during that session. These actions are saved to a response file.
We very strongly recommend using record mode to learn how response files
are generated. It is much easier to learn how to do something in graphical
mode then see the equivalent commands generated to a response file.
skipInstall mode is a useful companion to recording mode. The skipInstall
mode causes IM to perform a “dry run” of all actions. No software is installed,
unintalled, or modified in skipInstall mode. Also, skipInstall mode maintains a
dummy set of “agent data” -- it is able to keep track of a fake set of software,
which allows you to emulate complex installations without actually installing
any software at all. (Note that you do need to install WebSphere Application
Server V7 in order to use skipInstall mode, however you do not need to install
actual feature packs.)
You can combine both record mode and skipInstall mode in order to generate
response files without having to devote time or filesystem space normally
required for installing products.
IBM Software Group
Recording a response file

 IM graphical interface will indicate that it is recording response file
Installation Manager In
Record Mode
 Don’t specify IM's true agent data directory with skipInstall –

recommend using a dummy repository instead
 Once response file is recorded, you can use it on another system
 Be sure to edit the response file so paths match those on the system
where the install is taking place
 Keep the same dummy agent data directory to allow you to record
response files for future updates, installs, or uninstalls for the same
environment when using -skipInstall
 Sample response file on next page
When running IM in recording mode, the graphical interface will indicate the
mode on the title bar.
As mentioned previously, “skipInstall” mode allows IM to simulate installations
without actually installing IBM software products. By using the “-skipInstall
agentDataLocation” argument along with the “-record responsefile.xml”
argument, you can create a response file for an installation process without
performing the installation. The agentDataLocation location stores the data for
the dummy installation data. You can use that same agentDataLocation later
to perform subsequent operations such as simulating fix pack installs or
uninstalling products.
Important:
Do not specify the current directory for a new agentDataLocation location.
Also, do not specify IM's default agent data directory for the
agentDataLocation with “-skipInstall”, because this will cause dummy data to
be added (or removed) from the agent data which keeps track of real product
installations on the system.
Once you have created the response file, keep that same dummy agent data
directory for future use. As mentioned above, you can simulate other
operations such as fix pack installs or product uninstalls with that data.
IBM Software Group
Application Server Details
IMPORT
Repository Details
Shared Resource
Directory
Install Options
Here is a sample response file. This response file will Import WebSphere
Application Server V7.0 on Windows, then install the base package of the
XML Feature Pack along with XML Feature Pack Fix Pack 5. Each relevant
section (including the option striped in cyan coloring at the top) is discussed in
the subsequent slides.
IBM Software Group
<agent-input> section

Purpose: Set global options for this IM session

Example: Recommended for most circumstances
 <agent-input clean=‘true’ temporary=‘true’>

clean – determines whether other preferences in response file are used
 true – only use the repositories and other preferences specified in this response file
false – use the repositories and other preferences that are specified in this response file
and Installation Manager's preferences
 temporary – determines if settings are saved to persistent preferences
 true – repositories and other preferences specified in the response file do not persist in
false – repositories and other preferences specified in the response file persist in
 Versions prior to IM 1.4.3 also used a required option named

acceptLicense='true'. This option is deprecated as of IM 1.4.3 and higher.
 Use command-line option “-acceptLicense” instead
The <agent-input> options are typically the first options in a response file.
These options set some global settings for the IM session which is executing
this response file. The “clean” and “temporary” attributes affect how IM uses
the repositories and other preference settings.
The Clean attribute settings are indicated on the slide text: It determines
whether other preferences in response file are used. When set to true, it only
uses the repositories and other preferences specified in this response file.
This is the recommended setting.
The Temporary attribute settings are indicated on the slide text as well: It
determines if settings are saved to persistent preferences in IM. When set to
true, the repositories and other preferences specified in the response file do
not persist in Installation Manager. This is the recommended setting.
IM 1.4.2 and earlier also used an attribute called “acceptLicense”, which may
still appear in sample response files, or response files recorded in those
versions of IM. As of IM 1.4.3, this option is is no longer needed in the
response file. Instead, when using IM 1.4.3 and later, specify the
“-acceptLicense” option on the command-line when invoking an IM command.
IBM Software Group
<server> section
 Purpose: Provide locations for respositories
 Example: Local repositories for XML feature pack
 <server>
<repository location='C:\IMAIX\xml_and_import_repositories\local-repositories'/>
<repository location='C:\IMAIX\xml.1.0.0.1.fp\xml.1.0.0.1.fp'/>
<repository location='C:\IMAIX\was.7.0.import'/>
</server>
 When using same response file on different system,

ensure the repository location specified in response file is
correct
The <server> options determine where all the repositories are located which
should be used during this IM session.
Repositories are locations that Installation Manager queries for installable
packages. You can specify directories (local repositories) or http:// and/or ftp://
URLs (web repositories). Note that the system must have Internet access to
be able to retrieve web repositories from ibm.com.
If you record a response file on one system, then transfer it to another system
to be executed by IM, be sure that the repository locations are still correct on
the other system. If they are not, edit the response file to correct them.
IBM Software Group
<profile> section
 Purpose: Provide details about product to be modified
 Example: Application server product installed on Linux®
</profile>
 InstallationLocation – specifies the directory path to an existing installation of
WebSphere Application Server V7.0.
 Id – package group name assigned to the imported installation of WebSphere Application

Server. If the product is already imported, then use the same name that has been used
previously.
 The installed.xml file under the agent data directory tracks which profile ID names
are in use. Consult that file to determine which name is associated with an already-
imported product. (More details about the agent data later.)
The <profile> options specify which product installation(s) (also called

package groups) will be modified when IM executes this response file.
There are several attributes to be concerned with here:
InstallationLocation
id
data key: eclipseLocation
data key: user.import.profile
data key: user.cic.imported
The installationLocation and id attributes are explained on the slide.

The first time a WSAS V7.0 product installation is imported, its “id” can be
chosen. We recommend using an ID which is similarly-formatted to what is
shown on this slide.
Once WSAS V7.0 is imported, you need to use a consistent “id” value in the
future. If you forget which ID is associated with a WSAS V7.0 installation
instance, you can look it up in IM's “installed.xml” file in the IM agent data
directory. More details are explained about this later.
IBM Software Group
Data keys in <profile> section

 Example: Application server product installed on Linux
</profile>
 eclipseLocation – must set this to same value used for installLocation
 user.import.profile – set to 'true' to perform Import of WebSphere product

 It is okay to set this to 'true' even if product has already been imported.
 user.cic.imported – Set value to the offering ID key that matches the product edition:
 com.ibm.websphere.EXPRESS.v70
This continues the discussion of the <profile> attributes. The eclipseLocation,

user.import.profile data key, and user.cic.imported data keys are explained
here.
Note that the user.cic.imported data key must be paired with the offering ID
key that matches the edition of WSAS. Here are the possible values:
com.ibm.websphere.EXPRESS.v70
IBM Software Group
<import> section
 Purpose: Provide additional information for import process
 Example: Importing a Network Deployment installation
 <import profile='IBM WebSphere Application Server - ND' type='WAS'/>
 This data is required if performing an import, and has no effect (can be omitted) if not
performing an import
 profile – specifies the name of the package group you will associate with this product
installation. Must set this to the same value used in the <profile> section. If the product
has already been imported before, then this value must match the value used previously.
(More details about this later – this value can be retrieved from 'installed.xml'.)
 type – always set to 'WAS'.
The <import> section is necessary when the <profile> data key,

user.import.profile, is set to true.
Note that the “profile” value must match the <profile> “id” value exactly.
IBM Software Group
<install> section
 Purpose: Declare which packages to install or update
</install>
 modify option – determines whether you are adding a sub-feature to an already-installed

product; e.g., adding the “SDO” feature to an already-installed SCA feature pack. Note
that feature packs themselves (CEA, SCA, XML, etc.) are not sub-features. Most of the
time, you will use modify='false'.
 offering section – each offering section instructs IM to install a package. The “offerings”
determine which repositories (or parts of repositories) are installed. You can use these to
install a new feature pack or upgrade an existing feature pack with a fix pack.
 Multiple offerings can be listed in an <install> section in order to install or update
multiple feature packs in a single IM session.
The <install> section declares which packages will be installed from the list of
repositories.
There are a couple attributes to be concerned with:
modify attribute
offerings
The modify attribute is only set to true when you are adding a new sub-feature
to the product specified by the profile 'id'. This is not something that is done
often with WSAS V7.0 feature packs, so you will usually leave this set to
'false'. (As of late 2011, the only circumstance where this would be set to
'true' is if you have already installed the SCA feature pack without the SDO
subfeature, and you now want to add the SDO subfeature.)
The offering attributes determine which packages are installed. Several
packages can be installed in a single IM session, so several <offering>
sections can be listed under a single <install> section.
IBM Software Group

</install>
 id – required parameter – specifies the name of a package to be installed. The package

needs to be part of at least one of the repositories declared in the <server> section. (How
to determine the “id” of a package is explained later.)
 version – optional parameter – determines which version of the package is installed. If

you have several repositories that all use the same ID (such as the XML Feature Pack
offering, XML Fix Pack 3, XML Fix Pack 5, and XML Fix Pack 7), then specifying the
version determines which of the packages get installed.
 If this parameter is omitted, then the newest (highest) version package (available
from the repository list) is installed.
As mentioned above, each <install> section can have several <offering>

sections. Each offering has its own set of attributes to be concerned with:
id
profile
version
features
The id and profile parameters are required.
The version and features parameters are optional.
This slide describes the id and version attributes.
The “id” attribute names a package to be installed. Details about how to find a
package “id” inside a repository are explained later.
If a version attribute is provided, then the offering will be installed at the
version level specified as long as it is available in the list of repositories. If the
version attribute is not provided, then the default behavior is to install the
highest version available in the repositories.
IBM Software Group

</install>
 features – optional parameter – specifies the name of a feature to be installed from the
offering. All feature pack offerings have at least one feature (the “core” feature), and
some have additional features (such as the SDO feature in the SCA feature pack).
 If you specify this option, be sure to at least specify the “core” feature. If you omit
this option, all features are installed.
 profile – required parameter – specifies the profile ID of a product to be updated. This

must match the profile ID specified in the <profile> section.
The features attribute is optional.

Offerings always have at least one feature: A “core” feature, which must be
installed in order for the product to function. If other feature names are
specified, then only those features will be installed.
If the features attribute is omitted, then the default behavior is to install the
default set of features for the offering.
Note that the “profile” value must exactly match the “id” specified in the
<profile> section.
IBM Software Group
<preferences> - Shared resources location

 Purpose: Sets the location of shared resources directory
 Example: Setting shared resources directory on Windows
 <preference value='C:\IBM\WebSphere\AppServer-Shared'
name='com.ibm.cic.common.core.preferences.eclipseCache'/>
 name – there are many <preferences>. The name of this particular setting is
“com.ibm.cic.common.core.preferences.eclipseCache”. You must use that value when
setting the shared resources directory.
 value – specify the full path of the shared resources directory here
 Same rules apply for shared directory as discussed earlier – shared directory can
only be set for IM the first time a product is imported, and must be the same for all
products afterward.
 All other <preference> values should remain at the default values recorded in response
file or copied from sample response file, unless there is a specific need to change an
option
The <preferences> data values are global settings which control IM's
behavior. Most global settings are fine as default settings and do not need
deep discussion here. However, the Shared Resources Location setting is
worth additional discussion.
The Shared Data Location acts as a cache for IM, maintaining data about
local and web repositories. The Shared Data Location acts as a staging area
for installation and upgrade tasks.
The first time a product is installed, or a WSAS V7.0 instance is imported, you
can choose the location of the shared data. After the shared data location is
set, it cannot be changed using a response file or the graphical interface. If
you attempt to use a different Shared Resources Location than the one
already chosen, then the setting is ignored.
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.
IBM Software Group
Finding data for response file

 To verify which profile ID was used for a previous import, consult
the installed.xml in the agent data directory – open in browser
 A feature pack's Offering ID and fix pack version number are

listed in repository.xml in a feature pack's main or
“local-repositories” directory
As mentioned earlier, sometimes you need to use data which has been set by
previous sessions using IM.
Profile ID:
When updating a WSAS V7.0 instance which has already been imported, you
need to use the same Profile ID that had been used the first time WSAS V7.0
was imported. If you don't know what the Profile ID should be, then you can
look it up in a file named “installed.xml”. That file is located under the IM
Agent Data directory (also known as the IM_DATA directory). This location is
explained later.
For best results, open the “installed.xml” file in a web browser. When it is
opened from the IM_DATA Directory, it will appear nicely-formatted, as shown
in the screenshot clip at the top of this slide.
Note that you can also choose the “View installed products” option under the
File menu in Installation Manager to see this data.
Feature Pack offering ID and version number:
If you are unsure about what a feature pack's Offering ID or version number
are for a particular fix pack, then review the files in the feature pack's
repository. Specifically, look for the file named “repository.xml” in the
repository's main directory, or the “local-repositories” subdirectory if it exists.
As indicated in the graphics in the lower part of the slide, an XML tag in the file
indicates the Offering ID and version in that feature pack or fix pack.
IBM Software Group


In this example, we have obtained the XML Feature Pack repository, the WAS
Import Repository, and XML Fix Pack 5 repository

This will either install a fresh copy of XML Feature Pack and update it to V1.0.0.5,
or it will update an existing XML Feature Pack to Fix Pack 5. It does this because
Fix Pack 5 is the highest level repository in the repository location list.

<server>
</server>

Then, specify the feature pack to be updated in <install> section
profile='IBM WebSphere Application Server - ND' />
</install>
This is an example of what the <server> and <install> sections of a response

file look like when installing the XML Feature Pack with Fix Pack 5 (version
1.0.0.5).
These two sections will look the same whether you are installing the XML
Feature Pack at 1.0.0.5 for the first time, or you are updating an existing
feature pack with Fix Pack 5.
Note that because we did not specify a version value in the <offering> section,
IM will automatically install the latest version in available in the repository list.
In this example, the repository list has the base install package for XML as
well as Fix Pack 5.
Note that this is not a complete response file example. This is just illustrating
that you can use similar <server> and <install> sections whether you are
installing the feature pack for the first time, or upgrading it.
IBM Software Group


Alternative example: We happen to have Fix Packs 3, 5, and 7, but we really want
to update XML to fix pack 5

<server>
</server>

Then, specify the feature pack to be updated in <install> section, being sure to
specify the exact version number to install 1.0.0.5
</install>
This extends the previous example. Here we have a repository list that has
Fix Packs 3, 5, and 7 for the XML feature pack. (You can also imagine that
this list connects to the ibm.com web repository instead, which has ALL
available feature pack fix packs.)
In this example, although we have several fix packs available, we specifically
want to upgrade to Fix Pack 5. In the <offering> section, we specify the
version number which identifies Fix Pack 5:
version='1.0.5.20100406_1332'
That version number isn't intuitive, so how do we know what it is supposed to
be? As mentioned earlier, you can refer to the “repository.xml” file in the Fix
Pack 5 repository's files. The version number for Fix Pack 5 is listed there.
Note that you can also generate this version number by using IM's “record
mode” to record a response file. This is a reason why we recommend using
record mode – it looks up this data for you.
IBM Software Group
Sample: ifix install

 Updating product with interim fix generally follows the same pattern
in the <install> section
<offering id='PM12345_FEATUREPACK'

Generally, ID of interim fix is provided in readme file bundled with fix, or
the ID matches the name of the interim fix repository .zip file provided by
IBM

Review repository.xml associated with fix for exact details
Here is another brief example, similar to the Fix Pack 5 example. In this
example, an interim fix is being installed.
Again, for details about the Offering ID for an interim fix, refer to its
“repository.xml” file or use record mode.
IBM Software Group


In this example, assume that XML Feature Pack 1.0.0.5 is installed

Update the <profile> section with a data key to indicate that profiles should
be automatically unaugmented, removing data from a specific feature pack
<profile id='IBM WebSphere Application Server – ND'>

Note: If more than one feature pack is being uninstalled, then include a separate
unaugment <data> key for each feature pack. Some feature pack offering ID values are:
com.ibm.websphere.SCA.v10
com.ibm.websphere.XML.v10
com.ibm.websphere.CEA.v10
com.ibm.websphere.ARIESJPA.v10
For example:
<data key='user.confirm.unaugment,com.ibm.websphere.SCA.v10' value='true'/>
This example shows some sections of a response file for uninstalling a

Feature Pack or a Feature Pack's fix pack. This example shows various
uninstall-related operations associated with an XML feature pack which was
installed previously.
Profiles augmented by a WebSphere Application Server Feature Pack must
have those feature pack specific changes removed before the feature pack
can be uninstalled. This is called “unaugmenting”.
The uninstaller will not allow you to uninstall a feature pack if it detects that
any profiles are augmented. By setting the data key named
“user.confirm.unaugment,com.ibm.websphere.XML.v10” to “true”, the
uninstaller will run a script which unaugments the XML feature pack data from
all profiles.
You can specify the unaugmentation option for several feature packs in a
single <profile> section.
IBM Software Group


Update the <uninstall> section with the offering ID of the feature packs to be
uninstalled. The feature pack and all its fix packs will be uninstalled.
</uninstall>
 The id and profile attributes are required.
 Alternatively, specify a version and/or feature attribute to uninstall a specific

fix pack or sub-feature instead of uninstalling the entire feature pack. This
sample uninstalls Fix Pack 5:
profile='IBM WebSphere Application Server - ND'
version='1.0.5.20100406_1332'/>
</uninstall>
This continues the uninstall example from the previous slide.

If the “version” and “feature” attributes are not specified in the <uninstall>'s
<offering> section, then the whole feature pack is uninstalled.
If the version attribute is specified, then that specific fix pack is uninstalled.
(See the install example earlier for details about finding the version number.)
IBM Software Group


Another alternative: Use rollback instead of uninstall. Works similarly to
rollback described earlier.
<rollback>
profile='IBM WebSphere Application Server - ND' features=''/>
</rollback>
Similar to the <uninstall> command, there is also a separate <rollback>

command available. The <rollback> command is similar to the <uninstall>
command because it is capable of uninstalling fix packs from a feature pack.
With the rollback command, you must choose the version which you want to
roll back to. (In other words, choose the version number that you want to
have when the operation completes.)
In this example, the XML feature pack is being rolled-back to version 1.0.0.0.
All fix packs and interim fixes are removed.
IBM Software Group
Important Directories

IBM Software Group
Directories (Shared Resources Directory)

 This location acts as a cache for data retrieved from local repositories or web
repositories. Improves performance on systems where frequent installs /
uninstalls take place.
 Location is selected the first time a package is installed by Install Manager, or
during Import
 Multiple products share this same directory
 Choose location with reasonable disk space free
 Deleting this directory is not recommended
 Cannot be changed or moved once selected
Sample Shared Resource directory from Windows
As discussed earlier, the Shared Resources Directory acts as a cache of data

related to local and web repositories. It contains files that can be shared by
multiple packages and product installations. This directory's location can only
be selected the first time you install a package with the IBM Installation
Manager.
For best results, select a filesystem with ample available space. This directory
will grow as more products and packages are installed. It is good practice to
use the recommended shared resources directory, which is usually on the
same filesystem as the products (or first product) are being installed.
It is recommended to take backup of this directory when taking other
Operating System Backups. The contents of this directory should not be
deleted in an effort to conserve filesystem space.
IBM Software Group
 appDataLocation: also called Installation Manager Agent Data Directory or
IM_DATA directory
 IBM Installation Manager uses this to track data associated with packages it has
installed on the system
 This data is very important and should be backed-up regularly along with
WebSphere products
 Location of data can be changed using -dataLocation (or -dL ), but make sure to
use -dataLocation option every time Installation Manager programs are used
 Table of default
locations for
IM_DATA:
The agent data location, or appDataLocation, is the directory that Installation

Manager uses to track data that is associated with installed products. This
includes the state of each product (such as the list and data about each
installed fix pack), history of operations, and logs.
Changing the content, files, or directories in the agent data location directory
or subdirectories is not supported. Changes to these files might prevent
Installation Manager from working.
The data in this directory is extremely important. If this directory becomes lost
or corrupted, then it may not be possible to install fix packs or even uninstall
products. Because it is so important, IBM recommends taking backups of this
directory whenever other important files are backed-up.
The default IM_DATA locations are listed on the slide above.
You can direct IM to use a different directory to store IM_DATA. The
“-dataLocation” or “-dL” prameter can do this. If you choose to do this, then
the specified location must be used each time you use Installation Manager or
the Installation Manager installer.
IBM Software Group
 The default appDataLocation is set by the cic.appDataLocation
property in the config.ini file – location depends on OS
 Windows: install_dir\IBM\Installation Manager\eclipse\configuration
 Linux and UNIX: install_dir/IBM/InstallationManager/eclipse/configuration
 IBM does not recommend changing this value in config.ini file
 To determine the location of Installation Manager, check in these

locations:
 Windows Registry key: HKLM\SOFTWARE\IBM\Installation Manager\location
 Linux and UNIX:
• Open the /etc/.ibm/registry/InstallationManager.dat file
• Look at the location entry. Example: location=/var/ibm/InstallationManager
This slide shows information about where you can look to find information
about where Installation Manager is installed, and where that Installation
Manager sets its appDataLocation by default.
IBM Software Group
Viewing logs from


IBM Software Group
Install Manager GUI can be used to view Installed packages, Installation history
and logs.
Installation Manager's graphical mode has built-in viewers for important data.
You can use the viewers to see:
Logs
Installation history
Installed packages
Each of those three viewers are listed under the File menu. The log viewer is
particularly useful for troubleshooting, because you can sort log events
chronologically or by severity (which allows errors and warning messages to
be sorted to the top of the list).
IBM Software Group
From the Logs folder under Data directory open index.xml in a browser
You can also view the log and history data manually if you do not have access
to the graphical interface.
In the example screenshots, the left clip shows a Windows file browser
viewing the IM_DATA\logs directory. If you view the “index.xml” file from that
directory in a web browser such as Firefox, you will see a nicely-formatted list
of log files and a summary of the number of warnings and errors in each.
Note that the nicely-formatted view only works when the “index.xsl” or other
.xsl files are present in the same directory as the files you are viewing in a web
browser. If you need to copy the files to another system to view them, it's
usually best to copy the entire “logs” directory to that other system for viewing.
The location of the IM_DATA directory was mentioned previously; refer back
to that information about how to find IM_DATA.
The IM_DATA directory also has other useful data which you can browse:
- The “installed.xml” file in the IM_DATA directory
- The list of history events associated with each product, located in the
IM_DATA/histories directory. (View the “index.xml” file in that directory to see
more data.)
IBM Software Group
Best Practices and

Common Problems

IBM Software Group
Best Practices
 Each of the following should have unique path
 Installation Manager Install Directory
 Shared Resources Directory
 Install Manager Data Directory
 IM can be installed and run as non-root user

 Highly recommended to use WSAS as non-root
 Use same user to install and update Feature Packs

 When installing multiple feature packs using silent mode,
prepare the response file using record mode
Throughout this presentation, we have mentioned some best practices

associated with various activities. Here are some more best practices which
haven't mentioned earlier, or are worth reiterating.
The point about using the “same user” to install and update Feature Packs is
worth expanding on. It is best practice to use the same user to install and
update the product. It is simpler to also use this same user to run the product.
However, for security reasons, it may be necessary to run the application
servers as a different user. Doing this is outside the scope of this
presentation. But, please keep in mind that the user running installation
manager must have write access to all of the files located in the product (such
as all the files under WAS_HOME), and that user must also have write access
to the files in each profile.
IBM Software Group
Best Practices
 Repositories can be stored on a networked resource and
accessed through a networked filesystem (or a UNC path on
Windows)
 Multiple systems can access the same collection of local repositories
simultaneously
 Augmentation
 Must augment profiles once a feature pack is installed
 Must unagument profiles if uninstalling a feature pack
 Keep copies of all local repositories

 Maintain a copy of the appDataLocation data used with
“-skipInstall”
Local repositories can be stored on a networked filesystem. The network

filesystem can be mounted, and repositories can be accessed like normal
local repositories. On Windows, you can use UNC paths to access them,
provided that the current user has proper credentials to access them.
Augmentation can take place using the Profile Management Tool or the
manageprofiles command-line tool. Unaugmentation can take place using the
manageprofiles tool, or you can choose to have the uninstaller automatically
unaugment profiles.
Mentioned earlier, but worth reiterating: If you use local repositories, do not
discard them after finishing installing a feature pack. They are needed again
when you apply fix packs.
Also, be sure to maintain a copy of the data generated when you use the
“-skipInstall” parameter and record mode.
IBM Software Group

 When trying to install XML Feature pack on WSAS 7.0.0.15
using Local Repositories, and getting the following error:
Repositories in preferences
Error
On GUI
The “Synchronization Error” show in the left screenshot is a common

occurrence.
When Installation Manager detects that WSAS V7.0's fix pack level has been
changed using the UpdateInstaller utility, IM will need to synchronize its data
with the new state of the WSAS product.
In order to do this, IM needs access to the WSAS Import Repository.
However, as newer versions of WSAS are released, the WSAS Import
Repository needs to be updated as well. If the WSAS Import Repository is
missing or outdated, then this error occurs when IM attempts to synchronize
with the WSAS product.
This needs to be resolved before any installs, updates, or uninstalls can take
place.
(NOTE: The “WSAS Import Repository” mentioned here is frequently also

referred to as the “WAS Import Repository”.)
IBM Software Group

 XML Feature Pack Repository has Sync repositories for Application Server
fix pack 7. WSAS v7.0.0.7 should synchronize fine, but if the product is
upgraded to higher fix pack (like 7.0.0.15) then latest WSAS Import
Repositories are needed for product to synchronize with IM
WSAS Sync repository with Latest WSAS Import repository

XML Feature Pack Repository
NOTE: Always keep a copy of the latest WSAS import repositories.
This continues the discussion concerning the WSAS Import Repositories.

The Feature Packs include a copy of a WSAS Import Repository. So, when
installing a feature pack, you may find that you do not need a WSAS Import
Repository.
But, the copy of the WSAS Import Repository included in a feature pack can
become outdated as new WSAS Fix Packs are released. The screenshots
illustrate this fact; the left screenshot shows an Import Repository included
with a feature pack, but it is outdated. The right screenshot shows a more
modern Import Repository, which contains information about more WSAS Fix
Pack levels.
The latest WSAS Import Repository is always available at this location on
ibm.com:
http://public.dhe.ibm.com/software/websphere/downloads/was/import/
It is updated whenever WSAS V7.0 releases a new fix pack level.
Note that if you use web repositories which connect to ibm.com, then you do
not need this file, because it is already available in the web repositories
IBM Software Group
Problem: Java SDK fixpack version not same

as WSAS fixpack
 Application Server is at 7.0.0.19 but Java SDK is at 7.0.0.15

 Both fix packs have to be at same level for Import to succeed
When Importing WSAS using IM, the WSAS Fix Pack level and Java SDK Fix
Pack level must be the same.
The fix pack levels also need to be the same when WSAS is synchronized
with IM.
IBM Software Group
Problem: What do I download to install latest

version of XML feature pack ?
 Base Code of Feature pack can be downloaded from
Support page (requires IBM web site ID)
 Will download as <featurepack_name>_and_import_repositories.zip
 For XML, xml_and_import_repositories.zip
 Example from Fixpack 1.0.0.9 download page:
XML fixpack 1.0.0.9

WSAS Import
Repository
XML Import or Mini
XML only used if XML
1.0.0.0 (GA) is installed
and is being updated to
1.0.0.9
When you are installing a feature pack for the first time, you need the feature
pack's base install package. The fix pack package is not sufficient to install an
entire feature pack.
Downloading the base install repository
Having trouble finding a feature pack's base repository? Start here:
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Go to the V7.0 section and find the name of the feature pack. Click on the link
to that feature pack to go to the latest Fix Pack page for that feature pack.
From the Fix Pack page, look for a link in the Download Description which
takes you to the Overview page for that feature pack. The overview page has
a Download button (a large purple button graphic) which leads you to the page
from which you can download the feature pack's base repository. Note that
this requires an IBM ID to accomplish. These feature packs need to be
maintained on a separate site from the fix packs, because they are treated as
if you are downloading a whole product (but a free product) from IBM.
Downloading fix pack repositories
Generally, you only need to download the first repository listed on a feature
pack fix pack support page. See the diagram on the slide.
The second link is for the latest WSAS Import repository which is necessary if
you don't have the latest copy. The third link is not needed if you always keep
a copy of the base install repository for a feature pack.
IBM Software Group

 Agent data directory (IM_DATA)
 Using Graphical Installation Manager
 Using Command line navigate to eclipse/tools subdirectory in the

location where you installed Installation Manager
• Windows: imcl.exe exportInstallData outputFileName
• Unix and Linux: ./imcl exportInstallData outputFileName
• z/OS: ./imcl exportInstallData outputFileName
 Send the zip file created to support along with files listed on next slide
This is data needed for support to review if PMR is opened with IBM support.
We recommend reviewing the recommended MustGather data for WSAS
V7.0 feature packs if you are opening a PMR. That page is here:
http://www-01.ibm.com/support/docview.wss?uid=swg21397645
The “data export” described on this slide is especially helpful for support.
Please see the next slide for other useful data to send to IBM.
IBM Software Group
 In addition to this, we need

Logs directory from Application Server
All XML files from Application Server's
properties/version/nif/backup directory
Response file used for installation
• Only needed if performing a silent install
Screenshot of error if using Graphical Interface
• If you are installing IM and the graphical interface does not
appear, or if it appears but prints errors to the console, please
copy and paste the console errors to us
This describes more data which is useful for IBM troubleshooting IM issues
with managing feature packs on WSAS V7.0.
IBM Software Group
Additional WebSphere Product Resources

 Learn about upcoming WebSphere Support Technical Exchange webcasts, and access
previously recorded presentations at:
http://www.ibm.com/software/websphere/support/supp_tech.html
 Discover the latest trends in WebSphere Technology and implementation, participate in

technically-focused briefings, webcasts and podcasts at:
http://www.ibm.com/developerworks/websphere/community/
 Join the Global WebSphere Community:
http://www.websphereusergroup.org
 Access key product show-me demos and tutorials by visiting IBM Education Assistant:
http://www.ibm.com/software/info/education/assistant
 View a webcast replay with step-by-step instructions for using the Service Request (SR)
tool for submitting problems electronically:
http://www.ibm.com/software/websphere/support/d2w.html
 Sign up to receive weekly technical My Notifications emails:
http://www.ibm.com/software/support/einfo.html
This chart includes links to a number of sites that provide valuable online resources for
WebSphere products. Visit the WebSphere Support Technical Exchange site to learn
more about upcoming WebSphere Support Technical Exchange webcasts, like the one
you attended today, and access previously recorded presentations. developerWorks
offers in-depth technical information. Visit websphereusergroup.org for user group
information and more product information. The IBM Education Assistant consists of self-
help modules to get new users up the learning curve quickly. The SR tool is for Passport
Advantage clients to open, update and view PMRs online. And the My Notifications link on
all product support pages lets you sign up for weekly e-mail updates for products of
interest to you.
56
IBM Software Group
Connect with us!
1. Get notified on upcoming webcasts

Send an e-mail to wsehelp@us.ibm.com with subject line “wste
subscribe” to get a list of mailing lists and to subscribe
2. Tell us what you want to learn

Send us suggestions for future topics or improvements about our
webcasts to wsehelp@us.ibm.com
3. Be connected!
Connect with us on Facebook
Connect with us on Twitter
57
IBM Software Group
Questions and Answers

WSTE 10272011 BestPracticesInstallingWASV7FeaturePacks

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WSTE 10272011 BestPracticesInstallingWASV7FeaturePacks

Uploaded by

Copyright:

Available Formats

®

IBM Software Group

Best Practices for Installing WebSphere

WebSphere® Support Technical Exchange

WebSphere® Support Technical Exchange 2 of 58

WebSphere® Support Technical Exchange 3 of 58

Introduction to Installation Manager

 Starting with WebSphere Application Server v7.0,

WebSphere® Support Technical Exchange 4 of 58

ISMP vs. Installation Manager

 IBM Installation Manager (IM)

WebSphere® Support Technical Exchange 5 of 58

WebSphere® Support Technical Exchange 6 of 58

Feature Fix Pack

WebSphere® Support Technical Exchange 7 of 58

WebSphere® Support Technical Exchange 8 of 58

 Must use Import feature for Installation Manager to

 The Import button is only visible after a WebSphere

WebSphere® Support Technical Exchange 9 of 58

WebSphere® Support Technical Exchange 10 of 58

WebSphere® Support Technical Exchange 11 of 58

Installation Manager graphical options

WebSphere® Support Technical Exchange 12 of 58

Installation Manager graphical options

WebSphere® Support Technical Exchange 13 of 58

If checked will list all available offerings

WebSphere® Support Technical Exchange 14 of 58

Select recommended is checked in both cases above.

WebSphere® Support Technical Exchange 15 of 58

Install Sequence was:

Will Roll back to 1.0.0.3

Will Roll back to 1.0.0.0

WebSphere® Support Technical Exchange 16 of 58

If checked will uninstall Application Server

Will uninstall complete Feature Pack

WebSphere® Support Technical Exchange 17 of 58

WebSphere® Support Technical Exchange 18 of 58

 A single response file can perform multiple operations; i.e.,

WebSphere® Support Technical Exchange 19 of 58

 imcl -help will list options available with imcl command

WebSphere® Support Technical Exchange 20 of 58

Recording mode and skipInstall mode

 skipInstall mode allows IM to operate in a mode where it does

 Both modes can be combined

WebSphere® Support Technical Exchange 21 of 58

Recording a response file

 Don’t specify IM's true agent data directory with skipInstall –

WebSphere® Support Technical Exchange 22 of 58

Application Server Details

WebSphere® Support Technical Exchange 23 of 58

 Versions prior to IM 1.4.3 also used a required option named

WebSphere® Support Technical Exchange 24 of 58

 When using same response file on different system,

WebSphere® Support Technical Exchange 25 of 58

 Id – package group name assigned to the imported installation of WebSphere Application

WebSphere® Support Technical Exchange 26 of 58

Data keys in <profile> section

 user.import.profile – set to 'true' to perform Import of WebSphere product

WebSphere® Support Technical Exchange 27 of 58

 type – always set to 'WAS'.

WebSphere® Support Technical Exchange 28 of 58

 modify option – determines whether you are adding a sub-feature to an already-installed

WebSphere® Support Technical Exchange 29 of 58