IBM Optim Manager, Version 2.2
Installation guide
Note
Before using this information and the product it supports, read
the information in Notices.
This edition applies to version 2.2 of IBM Optim
Manager and to all subsequent releases and modifications until otherwise
indicated in new editions. Instructions are written for version 1.4.1
of Installation Manager, which is compatible with Optim Manager 2.2.
Copyright International Business Machines Corporation 2010.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Installing IBM Optim Manager
You use the Installation Manager product to install, update,
and uninstall the Optim Manager product.
For information about configuring and using the Optim™ Manager environment, refer
to the documentation location on the installation disc.
Installation roadmap for IBM Optim Manager
The installation roadmap lists the high-level steps for
installing IBM® Optim Manager.
This roadmap describes a typical installation using the Installation
Manager Install wizard. If you are installing the product silently,
see the Silent installation road maps.
Roadmap for installing the product package
Perform
these tasks to install the product:
- Verify that your computer
and user ID meet the minimum requirements for installing the product.
- Review the rest of the planning
information .
- Complete any necessary
pre-installation tasks.
- Install the product using
the Installation Manager Install wizard.
- Perform any necessary
post-installation tasks.
Silent installation road maps
The typical silent installation path is to use the Installation
Manager installer to install Installation Manager, and then to use
Installation Manager to record a response file, then to silently install
software packages. Optionally, you can use the Installation Manager
installer to install Installation Manager and software packages at
the same time. When you install in silent mode, the user interface
is not available; instead, a response file inputs the commands that
are required to install the software packages.
There are two main road maps for performing a silent installation.
- Use Installation Manager to silently install software packages:
- Install Installation Manager using the Installation Manager installer.
- Record a response
file using Installation Manager, or Create a response file manually.
- Run the Installation Manager
in silent mode to perform the operation silently.
- Use the Installation Manager installer to silently install software
packages:
- Create a response file manually that
includes commands to install Installation Manager and other packages.
- Run the Installation Manager
installer with the response file.
Installation introduction
This section contains instructions for installing, updating,
and uninstalling your product package.
Installation terminology
Understanding these terms and conventions can help you
take full advantage of the installation information and your product.
These
terms are used in the installation topics.
- Admin user
- A user who has write administrative privileges. In the context
of installing, having write administrative privileges means that the
user can write to the default common installation location. On Linux or Unix operating systems, this is the "root"
or any user who is using "sudo" to start Installation Manager. On
a Microsoft Windows XP operating system, a user with
write administrative privileges is any user who is a member of the
"Administrators" group. On a Microsoft Windows Vista, Windows Server 2008, or Windows 7 operating system, this is the user
who is using "Run As Administrator" to start Installation Manager
or launch pad.
- Extension
- A type of product package that provides additional function to
another product package. You cannot install the extension without
also installing the package that it extends.
- Installation directory
- The location of product artifacts after the package is installed.
- Non-admin user
- A user who does not have write administrative privileges. In the
context of installing, this means that this user can only install
into the home directory.
- Package
- An installable unit of a software product. Software product packages
are separately installable units that can operate independently from
other packages of that software product.
- Package group
- A package group represents a directory in which different product
packages share resources with other packages in the same group. When
you install a package using Installation Manager, you can create a
new package group or install the packages into an existing package
group. (Some packages cannot share a package group, in which case
the option to use an existing package group is disabled.) Sharing
a package group is sometimes also referred to as "shell sharing."
- Repository
- A persistent storage area where packages are available for download.
A repository can be disc media, a folder on a local hard disk, or
a server or Web location.
- Shared resources directory
- In some instances, product packages can share resources. These
resources are located in a directory that the packages share.
Installation default values and conventions
The installation documentation uses conventions such as Shared
resources directory that infer specific directory locations.
This topic describes the conventions in use for this product and the
associated default value.
Table 1. Installation documentation conventions and default values
Name |
Convention in installation documentation |
Default Value |
Installation Manager installation directory |
Installation Manager directory |
- Admin installation:
- On Windows: C:\Program
Files\IBM\Installation Manager
- On Linux or Unix systems: /opt/IBM/Installation
Manager
- Non-admin installation:
- On Windows systems:
- On Linux or Unix systems:
|
Installation manager shared resources directory |
Shared resources directory |
- Admin installation:
- On Windows systems: C:\Program
Files\IBM\SDPShared
- On Linux or Unix systems: /opt/IBM/SDPShared
- Non-admin installation:
- On Windows systems: user.home\IBM\SDPShared
- On Linux or Unix systems: user.home/IBM/SDPShared
|
Product installation directory |
Product directory |
- Admin installation:
- On Windows systems:
- Optim Manager, Optim Management Server, WASCE,
and Optim Shared
Libraries: C:\Program Files\IBM Optim\shared
- Optim Proxy: C:\Program Files\IBM Optim\proxy
- On Linux or Unix systems:
- Optim Manager, Optim Management Server, WASCE,
and Optim Shared
Libraries: /opt/IBM/shared
- Optim Proxy: /opt/IBM/proxy
- Non-admin installation:
- On Windows systems:
- Optim Manager, Optim Management Server, WASCE,
and Optim Shared
Libraries: C:\Program Files\IBM Optim\shared
- Optim Proxy: C:\Program Files\IBM Optim\proxy
- On Linux or Unix systems:
- Optim Manager, Optim Management Server, WASCE,
and Optim Shared
Libraries: /opt/IBM/optim/shared
- Optim Proxy: /opt/IBM/optim/proxy
|
Planning the installation
Read all of the following topics before you begin to install
or update any of the product features. Effective planning and an understanding
of the key aspects of the installation process can help ensure a successful
installation.
Installation Manager overview
IBM Installation
Manager is a program for installing, updating, and modifying packages.
It helps you manage the IBM applications,
or packages, that it installs on your computer. Installation Manager
does more than install packages: It helps you keep track of what you
have installed, determine what is available for you to install, and
organize installation directories.
Installation Manager provides tools that help you keep packages
up to date, modify the packages, manage the licenses for your packages
if required, and uninstall the packages from your system.
Version 1.4.1 of Installation Manager is included with
the product. You can also download Installation Manager Version 1.4.x
directly from www.ibm.com. All instructions in this Installation Guide
assume that you are using the included version of Installation Manager.
If you upgrade later to a higher version of Installation Manager,
some of the instructions might not be accurate. The Installation Manager
information center is on the Web at: http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp
Installation Manager includes six wizards that make it easy to
maintain packages through their life cycles:
- The Install wizard walks you through the
installation process. You can install a package by simply accepting
the defaults, or you can modify the default settings to create a custom
installation. Before you install, you are provided with a complete
summary of your selections throughout the wizard. Using the wizard
you can install one or more packages at one time.
- The Update wizard will search for available
updates to packages that you have installed. An update might be a
released fix, a new feature, or a new version of the product. Details
of the contents of the update are provided in the wizard. You can
choose whether to apply an update
- The Manage Licenses wizard helps you set
up the licenses for your packages. Use this wizard to change your
trial license to a full license, to set up your servers for floating
licenses and to select which type of license to use for each package.
Not all product packages require licenses.
- The Roll Back wizard enables you to revert
to a previous version of a package.
- The Uninstall wizard will remove a package
from your computer. You can uninstall more than one package at a time.
- With the Modify wizard you can modify certain
elements of a package that you have already installed. During the
first installation of the package, you select the features that you
want to install. If you find later that you require other features,
you can use the modify packages wizard to add them to your package.
You can also remove features and add or remove languages.
Installing IBM Installation
Manager
IBM Installation
Manager is the tool that you use to install your software packages.
It is installed automatically when you start the installation for
your product offering.
If you start the installation of the product by using the
launchpad from the product DVD, IBM Installation
Manager automatically starts even if it is not already installed.
If the correct version of Installation Manager is not installed, you
will install Installation Manager on your computer during the process
of installing the product.
The latest version of Installation Manager
might be required for your package. Updates are discovered if you
have not cleared the Search service repositories for updates check
box on Repositories page in the Preferences window
of Installation Manager.
Note:
Installation Manager is installed
only once for each user ID on the computer.
Starting IBM Installation
Manager
If you start the installation of the product from the launchpad, IBM Installation Manager automatically
starts even if it is not already installed.
If you already installed Installation Manager, you can start
it manually:
- On Windows systems:
Click Start > All Programs > IBM Installation Manager > IBM Installation
Manager
- For Linux or Unix: Change to Installation
Manager directory/eclipse and run IBMIM
Installation requirements
Installation requires the correct hardware, operating system, software,
and other factors.
Hardware and software requirements for IBM Optim Manager
Verify that your hardware and software meet or exceed the
minimum requirements. If your hardware and software do not meet the
minimum requirements, you might be unable to install or run the product.
Before you can install the product, verify that your system meets
the minimum hardware requirements.
For the most up to date Optim Manager and Optim Management Server system requirements,
see the technote on the Web: http://www.ibm.com/support/docview.wss?uid=swg27019158
For the most up to date Optim Proxy system
requirements, see the technote on the Web: http://www.ibm.com/support/docview.wss?uid=swg27019159
- Compatible operating systems
- Do not attempt to install the product on operating systems other
than those that are listed. Installation Manager might run on other
operating systems, but the product package installation can fail.
If installation fails, uninstallation sometimes also fails.
Optim Manager and Optim Management Server supported operating
systems are listed on the product system requirements Web page: http://www.ibm.com/support/docview.wss?uid=swg27019158
Optim Proxy supported operating
systems are listed on the product system requirements Web page: http://www.ibm.com/support/docview.wss?uid=swg27019159
User privilege requirements
You must have a user ID that meets specific requirements
before you can install your product.
Your user ID must not contain double-byte characters.
There are two methods of installation: administrative and non-administrative.
For information about how to choose between these two options, see
the topic: Installation terminology
Implications of using an admin or non-admin user ID
when installing
Table 2. The following table describes what happens when user ID's with different access privileges are used when installing
User ID authority |
Case where you install as Non-admin |
Case where you install as Admin |
Non-admin (current user) |
- If Installation Manager is not already installed, it is installed
for the current user only.
- After Installation Manger is installed, products can only be installed
for the current user.
|
- For operating systems other than Microsoft Windows Vista:
An error message occurs.
- For Microsoft Windows Vista: You are prompted
to log on with an Admin user ID.
|
Admin |
An error message occurs. |
- If not already installed, Installation Manager is installed for
All Users.
- Any products installed with this Installation Manager are for
All Users
|
Additional requirements for Linux and Unix operating systems
If you use a Linux or Unix operating system, then you must check
that your computer meets the requirements listed in this topic.
Environment variable might need setting for Firefox
or Mozilla browsers
You might need to set the environment
variable MOZILLA_FIVE_HOME to the folder containing your Firefox or
Mozilla installation. For example, setenv MOZILLA_FIVE_HOME /usr/lib/firefox-1.5.
Firefox browsers must be dynamically linked
To
support the SWT browser widget, your Firefox browser must be dynamically
linked, which means it was not downloaded from mozilla.org, but was
compiled from source. This is typically the case when the Firefox
comes as part of the distribution (that is, it is in a place such
as /usr/lib/firefox).
One way to ensure that this is true is
to see if it is the browser that is pointed at by /etc/gre.conf. The
purpose of this gre.conf file is to point at an embeddable browser.
SUSE Linux might
require a fix for invisible text problem
If your operating
system is SUSE Linux Enterprise
Desktop 10 SP1 or SUSE Linux Enterprise
Server 10 SP1, then you might need the following operating system
update to resolve a problem with text not being displayed in some
editors:http://support.novell.com/techcenter/psdb/44ab155e3202595389c101e6cf7e20f2.html.
Planning what features to install
You can customize your software product by selecting which
features to install.
When you install the product package by using IBM Installation Manager, the installation wizard
displays the features in the available product package. From the features
list, you can select which to install. A default set of features is
selected for you (including any required features). Installation Manager
automatically enforces any dependencies between features and prevents
you from clearing any required features.
Tip:
After you
finish installing the package, you can still add or remove features
from your software product by running the Modify Packages wizard in
Installation Manager.
The following tables show the features of the
product that you can install for each package.
Default selections of features to install might vary. If a feature
already exists in your shared resources directory, it will not be
selected by default and will not be installed again.
- Optim Management Server
-
Feature |
Description |
Optim Management Server
WAR File |
The Optim Management
Server WAR files contains the necessary Optim Management
Server components to run on your preferred application server such
as IBM WebSphere® Application Server Community
Edition (WAS-CE). |
Optim Replacement
Data Database |
The Optim Replacement
Data Database is an Apache Derby database that contains replacement
data. When you use Optim Designer
to create services with privacy policies, you can set the privacy
policies to use the replacement data to mask data in other databases. |
Replacement Data, Sample Data, and User Data in Comma Separated
Format (with associated DDL) |
This feature installs replacement data files, sample data
files, and manager user data files in comma-separated (CSV) format,
with accompanying Data Definition Language (DDL) files. Use these
files to create replacement data tables, sample data tables, and manager
user tables in the database of your choice. You could then use these
tables instead of installing and using the Optim Replacement Data Database. |
- Optim Manager
-
Feature |
Description |
Optim Manager WAR
File |
The Optim Manager
WAR files contains the necessary Optim Manager
components to run on your preferred application server such as IBM WebSphere Application Server Community
Edition (WAS-CE). |
- Optim Shared Libraries
-
Feature |
Description |
External Data Store Support |
The Optim Shared Libraries
component contains native libraries that are required by all Optim components (Optim Designer, Optim Manager, Optim Management Server, and Optim Proxy). This component must
be installed on every machine that has any other another Optim component installed and must be present
before any Optim component
can be executed on this machine. |
Optim Designer and Optim Manger Documentation |
This feature installs documentation for Optim Designer and
the Optim Manager environment. |
Installation considerations
Part of planning entails making decisions about things such as
installation locations, working with other applications, or extending Eclipse.
This information helps you with these decisions.
Installation directories
IBM Installation
Manager uses two directories when installing product artifacts.
Shared resources directory
The
shared
resources directory is where some product resources are installed
so that they can be used by multiple product package groups. You define
the shared resources directory the first time that you install IBM Installation Manager. For best
results, use your largest disk drive for shared resources directories.
You cannot change the directory location unless you uninstall Installation
Manager.
Package groups
During
installation, you specify a
package group into which
to install a product.
- A package group represents a directory in which products might
share resources with other products in the same package group. This
option is also sometimes called "shell sharing."
- Not all products can share a package group, in which case the
option to use an existing package group will be disabled.
- When you install a product using Installation Manager, you either
create a package group or install the product into an existing package
group. A new package group is assigned a name automatically; however,
you choose the installation directory for the package group.
- After you create a package group you cannot change the installation
directory. The installation directory contains files and resources
shared by the products installed into that package group.
- When you install multiple products at the same time, all products
are installed into the same package group.
Optim Manager Packages
Optim Manager includes
several installation packages.
The following installation packages are available.
- IBM WebSphere Application Server Community
Edition (WAS-CE)
- IBM WebSphere Application Server Community
Edition (WAS-CE) is a lightweight J2EE application server. It is based
upon Apache Geronimo technology developed by the Apache Software Foundation.
The Optim Management Server and Optim Manager each require a J2EE
application server.
WAS-CE can be used to simultaneously host
the Optim Management Server
and Optim Manager when installing
these two components on the same machine. If you plan on using WAS-CE
as your application server, only install one instance of WAS-CE on
this machine.
You can install WAS-CE in the same package group
as the following packages: Optim Management
Server, Optim Manager, and
the Optim Shared Libraries.
- Optim Management Server
- The Optim Management Server
delegates the operations in an Optim service,
set up in the Optim Designer,
to one or more Proxies. The Management Server also manages the configuration
needed to find Proxies and delegates services to them. Only the Management
Server communicates with a Proxy. The Management Server also hosts
the Optim Manager.
The Optim Management Server requires
a J2EE application server.
The Optim Management
Server installation copies a Web Archive file (WAR), management-server.war,
to the computer.
You can install the Optim Management Server in the same package
group as the following packages: WAS-CE, Optim Manager, and the Optim Shared Libraries.
- Optim Manager
- The Optim Manager is a
web application used to run and monitor Optim data
management services. The Manager is displayed in a web browser connected
to an Optim Management Server.
The Optim Manager requires a J2EE application
server.
The Optim Manager
installation copies a Web Archive file (WAR), optim.war, to the computer.
You
can install the Optim Manager
in the same package group as the following packages: WAS-CE, Optim Management Server, and the Optim Shared Libraries.
- Optim Proxy
- The Optim Proxy is a distributed
process that executes data management services on the behalf of the Optim Management Server. For fastest
processing, install the Optim Proxy
on the same machine as the data source or on a computer with a fast
connection to the data source.
You cannot install
the Optim Proxy in the same
package group as the other Optim Manager
installation packages.
- Optim Shared Libraries
- The Optim Shared Libraries
component contains native libraries that are required by all Optim components (Optim Designer, Optim Manager, Optim Management Server, and Optim Proxy). This component must
be installed on every machine that has another Optim component installed and must be present
before any Optim component
can be executed on this computer.
This package also includes documentation
for Optim Designer and the Optim Manager environment.
You can install the Optim Shared Libraries in the same
package group as the following packages: WAS-CE, Optim Management Server, and Optim Manager. If the same version of Optim
Shared libraries is already installed on a computer, then you do not
need to install it again.
Coexistence considerations
Coexistence refers to the installed products on the same
computer.
Package group coexistence considerations
You can install multiple compatible products into the same
package group.
Coexistence within a package group
When
you install each product package, you select whether you want to install
the product package into an existing package group or whether you
want to create a new package group. IBM Installation
Manager offers only products that are designed to share a package
group and meet version compatibility and other requirements. If you
want to install more than one product at a time, the products must
be able to share a package group.
Any number of eligible products
can be installed to a package group. When a product is installed,
the product functions are shared with all of the other products in
the package group. If you install a development product and a testing
product into one package group, when you start either of the products,
you have both the development and testing functions available to you
in your user interface. If you add a product with modeling tools,
all of the products in the package group will have the development,
testing, and modeling functions available.
The
Optim version 2.1 components cannot exist on the same system as the
Optim version 2.2 components.
Coexistence between package groups
Multiple
instances of a product package can exist on the same computer and
they are automatically installed into separate package groups. The
product packages can be at different versions or fix levels.
If
you update a product package, you update only that instance of the
product.
Pre-installation tasks
Before you install, you might need to prepare or configure your
computer.
Pre-installation checklist
Review the following information and ensure the pre-installation
steps are completed as required.
__ 1.
If you are installing from an electronic image downloaded
from IBM Passport Advantage®, verify that
you have all the required parts and extracted the download files correctly.
__ 2.
(For Linux or Unix) If you are installing from physical
media, mount your DVD drive.
__ 3.
(For Linux or Unix) If you want the product to be used by
users other than root, then set the umask variable to 0022 before
you install the product. To set this variable, log in as root
user, start a terminal session, and type umask 0022.
__ 4.
(For Linux or Unix) Increase the number of file handles
on your computer.
__ 5.
Ensure that you are logged on to your computer with an
appropriate user ID.
__ 6.
Optional: If you are installing from an intranet
site, specify the repository.
Verifying and extracting electronic images
If you download the installation files from IBM Passport
Advantage, you must extract the electronic image from the compressed
files before you can install the software.
If you select the Download Director option for downloading
the installation files, the Download Director applet automatically
verifies the completeness of each file that it processes.
When extracting the installation files from the downloaded
compressed files, do the following things:
- Ensure that you preserve the directory structure of compressed
files when you extract them.
- Extract the contents of all of the compressed files to the same
directory. For Linux or Unix, do not include spaces in the directory
names, or you won't be able to run the command to start the launchpad
from a command line.
- You must not mix files from one install kit with another install
kit.
Mounting a drive
With some operating systems, such as Linux or Unix, you
must mount the appropriate drive before you can access data on the
product disc.
Important:
Insert the product disc into the drive
before mounting the drive.
For Linux or Unix:
- Log in as a user with root authority.
- Insert the DVD in the drive and enter the following command:mount
-t iso9660 -o ro /dev/cdrom /cdrom The /cdrom variable represents the mount
point of the DVD.
- Log out.
Some window managers can automatically mount your DVD drive
for you. Consult your computer documentation for more information.
Specifying the repository
A repository is a location for storing installation or
update package data. By default, IBM Installation
Manager uses an embedded URL in each product package to connect to
a repository server through the Internet and search for available
installation packages and new features. You can set these repository
locations on the Repositories page in the Preferences window.
Note:
Before starting the installation process, be sure to
obtain the installation package repository URL from your administrator
or IBM.
This task is only necessary to complete if you are installing
from a repository other than the default repository on the Internet
or the product media. For example, your organization might require
you to redirect the repository to use intranet sites.
The repository is located in the /repo directory
on the installation disc.
To specify a repository, complete the
following steps:
- Start IBM Installation
Manager.
- On the Start page, click File > Preferences.
- In the Preferences widow, click Repositories. The Repositories page opens, showing available repositories,
their locations, and whether they are connected.
- On the Repositories page, click Add
Repository.
- In the Add repository dialog box,
type the URL of the repository location or use Browse to
find a .zip or JAR file that contains a repository, a diskTag.inf
file, or the repository.config file of an expanded repository; then
click OK. The new repository
location is listed. If the repository is not connected, a red x is
displayed in the Connection column.
Note:
Updates
to packages can be stored in service repositories, for example IBM support sites or local update
repositories, which might be linked to the repositories you have listed
in the previous procedure. To search for updated packages in these
linked service repositories, make sure Search service repositories
during installation and updates is selected. This option
is selected by default.
- Click OK to close the Preferences window.
Installing software
To install your product package, follow the
procedures and information in these topics.
Installing IBM Optim Manager with
the Installation Manager Install wizard
This topic provides the instructions for installing Optim Manager with
the Installation Manager Install wizard.
Complete any necessary pre-installation
tasks.
This information describes how to start the product package
installation for a typical installation. You typically install the
product package using the installation launchpad and the Installation
Manager Install wizard. For information about how to install the product
package silently, see the silent installation information.
For
products that are installed by IBM Installation
Manager, starting the installation process causes IBM Installation Manager to start even if it
is not already installed. You will then install Installation Manager
on your computer during the process of installing the product package.
The installation wizard is pre-configured with the location of the
repository that contains the installation package.
Note:
If a new
version of Installation Manager is
found when you start the installation, you are prompted to confirm
that you want to install it before you can continue. Click OK to
proceed. Installation Manager automatically
installs the new version, stops, restarts, and resumes.
The launchpad includes options to perform either
an administrative or a non-administrative installation.
To install IBM Optim Manager with
the Installation Manager Install wizard:
- Insert the product DVD into your DVD drive. For Linux and Unix, ensure that you have mounted the DVD
drive.
If autorun is enabled on your computer,
the launchpad automatically opens.
To
start the installation manually, follow the next step.
- Optional: To start the installation
manually, run launchpad.exe or launchpad.sh,
which is located in the root directory of the DVD.
As
an alternative if you have already installed Installation Manager
separately, you can also start the installation process by following
these steps:
- Start Installation Manager.
- Configure the Installation
Manager repository preferences.
- Run the Installation Manager Install wizard to install the product
package.
- Optional: If you are installing with the launchpad,
read the product information.
- Optional: If you are installing with the launchpad,
click Install the IBM Optim Manager Components to
open the Installation Manager Install wizard.
- In the Install Packages page of
the Installation Manager Install wizard, select the packages to install:
- You can install the Optim Management
Server, Optim Manager, Optim Shared Libraries, and
WAS-CE packages at the same time.
- You must install the Optim Proxy
package separately.
- You can install updates at the same time that you install
the base product package, if updates are available. To search for
updates to the packages, click Check for Other Versions
and Extensions. Installation Manager searches
for updates at the predefined IBM update
repository for the product package. It also searches any repository
locations that you have set manually in the Installation Manager Preferences
window.
- To learn more about the packages that you can install,
click the package name. A description of the package is displayed
in the Details pane.
- Click Next.
- On the Licenses page, read the license agreements for the
selected packages. On the left-hand side of the License page,
click each package version to display its license agreement.
- If you agree to the terms of all of the license agreements,
click I accept the terms of the license agreements.
- Click Next to continue.
- If you are installing Installation Manager:
On the Location page, type the path for the shared resources directory in
the Shared Resources Directory field, or accept
the default path. If you are installing on Linux, ensure that you do not
include any spaces in the directory path. The shared resources
directory contains resources that can be shared by one or more package
groups.
Important:
You can specify the shared
resources directory only at the time that you install Installation Manager. Use
your largest disk for this to help ensure adequate space for the shared
resources of future packages. You cannot change the directory location
unless you uninstall all packages.
- Click Next to continue.
- On the Location page, create a package group to
install the product package into, or select an package group. A package group represents
a directory in which packages share resources with other packages
in the same group. To create a new package group:
- Click Create a new package group.
- Type the path for the installation directory for the
package group. (If you are installing on Linux, ensure that you do not
include any spaces in the directory path.) The name
for the package group is created automatically.
After you select a package group, click Next.
- On the Features page under Languages,
select the languages for the package group. The corresponding national
language translations for the user interface and documentation for
the product package will be installed.
- On the Summary page, review your choices before installing
the product package. If you want to change the choices that you made
on previous pages, click Back, and make your
changes. When you are satisfied with your installation choices, click Install to
install the package. A progress indicator shows the
percentage of the installation completed.
- When the installation process is complete, a message confirms
the success of the process.
- Click View log file to open the
installation log file for the current session in a new window. You
must close the Installation Log window to continue.
- Click Finish to launch the selected
package. The Install Package wizard closes and you are returned to
the Start page of Installation Manager.
- Close Installation Manager.
Complete any necessary post-installation
tasks.
- Related concepts
- Coexistence considerations
Coexistence refers to the installed products on the same computer.
- Installation terminology
Understanding these terms and conventions can help you take full advantage of the installation information and your product.
Installing silently
You can install a product package silently by using either
Installation Manager in silent installation mode or by using the Installation
Manager installer. When you run Installation Manager in silent mode,
the user interface is not available; instead, a response file inputs
the commands that are required to install the product package.
Silent installation road maps
The typical silent installation path is to use the Installation
Manager installer to install Installation Manager, and then to use
Installation Manager to record a response file, then to silently install
software packages. Optionally, you can use the Installation Manager
installer to install Installation Manager and software packages at
the same time. When you install in silent mode, the user interface
is not available; instead, a response file inputs the commands that
are required to install the software packages.
There are two main road maps for performing a silent installation.
- Use Installation Manager to silently install software packages:
- Install Installation Manager using the Installation Manager installer.
- Record a response
file using Installation Manager, or Create a response file manually.
- Run the Installation Manager
in silent mode to perform the operation silently.
- Use the Installation Manager installer to silently install software
packages:
- Create a response file manually that
includes commands to install Installation Manager and other packages.
- Run the Installation Manager
installer with the response file.
Using the Installation Manager installer
The Installation Manager installer is the tool used to
install Installation Manager silently. It can also be used to install
packages.
The Installation Manager installer is a command-line utility. Run
the Installation Manager installer to silently install and uninstall
Installation Manager. You can also install software packages using
the Installation Manager installer.
If you do not already have Installation Manager installed on your
computer, you might choose to use the Installation Manager installer
to install both Installation Manager and packages together using a
single command. This sample
response file provides an example for installing Installation
Manager and a software package. If you already have Installation
Manager installed on your computer, you can simply use Installation Manager to install
packages .
Installing Installation Manager silently
Use the Installation Manager installer to install Installation
Manager silently.
The Installation Manager installer is used to install
the Installation Manager. You can install the Installation Manager
as an administrator, or in non-administrator modes. Follow the example
below to install Installation Manager.
- Unzip the Installation Manager installer. The Installation
Manager kit is available from: http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/im/.
Select the version number that you want to install, for example 141/,
then select the zips directory.
- Switch to the InstallerImage_platform subdirectory.
- Enter one of the following commands:
- To install as an administrator on Windows: installc --launcher.ini
silent-install.ini -log <log file path and name> For
example: installc --launcher.ini silent-install.ini -log
c:\mylogfile.xml
- To install as non-administrator on Windows: userinstc --launcher.ini
user-silent-install.ini -log <log file path and name> For
example: userinstc --launcher.ini user-silent-install.ini
-log c:\mylogfile.xml
- For other platforms as an administrator: install
--launcher.ini silent-install.ini -log <log file path and name> For
example, install --launcher.ini silent-install.ini -log
/root/mylogs/mylogfile.xml
- For other platforms as non-administrator: userinst
--launcher.ini user-silent-install.ini -log <log file path and
name> For example, userinst --launcher.ini
user-silent-install.ini -log /root/mylogs/mylogfile.xml
After you install Installation Manager silently, you can use
Installation Manager or the Installation Manager installer to silently
install packages.
Changing the default installation location
You can change the default location for installing Installation
Manager by modifying the install.xml response file.
The Installation Manager installer uses a default response
file to install Installation Manager installer. You can modify the
file to change the default installation location.
- Go to the InstallerImage_platform directory
- Locate the response file install.xml
- Modify the location for installing Installation Manager
by adding profile information and using the data key and value attributes
to specify the installation location. The installation
location must be a directory named eclipse.
Changes were made to the default install.xml response
file to change the installation location to C:\IBM\InstallationManager.
<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean='true' temporary='true'>
<!-- add a profile and specify the installation location using the data value attribute. The location must end in \eclipse -->
<profile kind='self' installLocation='C:\IBM\InstallationManager\eclipse' id='IBM Installation Manager'>
<data key='eclipseLocation' value='C:\IBM\InstallationManager\eclipse'/>
</profile>
<server>
<repository location='.'/>
</server>
<!-- add the profile information but do not modify the features, id, and version number -->
<install>
<offering profile='IBM Installation Manager' features='agent_core,agent_jre' id='com.ibm.cic.agent' version='1.2.0.20080624_0100'/>
</install>
</agent-input>
Silently installing packages using the Installation Manager
installer
Use the Installation Manager installer to install Installation
Manager and other software packages.
To install software packages using the Installation Manager
installer, you must first create
a response file.
You can use the Installation Manager installer to silently
install Installation Manager and software packages at the same time.
Optionally, use the installer to install Installation Manager, then
use Installation Manager to install packages silently.
To silently
install packages using the Installation Manager installer, from the
InstallerImage_platform directory, enter the following
command:
- For Windows as administrator: installc.exe
--launcher.ini silent-install.ini -input <response file path and
name> -log <log file path and name>. For example: installc.exe
--launcher.ini silent-install.ini -input c:\myresponse\responsefile.xml
-log c:\mylog\silent_install_log.xml.
- For Windows as non-administrator: userinstc.exe
--launcher.ini user-silent-install.ini -input <response file path
and name> -log <log file path and name>. For example: userinstc.exe
--launcher.ini user-silent-install.ini -input c:\myresponse\responsefile.xml
-log c:\mylog\silent_install_log.xml .
- For other platforms as administrator: install
--launcher.ini silent-install.ini -input <response file path and
name> -log <log file path and name>. For example: install
--launcher.ini silent-install.ini -input /root/myresponse/responsefile.xml
-log /root/mylog/silent_install_log.xml
- For other platforms as non-administrator: userinst
--launcher.ini user-silent-install.ini -input <response file path
and name> -log <log file path and name>. For example: userinst
--launcher.ini user-silent-install.ini -input /root/myresponse/responsefile.xml
-log /root/mylog/silent_install_log.xml
The following table describes the arguments used with the
silent installation command:
Argument |
Description |
-vm |
Specifies the Java launcher.
In silent mode, always use java.exe on Windows, and java on other platforms. |
-nosplash |
Specifies that the splash screen should be suppressed. |
--launcher.suppressErrors |
Specifies that the JVM error dialog should be suppressed. |
-silent |
Specifies that the Installation Manager installer or Installation
Manager should be run in silent mode. |
-input |
Specifies an XML response file as the
input to Installation Manager installer or the Installation Manager.
A response file contains commands that installer or Installation Manager
runs. |
-log |
(Optional) Specifies a log file that records the result of
the silent installation. The log file is an XML file.
If your silent
installation session is successful, the log file will contain just
the root element of <result> </result>. However,
if errors occur during the installation, the silent install log file
will contain error elements and messages. |
-updateAll |
(Optional) All available updates to are installed. |
-installAll |
(Optional) All available products are installed. |
--launcher.ini silent-install.ini |
Specifies the location of the product .ini file to use.
If this argument is not specified, the executable will check for a
file in the same directory as the launcher with the same name and
the extension ".ini". For example, installc.exe checks for installc.ini.
The silent-install.ini file that is located in the same directory
as the installc.exe file contains the initialization parameters for
installing silently and should always be present. |
--launcher.ini user-silent-install.ini |
Specifies the location of the product .ini file to use
for a non-administrator install. If this argument is not specified,
the executable will check for a file in the same directory as the
launcher with the same name and the extension ".ini". For example,
install.exe checks for install.ini. The silent-install.ini file that
is located in the same directory as the install.exe file contains
initialization parameters that are applicable to installing silently
and should always be present. |
-accessRights |
Defines whether the IM operates in admin or nonAdmin mode.
For nonAdmin mode this argument should always be used with 'nonAdmin'
parameter:
-accessRights nonAdmin For admin mode it should
be used with admin parameter:
-accessRights admin
If
this argument is not used, the default value is set based on current
user permissions.
Note:
For Windows XP
users who are members of Administrator group, the default is always -accessRights
admin. For these users to run in nonAdmin mode -accessRights
nonAdmin argument should be passed explicitly. |
-showProgress |
Displays a progress bar to the console. |
-ShowVerboseProgress |
Displays progress text to the console. For example, the text
"Rebooting the machine to complete the install" is displayed when
a reboot is required. |
The Installation Manager installer has an initialization
or .ini file silent-install.ini (or user-silent-install.ini for
non-administrator installations) that includes default values for
the arguments in the table. For example, a default silent-install.ini
file might look something like this:
-accessRights
admin
-vm
C:\Program Files\IBM\Installation Manager\eclipse\jre_5.0.2.sr5_20070511\jre\bin\java.exe
-nosplash
--launcher.suppressErrors
-silent
-vmargs
-Xquickstart
-Xgcpolicy:gencon
If the installation is successful, it will return a status
of "0" an unsuccessful operation will return a non-zero number.
When
Installation Manager installer is run, it reads the response file
and (optionally) writes to a log file to the directory specified.
If you specified a log file and directory, the log file will be empty
if operation was successful, for example:
<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>
The log file will contain an error element if the
operation was not completed successfully.
A log file for Installation
Manager is also available. The default locations for the Installation
Manager log file are
- For Windows as non-admin:
C:\Documents and Settings\<my id>\Application Data\IBM\Installation
Manager\logs
- For Windows as admin:
C:\Documents and Settings\All Users\Application Data\IBM\Installation
Manager\logs
- For other platforms: /var/ibm/InstallationManager/logs
Installing silently with Installation Manager
Launch Installation Manager in silent mode with a response
file to install, uninstall, update, or modify packages silently. Installation
Manager is the tool that you typically use to install packages silently.
If you do not already have Installation Manager installed on your
computer, you can also use the Installation
Manager installer to install both Installation Manager and
packages together silently using a single command.
Silently installing packages using Installation Manager
Use Installation Manager in silent mode to install product
packages from a command line.
After you install Installation Manager, use it in silent
mode to install packages. This file explains how to install packages
using the Installation Manager.
To run Installation Manager
in silent mode, run the following command from the eclipse subdirectory
in the directory where you installed Installation Manager:
- For Windows: IBMIMc.exe
--launcher.ini silent-install.ini -input <response file path and
name> -log <log file path and name>. For example: IBMIMc.exe
--launcher.ini silent-install.ini -input c:\mylog\responsefile.xml
-log c:\mylog\silent_install_log.xml
- For other platforms: IBMIM
--launcher.ini silent-install.ini -input <response file path and
name> -log <log file path and name>. For example: IBMIM
--launcher.ini silent-install.ini -input /root/mylog/responsefile.xml
-log /root/mylog/silent_install_log.xml
The following table describes the arguments that are used
with the silent installation command:
Argument |
Description |
-vm |
Specifies the Java launcher.
In silent mode, always use java.exe on Windows, and java on other platforms. |
-nosplash |
Specifies that the splash screen should be suppressed. |
--launcher.suppressErrors |
Specifies that the JVM error dialog should be suppressed. |
-silent |
Specifies that the Installation Manager installer or Installation
Manager should be run in silent mode. |
-input |
Specifies an XML response file as the
input to Installation Manager installer or the Installation Manager.
A response file contains commands that installer or Installation Manager
runs. |
-log |
(Optional) Specifies a log file that records the result of
the silent installation. The log file is an XML file.
If your silent
installation session is successful, the log file will contain just
the root element of <result> </result>. However,
if errors occur during the installation, the silent install log file
will contain error elements and messages. |
-updateAll |
(Optional) Specifies that all available updates are installed. |
-installAll |
(Optional) Specifies that all available products are installed. |
--launcher.ini silent-install.ini |
Specifies the location of the product .ini file to use.
If this argument is not specified, the executable will check for a
file in the same directory as the launcher with the same name and
the extension .ini. For example, IBMIM.exe checks for IBMIM.ini and
install.exe checks for install.ini. The silent-install.ini file that
is located in the same directory as the IBMIM.exe file contains initialization
parameters that are applicable to installing silently and should always
be present. |
--launcher.ini user-silent-install.ini |
Specifies the location of the product .ini file to use
for Windows as non-admin.
If this argument is not specified, the executable will check for a
file in the same directory as the launcher with the same name and
the extension ".ini". For example, IBMIM.exe checks for IBMIM.ini.
The user-silent-install.ini file that is located in the same directory
as the IBMIM.exe file contains initialization parameters that are
applicable to installing silently and should always be present. |
-showProgress |
Displays a progress bar to the console. |
-ShowVerboseProgress |
Displays progress text to the console. For example, the text
"Rebooting the machine to complete the install" is displayed when
a reboot is required. |
-accessRights |
Specifies whether the Installation Manager operates in admin
or nonAdmin mode. For nonAdmin mode, this argument should always be
used with the 'nonAdmin' parameter:
-accessRights nonAdmin For
admin mode, this argument should be used with the 'admin' parameter:
-accessRights admin
If
this argument is not used, the default value is set based on current
user permissions.
Note:
For Windows XP
users who are members of Administrator group, the default is always -accessRights
admin. For these users to run in nonAdmin mode, the -accessRights
nonAdmin argument should be passed explicitly. |
The Installation Manager has an initialization
or .ini file silent-install.ini that includes default
values for the arguments in the table. For example, the silent-install.ini
file might look something like this:
-accessRights
admin
-vm
C:\Program Files\IBM\Installation Manager\eclipse\jre_5.0.2.sr5_20070511\jre\bin\java.exe
-nosplash
--launcher.suppressErrors
-silent
-vmargs
-Xquickstart
-Xgcpolicy:gencon
If the installation is successful, it will return a status
of "0" an unsuccessful operation will return a non-zero number.
When
Installation Manager installer is run, it reads the response file
and (optionally) writes to a log file to the directory specified.
If you specified a log file and directory, the log file will be empty
if operation was successful, for example:
<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>
The log file will contain an error element if the
operation was not completed successfully.
A log file for Installation
Manager is also available. The default locations for the Installation
Manager log file are
- For Windows as non-admin:
C:\Documents and Settings\<my id>\Application Data\IBM\Installation
Manager\logs
- For Windows as admin:
C:\Documents and Settings\All Users\Application Data\IBM\Installation
Manager\logs
- For other platforms: /var/ibm/InstallationManager/logs
Silently installing all available products using Installation
Manager
You can search for and silently install all available products
using the Installation Manager.
Follow these steps to find and install all available products
using Installation Manager in silent mode:
- On a command line, change to the eclipse subdirectory in
the directory where you installed Installation Manager.
- Enter and run the following command:
- For Windows: IBMIMc.exe
--launcher.ini silent-install.ini -installAll
- For other platforms: IBMIM
--launcher.ini silent-install.ini -installAll
All connected repositories are searched, and all available
products that are found are installed.
Silently installing updates to all installed products using
Installation Manager
You can use Installation Manager to silently search for
and install updates for all currently installed products.
Follow these steps to find and install all available updates
for products that are installed:
- On a command line, change to the eclipse subdirectory in
the directory where you installed Installation Manager.
- Enter and run the following command:
- For Windows: IBMIMc.exe
--launcher.ini silent-install.ini -updateAll
- For other platforms: IBMIM
--launcher.ini silent-install.ini -updateAll
All available product updates that are known to Installation
Manager are installed.
Silently installing from authenticated repositories with Installation
Manager
You can silently install from an authenticated repository;
however, authenticated repositories need the appropriate credentials
for access.
Installation Manager uses the Eclipse infrastructure (www.eclipse.org)
to save credentials in a file called a key ring file. While the contents
of the key ring file are encrypted, you can provide an additional
level of security by specifying a password to open the key ring file.
For additional information on key ring files, refer to the Eclipse
workbench user's guide available from www.eclipse.org.
To
access authenticated repositories in silent mode, complete the following
steps:
- Start Installation Manager in the user interface (UI) mode
and specify the following command-line parameters: -keyring <file>
-password <password>. For example, IBMIM
-keyring c:\my_directory\im.keyring
- When you use Installation Manager in UI mode and access
a protected repository, a window opens so that you can enter the credentials.
Enter the correct credentials and then save them. Ensure that the Save
password check box is selected. The credentials
are saved into the specified key ring file.
- Use the -keyring <file> -password <password> command
line parameter when starting Installation Manager in silent mode.
During silent install, the credentials for the protected repository
are retrieved from the key ring file specified in the command line.
For example:
- On Windows: IBMIMc.exe
--launcher.ini silent-install -input <input file path and name>
-keyring <key ring file path and name> -password <password>
- On other platforms: IBMIM
--launcher.ini silent-install -input <input file path and name>
-keyring <key ring file path and name> -password <password>
Silently uninstalling Installation Manager
Use the uninstall script to silently uninstall Installation
Manager.
The uninstall script is stored in the Installation Manager
uninstall directory. Follow these steps to silently uninstall Installation
Manager:
- On a command line, change to the uninstall directory for
the Installation Manager.
- For Windows, the
default location for non-administrator is: C:\Documents and
Settings\All Users\Application Data\IBM\Installation Manager\uninstall.
- For Windows, the
default location for administrator is: C:\Documents and Settings\<user
id>\Application Data\IBM\Installation Manager\uninstall.
- For other platforms, the default location
for non-administrator is: <userhomedirectory>/var/ibm/InstallationManager/uninstall
- For other platforms, the default location
for administrator is: /var/ibm/InstallationManager/uninstall
- Enter the following command:
- On Windows as administrator: uninstallc.exe
--launcher.ini silent-uninstall.ini
- On Windows as non-administrator:userinstc.exe
--launcher.ini silent-uninstall.ini
- On other platforms, enter: uninstall --launcher.ini
silent-uninstall.ini
Response files
A response file is an XML file that contains the data needed
to perform installation operations in silent mode.
Response files are used by both Installation Manager and the Installation
Manager installer to perform installation operations silently. You
can record a response file by recording preferences and installation
actions in Installation Manager in user interface mode, or you can
create one manually using the documented list of response file commands
and preferences.
A response file is an XML file that contains data read by Installation
Manager in silent mode. Using a response file, you can perform almost
any action that you can perform using Installation Manager in wizard
mode. For example, with a response file you can specify the location
of the repository that contains the packages, which package to install,
and which features to install for that package. You can also use a
response file to modify your installed package, to apply updates,
and to apply a license.Sample response file: Installing Installation Manager and packages
Recording a response file with Installation Manager
You can create a response file by recording your actions
in Installation Manager. When you record a response file, all of the
selections that you make in Installation Manager are stored in an
XML file. When you run Installation Manager in silent mode, Installation
Manager uses the data in the XML response file to perform the installation.
When you are recording a response file, you can choose to
perform the actions, for example installing a package, or you can
choose to just record the create a response file without performing
the actions. Note that when you are recording a response file, preferences
that you set, including repository settings, are not stored. Follow
these steps to record a response file:
- On a command line, change to the eclipse subdirectory in
the directory where you installed Installation Manager. For example:
- For Windows: cd
C:\Program Files\IBM\Installation Manager\eclipse
- For other platforms: cd /opt/IBM/InstallationManager/eclipse
- On a command line, type the following command to start
the Installation Manager, substituting your own file name and location
for the response file and (optionally) the log file:
- You can record a response file without performing any wizard
actions by adding the optional -skipInstall <agentDataLocation> argument.
Note that <agentDataLocation> must be a writable
directory.
For Windows: IBMIM
-record <response file and path name> -skipInstall <a writable
directory for agent data location>. For example IBMIM
-record c:\mylog\responsefile.xml -skipInstall c:\temp\recordData
When
you add this argument:
- The packages are not installed or uninstalled. The artifacts are
not be downloaded and the actions are not be executed.
- Installation Manager saves the data to the location that you specified.
- Recording the response file is faster, because the Installation
Manager is not performing actions, it is just recording the data.
You can use the same <agentDataLocation> in
the next recording session to record license management, updates,
or modifications to the product. These changes will be added to the
agent data location.
- Follow the on-screen instructions in the appropriate wizard.
If you copied the repository to a new location, you can set the location
of the repository using the File > Preferences > Repository Location dialog.
- Click Finish, then close Installation Manager.
An XML response file is created and saved in the location
that you specified in the command.
Creating a response file manually
If you want to use the silent installation capabilities of Installation
Manager, you need to create a response file that contains all of the commands
that Installation Manager must run. The recommended way to do this is to create
a response file by recording your actions as you install a package. However,
you can also create or edit a response file manually.
There are two categories of commands for the response file:
- Preference commands are
used to set preferences for Installation Manager that you set from the File > Preferences menu,
such as repository location information.
- Wizard commands are
used to emulate the install, update, modify, and uninstall wizards in Installation
Manager.
Response file commands
You can use this reference table to learn more about response
file commands.
Response file commands |
Description |
Profile
<profile
id="the profile (package group) id"
installLocation="the install location of
the profile">
<data key="key1" value="value1"/>
<data key="key2" value="value2"/>
</profile> |
A profile is an installation location. Use this command to
create a package group (or installation location). If the specified
package group already exists, then the command has no effect. Currently,
when creating the profile, the silent install will also create two
installation contexts; one for Eclipse and one
for native.
You can use the <data> element
to set profile properties.
The following list contains the currently
supported keys and related values:
- The eclipseLocation key specifies an existing
Eclipse location value, such as c:\myeclipse\eclipse.
- The cic.selector.nl key specifies the Natural
Language (NL) locale selections, such as zh, ja,
and en.
Note:
Separate multiple NL values with commas.
The
following list contains the language codes. Not every language is
supported in every product:
- English (en)
- French (fr)
- Italian (it)
- Simplified Chinese (zh)
- Russian (ru)
- Traditional Chinese (Taiwan) (zh_TW)
- Traditional Chinese (Hong Kong) (zh_HK)
- German (de)
- Japanese (ja)
- Polish (pl)
- Spanish (es)
- Czech (cs)
- Hungarian (hu)
- Korean (ko)
- Portuguese (pt_BR)
|
Repositories
<server>
<repository location="http://example/
repository/">
<repository location="file:/C:/
repository/">
<!--add more repositories below-->
<...>
</server> |
Use this command to specify the repositories that are used
during a silent installation. Use a URL or UNC path to specify remote
repositories; or use directory paths to specify local repositories. |
Install
<install>
<offering profile= "profile id"
features= "feature ids"
id= "offering id" version= "offering
version" selected="true"></offering>
<!--add more offerings below>
<...>
</install> |
Use this command to specify the installation packages that
will be installed.
The profile ID must match an existing profile
or a profile created by the set profile command.
Feature IDs
can be optionally specified by a comma-delimited list, such as "feature1,
feature2" and so on. If no feature IDs are specified, all the default
features in the specified offering will be installed.
Note:
Required
features will be included for installation, even if they are not explicitly
specified in the comma-delimited list.
The version number
is not required. If no version is specified, the Installation Manager
will install the most recent product with the specified id and any
available updates and fixes.
The 'selected' attribute is optional.
By default, 'selected' is set to "true". When 'selected' is set to
"false", silent install will not install the package. While running
in the wizard mode, the package will be displayed in the package selection
page but not selected initially. |
Update (in wizard mode)
<update>
<offering profile= "profile id">
</update> |
Use this command to specify the profile that will be updated.
The profile ID must match an existing profile.
Note:
This command
can only be used in wizard mode to invoke the update wizard; it does
not work in silent mode. |
Modify (in wizard mode)
<modify>
<offering profile= "profile id">
</modify> |
Use this command to specify the profile that will be modified.
The profile ID must match an existing profile.
Note:
This command
can only be used in wizard mode to invoke the update wizard; it does
not work in silent mode. |
Modify <install
modify="true"> or <uninstall modify="true"> (optional
attribute)
<uninstall modify="true">
<offering profile="profile id"
id="Id" version="Version"
features="-"/>
</uninstall> |
Use the <install modify="true"> attribute
on install and uninstall commands to indicate that you want to modify
an existing install. The default value is false.
If the intent of the modify operation is only to install additional
language packs, then a hyphen "-" should be used in the offering feature
id list to indicate that no new features are being added.
Important:
You must specify modify="true" and
a hyphen "-" for the features list as specified
in the example; otherwise, the install command will install the offering's
default features and the uninstall command will remove all of the
features. |
Uninstall
<uninstall>
<offering profile= "profile id"
features= "feature ids"
id= "offering id" version= "offering
version"></offering>
<!--add more offerings below>
<...>
</uninstall> |
Use this command to specify the packages that will be uninstalled.
The
profile ID must match an existing profile or a profile specified in
a profile command. In addition, if there are no feature IDs specified,
then all of the features in the specified offering will be uninstalled;
if there are no offering IDs specified, then all of the installed
offerings in the specified profile will be uninstalled. |
Rollback
<rollback>
<offering profile= "profile id"
id= "offering id"
version= "offering version">
</offering>
<!--add more offerings below
<...>
</rollback> |
Use this command to roll back to the specified offerings
from the version that is currently installed on the specified profile.
You cannot specify features in a roll back command. |
InstallAll
<installALL/>
Note:
This
command is equivalent to using
-silent -installAll . |
Use this command to silently search for and install all available
packages. |
UpdateAll
<updateALL/>
Note:
This
command is equivalent to using
-silent -updateAll . |
Use this command to silently search for and update all available
packages. |
License
<license policyFile="policy file
location"/>
For example:
<license policyFile="c:\mylicense.opt"/> |
If your product package requires an installed license, use
this command to generate a response file that contains a license command
by starting the license wizard after starting Installation Manager
in record mode.
During record mode, if you set flex options through
the license management wizard, the options that you set will be recorded
in a license policy file named "license.opt" in the same directory
as the generated response file and the response file will contain
a license command that references the policy file. |
Additional response file attributes
Response file attribute |
Description |
Clean
<agent-input clean="true">
</agent-input> |
By default, the clean attribute
is set to 'false'. Installation Manager will use the repository and
other preferences that are specified in the response file as well
as the existing preferences that are set in the Installation Manager.
If a preference is specified in the response file and set in the Installation
Manager, the preference that is specified in the response file takes
precedence.
If the clean attribute is
set to 'true', Installation Manager will use the repository and other
preferences that are specified in the response file and the existing
preferences that are set in the Installation Manager will not be used. |
Temporary
<agent-input clean="true" temporary="false">
</agent-input> |
By default, the temporary attribute
is set to 'false' and the preferences that are set in your response
file will be persisted. When you set the temporary attribute
to 'true', the preferences that are set in the response file will
not be persisted.
You can use the temporary and clean attributes
together. For example, if you set clean to 'true' and temporary to
'false', after running the silent install the repository setting that
is specified in the response file will override the preferences that
were set in the previous sessions using Installation Manager. |
License agreement acceptance
<agent-input acceptLicense="false">
</agent-input> |
By default, you do not agree to accept the licenses
that an installation package carries when using Installation Manager
in silent installation mode. If the package you are installing has
a license agreement that must be accepted, the silent installation
operation will fail. To accept the license agreement, you must set
the attribute to <agent-input acceptLicense="true">.
By doing so, you agree to accept the license agreements for every
package specified in the response file. |
Reboot later
<agent-input rebootLater="false">
</agent-input> |
By default, rebootLater is set to
'false' and if the response file installs any package that requires
rebooting the system on Windows,
Installation Manager will reboot the system after the execution of
the response file is finished.
When rebootLater is
set to 'true', the system will not reboot. |
Silent installation preference commands
Although you typically specify preferences using the Preferences
window, you can also specify preferences (identified as keys) in a
response file for use during a silent installation.
Note:
You can specify more than one preference in a response
file.
When you define preferences in a response file,
your XML code will look similar to the following example:
<preference
name = "the key of the preference"
value = "the value of the preference to be set">
</preference>
Use the following table to identify keys and
their associated values for silent installation preferences:
Key |
Value |
Notes |
com.ibm.cic.common.core.preferences.logLocation |
Specifies the location of Installation Manager log file. |
Important:
This key is optional and is designed
for testing and debugging. If you do not specify a location for the
log file, both silent installation and the UI version of Installation
Manager will use the same location. |
com.ibm.cic.license.policy.location |
Specifies a URL that defines where the remote license policy
file resides. |
Not required for products that do not require an installed
license. |
com.ibm.cic.common.core.preferences.http.proxyEnabled |
True or False |
Proxy servers enable connection to remote servers from behind
the firewall. False is the default value. Use this
option to enable an HTTP or SOCKS proxy. After the proxy is enabled,
the proxy will be used for all server communications. |
com.ibm.cic.common.core.preferences.http.proxyHost |
Host name or IP address |
|
com.ibm.cic.common.core.preferences.http.proxyPort |
Port number |
|
com.ibm.cic.common.core.preferences.http.proxyUseSocks |
True or False |
Proxy servers enable connection to remote servers from behind
the firewall. False is the default value. Enable
this option so that you can specify a SOCKS proxy host address (required)
and a SOCKS proxy port number (optional). |
com.ibm.cic.common.core.preferences.SOCKS.proxyHost |
Host name or IP address |
|
com.ibm.cic.common.core.preferences.SOCKS.proxyPort |
Port number |
|
com.ibm.cic.common.core.preferences.ftp.proxyEnabled |
True or False |
False is the default value. An FTP proxy
is an application-level gateway for FTP. An FTP proxy securely forwards
command and data streams between a client and server. This forwarding
function is useful to firewalls and FTP masquerades. An FTP proxy
also can fix connections to the FTP server and helps provide proxy
authentication. |
com.ibm.cic.common.core.preferences.ftp.proxyHost |
Host name or IP address |
|
com.ibm.cic.common.core.preferences.ftp.proxyPort |
Port number |
|
com.ibm.cic.common.core.preferences.eclipseCache |
c:\IBM\common (Windows)
/opt/IBM/common (Linux)
Note:
The
paths above are default values for this preference; typically, install
packages provide their own values for this preference. |
You cannot change this location if you have already installed
a package. |
com.ibm.cic.agent.core.pref.offering.service.repositories.areUsed |
True or False |
Change this preference to False to disable
it. When this preference is set to True, all linked
repositories will be searched when products are installed or updated. |
com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts |
True or False |
Change this preference to False to disable
it. When this preference is set to True, the files
that are required to roll the package back to a previous version are
stored on your system. When this preference is set to False,
these files are not stored. If you do not store these files, you must
connect to your original repository or media to roll back. |
com.ibm.cic.common.core.preferences.repositoryLocations_EDITABLE |
True or False |
Use this preference to specify whether users can make changes
to the repositories after the product is installed. |
com.ibm.cic.common.core.preferences.directArtifactAccessMode |
True or False |
The default is False. Before Installation
Manager begins the installation process, all required installation
files are downloaded to the shared repository location. When this
preference is set to True, Installation Manager
accesses the installation files directly from the input repositories
during the installation process instead of first downloading and verifying
them. |
com.ibm.cic.common.core.preferences.searchForUpdates |
True or False |
The default is False. When this preference
is set to True, Installation Manager searches for
updates to itself before performing the silent installation. |
Sample response files
You can use an XML-based response file to specify predefined
information such as silent installation preferences, repository locations,
installation profiles, and so on. Response files are beneficial for
teams and companies that want to install software packages silently
and to standardize the locations and preferences for the packages.
It can be helpful to record a response file and then tailor the
contents to suit your needs. See Recording a response file with Installation Manager for more information
on recording a response file.
Sample response files are also included on the installation disc,
in the scripts directory.
Sample response file: Installing Installation Manager and packages
This is a sample response file for installing Installation
Manager and a package at the same time.
Sample response file for installing Installation Manager
and a software package |
<agent-input clean="true" temporary="true">
<!-- add preferences -->
<preference name="com.ibm.cic.common.core.preferences.http.proxyEnabled"
value="false"/>
<!-- create the profile if it doesn't exist yet -->
<profile id="IBM Software Delivery Platform" installLocation="c:/temp/my_profile"></profile>
<server>
<repository location=
"http://a.site.com/local/products/sample/20090215_1542/repository/"></repository>
</server>
<!-- add the offerings and features to install. You can install Installation Manager and packages in one response file -->
<install>
<offering id="com.ibm.cic.agent" version="1.3.0.20090114_0637" />
<offering features="com.ibm.rad.sdpcore,com.ibm.rad.jre,com.ibm.rad.webtools_core,com.ibm.rad.pde,com.ibm.rad.data_tools" profile="IBMSoftware Delivery Platform" id="com.ibm.rational.application.developer" version="7006_20080320_1728"/>
</install>
</agent-input> |
Sample response file: Installing a package
This is a sample response file for installing a software
package.
Sample response file for a software package |
<agent-input>
<server>
<repository location=
"http://a.site.com/local/products/sample/20060615_1542/repository/"></repository>
</server>
<!-- use default installation location and choose the latest version of the offering that is available in the repository -->
<install>
<offering features= "core" id= "ies">
</offering>
</install>
</agent-input> |
Running Installation Manager with a response file in wizard
mode
You can install, update, modify, or uninstall software
packages with Installation Manager in wizard mode, using a response
file.
Installation Manager can be run in silent mode or wizard mode.
To start Installation Manager in wizard mode, enter the following
on the command line:IBMIM -mode wizard -input <response> where <response> is
the response file path and name.
Based on the commands in your response file, Installation Manager
will start in one of the following wizards: install, update, modify,
or uninstall. Your response file can only contain commands for one
of the Installation Manager wizards. For example, the response file
can include either:
- server, preference, and install commands
- server, preference, and update commands
- server, preference, and modify commands
- server, preference, and uninstall commands
Export data for problem analysis
You can generate a .zip file that contains data for problem
analysis. This file is used by IBM Support
to help troubleshoot the problem.
- On a command line, change to the eclipse subdirectory in
the directory where you installed Installation Manager.
- Enter and run the following command:
- For Windows: IBMIMc.exe
--launcher.ini silent-install.ini -exportInstallData <installDataFile>.
Where <installDataFile> is the name of the
file to be generated that contains the exported data in .zip file
format.
- For other platforms: IBMIM --launcher.ini
silent-install.ini -exportInstallData <installDataFile>.
Where <installDataFile> is the name of the
file to be generated that contains the exported data in .zip file
format.
A .zip file that contains the installation data is created.
Using the Installation Manager installer to perform other operations
If you cannot instal Installation Manager, the Installation
Manager installer can optionally be used to perform other silent installation
operations.
Installing all available products using the Installation Manager
installer
You can search for and silently install all available products
using the Installation Manager installer.
Follow these steps to find and install all available products
using Installation Manager installer:
- Switch to the InstallerImage_platform subdirectory.
- Enter and run the following command:
- For Windows as
admin: installc.exe --launcher.ini silent-install.ini
-installAll
- For Windows as
non-admin: userinstc.exe --launcher.ini user-silent-install.ini
-installAll
- For other platforms: install --launcher.ini
silent-install.ini -installAll
All available products found searching the connected repositories
are installed.
Silently installing updates to all products using the Installation
Manager installer
You can silently search for and install updates for all
installed products with the Installation Manager installer.
Follow these steps to find and install all available updates
for products that are installed.
- Switch to the InstallerImage_platform subdirectory.
- Select, enter and run the appropriate command:
- For Windows as
admin: installc.exe --launcher.ini silent-install.ini
-updateAll
- For Windows as
non-admin: userinstc.exe --launcher.ini user-silent-install.ini
-updateAll
- For other platforms: install --launcher.ini
silent-install.ini -updateAll
All available product updates known to Installation Manager
are installed.
Silently installing from authenticated repositories using the
Installation Manager installer
You can silently install from an authenticated repository;
however, authenticated repositories need the appropriate credentials
for access.
You must have Installation Manager installed to install a
software package from an authenticated repository.
Installation Manager uses the Eclipse infrastructure to save
credentials in a file called a key ring file. While the contents of
the key ring file are encrypted, you can provide an additional level
of security by specifying a password to open the key ring file. For
additional information on key ring files, refer to the Eclipse workbench
user's guide available from www.eclipse.org.
To access authenticated
repositories in silent mode, complete the following steps:
- Start Installation Manager in user interface mode and specify
the following command-line parameters: -keyring <file>
[-password <password>]. For example, installc
-keyring c:\my_directory\im.keyring
- When you use Installation Manager in wizard mode and access
a protected repository, a window opens where you can enter your credentials.
Enter the correct credentials and then save them. Ensure that the Save
password check box is selected. The credentials
are saved into the specified key ring file.
- From the eclipse directory in the location you installed
Installation Manager in silent mode and specify the following command
line parameter: -keyring <file> [-password <password>].
During silent install, the credentials for the protected repository
are retrieved from the key ring file specified in the command line.
- On a command line, enter the appropriate command:
- On Windows as admininstallc.exe
--launcher.ini silent-install -input <input file path and name>
-keyring <key ring file path and name> -password <password>
- On Windows as non-adminuserinstc.exe
--launcher.ini user-silent-install -input <input file path and
name> -keyring <key ring file path and name> -password <password>
- On other platforms, use install --launcher.ini
silent-install -input <input file path and name> -keyring <key
ring file path and name> -password <password>
Deploying and installing to the enterprise
If you need to install the product to multiple systems,
refer to the available articles on the installation Web site.
The Installation Manager information
center contains articles that will help you install your product in
an enterprise environment. Visit the information center for Installation
Manager 1.4.1 at http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.
Post-installation tasks
After you have installed your product package, complete the post-installation
tasks or configure your product package as required.
Post-installation checklist
After you have installed your product, complete several
tasks to configure and verify the installation.
Review the following information and ensure the post-installation
steps are completed as required.
Verify your installation and ensure that you can start
your product. For information about starting the Optim components, refer to the Configuring Optim Solution Components document.
Modifying installed product packages
The Modify Packages wizard in the IBM Installation Manager enables you to change
the feature and language selections of an installed product package.
You can also use the Modify Packages wizard to install new features
that might be included in a package update, such as a refresh pack.
By default, Internet access is required unless the repository
preferences points to a local update site. See the Installation Manager
help for more information.
Note:
Close all programs that were installed
using Installation Manager before modifying.
To modify an installed product package:
- Start IBM Installation
Manager.
- On the Start page, click Modify.
- In the Modify Packages wizard, select the product package
group and click Next.
- On the Languages page, select the languages for the package
group and click Next. The corresponding
national language translations for the user interface and documentation
for the packages will be installed. Note that your choices apply to
all packages installed under this package group.
- On the Features page, select the features that you want
to install or remove. Some products do not have optional features.
- To learn more about a feature, click the feature and
review the brief description under Details.
- If you want to see the dependency relationships between
features, select Show Dependencies. When you
click a feature, any features that depend on it and any features that
are its dependents are shown in the Dependencies window. As you select
or exclude features in the packages, Installation Manager will automatically
enforce any dependencies with other features and display updated download
size and disk space requirements for the installation.
- Click Next
- On the Summary page, review your choices before modifying
the installation package and click Modify.
- Optional: When the modification process completes,
click View Log File to see the complete log.
- Click Finish to close the wizard.
Updating installed product packages
Package updates provide fixes and updates to installed
product packages. You can use the Update Packages wizard
in IBM Installation Manager
to install updates for product packages that were installed by using IBM Installation Manager.
Internet access is required unless your repository preferences
points to a local update site.
Each installed package has the
location embedded for its default IBM update
repository. For Installation Manager to search the IBM update repository locations for the installed
packages, the preference Search service repositories during
installation and updates on the Repositories preference
page must be selected. This preference is selected by default.
See
the Installation Manager help for more information.
Important:
- Close all programs that were installed using Installation Manager
before updating.
- During the update process, Installation Manager might prompt you
for the location of the repository for the base version of the package.
If you installed the product from DVDs or other media, they must be
available when you use the update feature.
To find and install product package updates:
- Start IBM Installation
Manager.
- On the Start page of IBM Installation
Manager, click Update.
- Optional: If a required version of IBM Installation Manager is not
detected on your computer, you must continue with the update of Installation
Manager. Follow the instructions in the wizard to complete the update.
- In the Update Packages wizard, select the product package
group that you want to update or click the Update All check
box and click Next. Installation
Manager searches for updates in its repositories and the predefined
update sites for the product.
- On the Update page, if updates for a package are found,
they are displayed in the Updates list below
their corresponding package and only recommended updates are displayed
by default. Complete the following steps:
- To display all updates found for the available packages,
click Show all.
- To learn more about an update, click the update and
review its description under Details. If additional
information about the update is available, a More info link
will be included at the end of the description text. Click the link
to display the information in a browser. Review this information before
installing the update.
- Select the updates that you want to install or click Select
Recommended to restore the default selections. Updates
that have a dependency relationship are automatically selected or
cleared.
- Click Next.
- On the Licenses page, read the license agreements for the
selected updates. On the left side of the License page, the list of
licenses for the updates you selected is displayed; click each item
to display the license agreement text. If you agree to the terms of
all the license agreements, click I accept the terms of
the license agreements and Click Next.
- On the Features page, select the features that you want
to update and complete the following steps:
- To learn more about a feature, click the feature and
review the brief description under Details.
- If you want to see the dependency relationships between
features, select Show Dependencies. When you
click a feature, any features that depend on it and any features that
are its dependents are shown in the Dependencies window. As you select
or exclude features in the packages, Installation Manager will automatically
enforce any dependencies with other features and display updated download
size and disk space requirements for the installation.
- Click Next
- On the Summary page, review your choices before installing
the updates.
- If you want to change the choices you made on previous
pages, click Back, and make your changes.
- When you are satisfied, click Update to
download and install the updates. A progress indicator shows the percentage
of the installation completed.
- Optional: When the update process completes,
a message that confirms the success of the process is displayed near
the top of the page. Click View log file to
open the log file for the current session in a new window. You must
close the Installation Log window to continue.
- Click Finish to close the wizard.
- Optional: Only the features that you already
have installed are updated using the Update wizard.
If the update contains new features that you would like to install,
run the Modify wizard and select the new features
to install from the feature selection panel.
Reverting updates to previous versions
You can remove an update, such as a fix pack, to a product
package to revert to a previous version by using the Roll Back Packages
wizard of IBM Installation Manager.
During the rollback process, Installation Manager must access
files from the earlier version of the package. By default, these files
are stored on your computer when you upgrade to a new package. If
you have deleted the files that are saved locally for rollback or
cleared the Save files for rollback check box
in the Preferences page (File > Preferences > Files for
Rollback) while upgrading, you will not be able to roll
back to the previous version without the media or repositories that
were used to install that version of the package.
Use the rollback feature if you have applied an update
to a product package and decide later that you want to remove the
update and revert to the earlier version of the product. When you
use the rollback feature, Installation Manager uninstalls the updated
resources and reinstalls the resources from the previous version.
You can only roll back one version level at a time.
For more
information, see the Installation Manager online help or Information
Center.
To revert an update to a previous version, complete
the following steps:
- Start IBM Installation
Manager.
- On the Start page, click Roll Back.
- In the Roll Back Packages wizard, from the Package
Group Name list, select the package that you want to revert
to the previous version and click Next.
- Follow the instructions in the wizard.
Uninstalling software
You can use the Uninstall option
in IBM Installation Manager
to uninstall software that were installed by using Installation Manager
from your computer.
For Windows, you
can use the Control Panel and,
for Linux and UNIX, you can use the Uninstall IBM
Installation Manager icon on your computer's desktop
to uninstall IBM Installation
Manager.
Uninstalling product packages
You can use the Uninstall option
in IBM Installation Manager
to uninstall a product package from a single installation location.
You can also uninstall all the installed packages from every installation
location.
To uninstall a product package, you must log in to the system
by using the same user account that you used to install the product
package. You must close the programs that you installed by using IBM Installation Manager.
To uninstall a product package, complete the following steps:
- Start IBM Installation
Manager.
- On the Start page click Uninstall.
- On the Uninstall Packages page, from
the Installation Packages list, select the
product package that you want to uninstall and click Next.
- On the Summary page, review the list
of packages that will be uninstalled and click Uninstall. The Complete page is displayed after the packages are
removed.
- Click Finish.
Uninstalling IBM Installation
Manager
You can follow the instructions below to uninstall IBM Installation Manager.
Before you can uninstall IBM Installation
Manager, you must uninstall all of the packages, including products
that were installed by IBM Installation
Manager. You must close Installation Manager before attempting to
uninstall the program. You must log in to the computer by using the
same user account that you used to install Installation Manager.
To uninstall Installation Manager, complete the following
steps:
- To uninstall Installation Manager from Windows, complete the following steps: :
- Click Start > Control
Panel.
- In the Control Panel window, click Add
or Remove Programs.
- In the Add or Remove Programs window, select IBM
Installation Manager and click Remove.
- In the Add or Remove Programs dialog box,
click Yes to continue with the removal.
- To uninstall Installation Manager from Linux or Unix, complete
the following steps:
- Open a terminal window and run /var/ibm/InstallationManager/uninstall/uninstall if
this was an installation by root.
- In the IBM Installation
Manager Uninstall Packages wizard, click Next;
then click Uninstall.
Notices
Note to U.S. Government Users Restricted Rights - Use, duplication
or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information was developed for products and services offered
in the U.S.A. IBM may not offer the products, services, or features
discussed in this document in other countries. Consult your local IBM representative
for information on the products and services currently available in
your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual
property right may be used instead. However, it is the user's responsibility
to evaluate and verify the operation of any non-IBM product, program,
or service.
IBM may have patents or pending patent applications
covering subject matter described in this document. The furnishing
of this document does not grant you any license to these patents.
You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information,
contact the IBM Intellectual Property Department in your country
or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the
United Kingdom or any other country where such provisions are inconsistent
with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES
THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply to
you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided
for convenience only and do not in any manner serve as an endorsement
of those Web sites. The materials at those Web sites are not part
of the materials for this IBM product and use of those Web sites
is at your own risk.
IBM may use or distribute any of the information
you supply in any way it believes appropriate without incurring any
obligation to you.
Licensees of this program who wish to have information about it
for the purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged,
should contact:
Intellectual Property Department
IBM Corporation
Silicon Valley Lab
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.
Such information may be available, subject to appropriate terms
and conditions, including in some cases, payment of a fee.
The licensed program described in this documentation and all licensed
material available for it are provided by IBM under
terms of the IBM Customer Agreement, IBM International
Program License Agreement or any equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers
of those products, their published announcements or other publicly
available sources. IBM has not tested those products
and cannot confirm the accuracy of performance, compatibility or any
other claims related to non-IBM products. Questions on the capabilities
of non-IBM products should be addressed to the suppliers of those
products.
All statements regarding IBM's future direction or intent are subject
to change or withdrawal without notice, and represent goals and objectives
only.
Trademarks and service marks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corporation in the United States,
other countries, or both. These and other IBM trademarked terms are
marked on their first occurrence in this information with the appropriate
symbol (® or ™), indicating US registered or common law trademarks
owned by IBM at the time this information was published. Such trademarks
may also be registered or common law trademarks in other countries.
A complete and current list of IBM trademarks is available on the
Web at http://www.ibm.com/legal/copytrade.shtml
Microsoft and Windows are trademarks of Microsoft Corporation in
the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.
UNIX is a registered trademark of The Open Group in the United
States and other countries.
Other company, product or service names, may be trademarks or service
marks of others.