IBM Rational Application Developer
, Version 7.0
Installation guide
Version 7.0
Note
Before using this information and the product it supports, read the information
in Notices.
First Edition (December 2006)
This edition applies to version 7.0 of IBM Rational Application Developer (part number
5724-J19) and to all subsequent releases and modifications until otherwise
indicated in new editions.
Copyright International Business Machines Corporation 2000, 2006. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Overview
This installation guide provides instructions for installing and
uninstalling IBM(R) Rational(R) Application Developer.
Refer to the readme file for
information about installation issues and limitations.
Note:
Refer to
http://www.ibm.com/software/rational/support/documentation/ for updated documentation and troubleshooting
information.
IBM Installation
Manager
IBM Installation Manager is a
program that helps you install the Rational Application Developer product
packages on your workstation. It also helps you update, modify, and uninstall
this and other packages that you install. A package can be a product, a group
of components, or a single component that is designed to be installed by Installation Manager.
Regardless of which installation scenario you follow to install Rational Application Developer on
your workstation, use Installation Manager to
install your Rational package.
IBM Installation Manager offers
a number of time-saving features. It keeps track of what you are about to
install, software components that you have already installed, and components
that are available for you to install. It searches for updates so you know
that you are installing the latest version of a Rational product package. Installation Manager also
provides tools for managing licenses for the product packages that it installs.
It provides tools for updating and modifying packages. You can also use Installation Manager to uninstall
product packages.
IBM Installation Manager comprises
five wizards that make it easy to maintain your product packages through their
lifecycles:
- The Install Packages wizard walks you through the
installation process. You can install a product package by simply accepting
the defaults, or you can modify the default settings to create a custom installation.
Before you install a product package, you are provided with a complete summary
of the selections that you have made throughout the wizard. With the wizard
you can install one or more product packages at the same time.
- The Update Packages wizard searches for available
updates to product packages that you have installed. An update might be a
released fix, a new feature, or a new version of the Rational product. Details of the contents
of the update are provided in the wizard. You can choose whether to apply
an update.
- With the Modify Packages wizard you can modify specific
elements of a package that you have already installed. During your initial
installation of the product package, you select the features 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 product package installation. You can
also remove features, and add or remove languages.
- The Manage Licenses wizard helps you to 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.
- The Uninstall Packages wizard helps you to remove
a product package from your computer. You can uninstall more than one package
at a time.
The IBM Rational Software
Development Platform is a common development environment that contains the
development workbench and other software components that share multiple products.
The development platform includes the following offerings:
- Rational Application Developer
- Rational Application Developer Community Edition
- Rational Functional Tester
- Rational Performance Tester
- Rational Software Architect
- Rational Software Modeler
- Rational Systems Developer
Also available but not part of the platform is Rational Manual Tester. Manual Tester is included
with Rational Functional Tester,
or it can be purchased separately.
About Rational Application Developer
IBM Rational Application Developer for WebSphere(R) Software
is a comprehensive integrated development environment with full support for
the J2EE programming model, including accelerated Web, Java(TM), Web
services, and Enterprise JavaBeans(TM) (EJB)development.
The IBM Support Assistant (ISA) is a free local
software serviceability workbench for Linux(R) operating systems that helps you
resolve questions and problems with IBM software products. It provides quick
access to support-related information along with serviceability tools for
problem determination. For more information refer to http://www.ibm.com/software/support/isa/.
Installation requirements
This section details hardware, software, and user privilege requirements
that must be met in order to successfully install and run your software.
Hardware requirements
Before you can install the product, verify that your system meets
the minimum hardware requirements.
Software requirements
Before you can install the product, verify that your system meets
the software requirements.
Operating system
The following operating systems
are supported for this product:
- Microsoft Windows(R) XP
Professional with Service Pack 1 or 2
- Windows XP Professional x64 Edition
(running on AMD processor)
- Microsoft Windows 2000
Professional with Service Pack 4
- Microsoft Windows 2000
Server with Service Pack 4
- Microsoft Windows 2000
Advanced Server with Service Pack 4
- Microsoft Windows Server
2003 Standard Edition with Service Pack 1
- Microsoft Windows Server
2003 Enterprise Edition with Service Pack 1
- Red Hat Enterprise Linux Workstation
Version 4.0
- Red Hat Desktop Version 4.0 (running
in 32-bit mode)
- SUSE Linux Enterprise Server (SLES) Version
9 (all service packs; running in 32-bit mode)
Note:
The listed operating systems support
all of the languages that are supported by Rational Application Developer.
Note:
This
version of the IBM Rational Software Development Platform was
developed for use with Eclipse ID 3.2.1 with updates. You can only
extend
an existing Eclipse IDE of version 3.2.1 with latest updates from eclipse.org.
If
you use SUSE Linux Enterprise
Server (SLES) Version 9, then you must have the IBM JRE 1.5 (SR3) installed
before you can extend an existing Eclipse IDE.
Additional software requirements
User privileges requirements
You must have a user ID that meets the following requirements before
you can install Rational Application Developer.
- Your user ID must not contain double-byte characters.
-
You
must have a user ID that belongs to the Administrators group.
-
You must be able to log in as root.
Planning to install
Read all the topics in this section before you begin to install
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 scenarios
There are a number of scenarios that you can follow when installing Rational Application Developer.
The following are some of the factors that might determine your installation
scenario:
- The format and method by which you
access your installation files (for example, from CDs or files downloaded
from IBM Passport
Advantage(R)).
- The location for your installation (for example, you can install the product
onto your own workstation, or make the installation files available to your
enterprise}.
- The type of installation (for example, you can use the Installation Manager
GUI, or install silently).
These are the typical installation scenarios you might follow:
- Installing from the CDs.
- Installing from a downloaded electronic image on your workstation.
- Installing from an electronic image on a shared drive.
- Install from a repository on an
HTTP or HTTPS server.
Note that in the latter three scenarios you can choose to run the Installation
Manager program in silent mode to install Rational Application Developer.
For details on running Installation Manager in silent mode, see Installing silently.
Installing from CDs
In this installation scenario,
you have the CDs that contain the product package files, and typically you
are installing Rational Application Developer on
your own workstation. Refer to Installing Rational Application Developer from
CDs: task overview for
an overview of the steps.
Installing from a downloaded electronic image on your workstation
In this scenario, you have downloaded
the installation files from IBM Passport Advantage and you will install Rational Application Developer on your
own workstation. Refer to Installing Rational Application Developer from
an electronic image on your workstation: task overview for
an overview of the steps.
Installing from an electronic image on a shared drive
In
this scenario, you will place the electronic image on a shared drive so that
users in your enterprise can access the installation files for Rational Application Developer from
a single location. Refer to Installing Rational Application Developer from
an electronic image on a shared drive: task overview for
an overview of the steps.
Installing
from a repository on an HTTP server
This scenario represents the
fastest method for installing the product across a network. This scenario
differs from the shared-drive installation, In order to place product package
files for Rational Application Developer on
an HTTP Web server, you must use this utility application - IBM Packaging
Utility. This utility is provided with Rational Application Developer to
copy the installation files in a format - a package - that can be used
for installing Rational Application Developer directly
from a HTTP Web server. The directory on the HTTP Web server that contain
the package is called a repository. Note that, in this scenario, the
installation files for only Rational Application Developer are
placed in the package. Refer to Installing Rational Application Developer from
a repository on a HTTP Web server: task overview and Placing Rational Application Developer on
an HTTP Web server: task overview for an overview of the steps.
Deciding which features to install
With version 7.0, you can customize your software product by selecting
which features of Rational Application Developer to
install.
When you install the Rational Application Developer product
package 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.
Note:
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. See
Modifying installations for
more information.
Features
The following table shows the features of Rational Application Developer that
you can choose to install. Default selections of features to install may vary.
If a feature already exists in your shared resources directory, it will not
be selected by default and will not be installed again.
Feature |
Description |
Selected for installation by default |
Web development tools |
Provides tools for building J2EE Web applications using JavaServer
Faces, JavaServer Pages, servlets, and HTML. |
Yes |
Struts tools |
Provides tools for developing J2EE Web applications using the Apache
Struts framework. |
No |
Crystal Reports tools |
Provides visual tools for developing applications that require reporting
capabilities that Crystal Reports provides. |
Yes |
J2EE and Web Services development tools |
Provides tools for developing J2EE applications and Web services. |
Yes |
Java client application editor |
Provides tools for building and testing graphical user interface Java client
applications using the SWT, AWT, or Swing UI libraries. |
Yes |
Visualization editors |
Provides a graphical editing environment for creating Java classes,
enterprise beans, data tables, and XML schemas. |
Yes |
Code review |
Inspects your code for rule compliance and best practices. Code review
highlights potential problems and suggests code changes for improved quality.
In some cases, it can automatically apply fixes for compliance. |
Yes |
Test and Performance Tools Platform (TPTP) |
Provides Eclipse tools for testing applications. Tool capabilities
include profiling, monitoring, logging, component testing (Junit), and static
analysis or code review. |
Yes |
J2EE Connector (J2C) tools |
Provides a robust set of tools to help you create J2C client applications
for CICS(R) and IMS(TM) systems.
Use the data binding wizards to create Java marshalling code for COBOL, PL/I, and
C languages. |
No |
Rational ClearCase(R) SCM
Adapter |
Provides the IBM Rational ClearCase SCM and ClearCase MVFS
plug-ins, which enable creating managed versions of software artifacts in ClearCase versioned
object bases (VOBs). These plug-ins use snapshot views and dynamic views when ClearCase VOB
and view servers are also installed. |
Yes |
Rational RequisitePro(R) integration
(for Windows only) |
Provides a tightly integrated requirements management tool with traceability
between requirements and software artifacts when IBM Rational RequisitePro is installed. |
No |
Rational
Unified Process(R) (RUP(R)) Process Advisor and Process Browser |
Provides the Process Advisor, for context-sensitive guidance on developing
software and using the IBM Rational Software Development Platform, and the
Process Browser, for help related to your current tasks, artifacts, and tools. |
Yes |
Transformation authoring |
Provides tools to create custom transformations and customize existing
transformations. Transformations automate the task of generating model content
and implementation code. |
No |
Plug-in development environment (PDE) |
Provides tools for creating, developing, testing, debugging, and
deploying Eclipse plug-ins, which can be used to extend the Eclipse environment. |
No |
Java Emitter Template (JET) extensibility |
Using the JET technology extensibility features, you can develop
JET transformations and control the JET engine through programming interfaces
(APIs), extension points, and utilities. |
No |
Data tools |
Provides relational database tools for defining and working with
databases. You can define and work with tables, views, and filters; create
and work with SQL statements; create and work with DB2(R) routines, and create and work with SQLJ
files. You can also use the tools to generate SQL DDL, DADX, and XML files. |
No |
Portal tools |
Provides tools to create, customize, test, debug, and deploy portal
applications. The Portal development tools support IBM WebSphere Portal versions 5.1 and
6.0. |
No |
WebSphere Application
Server development tools |
Provides tools for WebSphere Application Server development. |
Yes |
WebSphere Application
Server compile-time dependencies |
Provides required components for building, compiling, debugging,
and deploying applications for IBM WebSphere Application Server. |
Yes |
IBM WebSphere Application
Server Express, version 5.1 |
Provides IBM WebSphere Application Server Express, version 5.1,
as your targeted runtime environment. |
No |
IBM WebSphere Application
Server, version 5.1 |
Provides IBM WebSphere Application Server, version 5.1, as your
targeted runtime environment. |
No |
IBM WebSphere Application
Server, version 6.0 |
Provides IBM WebSphere Application Server, version 6.0, as your
targeted runtime environment. |
No |
IBM WebSphere Application
Server, version 6.1 |
Provides IBM WebSphere Application Server, version 6.1, as your
targeted runtime environment. |
Yes |
Upgrade and coexistence considerations
If you have a previous version of the product, or if you plan to
install multiple Rational Software Development Platform products
on the same workstation, review the information in this section.
Offering coexistence considerations
Some products are designed to coexist and share function when they are
installed in the same package group. A package group is a location where you
can install one or more software products or packages. When you install each
package, you select whether you want to install the package to an existing
package group, or whether you want to create a new one. IBM Installation
Manager will block products that are not designed to share or do not meet
version tolerance 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.
At the time of release, the following products will share function when
installed to a package group:
- Rational Application
Developer
- Rational Software
Architect
- Rational Functional
Tester
- Rational Performance
Tester
- Rational Software
Modeler
- Rational Systems
Developer
Any number of eligible products can be installed to a package group. When
a product is installed, its function is 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 functionality 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 functionality available.
If you install a development product and later purchase a development product
with increased functionality and add that product to the same package group,
the additional function will be available in both products. If you uninstall
the product with the greater functionality, the original product remains.
Note that this is a change from the 'upgrade' behavior of version 6 products
in the Rational Software
Development Platform group.
Note:
Each product installed into a unique location may
be associated with only one package group. A product must be installed into
multiple locations in order to be associated with multiple package groups. Rational Functional Tester and Rational Performance Tester can be
installed into only one location on a computer.
Upgrade considerations
You cannot change a previous version of Rational Application Developer that
is already installed on your workstation to version 7.0. However, Rational Application Developer version
7.0 can coexist with earlier versions.
You can migrate your workspace, projects and artifacts from WebSphere Studio
Developer version 5.1.2 and Rational Application Developer version
6.0 to version 7.0. Refer to the migration documentation in the online help
for details.
Note that the first time you start Rational Application Developer version
7 it defaults to a new workspace. Do not open your existing workspace in Rational Application Developer version
7.0 until you read the migration documentation.
If you have a previous version of Agent Controller, you should stop it,
uninstall it, and clean up any leftover files before installing this version
of Agent Controller. For more information, refer to Chapter 6, "Installing
Agent Controller".
Installation repositories
IBM Installation Manager retrieves
product packages from specified repository locations.
If the launchpad is used to start Installation Manager,
the repository information is passed to Installation Manager.
If the Installation Manager is
started directly, you must specify an installation repository that contains
the product packages that you want to install. See Setting repository preferences in Installation Manager.
Some organizations bundle and host their own product packages on their
intranet. For information about this type of installation scenario, see Installing
from a repository on an HTTP server.
Your system administrators will need to provide you with the correct URL.
By default, IBM Installation Manager uses
an embedded URL in each Rational software development product to connect
to a repository server over the Internet. Installation Manager then searches
for the product packages as well as new features.
Setting repository preferences in Installation Manager
When you start the installation of Rational Application Developer from
the launchpad program, the location of the repository that contains
the product package you are installing is automatically defined in IBM Installation
Manager when it starts. However, if you start Installation Manager directly
(for example, installing Rational Application Developer from
a repository located on a Web server) then you must specify the repository
preference (the URL for the directory that contains the product package) in
Installation Manager before you can install the product package. Specify these
repository locations on the Repositories page of the Preferences window. By
default, Installation Manager uses an embedded URL in each Rational software
development product to connect to a repository server through the Internet
and search for installable packages and new features. Your organization may
require you to redirect the repository to use intranet sites.
Note:
Before starting the installation process, be sure to obtain
the installation package repository URL from your administrator.
To add, edit, or remove a repository location in Installation Manager:
- Start Installation Manager.
- On the Start page of Installation Manager, click File -> Preferences,
and then click Repositories. The Repositories
page opens, showing any available repositories, their locations, and whether
they are accessible.
- On the Repositories page, click Add
Repository.
- In the Add repository window, type the URL
of the repository location or browse to it and set a file path.
- Click OK. If you entered a HTTPS repository
location, then you will be prompted to enter a user ID and password. The new or changed repository location is listed. If the repository
is not accessible, a red x is displayed in the Accessible column.
- Click OK to exit.
Package groups and the shared resource directory
When you install the Rational Application Developer package
with IBM Installation Manager, you
must choose a package group and a shared resource directory.
Package groups
During the installation process,
you must specify a package group for the Rational Application Developer package.
A package group represents a directory in which packages share resources with
other packages in the same group. When you install the Rational Application Developer package
with Installation Manager,
you can create a new package group or install the packages into an existing
package group. (Some packages might not be able to share a package group,
in which case the option to use an existing package group will be disabled.)
Note
that when you install multiple packages at the same time, all the packages
are installed into the same package group.
A package group is assigned
a name automatically; however, you choose the installation directory for the
package group.
After you create the package group by successfully installing
a product package, you cannot change the installation directory. The installation
directory contains files and resources specific to the Rational Application Developer product
package installed into that package group. Resources in the product package
that can potentially be used by other package groups are placed in the shared
resources directory.
Shared resources directory
The shared resources
directory is the directory where installation artifacts are located so
that they can be used by one or more product package groups.
Important:
You
can specify the shared resources directory once: the first time that you install
a package. We suggest that you use your largest drive for this. You cannot
change the directory location unless you uninstall all packages.
Extending an existing Eclipse IDE
When you install the Rational Application Developer product
package, you can choose to extend an Eclipse integrated development environment
(IDE) already installed on your computer by adding the functions that the Rational Application Developer package
contains.
The Rational Application Developer package
that you install with IBM Installation Manager is
bundled with a version of the Eclipse IDE or workbench; this bundled workbench
is the base platform for providing the functionality in the Installation Manager package.
However, if you have an existing Eclipse IDE on your workstation, then you
have the option to extend, that is, add to the IDE the additional functionality
provided in the Rational Application Developer package
- that Eclipse instance.
To extend and existing Eclipse IDE: in the Location page of the Install
Packages wizard, select the Extend an existing Eclipse IDE option.
You might extend your existing Eclipse IDE, for example, because you want
to gain the functionality provided in the Rational Application Developer package,
but you also want to have the preferences and settings in your current IDE
when you work with the functionality from the Rational Application Developer package.
You also might want to work with plug-ins you have installed that already
extend the Eclipse IDE.
Your existing Eclipse IDE must be version 3.2.1 plus the latest updates
from eclipse.org to be extended. Installation Manager checks
that the Eclipse instance you specify meets the requirements for the installation
package.
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 Rational Application Developer.
You may want to verify the completeness of the downloaded files before extracting
the image.
You can compare the published MD5 values with the checksum of
the downloaded files to check if the downloaded file is corrupt or incomplete.
Extract each compressed file to the same directory.
Do
not include spaces in the directory names, or you won't be able to run the
launchpad.sh command to start the launchpad from a command line.
Preinstallation tasks
Before you install the product, complete these steps:
- Confirm that your system meets the requirements described in the
section Installation requirements.
- Confirm that your user ID meets the required access
privileges for installing the product. See User privileges requirements.
- Read the section Planning to install and give particular attention to
the topic Upgrade and coexistence considerations.
-
If you want to enable the product to be
used by users other than root, then you must set to 0022, the umask variable before
you install the product. To set this variable, log in as root user, start
a terminal session, and type umask 0022.
Installation tasks
The following sections provide an overview of the installation scenarios
that are described in the section Installation scenarios.
You can access detailed instructions from links in the main steps.
Installing Rational Application Developer from
CDs: task overview
In this installation scenario, you have the CDs that contain the
installation files, and typically you are installing Rational Application Developer on
your own workstation.
The following are the general steps for installing from CDs:
- Complete the preinstallation steps listed in Preinstallation tasks.
- Insert the first installation CD into your CD drive.
-
Mount the CD drive.
- If autorun is enabled on your system, the Rational Application Developer launchpad
program automatically opens. If autorun is not enabled, start the launchpad
program. Refer to Starting the launchpad program for
details.
- Start the installation of Rational Application Developer from
the launchpad. For details, see Starting an installation from the launchpad program.
If IBM Installation
Manager is not detected on your workstation, you are prompted to install it
and then the installation wizard starts. Follow the on-screen instructions
in the wizard to complete the installation of Installation Manager. See Installing Installation Manager on Windows for details.
When
the installation of Installation Manager completes, or if it is already on
your computer, Installation Manager starts and automatically begins the Install
Packages wizard.
- Follow the on-screen instructions in the Install Packages wizard
to complete the installation. For details, see Installing IBM Rational Application Developer using
the IBM Installation Manager graphical
interface.
- Configure your license. By
default, a trial license for Rational Application Developer is
included. You must configure the license to ensure that you have continued
access to the product. Refer to Managing licenses for
details.
-
Increase the number of file handles on
your workstation. For details, see Increasing the number of file handles on Linux workstations.
- Install
optional software that is included with Rational Application Developer. For more information, see Installing optional software.
Installing Rational Application Developer from
an electronic image on your workstation: task overview
The following are the general steps for installing Rational Application Developer from
an electronic installation image.
- Ensure that your workstation has sufficient space to store both
the files you must download from IBM Passport Advantage and the
extracted installation image. Refer to Hardware requirements.
- Download all required parts for the product image from IBM Passport
Advantage to a temporary directory.
- Extract the installation image from the downloaded file and verify
that the installation image is complete. See Verifying and extracting electronic images for
details.
- Continue with the steps in Installing from an electronic image below.
Installing from an electronic image
- Complete the preinstallation steps listed in Preinstallation tasks.
- Start the launchpad program. Refer to Starting the launchpad program for
details.
- Start the installation of Rational Application Developer from
the Launchpad. For details, see Starting an installation from the launchpad program.
If IBM Installation
Manager is not detected on your workstation, you are prompted to install it
and then the installation wizard starts. Follow the on-screen instructions
in the wizard to complete the installation of Installation Manager. See Installing Installation Manager on Windows for details.
When
the installation of Installation Manager completes, or if it is already on
your system, Installation Manager starts and automatically begins the Install
Packages wizard.
- Follow the on-screen instructions in the Install Packages wizard
to complete the installation. For complete details, see Installing IBM Rational Application Developer using
the IBM Installation Manager graphical
interface.
- Configure your license. By
default, a trial license for Rational Application Developer is
included. You must configure the license to ensure you have continued access
to the product. Refer to Managing licenses for details.
-
Increase the number of file handles on
your workstation. For details, see Increasing the number of file handles on Linux workstations.
- Install
optional software that is included with Rational Application Developer.For more information, see Installing optional software.
Installing Rational Application Developer from
an electronic image on a shared drive: task overview
In this scenario, you will place the electronic image on a shared
drive so that users in you enterprise can access the installation files for Rational Application Developer from a single
location.
The following steps are performed by the person who places the installation
image on a shared drive.
- Ensure that your shared drive has sufficient disk space to store
both the files you must download from IBM Passport Advantage and the
extracted installation image. Refer to Hardware requirements for
details.
- Download all required parts for the product image from IBM Passport
Advantage to a temporary directory on the shared drive.
- Extract the installation image from the downloaded files into an
accessible directory on the shared drive and verify the installation image
is complete. See Verifying and extracting electronic images for details.
To install Rational Application Developer from
the installation files on the shared drive:
- Change to the disk1 directory on the shared drive containing the installation
image.
- Follow the steps in Installing from an electronic image.
Installing Rational Application Developer from
a repository on a HTTP Web server: task overview
In this scenario, the product packages are retrieved by IBM Installation Manager from
an HTTP Web server.
These steps assume the repository containing the package for Rational Application Developer has
been created on the HTTP Web server.
To install the Rational Application Developer package
from a repository on an HTTP server:
- Complete the preinstallation steps listed in Preinstallation tasks.
- Install IBM Installation Manager.
Refer to Managing IBM Installation Manager. In this scenario, for example, the Installation Manager installation
files are available from a shared drive.
- Start Installation Manager.
Refer to Starting Installation Manager on Windows for
details.
- Set the URL of the repository containing the package of Rational Application Developer as
a repository preference in Installation Manager. See Setting repository preferences in Installation Manager.
- Start the Install Packages wizard in Installation Manager and follow
the on-screen instructions in the Install Packages wizard to complete the
installation. For complete details, see Installing IBM Rational Application Developer using
the IBM Installation Manager graphical
interface.
- Configure your license. By
default, a trial license for Rational Application Developer is
included. You must set the license to ensure you have continued access to
work with the product. Refer to Managing licenses for
details.
-
Increase the number of file handles on
your workstation. For details, see Increasing the number of file handles on Linux workstations.
- Install
optional software included with Rational Application Developer. For more information, see Installing optional software.
Placing Rational Application Developer on
an HTTP Web server: task overview
To prepare Rational Application Developer for
installation from a repository located on an HTTP Web server:
- Ensure that your HTTP or HTTPS Web server has sufficient disk space
to store the product package. Refer to Hardware requirements.
- Ensure that your workstation has sufficient disk space to store
both the files you must download from IBM Passport Advantage and the
extracted installation image. Refer to Hardware requirements
- Download all required parts for the product image from IBM Passport
Advantage to a temporary directory on your workstation.
- Extract the installation image from the downloaded files into another
temporary directory on your workstation and verify that the installation image
is complete. See Verifying and extracting electronic images for details.
- Install on your workstation the IBM Packaging Utility from the Auxiliary
CD (or electronic disk) appropriate for your platform.
- Using the Packaging Utility, copy the Rational Application Developer product
package.
- Copy the output of the Packaging Utility to a HTTP or HTTPS Web
Server.
- Copy the installation files for IBM Installation Manager from the Auxiliary
CD's to a shared drive.
- Instruct users in your organization to install Installation Manager.
- Provide users the URL for the repository that contains the Rational Application Developer product
package you created earlier.
Managing IBM Installation Manager
Installing Installation Manager on Windows
IBM Installation Manager is installed
by the launchpad. For more information on this process, refer to Installing from the launchpad program.
To
install Installation Manager manually:
- Run setup.exe from the InstallerImager_win32 folder
on the first installation disk.
- Click Next on the Welcome screen.
- Review the license agreement on the License Agreement page and
select I accept the terms in the license agreement to
accept. Click Next.
- Click the Change button on the Destination
Folder page to change the installation location if required. Click Next.
- Click Next on the Setup Type page.
- Click Install on the Ready to Install Program
page. The Completed page opens after the installation is complete.
- Click Finish.
Installing Installation Manager on Linux
IBM Installation Manager is installed
by the launchpad. For more information on this process, refer to Installing from the launchpad program.
To
install Installation Manager manually:
- Open a terminal window with root user privileges.
- Run setupLinux.bin from the InstallerImager_linux
folder on the first installation disk.
- Click Next on the Welcome screen.
- Review the license agreement on the License Agreement page and
select I accept the terms in the license agreement to
accept. Click Next.
- If necessary, edit the installation directory location. Click Next.
- Click Install on the information summary
page.
- Click Finish on the InstallShield Wizard
Completed page.
Starting Installation Manager on Windows
IBM Installation Manager should
be started from the launchpad program. Doing so starts Installation Manager with
a configured repository preference and selected Rational Application Developer packages.
If you start Installation Manager directly,
then you must set a repository preference and choose product packages manually.
To
start Installation Manager manually:
- Open the Start menu from the Taskbar.
- Select All Programs -> IBM
Installation Manager -> IBM Installation Manager.
Starting Installation Manager on Linux
IBM Installation Manager should
be started from the launchpad program. Doing so starts the Installation Manager with
a configured repository preference and selected Rational Application Developer packages.
If you start Installation Manager directly,
then you must set repository preference and choose product packages manually.
To
start Installation Manager manually:
- Open a terminal window with root user privileges.
- Run /opt/IBM/InstallationManager/launcher_shortcut.
Uninstalling Installation Manager on Windows
To uninstall Installation Manager manually:
- Run setup.exe from the InstallerImager_win32 folder
on the first installation disk.
- Click Next on the Welcome screen.
- Select the Remove button on the Program
Maintenance page. Click Next.
- Click Next on the Setup Type page.
- Click Remove on the Remove the Program page.
- Click Finish on the InstallShield Wizard
Completed page.
Note:
You can also uninstall Installation Manager by using the Control
Panel (clicking Start -> Settings -> Control Panel and double-clicking Add
or Remove Programs.
Uninstalling Installation Manager on Linux
IBM Installation Manager must
be uninstalled using the package management tool that is included with your Linux version.
To
uninstall Installation Manager manually on Linux:
- Open a terminal window with root user privileges.
- Change directory to the installation directory of Installation
Manager (by default, /opt/IBM/InstallationManager) and then
change to _uninst.
- Run .uninstaller.bin.
Silently installing and uninstalling Installation Manager
IBM Installation
Manager can be silently installed and uninstalled.
Silently installing Installation Manager on Windows
To silently install Installation Manager onto a default install location
on Windows:
- Change directory to InstallerImage_win32 folder on the first installation
disk.
- Run setup.exe /S /v"/qn"
If you want to change the install location, you can add INSTALLDIR
property inside the /v option. For example: setup.exe /S /v"/qn
INSTALLDIR=\"C:\InstallationManager\""
Silently installing Installation Manager on Linux
To silently install Installation Manager onto a default install location
on Linux
- Change directory to InstallerImage_linux folder on the first installation
disk.
- Run setupLinux.bin -silent -V licenseAccepted=true.
Use the option -V licenseAccepted=true to indicagte
that you accept the license agreement on the use of Installation Manager.
If you want to change the install location, you can add -P installLocation="<new
dir>" flag. For example:
-PsetupLinux.bin -silent -P installLocation="/opt/myIM" -V licenseAccepted=true.
Silently uninstalling Installation Manager from Windows
To silently uninstall Installation Manager on Windows:
Run the following command in the command prompt: msiexec
/x {DBD90D51-BD46-41AF-A1F5-B74CEA24365B}
Silently uninstalling Installation Manager from Linux
To silently uninstall Installation Manager on Linux:
- Open a terminal window with root user privileges.
- Change directory to the installation directory of Installation
Manager, and then change to the _uninst directory.
- Run the following command: ./uninstaller.bin -silent.
Installing from the launchpad program
The launchpad program provides you with a single location to view
release information and start the installation process.
Use the launchpad program to start the installation of Rational Application Developer in
the following cases:
- Installing from the product CDs.
- Installing from an electronic image on your workstation.
- Installing from an electronic image on a shared drive.
By starting the installation process from the launchpad program, IBM Installation Manager will
start preconfigured with the location of the repository that contains the Rational Application Developer package.
If you install and start Installation Manager directly,
then you must set repository preference manually.
To install from the
launchpad:
- Complete the preinstallation tasks described in Preinstallation tasks,
if you have not done so already.
- Start the launchpad program. See Starting the launchpad program.
- Start the installation of Rational Application Developer.
See Starting an installation from the launchpad program.
Follow the on-screen instructions in the Install Packages wizard
to complete the installation. For complete details, see Installing IBM Rational Application Developer using
the IBM Installation Manager graphical
interface.
Starting the launchpad program
Complete the preinstallation tasks described in Preinstallation tasks,
if you have not done so already.
If you are installing from a CD and autorun is enabled on your workstation,
then the Rational Application Developer launchpad
starts automatically when you insert the first installation disc into your
CD drive. If you are installing from an electronic image, or if autorun is
not configured on your workstation, then you must start the launchpad program
manually.
To start the launchpad program:
- Insert the IBM Rational Application Developer CD
into your CD drive.
Ensure that you have mounted
the CD drive.
- If autorun is enabled on your system, the IBM Rational Application Developer launchpad
program automatically opens. If autorun is not enabled on your system:
-
Run
launchpad.exe located in the root directory of the CD.
-
Run launchpad.sh located in the root directory
of the CD.
Starting an installation from the launchpad program
- Start the launchpad program.
- If you have not done so already, read
the release information by clicking Release notes.
- When you are ready to begin the installation, click Install IBM Rational Application Developer.
- A message window opens to inform you whether the program IBM Installation Manager is
detected on your workstation.
- If IBM Installation Manager is not
detected on your system, then you are informed that you must install it before
you can continue.
- Click OK to install IBM Installation Manager.
The IBM Installation Manager installation
wizard starts.
- Follow the on-screen instructions in the wizard to complete the installation
of IBM Installation Manager. Refer
to Installing Installation Manager on Windows for
more information.
- When the installation of IBM Installation Manager completes
successfully, click Finish to close the wizard.
- Read the message that opens and click OK. Installation Manager starts
and automatically opens the Install Packages wizard.
- If IBM Installation Manager is detected
on your system, click OK and Installation Manager starts
and automatically opens the Install Packages wizard.
- Follow the on-screen instructions in the Install Packages wizard
to complete the installation. For complete details, see Installing IBM Rational Application Developer using
the IBM Installation Manager graphical
interface
Installing IBM Rational Application Developer using
the IBM Installation Manager graphical
interface
The following steps describes installing the IBM Rational Application Developer package
with the Installation Manager GUI.
- The Install page lists all the packages that Installation Manager finds
in the repositories that it searches. If two different versions of a package
are discovered, only the most recent, or recommended, version of the package
is displayed.
- To display all versions of any package found by Installation Manager,
click Show all versions.
- To return to the display of only the recommended packages, click Show
only recommended.
- Click the IBM Rational Application Developer package
to display its description in the Details pane.
- To search for updates to the IBM Rational Application Developer package,
click Check for updates. Installation Manager searches
for updates at the predefined Web site for the product package. It also searches
any repository locations that you have set. A progress indicator shows the
search is taking place. You can install updates at the same time that you
install the base product package.
- If updates for the IBM Rational Application Developer package
are found, then they will be displayed in the Packages list
on the Install Packages page below their corresponding package. Only recommended
updates are displayed by default.
- To view all updates found for the available packages, click Show
all versions.
- To display a package description under Details,
click on the package name.
- Select the IBM Rational Application Developer package
and any updates to the package that you want to install. Updates that have
dependencies are automatically selected and cleared together. Click Next to
continue.
Note:
To install multiple packages at the same time,
then all the packages will be installed into the same package group.
- On the Licenses page, read the license agreement for the selected
package. If you selected more than one package to install, there might be
a license agreement for each package. On the left side of the License page,
click each package version to display its license agreement. The package versions
that you selected to install (for example, the base package and an update)
are listed under the package name.
- 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.
- On the Location page, type the path for the shared resources
directory in the Shared Resources Directory field;
or, accept the default path. The shared resources directory contains resources
that can be shared by one or more package groups. Click Next to
continue.
The default path is:
-
C:\Program
Files\IBM\SDP70Shared
-
/opt/IBM/SDP70Shared
Important:
You can specify the shared resources directory
only the first time that you install a package. 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.
- On the Location page, either choose an existing package group to
install the IBM Rational Application Developer package
into, or create a new one. 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. The name for the package group is created automatically.
The
default path is:
-
C:\Program
Files\IBM\SDP70
-
/opt/IBM/SDP70
- Click Next to continue.
- On the next Location page,
you can choose to extend an existing Eclipse IDE already installed on your
system, adding the functionality in the packages that you are installing.
You must have Eclipse Version 3.2.1 with the latest updates from eclipse.org
to select this option.
- If you do not want to extend an existing Eclipse IDE, click Next to
continue.
- To extend an existing Eclipse IDE:
- Select Extend an existing Eclipse.
- In the Eclipse IDE field, type or navigate to the
location of the folder containing the eclipse executable file (eclipse.exe
or eclipse.bin). Installation Manager will
check if the Eclipse IDE version is valid for the package that you are installing.
The Eclipse IDE JVM field displays the Java Virtual
Machine (JVM) for the IDE that you specified.
- Click Next to continue.
- 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 IBM Rational Application Developer package
will be installed. Note that your choices apply to all packages installed
under this package group.
- On the next Features page, select
the package features that you want to install.
- Optional: To see the dependency relationships between
features, select Show Dependencies.
- Optional: Click a feature to view its brief description
under Details.
- Select or clear 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.
- When you are finished selecting features, click Next to
continue.
- On the Summary page, review your choices before installing the IBM Rational Application Developer package. If
you want to change the choices 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 completed, 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.
- In the Install Package wizard, select whether you want IBM Rational Application Developer to
start when you exit.
- Click Finish to launch the selected package.
The Install Package wizard closes and you are returned to the Start page of Installation Manager.
Installing silently
You can install the Rational Application Developer product
package by running Installation Manager in silent installation mode. When
you run Installation Manager in silent mode, the user interface is not available;
instead, Installation Manager uses a response file to input the commands that
are required to install the product package.
Running Installation Manager in silent mode is helpful because
it enables you to use a batch process to install, update, modify and uninstall
product packages through scripts.
Note that you must install Installation
Manager before you can silently install the Rational Application Developer package.
Refer to Managing IBM Installation Manager for details
on installing Installation Manager.
There are two main tasks required
for silent installation:
- Create the response file.
- Run Installation Manager in silent installation mode.
Creating a response file
You can create a response file by recording your actions as you
install a Rational Application Developer product
package using Installation Manager. When you record a response file, all of
the selections that you make in the Installation Manager GUI are stored in
an XML file. When you run Installation Manager in silent mode, Installation
Manager uses the XML response file to locate the repository that contains
the package, select the features to install, and so on.
To record a response file for installation (or uninstallation):
- On a command line, change to the eclipse subdirectory in the directory
where you installed Installation Manager. For example:
-
cd
C:\Program Files\IBM\Installation Manager\eclipse
-
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:
-
launcher.bat
-record <response file path and name>.xml -log <log file path and name>.xml.
For example, launcher.bat -record c:\mylog\responsefile.xml -log c:\mylog\record_log.xml
-
launcher.sh -record <response
file name>.xml -log <log file path and name>.xml. For example,
launcher.sh -record /root/mylog/responsefile.xml -log /root/mylog/record_log.xml
Note:
Ensure the file paths you enter exist; Installation Manager will
not create a directories for the response file and the log file.
- Follow the on-screen instructions in the Install Packages wizard
to make your installation choices, stopping when you reach the Summary page.
For details, see Installing IBM Rational Application Developer using
the IBM Installation Manager graphical
interface.
- Click Install, and then when the installation
process begins click Cancel.
- Click Finish, then close Installation Manager.
An XML response file is created and resides in the location specified
in the command.
Running Installation Manager in silent installation mode
You can run Installation Manager in silent installation mode from
a command line.
Refer to the Installation Manager online help for additional documentation
on how to run it in silent mode.
You run Installation Manager in silent
mode appending the -silent argument to the Installation
Manager start command launcher.bat (Windows) or launcher.sh (Linux).
-
launcher.bat
-silent [arguments]
-
launcher.sh -nosplash -silent
[arguments]
The following table describes the arguments used with the silent
installation command:
Argument |
Description |
-input |
Specifies an XML response file as the input to
Installation Manager. A response file contains commands that Installation
Manager runs. |
-log |
(Optional) Specifies a log file that records the result of the silent
installation. The log file is an XML file. |
To run Installation Manager in silent installation mode:
- On a command line, change to the eclipse subdirectory in the directory
where you installed Installation Manager. For example:
-
cd
C:\Program Files\IBM\Installation Manager\eclipse
-
cd opt/IBM/InstallationManager/eclipse
- Enter and run the following command, substituting your own locations
for the response file and, optionally, the log file:
-
.
launcher.bat -slient -input <response file path and name> -log <log
file path and name>For example, launcher.bat -silent
-input c:\mylog\responsefile.xml -log c:\mylog\silent_install_log.xml
-
launcher.sh -nosplash -silent<response
file name> -log <log file path and name>. For example, launcher.sh
-nosplash -silent -input /root/mylog/responsefile.xml -log /root/mylog/silent_install_log.xml
Installation Manager runs in silent installation mode; it reads the
response file and writes a log file to the directory you specified. While
you must have a response file when running in silent installation mode, log
files are optional.
Response file commands
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 the IBM Rational Application Developer package.
However, you can create or edit a response file manually.
There are two categories of commands for the response file:
- Preference commands are used to set preferences that are found
in Installation Manager under File -> Preferences..., such as repository location information.
- Silent installation commands are used to emulate the
Install Packages wizard in Installation Manager.
Silent install preference commands
While 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"
</preferences>
Use the following table to identify keys and their
associated values for silent installation preferences:
Key |
Value |
Notes |
com.ibm.cic.common.core. preferences. installDataLocation |
Specifies the installation location of Installation Manager data. |
Important:
This key is optional and is designed for use
in testing and debugging. If you do not specify an installation location for
Installation Manager, the silent installation and UI version of Installation
Manager will use the same location. |
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. |
|
com.ibm.cic.common.core. preferences.
http.proxyEnabled |
True or False |
False is the default value. |
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 |
False is the default value. |
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. |
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 |
Common component directory |
|
Silent installation commands
You can use this reference table to learn more about response file
commands for use during a silent installation.
Response file commands |
Description |
Profile
<profile
id="the profile id"
installLocation="the install location of
the profile">
</profile> |
Use this command to create an installation location. If the specified
installation location already exists, the command has no effect. Currently,
when creating the profile, the silent installation will also create two installation
contexts; one for Eclipse and one for native.
A profile is an installation location. |
Repositories
<server>
<repository location="http:/xxx/
repository/">
<repository location="file:/C:/
repository/">
<!--add more repositories below-->
<...>
</server> |
Use this command to specify the repositories used during a silent
installation. Each repository location can be a URL or a file path. |
Install
<install>
<offering profile= "profile id"
features= "feature ids"
id= "offering id" version= "offering
version"></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. |
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 installation packages that will be
uninstalled.
The profile ID must match an existing profile or a profile
specified in a profile command. Further, if there are no feature IDs specified,
all the features in the specified offering will be uninstalled; if there are
no offering IDs specified, all the installed offering in the specified profile
will be uninstalled. |
InstallAll
<installALL/>
Note:
This
command is equivalent to using
-silent -installAll . |
Use this command to silently search for and install all available
installable packages. |
UpdateAll
<updateALL/>
Note:
This
command is equivalent to using
-silent -updateAll . |
Use this command to silently search for and update all available
installable packages. |
Additional response file attributes
You can also include attributes in the response file for clean
mode and license agreement acceptance.
Clean mode attribute
You can apply a clean attribute
in a response file so that the silent installation functionality will not
preserve server and preferences settings in the user interface (UI) of Installation
Manager. If you want to run in clean mode, set the following attribute to true on
the opening response file tag:
<agent-input clean="true">
If
you set the clean attribute to true, the silent installation
will not preserve the server preference settings; these settings only take
effect in the current setting. When you view the Installation Manager UI after
the silent install is complete, notice that the repositories and other preferences
specified in your response file are displayed on the Preferences page. These
settings will not appear if you run the silent installation in clean mode.
Note:
The
clean mode attribute is designed for use during testing and debugging.
License agreement acceptance attribute
By default,
you agree to accept whatever license an installation package carries when
using Installation Manager in silent installation mode. If you do not want
to accept the license agreement, you can use an additional attribute in the <agent-input> element
that automatically fails the silent installation operation, <agent-input
acceptLicense="false">. If the installation package you are installing
has a license agreement that must be accepted, the silent installation operation
will fail.
Reference: Sample response file
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 installation packages silently and to standardize the
locations and preferences for installation packages.
Sample response file |
<agent-input >
<!-- add preferences -->
<preference name="com.ibm.cic.common.core.preferences. http.proxyEnabled"
value="c:/temp"/>
<!-- create the profile if it doesn't exist yet -->
<profile id="my_profile" installLocation="c:/temp/my_profile"></profile>
<server>
<repository location=
"http://a.site.com/local/products/sample/20060615_1542/repository/"></repository>
/server>
<install>
<offering profile= "my_profile" features= "core" id= "ies"
version= "3.2.0.20060615">
</offering>
/install>
</agent-input> |
Silent install log files
You can use silent install log files to examine the results of
a silent installation session.
The silent installation functionality creates an XML-based log
file that records the result of the silent install execution (as long as a
log file path is specified using -log <your log
file path>.xml). 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 with messages such as:
<result>
<error> Cannot find profile: profile id</error>
<error> some other errors</error>
</result> |
For detailed analysis, you can look at the logs
generated in the Installation Manager data area.
By using a preference command, you can optionally set the data area to your
preferred location, as shown in the response file topic.
IBM Packaging
Utility
Use the IBM Packaging Utility software to copy product packages
to a repository that can be placed on a Web server available over HTTP or
HTTPS.
The Packaging Utility software is located on the Auxiliary CD for
each platform (Windows and Linux) that is included with Rational Application Developer. If you
want to place a repository that contains a Rational Application Developer package
on a Web server that will be available over HTTP or HTTPS, you must use the
Packaging Utility to copy the product package of Rational Application Developer into
the repository.
Use this utility to perform the following tasks:
- Generate a new repository for product packages.
- Copy product packages to a new repository. You can copy multiple product
packages into a single repository, thereby creating a common location for
your organization from which product packages can be installed using IBM Installation
Manager.
- Delete product packages from a repository.
Refer to the online help for the Packaging Utility for full instructions
on using the tool.
Installing the Packaging Utility
The IBM Packaging
Utility must be installed from the Auxiliary CD before it can be used to copy
the Rational Application Developer product
package.
Use the following steps to install the IBM Packaging Utility software from the
Auxiliary CD:
- Start the installation from the Auxiliary CD
-
Change
to the Aux_CD_Win\PackagingUtility directory on the Auxiliary CD.PackagingUtility\PU_win32.zip
and run install_win32.exe.
-
Change to the Aux_CD_Lin/PackagingUtility
directory on the Auxiliary CD and run install_linux.bin.
- If IBM Installation
Manager is not detected on your workstation, you are prompted to install it
and then the installation wizard starts. Follow the on-screen instructions
in the wizard to complete the installation of Installation Manager. See Installing Installation Manager on Windows for details.
- When the installation of Installation Manager completes, or if
it is already on your computer, Installation Manager starts and automatically
begins the Install Packages wizard.
- Follow the on-screen instructions in the Install Packages wizard
to complete the installation.
Copying product packages to a HTTP server using the Packaging Utility
To
create a repository on a HTTP or HTTPS server, you must use the Packaging
Utility to copy the product package for Rational Application Developer
Note that this method does
not copy the optional software that is included with the Rational Application Developer installation
image. Only the Rational Application Developer files
that are installed using IBM Installation Manager are copied.
Note also
that the Packaging Utility can be used to combine multiple product packages
into a single repository location. Refer to the Packaging Utility online help
for more information.
To copy product packages with the packaging utility:
- If you are copying from a CD image, perform these tasks:
- Insert the first installation CD into your CD drive.
-
Mount the CD drive.
- If autorun is enabled on your system, the Rational Application Developer launchpad
program automatically opens. Close the launchpad program.
- Start the Packaging Utility.
- On the main page of the utility, click Copy product
package. The Prerequisite page opens, and presents
two options:
- I will be downloading product packages from IBM Web
- I will be obtaining the product packages from other sources
- Click I will be downloading product packages from IBM
Web.
Note:
You can use the I will be obtaining
the product packages from other sources option if you have already
defined an accessible repository.
- Click Next to advance to the Source page.
If there are no product packages to select, you must open a repository that
contains product packages.
- To open a repository, click the Open repository button. The Open Repository window opens.
Note:
A
repository can be a path to a directory in the file system, a disk drive containing
the first CD of the product, or a URL to a directory on a server.
- To define a repository location, click the Repository Location Browse button,
and then navigate to and select the Repository location - either the common
root directory that contains the electronic disk images or the drive
containing the first product installation CD. For example, if the Rational Application Developer files (disk1,
disk2, and so on) reside in C:\My product\unzip, you
should define this location as a repository.
- Click OK to define the repository location
and to close the Browse to a repository directory window.
- On the Destination page, click the Browse button
and select an existing repository directory, or create a new folder to store
the products.
- After you specify a repository for the selected product packages
and any fixes, click OK to close the Browse
to a directory window. The file path that you
just defined is listed in the Directory field on the Destination page.
- Click Next to advance to the Summary page. The Summary page displays the selected product
packages that will be copied into the destination repository. This page also
lists the amount of storage space that the copy requires, as well as the amount
of available space on the drive.
- Click Copy to copy the selected product
packages to the destination repository. A status bar opens at the
bottom of the wizard indicating how much time is remaining in the copy process. After the copy process is finished, a Complete page
opens and displays all of the product packages that were copied successfully.
- Click Done to return to the Packaging Utility
main page.
Now that you have used the Packaging Utility to copy the Rational Application Developer installation
files into a repository, you can place the repository on a Web server and
make the directories and files available over HTTP. (The repository can also
be placed on a UNC drive.)
Managing licenses
You can manage the licenses for your installed IBM Rational Software Development Platform products
and customized packages by using the Manage Licenses wizard and associated
Preferences pages. The Manage Licenses wizard displays license type and license
expiration information for each of your installed packages.
You can upgrade trial versions of an offering to licensed versions
by importing product activation kits. You can also enable IBM Rational Common
Licensing for offerings with trial or permanent licenses to obtain floating
license keys from a Rational license server.
Licenses
As a purchaser of IBM Rational software products, you can choose from
three types of product licenses: an Authorized User license, an Authorized
User Fixed Term License (FTL) and a Floating license. The best choice for
your organization depends upon how many people use the product, how often
they require access, and how you prefer to purchase your software.
Authorized User License
An IBM Rational Authorized User license permits
a single, specific individual to use a Rational software product. Purchasers
must obtain an Authorized User license for each individual user who accesses
the product in any manner. An Authorized User license cannot be reassigned
unless the purchaser replaces the original assignee on a long-term or permanent
basis.
For example, if you purchase one Authorized User license, you
can assign that license to one specific individual, who can then use the Rational software
product. The Authorized User license does not entitle a second person to use
that product at any time, even if the licensed individual is not actively
using it.
Authorized User Fixed Term License
An IBM Rational Authorized
User Fixed Term License (FTL) permits a single, specific individual to use
a Rational software
product for a specific length of time (the term). Purchasers must obtain an
Authorized User FTL for each individual user who accesses the product in any
manner. An Authorized User FTL cannot be reassigned unless the purchaser replaces
the original assignee on a long-term or permanent basis.
Note:
When
you purchase an Authorized User FTL under the Passport Advantage Express
program, IBM will
automatically extend the license term for an additional year at the prevailing
price unless you notify IBM before the license expires that you do not want an
extension. The subsequent FTL term starts when the initial FTL term expires.
The price for this subsequent term is currently 80% of the initial FTL price
but is subject to change.
If you notify IBM that you do not want to extend the license
term, then you must stop using the product when the license expires.
Floating license
An IBM Rational Floating license is a license
for a single software product that can be shared among multiple team members;
however, the total number of concurrent users cannot exceed the number of
floating licenses you purchase. For example, if you purchase one floating
license for a Rational software
product, then any user in your organization may use the product at any given
time. Another person who wants to access the product must wait until the current
user logs off.
To use floating licenses, you must obtain floating
license keys and install them on a Rational License Server. The server
responds to end-user requests for access to the license keys; it will grant
access to the number of concurrent users that matches the number of licenses
the organization purchased.
License enablement
If you are installing a Rational software product for the first
time or want to extend a license to continue using the product, you have options
on how to enable licensing for your product.
Licenses for Rational Software Development Platform offerings
are enabled in two ways:
- Importing a product activation kit
- Enabling Rational Common
Licensing to obtain access to floating license keys
Activation kits
Product activation kits contain
the permanent license key for your trial Rational product. You purchase, download
to your local machine, and then import the activation kit to enable the license
for your product. You import the activation kit to your product by using IBM Installation
Manager.
Rational Common
Licensing
You can obtain floating license keys, install Rational License
Server, and enable Rational Common Licensing for your product. Rational Common
Licensing provides the following benefits:
- License compliance enforcement across the organization
- Fewer license purchases
For more information on obtaining activation kits and Floating licenses,
see Purchasing licenses.
You can review license information for your installed packages,
including license types and expiration dates, from IBM Installation Manager.
To view license information:
- Start IBM Installation Manager.
- On the main page, click Manage Licenses.
The package vendor, current license types, and expiration dates are
displayed for each installed package.
Importing a product activation kit
After you download a product activation kit, you must import the
kit from the download location by using IBM Installation Manager.
You must purchase and download the activation kit to an accessible
workstation.
To import an activation kit and enable the new license key:
- Start IBM Installation Manager.
- On the main page, click Manage Licenses.
- On the Install Packages page, select a package and click Import
product enablement kit.
- Click Next. Details for
the selected package are displayed, including the current license kind and
the version range the license applies to.
- Browse to the path of the download location for the kit; then select
the appropriate Java archive (JAR) file and click Open.
- Click Next. The Summary
page displays the target install directory for the activation kit, the product
the new license applies to, and version information.
- Click Finish.
The product activation kit with its permanent license key is imported
to the product. The Manage Licenses wizard indicates whether the import is
successful.
Enabling floating licenses
If your team environment supports Rational Common Licensing,
you can enable floating licenses for your product and configure a connection
to obtain access to floating license keys.
For details on license server, license key, and Rational Common
Licensing administration, see the License Management Guide.
You must
obtain the license server connection information from your administrator.
To enable floating licenses as the license type for specified packages
and configure license server connections:
- Start IBM Installation Manager.
- On the main page, click Manage Licenses.
- On the Install Packages page, select a version
of a package, click Configure license servers, and
click Next.
- On the License Servers page, select the Enable
Rational Common Licensing check box.
- Configure one or more license server connections.
- Click the Add button.
- In the Add Server window, in the Name field,
type the host name of the license server.
- (Optional) In the Port field, type a
value for environments where a firewall is used. Do not assign a value to
this port unless your administrator instructs you to do so.
- Click OK.
- If your system administrator has given you the host names of
additional license servers, repeat the steps to add each server. For a redundant
servers configuration, in which three servers are used, type each host name
in this format: "hostname1", "hostname2", "hostname3". For each port number,
type accordingly: "host1port#", "host2port#", "host3port#".
- Click Next.
- (Optional) Configure the license usage order for your custom packages.
The order of licenses in the list determines the order in which your product
attempts to obtain license keys for specific licenses.
- Click Finish.
The Manage Licenses wizard indicates whether the floating licenses
configuration is successful.
When you open the enabled product next, a connection is created to
the license server to obtain a license key from the pool of available floating
license keys.
Purchasing licenses
You can purchase new licenses if your current product license is
about to expire or if you want to acquire additional product licenses for
team members.
To purchase licenses and enable your product, complete the following
steps:
- Determine the type of license you want to purchase.
- Go to ibm.com(R) or contact your IBM sales representative to purchase the
product license. For details, visit the IBM Web page on How to buy software.
- Depending on the type of license you purchase, use the Proof of
Entitlement you receive and do one of the following to enable your product:
- If you purchase Authorized User licenses for your product, go to Passport Advantage and follow the
instructions there for downloading your product activation kit.
- If you purchase Floating licenses for your product, click
the link to the IBM Rational Licensing and Download site, login
(IBM registration
is required), and then select the link to connect to the IBM Rational License
Key Center. There you can use your Proof of Entitlement to obtain floating
license keys for your license server.
Optionally, you can also go to Passport
Advantage to download the activation kit for your product. After importing
the activation kit, you have the option of switching from a floating to a
permanent license type if you use your PC offline for long periods.
When you want to import the activation kit or enable floating license
support for your product, use the Manage Licenses wizard in IBM Installation
Manager.
Increasing the number of file handles on Linux workstations
Important: For best results, before you work with your Rational product,
increase the number of file handles available for Rational Application Developer,
because it uses more than the default limit of 1024 file handles per process.
(A system administrator might need to make this change.)
Exercise caution
when using the following these steps to increase your file descriptors on Linux.
Failure to follow the instructions correctly might result in a computer that
will not start correctly. For best results, have your system administrator
perform this procedure.
To increase your file descriptors:
- Log in as root. If you do not have root access you will need to
obtain it before continuing.
- Change to the etc directory
- Use the vi editor to edit the initscript file in the etc directory.
If this file does not exist, type vi initscript to create
it.
Important: If you decide to increase the number
of file handles, do not leave an empty initscript file on your computer.
If you do so, your machine will not start up the next time that you turn it
on or restart.
- On the first line, type ulimit -n 4096 (the key
here is that the number is significantly larger than 1024, the default on
most Linux computers). Caution: do
not set this too high, because it can seriously impact system-wide performance.
- On the second line, type eval exec "$4".
- Save and close the file after making sure you have done steps 4
and 5.
Note:
Ensure you have followed the steps correctly, as
not doing this correctly will result in a machine that does not boot.
- Optional: Restrict your users or groups by modifying
the limits.conf file in the etc/security directory. Both SUSE Linux Enterprise
Server (SLES) Version 9 and Red Hat Enterprise Linux Version 4.0 have this file by default.
If you do not have this file, you might consider a smaller number in step
4 above (for example, 2048). You need to do this so that most users have
a reasonably low limit on the number of allowable open files per process.
If you used a relatively low number in step 4, it is less important to do
this. However, if you choose to set a high number in step 4, refraining from
establishing limits in the limits.conf file can seriously impact computer
performance.
The following is a sample limits.conf file would
look that restricts all users and then sets different limits for others afterwards.
This sample assumes you set descriptors to 8192 in step 4 earlier.
* soft nofile 1024
* hard nofile 2048
root soft nofile 4096
root hard nofile 8192
user1 soft nofile 2048
user1 hard nofile 2048
Note that the * in the example
above sets the limits for all users first. These limits are lower than the
limits that follow. The root user has a higher number of allowable descriptors
open, while user1 is in between the two. Make sure you read and understand
the documentation contained within the limits.conf file before making your
modifications.
For more information on the ulimit command, refer to the man page
for ulimit.
You can start Rational Application Developer from
the desktop environment or a command-line interface.
Click Start -> Programs -> <package group name> -> IBM Rational Application Developer -> IBM Rational Application Developer. For example, click Start -> Programs -> IBM
Software Development Platform -> IBM Rational Application Developer -> IBM Rational Application Developer
To start Rational Application Developer from
a command-line:
-
<product
installation directory>\eclipse.exe -product com.ibm.rational.rad.product.ide
-
<product
installation directory>/eclipse -product com.ibm.rational.rad.product.ide
Note that the first time you start Rational Application Developer version
7 it defaults to a new workspace. Do not open your existing workspace in Rational Application Developer version
7.0 until you read the migration documentation.
Modifying installations
The Modify Packages wizard in the IBM Installation Manager enables you to
change the language and feature selections of an installed product package.
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:
- From the Start page of the Installation Manager, click the Modify
Packages icon.
- In the Modify Packages wizard, select the installation location
for the Rational Application Developer product
package and click Next.
- On the Modify page, under Languages, select the languages for the
package group, then 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 package features that you want to install or remove.
- 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.
- When you are finished selecting
features, click Next.
- On the Summary page, review your choices before modifying the installation
package, and then click Modify.
- Optional: When the modification process completes,
click View Log File to see the complete log.
Updating Rational Application Developer
You can install updates for packages that were installed with IBM Installation
Manager.
By default, Internet access is required unless your repository preferences
points to your local update site. See the Installation Manager help for more
information.
Note:
Close all programs that were installed using Installation
Manager before updating.
To find and install product package updates:
- From the Start page of the Installation Manager, click Update
Packages.
- In the Update Packages page, select the location where the Rational Application Developer product
package is installed and then click Next. Installation
Manager searches for updates in its repositories and the predefined update
sites for Rational Application Developer.
A progress indicator shows the search is taking place
- If updates are found, they are shown on the Updates page. By default,
only recommended updates are displayed and they are selected by default. Click Show
All to display all available updates. Accept the default selections
or select other updates and click Next.
- On the Licenses page, read the license agreement for the updates.
If you agree to the terms of all of the license agreements, click I
accept the terms of the license agreements and then click Next.
- Review the details on the Summary page and then click Update. When the update process finished, the Complete page displays the
results.
- Optional: Click the View Log
File link to see the complete log.
- Click Finish to close the wizard.
Uninstalling Rational Application Developer
The Uninstall Packages option in the Installation Manager enables
you to uninstall packages from a single installation location. You can also
uninstall all the installed packages from every installation location.
To uninstall the packages, you must log in to the system using the
same user account that you used to install the product packages.
To uninstall the packages:
- Close the programs that you installed using Installation Manager.
- On the Start page click the Uninstall Packages icon.
- In the Uninstall Packages page, select the Rational Application Developer product
package that you want to uninstall. Click Next.
- In the Summary page, review the list of packages that will be uninstalled
and then click Uninstall. The Complete
page is displayed after the uninstallation finishes.
- Click Finish to exit the wizard.
Installing optional software
The following optional software is included on the Rational Application Developer installation
image:
- IBM WebSphere Portal Version 5.1 test environment
- IBM WebSphere Portal Version 6.0 test environment
- IBM Rational Agent Controller Version 7.0.1
- IBM Rational ClearCase LT
Version 7.0
- Crystal Reports Server XI Release 2
Installing the WebSphere Portal Test Environment version 5.1.0.x
The portal test environment allows you to test portal applications
from the Rational Application Developer workbench.
.
For complete instructions on installing and uninstalling WebSphere Portal
5.1.0.x on Windows and Linux workstations, as well as detailed
system requirements, see the WebSphere Portal 5.1 information center at http://www.ibm.com/websphere/portal/library.
Installing the WebSphere Portal Test Environment version 5.1.0.x
from a CD-ROM or electronic image
You must have Rational Application Developer installed
before you can install the portal test environment. We recommend that you
stop Rational Application Developer before
you start the portal test environment installation.
To install the WebSphere Portal Test Environment 5.1.0.x, follow
these steps:
- If you have installed any of WebSphere Application Server, WebSphere Portal, WebSphere Application
Server Integrated Test Environment, or WebSphere Portal integrated test environment,
ensure all of them are stopped and ensure you stop any HTTP servers. Otherwise,
the installation may fail.
- Start the WebSphere Portal test environment version 5.1 installation
program using one of the following methods:
- From the Rational Application Developer launchpad
program (see Starting the launchpad program),
click WebSphere Portal V5.1 test environment.
- Insert the setup CD of WebSphere Portal 5.1.0.x. On Windows systems,
the installation program should start automatically. If it does not, or if
you are installing on a Linux system, run the following command from the root
of the setup CD or disk image:
-
install.bat
-W dependency.useValidation=false
-
install.sh
-W dependency.useValidation=false
Note:
If you start the installation
program from an electronic image, you might
receive a ":bad interpreter : no such file or directory" error. To
start the installation successfully, change to the directory of the setup
disk image and then run the command dos2unix install.sh -W dependency.useValidation=false.
- Select the language you want the installation program run in and
click OK to continue
- Read the information in the Welcome page of the installation program
and click Next.
- Accept the license agreement and click Next
- Select the Test Environment radio button
and click Next. Depending on your platform,
you may receive an error message indicating the operating system prerequisite
check failed. This happens because some operating systems (for example, Red
Hat Enterprise Linux Workstation Version 3.0) are only supported in
the portal test environment. You can safely ignore this message -- click OK to
continue with the installation.
- Accept the default installation directory for WebSphere Application
Server V5.1, or browse to select a new one, and click Next.
The default installation directory isC:\Program Files\Portal51UTE\AppServer for Windows and opt/Portal51UTE/AppServer for Linux.
Unless you do not have enough space, the default installation directory is
recommended.
- Accept the default installation directory for the Portal Test Environment,
or browse to select a new one, and click Next. The
default installation directory is C:\Program Files\Portal51UTE\PortalServer for Windows and opt/Portal51UTE/PortalServer for Linux.
Unless you do not have enough space, the default installation directory is
recommended.
- Specify the user ID and password that you want to use with the
Portal Test Environment. Click Next.
- Review the information in the summary screen and click Next.
- When you are prompted to, insert the appropriate WebSphere Portal
5.1 CD and specify its drive location.
- When the installation is finished, click Finish to
close the installation program.
Using DB2 or
Oracle database as the WebSphere Portal configuration repository
By default, the WebSphere Portal 5.1 test environment installs
and uses the Cloudscape(TM) database
to store information about user identities, credentials, and permissions for
accessing portal resources. Cloudscape is a WebSphere Portal built-in Java database
that is well suited to basic portal environments.
To install and configure a DB2 or Oracle database, please refer to
the WebSphere Portal V5.1 InfoCenter at www.ibm.com/websphere/portal/library.
You can find the instructions in the WebSphere Portal version 5.1 InfoCenter
under Configuring -> Database. Note that when referring to the configuration
instructions in the InfoCenter, <wp_root> in the InfoCenter corresponds
to the installation directory of the WebSphere Portal 5.1 Test Environment,
and <was_root> in the InfoCenter corresponds to the installation
directory of WebSphere Application
Server V5.1 (see above for the default locations). Also, to verify the database
connection, you will create the WebSphere Portal 5.1 Test Environment
and start the server, instead of following the steps in the InfoCenter.
Uninstalling WebSphere Portal Test Environment version 5.1.0.x
You can uninstall WebSphere Portal Test Environment 5.1.0.x using
a graphical uninstallation program.
Refer to the complete instructions on uninstalling WebSphere Portal
5.1 from Windows and Linux systems found in the WebSphere Portal
5.1 information center athttp://www.ibm.com/websphere/portal/library. You will find information on decisions and steps
you might take before uninstalling as well as information on other uninstallation
methods, such as manually uninstalling.
To uninstall the WebSphere Portal test environment 5.1.0.x
using the graphical uninstallation program:
- Launch the uninstallation program by doing one of the following
steps:
- Windows only: Select WebSphere Portal from the Add/Remove
Programs window in the Control Panel.
- Start the uninstall program from a command prompt.
- Change to the directory: portal__server_root/uninstall
- Run the following command, according to your operating system:
- Select the language for the uninstallation, and click OK.
The welcome panel is displayed.
- Select the component to uninstall and click Next.
Note:
The WebSphere Application
Server uninstall program purposely leaves behind its root registry key in
the Windows registry.
- Click Next to display the confirmation panel.
- Click Next to begin the uninstallation process.
When the uninstallation program finishes, the program displays a confirmation
panel.
- Click Finish to close the uninstallation
program.
- Restart the machine. You must do this, especially if you intend
to install WebSphere Portal
again on the same machine.
Installing the WebSphere Portal Version 6.0 Test Environment
The portal test environment allows you to test portal applications
from the Rational Application Developer workbench.
.
For complete instructions on installing and uninstalling WebSphere Portal
6.0 on Windows and Linux workstations, as well as detailed
system requirements, see the WebSphere Portal 5.0 information center at http://www.ibm.com/websphere/portal/library.
Installing the WebSphere Portal Test Environment version 6.0 from
a CD-ROM or electronic image
The following instructions will guide you through installing WebSphere Portal
6.0. For complete details, refer to the IBM WebSphere Portal Version 6.0 Information
Center, available at ttp://www.ibm.com/websphere/portal/library.
To install the WebSphere Portal Test Environment
6.0, follow these steps:
- If you are installing from an electronic image, ensure that you
extracted or copied all the portal disk images into the same directory. Refer
to Extracting the downloaded files.
- If you have installed any of WebSphere Application Server, WebSphere Portal, WebSphere Application
Server Integrated Test Environment, or WebSphere Portal integrated test environment,
ensure all of them are stopped and ensure you stop any HTTP servers. Otherwise,
the installation may fail.
- Start the WebSphere Portal Test Environment version 6.0 installation
program using one of the following methods:
- From the Rational Application Developer launchpad
program (see Starting the launchpad program),
click WebSphere Portal V6.0 test environment.
- Insert the setup CD of WebSphere Portal 6.0. On Windows systems,
the installation program should start automatically. If it does not, or if
you are installing on a Linux system, run the following command from the root
of the setup CD or disk image:
-
install.bat
-
install.sh
- Select the language you want the installation program run in and
click OK to continue
- Read the information in the Welcome page of the installation program
and click Next.
- Read the license agreement and the non-IBM terms. If you agree,
select I accept the both the IBM and the non-IBM terms,
and click Next
- Accept the default installation directory for WebSphere Application
Server V6.0, or browse to select a new one, and click Next.
The default installation directory isC:\Program Files\IBM\Portal60UTE\AppServer for Windows and opt/IBM/Portal60/AppServer for Linux.
Unless you do not have enough space, the default installation directory is
recommended.
- Accept the default WebSphere application server properties,
or specify the following things:
- The cell name.
- The node within the WebSphere Application Server cell where you want
the WebSphere Portal
application server to be installed. This value must be unique among other
node names in the same cell. Typically, this value is the same as the host
name for the computer.
- The fully-qualified DNS name, short DNS name, or the IP address of the
computer that is running WebSphere Application Server. Do not use local
host or a loopback address.
- Enter the user ID and password for the WebSphere Application Server administrator.
Do not use blanks in either the user ID or the password, and ensure that the
password is at least five characters in length. This user ID is used to access WebSphere Application
Server with administrator authority after installation. Note that this user
ID is only used to log in to WebSphere Application Server and is not related
to any user IDs that are used to access the operating system itself. Click Next to
continue.
- Select if you want to install WebSphere Portal Process Server for
business process support, and click Next to continue. Important: If you are installing the product with the intention
of adding the resulting node to a managed cell or using the node as part of
a cluster, you can follow one of two approaches:
- If you require business process integration support in your managed cell
or cluster, you must install WebSphere Portal on a node that has already been
federated to a deployment manager. Exit this installation process, and refer
to the topic "Setting up a cluster" in the WebSphere Portal version 6.0 information
center.
- If you do not require business process integration support in your managed
cell or cluster, select Do not install WebSphere Process Server on this panel
and continue.
If you require business process integration support in your managed cell
or cluster, you must install WebSphere Portal on a node that has already been
federated to a deployment manager. Exit this installation process, and refer
to Setting up a cluster for instructions. If you install WebSphere Portal,
including support for business process integration, on an unmanaged node,
you will not be able to add that node to a managed cell or use it as part
of a cluster at a later time.
- Accept the default installation directory for the Portal Server
or browse to select a new one, and click Next. The
default installation directory is C:\Program Files\IBM\Portal60UTE\PortalServer for Windows and opt/IBM/Portal60UTE/PortalServer for Linux.
Unless you do not have enough space, the default installation directory is
recommended. If the directory that you specify does not exist,
it will be created. If you are installing on Windows, do not include periods (.)
in the installation path. Click Next
- Enter the user ID and password for the WebSphere Portal administrator. Do
not use blanks in either the user ID or the password, and ensure that the
password is at least five characters in length. This user ID is used to access WebSphere Portal
with administrator authority after installation. Note that this user ID is
only used to log in to WebSphere Portal and is not related to any user
IDs that are used to access the operating system itself. If you intend to
use a Lightweight Directory Access Protocol (LDAP) directory to manage your
users, ensure that the administrator user ID that you specify here conforms
to the recommendations that are specified in Special characters in user IDs
and passwords. Click Next.
- Verify the products to be installed and click Next. The installation program begins installing the selected components.
Throughout the installation and configuration process, the installation program
displays progress indicators for the different components.
Note:
The installation
can take some time to complete. Use the progress indicators and the process
monitoring facilities of your platform to monitor the overall progress of
the installation.
- If you are installing from the CDs: When you are prompted to, insert
the appropriate WebSphere Portal
6.0 CD and specify its drive location.
- When the installation is finished, the installation program displays
a confirmation panel listing the components that have been installed. Note
the following information before clicking Finish:
- The port number that is used to access WebSphere Portal is displayed on the
confirmation panel. Make a note of the port number for use in verifying the WebSphere Portal
URL. This value is also stored in the WpsHostPort property in the <portal
installation directory>/config/wpconfig.properties file.
- If you want to use the WebSphere Portal First Steps to access WebSphere Portal,
ensure that Launch First Steps is selected. From First Steps you can access WebSphere Portal
or read the WebSphere Portal
documentation.
- Click Finish.
- To verify that WebSphere Portal is running, open the following
URL in a browser: http://example.com:port_number/wps/portal, where example.com
is the fully qualified host name of the machine that is running WebSphere Portal
and port_number is the port number that is displayed on the confirmation panel.
For example, http://www.ibm.com:10038/wps/portal.
- WebSphere Portal
is up and running. Important: At this point you are running
with security enabled.
For information on using WebSphere Portal 6.0, refer to the IBM WebSphere Portal
Version 6.0 Information Center athttp://www.ibm.com/websphere/portal/library.
Using a DB2,
Oracle or SQL Server database as the WebSphere Portal configuration repository
The WebSphere Portal Test Environment, Version 6.0 stores configuration,
access control, such as user identities, credentials, and permissions for
accessing portal resources, and user data in a database. By default, WebSphere
Portal installs and uses the Cloudscape database. However, you might want
to use another supported database.
For information on installing and configuring another supported
database for use with WebSphere Portal V6.0, such as a DB2, Oracle or SQL Server database, please
refer to the WebSphere Portal V6.0 information center at www.ibm.com/websphere/portal/library.
You can find the instructions in the WebSphere Portal version 6.0 information
center under Configuring -> Configuring
databases.
Uninstalling WebSphere Portal Test Environment version 6.0
You can uninstall WebSphere Portal Test Environment 6.0 using a graphical
uninstallation program.
Refer to the complete instructions on uninstalling WebSphere Portal
6.0 from Windows and Linux systems found in the WebSphere Portal
6.0 information center at http://www.ibm.com/websphere/portal/library. You will find information on planning to uninstall
as well as information on other uninstallation methods, such as manually uninstalling.
To uninstall the WebSphere Portal test environment 6.0 using the
graphical uninstallation program:
- Review the information on planning to uninstall WebSphere Portal
6.0 from Windows and Linux systems found in the WebSphere Portal
6.0 information center at http://www.ibm.com/websphere/portal/library.
- Launch the uninstallation program by doing one of the following
steps:
- Windows only: Select WebSphere Portal from the Add/Remove
Programs window in the Control Panel.
- Start the uninstall program from a command prompt.
- Change to the directory: portal_server_root/uninstall
- Run the following command, according to your operating system:
-
./uninstall.sh
-
uninstall.bat
- Select the language for the uninstallation, and click OK.
The welcome panel is displayed.
- Select the component to uninstall and click Next.
Note:
The WebSphere Application
Server uninstall program purposely leaves behind its root registry key in
the Windows registry.
- Click Next to display the confirmation panel.
- Click Next to begin the uninstallation process.
When the uninstallation program finishes, the program displays a confirmation
panel.
- Click Finish to close the uninstallation
program.
- Restart the machine. You must do this, especially if you intend
to install WebSphere Portal
again on the same machine.
Installing Agent Controller
Agent Controller is a daemon that allows client applications to launch
and manage local or remote applications and provides information about running
applications to other applications. You must install Agent Controller separately
before you can use the following tools:
- Profiling tools to profile your applications. Agent Controller must be
installed on the same system as the application that you are profiling.
- Logging tools to import remote log files. Agent Controller must be installed
and running on the remote system from which the log files are imported.
- Component testing tool to run test cases. Agent Controller must be installed
on the systems on which you run the test cases.
- Tools for remote application testing on WebSphere Application Server version
5.0 or 5.1. (Agent Controller does not have to be installed for remote publishing of
applications; or for local application publishing or testing.) Note that WebSphere Application
Server version 6.0 has this functionality built in, so Agent Controller is
not required on version 6.0 target servers.
Note:
Hardware prerequisites
- Windows,
Linux/IA32: Intel(R) Pentium II
processor minimum. Pentium III
500 MHz or higher is recommended.
- AIX(R): PowerPC(R) 604e
233MHz (IBM RS/6000(R) 7043
43P Series) minimum
- HP-UX: PA8500 300MHz (HP Workstation C3000) minimum
- Solaris: UltraSPARC-IIi 300MHz (Sun Ultra 10 Workstation) minimum
- OS/40: iSeries(TM) (as
required by the operating system)
- z/OS(R),
LINUX/S39: zSeries(R) (as
required by the operating system)
- Linux/ppc64: POWER5(TM) processor
based pSeries(R)
and iSeries (as
required by the operating system)
- 512 MB RAM minimum (768 MB RAM is recommended)
- Disk space:
- You will require 100 MB minimum disk space for installing
- Display resolution:
- 800 x 600 display minimum (1024 x 768 recommended)
Supported platforms
Note for Linux: The Agent Controller is compiled using
libstdc++-libc6.2-2.so.3 shared library. Ensure that this shared library
exists under the /usr/lib directory. If it does not exist, you have to install
the RPM package compat-libstdc++ that comes with the operating system installation
media.
Agent Controller v7.0.1 is supported on the following platforms:
- AIX v5.2,
v5.3, and 5L on PowerPC (32-bit)
- z/OS V1R4,
V1R5, V1R6 and V1R7 on zSeries (32-bit)
- OS/400(R) V5R2,
V5R3 and V5R4 on iSeries
- Linux 2.4
and 2.6 kernel. Examples of supported distributions include:
- Red Hat Linux Advanced
Server v2.1 on Intel IA32
- Red Hat Enterprise Linux AS release 3 on PowerPC (64-bit)
- Red Hat Enterprise Linux (RHEL) v3.0 and v4.0
- SUSE Linux Enterprise
Server (SLES) v9 on Intel IA32
- SUSE Linux Enterprise
Server (SLES) v8 on zSeries (32-bit)
- Windows 2000
Server or Advanced Server (SP4) on Intel IA32
- Windows 2000
Professional (SP3) on Intel IA32
- Windows 2003
Server Standard and Enterprise (SP1) on Intel IA32
- Windows 2003
Server Enterprise x64 Edition (SP1) on EM64T (64-bit)
- Windows XP
Professional (SP2) on Intel IA32
- HP-UX v11.0, v11i on PA-RISC
- Sun Solaris v8, v9, and v10.0 on SPARC
Supported JVMs
In general, Agent Controller works with Java Virtual Machine (JVM) version 1.4 and
above. Here are the JVM versions (java -fullversion) that Agent Controller
has been tested on:
- AIX:
J2RE 1.4.1 IBM AIX build
ca1411-20040301
- AIX:
J2RE 1.5.0 IBM AIX build
pap32devifx-20060310 (SR1)
- HP-UX: J2RE 1.4.2.03-040401-18:59-PA_RISC2.0
- Linux for Intel IA32:
J2RE 1.4.1 IBM build
cxia321411-20040301; J2RE 1.4.2 IBM.
- Linux for Intel IA32:
J2RE 1.5.0 IBM Linux build
pxi32dev-20060511 (SR2)
- Linux for
PPC64: J2RE 1.4.2 IBM build cxp64142-20040917 (JIT enabled: jitc)
- Linux for
PPC64: J2RE 1.5.0 IBM Linux build pxp64devifx-20060310 (SR1)
- Linux for OS/390(R):
J2RE 1.4.1 IBM build
cx3901411-20040301
- Linux for OS/390:
J2RE 1.4.2 IBM build
cx390142-20050609
- z/OS:
J2RE 1.4.1 IBM z/OS Persistent
Reusable VM build cm1411-20030930
- z/OS:
J2RE 1.5.0 IBM z/OS build
pmz31dev-20051104a
- OS/400:
J2RE 1.4 IBM
- OS/400:
J2RE 1.5 IBM
- Solaris SPARC: Sun Java 2 Standard Edition (build 1.4.2_04-b05)
- Solaris SPARC: 1.5.0_06-b05
- Windows:
IA32 J2RE 1.4.1 IBM Windows 32
build cn1411-20040301a; J2RE 1.4.2 IBM Windows 32; Sun Java 2
Standard Edition (build 1.4.2_04-b05)
- Windows_IA32: 1.5.0_04-b05,J2RE 1.5.0 IBM Windows 32 build pwi32dev-20051222
- Windows_EM64T (64-bit): Sun Java 2 Runtime Environment, Standard Edition
(build 1.5.0_06-b05) v1.5.0 06
Locating the installation files
The installation files are located on the Agent Controller disk in the
following directories:
- For AIX: <Agent
Controller CD>/aix_powerpc
- For HP-UX: <Agent Controller CD>/hpux
- For OS/400: <Agent
Controller CD>/os400
- For Linux on
z/Series: <Agent Controller CD>/linux_s390
- For Linux on Intel IA32: <Agent
Controller CD>/linux_ia32
- For Linux on
PPC64: <Agent Controller CD>/linux_ppc64
- For Solaris: <Agent Controller CD>/solaris_sparc
- For Windows on Intel IA32: <Agent Controller CD>\win_ia32
- For Windows on Intel Extended Memory 64 Technology (64-bit): <Agent
Controller CD>\win_em64t
- For Windows on Intel Itanium(R) systems (64-bit): <Agent
Controller CD>\win_ipf
- For z/OS: <Agent
Controller CD>/os390
Installing Agent Controller on a workstation (AIX, HP-UX, Linux, Windows, Solaris)
Uninstalling previous versions of Agent Controller
- Note:
- Before installing Agent Controller version 7.0.1, you must uninstall the
previous version of Agent Controller:
- If Agent Controller 7.0 or 6.x is found, the Agent Controller v7.0.1
installer will block the installation with a warning: Please remove any existing IBM Rational Agent
Controller and run the install again. When using the silent installer, the
Agent Controller v7.0.1 installer will exit the installation without any warning.
- If a previous installation of Agent Controller v7.0.1 is found, the installer
displays the following warning: This product is already installed at <rac_install_dir>.
To overwrite the existing installation, click "Next"." If you choose to continue
with the installation, the installer will overwrite the existing installation.
When using the silent installer, the existing installation will be overwritten
without any warning.
When uninstalling Agent Controller V6.x on Windows,
you will need to manually remove any residual files. To do this, stop the
Agent Controller, uninstall it, and clean up any of the following files which
may be left behind after uninstalling:
Windows:
%RASERVER_HOME%\*.* (directory where
Agent Controller is installed)
%SystemRoot%\system32\piAgent.dll (Windows' system32
directory)
%SystemRoot%\system32\LogAgent.dll
%SystemRoot%\system32\hcbnd.dll
%SystemRoot%\system32\hcclco.dll
%SystemRoot%\system32\hccldt.dll
%SystemRoot%\system32\hccls.dll
%SystemRoot%\system32\hcclserc.dll
%SystemRoot%\system32\hcclsert.dll
%SystemRoot%\system32\hcclsm.dll
%SystemRoot%\system32\hcjbnd.dll
%SystemRoot%\system32\hclaunch.dll
%SystemRoot%\system32\hcthread.dll
%SystemRoot%\system32\piAgent.dll
%SystemRoot%\system32\rac.dll
%SystemRoot%\system32\sysperf.dll
When
uninstalling Agent Controller V6.x or V7.x on UNIX(R) platforms, you will need to manually
remove any residual files. To do this, stop the Agent Contoller, uninstall
it, and clean up any of the following files which may be left behind after
uninstalling:
Linux, AIX, HP-UX, Solaris:
$RASERVER_HOME/* (directory where Agent Controller is installed
/usr/lib/libpiAgent.so (or .sl on HP-UX)
/usr/lib/libLogAgent.so
/usr/lib/libhcbnd.so
/usr/lib/libhcclco.so
/usr/lib/libhccldt.so
/usr/lib/libhccls.so
/usr/lib/libhcclserc.so
/usr/lib/libhcclsert.so
/usr/lib/libhcclsm.so
/usr/lib/libhcjbnd.so
/usr/lib/libhclaunch.so
/usr/lib/libhcthread.so
In version 7.0.1,
Agent Controller is installed in these places:
Windows:<rac_install_dir>\bin
Linux:<rac_install_dir>/lib
Where <rac_install_dir> is the installation directory of Agent Controller.
Installing Agent Controller
- Log in as Administrator (or root).
- Change directory to the directory where you unzipped the installation
files for the appropriate platform.
- Close all Eclipse platforms before continuing with the installation.
- Run the program setup.exe. For non-Windows platforms, run setup.bin.
- Click Next on the welcome screen to proceed.
- Read the license agreement.
- Select I accept the terms in the license agreement and click Next to
proceed.
- Specify the path where Agent Controller should be installed and click
Next to proceed.
- Specify the path of the Java Runtime Environment (JRE) executable
program java.exe or java which Agent Controller should be using. The JRE
entered here will be used by Agent Controller for launching Java applications.
Therefore, you may want to change the JRE path pre-filled by the installer
program.
Note:
The JRE you provide at this time will be used both to run
Agent Controller and for Agent Controller to launch Java applications.
You may, however, later configure Agent Controller to a use separate JRE
for each of these functions. For details, refer to Agent Controller help
topic Configuring Applications to be launched by Agent Controller.
Click Next to
proceed.
- Optional: Specify the version of IBM WebSphere Application Server if "Remote
Support for WebSphere Application
Server" was selected in step 9 above. Click Next to proceed.
- Optional: Specify the paths of IBM WebSphere Application Server version
5.0 (Windows only)
and 5.1 if "Remote Support for WebSphere Application Server" was
selected in step 9 above. Click Next to proceed.
- Specify which hosts can access Agent Controller. The choices are:
Click Next to proceed.
- Choose the security setting
Note:
If you selected "Any computer", then
security is enabled by default (refer to "Enable" below). Communications
will be encrypted and all connections will be authenticated. To disable security,
refer to the Agent Controller documentation.
Click Next to proceed.
- Click Next on the summary screen to install Agent Controller.
- Click Finish after the installation has completed.
Installing Agent Controller silently
You can run the installation process silently using the following parameters
with the setup command:
Parameter |
Description |
-silent
This
variable is required if silent is used:
-V licenseAccepted=true |
Optional: tells the installer to run
silently otherwise you will get an install wizard with passed inputs. |
-P installLocation |
Optional: specifies the installation
path. The default installation path is '$D(install)/IBM/AgentController'.
Examples:
for Windows: C:\Program Files\IBM\AgentController
for
UNIX(R)/Linux: /opt/IBM/AgentController |
-V VJavaPath |
Required: specifies the fully-qualified
path of the java executable |
-V VAccessLocal
-V VAccessCustom
-V VAccessAll |
Optional: specifies how clients
can connect to Agent Controller (ALL, LOCAL, CUSTOM). Set only one of the
variables to "true" and the others to false. By default, VAccessAll="true"
- Any computer: VAccessAll="true" : allow any client
- This computer only : VAccessLocal="true" : allow only localhost
(default)
- Specific computers : VAccessCustom="true" : allow a list of clients
(also requires the -V VHosts parameter)
|
-V VHosts |
Required if VAccessCustom="true
specifies
the client hostnames, separated by commas |
The following two variables must both
be specified and should be set as opposites:
-V VSecurity="true" or "false"
-V VSecurityDisable="false"
or "true" |
Optional: (true, false)
default:
VSecurity=true
VSecurityDisable=false |
-V VUsers |
Required: if VSecurity="true"
specifies
which users can connect to Agent Controller |
-V VWAS6
-V VWAS5 |
Optional:
-V VWAS6="true" (default)
: If WAS V6 is used
-V VWAS5="true" : If WAS V5.x is used |
-V VWAS_HOME_V50
-V VWAS_HOME_V51 |
Optional: if -V VWAS5="true"
specifies
the installed location of IBM WebSphere Application Server 5.1 and 5.0 |
Examples:
Installing from the command line:
-P installLocation="D:\IBM\AgentController"
-V VJavaPath=" D:\jdk1.4.2\jre\bin\java.exe "
-V VAccessLocal="false"
-V VAccessCustom="true"
-V VAccessAll="false"
-V VHosts="host1,host2"
-V VSecurity="true"
-V VSecurityDisable="false"
-V VUsers="user1,user2"
-V VWAS5="true"
-V VWAS_HOME_V51="D:\WebSphere5.1\AppServer"
-V VWAS_HOME_V50="D:\WebSphere5.0\AppServer"
Installing using a response file:
You can create a response file, for example setup.rsp, to store all the
parameters, instead of specifying them on the command line. Following is
a Windows example,
Linux/UNIX platforms
would be similar:
setup.exe -silent -options setup.rsp
Contents of
the response file:
# Start of response file
-P installLocation="D:\IBM\AgentController"
-V licenseAccepted="true"
-V VJavaPath=" D:\jdk1.4.2\jre\bin\java.exe "
-V VAccessLocal="false"
-V VAccessCustom="true"
-V VAccessAll="false"
-V VHosts="host1,host2"
-V VSecurity="true"
-V VSecurityDisable="false"
-V VUsers="user1,user2"
-V VWAS5="true"
-V VWAS_HOME_V51="D:\WebSphere5.1\AppServer"
-V VWAS_HOME_V50="D:\WebSphere5.0\AppServer"
# End of response file
Starting and stopping Agent Controller on a Windows workstation
- On Windows, the Agent Controller system service (RAService.exe)
will be started automatically.
- Use the Windows Services dialog under Control Panel to start
or stop the Agent Controller service (Start > Settings > Control Panel
> Administrative Tools > Services>IBM Rational(R) Agent Controller).
Starting and stopping Agent Controller on a non-Windows workstation
- On non-Windows platforms, the Agent Controller process (RAServer) does
not start automatically. You must start it yourself.
- Important: The following environment settings for non-Windows
platforms must be set before starting Agent Controller.
- To start the Agent Controller process, change to the installation location's bin directory
(for example, /opt/IBM/AgentController/bin) and run
./RAStart.sh
- To stop the Agent Controller process, change to the installation location's bin directory
(for example, /opt/IBM/AgentController/bin) and run
./RAStop.sh
Uninstalling Agent Controller on a Windows workstation
- Agent Controller can be removed from the Add/Remove Programs dialog
under Control Panel.
- To perform a silent uninstallation, run the command uninstall.exe
-silent from the installation location's _uninst directory (for
example, C:\Program Files\IBM\AgentController\_uninst).
Uninstalling Agent Controller on a non-Windows workstation
- Run the program uninstall.bin from the installation location's
_uninst directory (for example, /opt/IBM/AgentController/_uninst).
- Follow the on-screen instruction to complete the uninstallation.
- To perform a silent uninstallation, use the command uninstall.bin
-silent.
Uninstalling Agent Controller that has multiple references on a workstation
Agent Controller version 7.0.1 prevents multliple instances of the product
from being installed on a single workstation. When additional installations
are performed, either by stand-alone install or as an embedded install inside
a product, Agent Controller records a reference to the name of the product
that is initiating the new installation.
If Agent Controller has been installed multiple times - in other words,
there are multiple reference counts - either by stand-alone install or as
an embedded install inside a product, it can be uninstalled only when the
last referencing product is uninstalled; the last referencing product still
requires Agent Controller.
If you attempt to uninstall Agent Controller while it is still required
by another product, the uninstallation will not proceed and you will receive
a message "This product cannot be uninstalled as it is required by another
product."
Installing Agent Controller on OS/400 (iSeries)
Uninstalling previous versions of Agent Controller
If you have a previous version of Agent Controller, stop it and uninstall
it before installing this version.
Installing Agent Controller
- On the iSeries host,
create a library called HYADESDC and another library called IBMRAC:
CRTLIB HYADESDC
CRTLIB IBMRAC
- On the iSeries host,
in the HYADESDC library, create an empty save file called HYADESDC.SAVF:
CRTSAVF HYADESDC/HYADESDC
- On the iSeries host,
in the IBMRAC library, create an empty save file called IBMRAC.SAVF:
CRTSAVF IBMRAC/IBMRAC
- Use FTP to add the file IBMRAC.SAVF from the installation CD to the library
IBMRAC located on the iSeries host using BINARY mode transfer.
- Use FTP to add the file HYADESDC.SAVF from the installation CD to the
library HYADESDC located on the iSeries host using BINARY mode transfer.
- Restore the save file HYADESDC.SAVF located on the iSeries host to the library HYADESDC,
by typing:
RSTOBJ OBJ(*ALL) SAVLIB(HYADESDC) DEV(*SAVF) SAVF(HYADESDC/HYADESDC)
- Restore the save file IBMRAC.SAVF located on the iSeries host to the library IBMRAC,
by typing:
RSTOBJ OBJ(*ALL) SAVLIB(IBMRAC) DEV(*SAVF) SAVF(IBMRAC/IBMRAC)
- Start QShell and create, on the integrated file system (IFS), the /opt/hyadesdc
directory.
- Restore the save file HYADESIFS.SAVF in HYADESDC to the IFS directory
/opt/hyadesdc. For example:
RST DEV('/QSYS.LIB/HYADESDC.LIB/HYADESIFS.FILE')
OBJ('/opt/hyadesdc/*')
- Restore the save file IBMRACIFS.SAVF in IBMRAC to the IFS directory /opt/hyadesdc.
For example, type the following command on one line:
RST DEV('/QSYS.LIB/IBMRAC.LIB/IBMRACIFS.FILE') OBJ('/opt/hyadesdc/*')
ALWOBJDIF(*ALL)
If you wish to install the National Language
packs, complete steps 11 through 16 below. If not, proceed to step 17.
- On the iSeries host,
in the HYADESDC library, create two empty save files called HYADESNL1.SAVF
and HYADESNL2.SAVF:
CRTSAVF IBMRAC/HYADESNL1
CRTSAVF IBMRAC/HYADESNL2
- Use FTP to add the NL files HYADESNL1.SAVF and HYADESNL2.SAVF from the
installation CD to the library HYADESDC located on the iSeries host
using BINARY mode transfer.
- On the iSeries host,
in the IBMRAC library, create two empty save files called IBMRACNL1.SAVF
and IBMRACNL1.SAVF:
CRTSAVF IBMRAC/IBMRACNL1
CRTSAVF IBMRAC/IBMRACNL2
- Use FTP to add the NL files IBMRACNL1.SAVF and IBMRACNL2.SAVF from the
installation CD to the library IBMRAC located on the iSeries host using BINARY mode transfer.
- Restore the save file HYADESNL1.SAVF and HYADESNL2.SAVF in HYADESDC to
the IFS directory /opt/hyadesdc. For example, type the following commands
on one line:
RST DEV('/QSYS.LIB/HYADESDC.LIB/HYADESNL1.FILE') OBJ
('/opt/hyadesdc/*') ALWOBJDIF(*ALL)
RST DEV('/QSYS.LIB/HYADESDC.LIB/HYADESNL2.FILE') OBJ
('/opt/hyadesdc/*') ALWOBJDIF(*ALL)
- Restore the save file IBMRACNL1.SAVF and IBMRACNL2.SAVF in IBMRAC to the
IFS directory /opt/hyadesdc. For example, type the following commands on
one line:
RST DEV('/QSYS.LIB/IBMRAC.LIB/IBMRACNL1.FILE') OBJ('/opt/hyadesdc/*')
ALWOBJDIF(*ALL)
RST DEV('/QSYS.LIB/IBMRAC.LIB/IBMRACNL2.FILE') OBJ('/opt/hyadesdc/*')
ALWOBJDIF(*ALL)
- After you have installed Agent Controller, change the directory to the
installed location's bin directory /opt/hyades/bin, and run the setup script
by typing:
./SetConfig.sh
- Follow the on-screen prompt to configure Agent Controller.
Starting and stopping Agent Controller on OS/400 (iSeries)
- To start Agent Controller, add the HYADESDC and the IBMRAC libraries to
the library list:
ADDLIBLE HYADESDC
ADDLIBLE IBMRAC
- Submit the RAStart job by typing:
SBMJOB CMD(CALL RASERVER) JOBD(RASTART)
- To stop Agent Controller, terminate the RAStart job by typing:
ENDJOB JOB(RASTART)
or,
change the directory to the installed location's bin directory /opt/hyades/bin,
and run the stop script:
./RAStop.sh
Uninstalling Agent Controller on OS/400 (iSeries)
- Remove the HYADESDC and IBMRAC library.
- Remove the IFS directory /opt/hyadesdc (including all subdirectories and
files).
Installing Agent Controller on z/OS (OS/390)
Uninstalling previous versions of Agent Controller
If you have a previous version of Agent Controller, stop it and uninstall
it before installing this version.
Installing Agent Controller
- In a UNIX System
Services shell, go to the directory where you want to install Agent Controller.
It is recommended that you install it in the /usr/lpp/ directory.
- Transfer the install images ibmrac.os390.pax, tptpdc.os390.pax to
the installation directory.
- Issue the following command to extract Agent Controller files:
pax -ppx -rvf ibmrac.os390.pax
- Issue the following command to extract the test and performance tools
(TPTP) Agent Controller files:
pax -ppx -rvf tptpdc.os390.pax
- Change the directory to the installation bin directory <rac_install_dir>/bin,
and run the script to create links to the Agent Controller libraries by typing:
./createLinks.sh
- Make the Agent Controller shared object files program controlled by issuing
the following commands in a UNIX System Services shell:
extattr +p /usr/lpp/IBM/AgentController/lib/*.so
If you wish to install the National Language packs, complete
steps 7 and 8 below. If not, proceed to step 9.
- Transfer the NL install images tptpdc.nl1.os390.pax, tptpdc.nl2.os390.pax,
ibmrac.os390.nl1.pax, ibmrac.os390.nl2.pax to the installation directory.
- Issue the following command to extract Agent Controller files:
pax -ppx -rf tptpdc.nl1.os390.pax
pax -ppx -rf tptpdc.nl2.os390.pax
pax -ppx -rf ibmrac.os390.nl1.pax
pax -ppx -rf ibmrac.os390.nl2.pax
- After you have installed Agent Controller, change the directory to the
installed location's bin directory /usr/lpp/IBM/AgentController/bin, and
run the setup script by typing:
./SetConfig.sh
- Follow the on-screen prompt to configure Agent Controller.
Data Channel usage on z/OS:
In order to set a large dataChannelSize in the serviceconfig.xml file you
may need to increase the maximum shared memory segment size setting on your
machine. To do this, increase the IPCSHMMPAGES value in the BPXPRMxx parmlib
member. This value is the maximum number of 4K pages that your data channel
can be. For example, if you want to set dataChannelSize to 32M, you must
set IPCSHMMPAGES to a value greater than 8192.
To allow Agent Controller to communicate with a large number of agents
simultaneously, you must set the IPCSHMNSEGS value in the BPXPRMxx parmlib
member to an appropriate value. This value specifies the maximum number of
attached shared memory segments for each address space. The default value
is 10 so you should increase this to 50.
For more information about the data channels used by Agent Controller,
refer to the online help information for Agent Controller.
For more information about z/OS BPXPRMXX parmlib members and how to
update them, refer to IBM z/OS MVSTM Initialization and
Tuning Reference.
Starting and stopping Agent Controller on the z/OS (OS/390)
Note: RAServer requires the directories of the JRE that contain
executable libraries such as libjvm.so to be added to the LIBPATH environment
variable. For example, if you are using the IBM JRE 1.4.1, the LIBPATH variable would
be set as follows:
export LIBPATH=/usr/lpp/java/IBM/J1.4/bin/classic:
/usr/lpp/java/IBM/J1.4/bin:$LIBPATH
- Start the server by logging in as root, opening the /usr/lpp/IBM/AgentController/bin
directory and issuing the command:
./RAStart.sh
- To stop the server, log in as root, open the /usr/lpp/IBM/AgentController/bin
directory, and issue the command:
./RAStop.sh
Uninstalling Agent Controller on the OS/390 (z/OS)
Using the Agent Controller security feature
The following list contains hints and tips for using the Agent Controller
security feature on all platforms:
- Authentication is provided by the operating system. Only users specified
at installation time will be allowed to authenticate. If the user name ANY is
provided, any valid user name and password pairs will be forwarded to the
operation system for authentication, otherwise only listed pairs will be
forwarded.
- When security is enabled, the users you specified at installation time
are required to authenticate with the operating system before any information
can be exchanged with Agent Controller. The workbench user must provide a
valid user name and password combination that is an operating system user
name and password.
- (Windows only) Domain name passwords will not
be authenticated. You must provide local user name and password pairs.
- There are no key management capabilities provided. Agent Controller uses
Java keystores
for security.
- A default keystore and exported certificate are in the Agent Controller
directory <rac_install_dir>\security for Windows, and <rac_install_dir>/security
for Linux.
Where <rac_install_dir> is the installation directory of Agent Controller.These
are samples only. You should replace these with a keystore containing meaningful
certificates.
Workbench/Agent Controller compatibility summary
Backward compatibility (using an older workbench with a version
6.0.1 Agent Controller): Yes, they are compatible, in that the new Agent Controller
supports all the features in previous versions (for example, Security on the
control channel). However, you will not be able to use new features, including
multiplexing (returning data via the control channel so that it can be secure).
Forward compatibility (using a 6.0.1 workbench with an older Agent
Controller): No, in general, is not supported.
Cross-version Inter-Agent-Controller compatibility: Some products
or tools (such as IBM Performance Optimization Toolkit) require that Agent
Controllers on multiple hosts (apart from the workbench) "discover" and communicate
with each other. Changes made from one version to the next surrounding this
function mean that if you need to use this function, you must use either Agent
Controller version 6.0.0.1 or Agent Controller version 6.0.1 on all involved
hosts. That is, you cannot mix and match versions when using dynamic discovery
between Agent Controller instances.
Known problems and limitations
This section covers known problems and limitations related to installing
and uninstalling Agent Controller. Except where otherwise noted, the following
information applies to all operating systems that are supported for Agent
Controller.
Agent Controller may fail to start on non-Windows platforms
Agent Controller may fail to start on non-Windows platforms with the following
message:
RAServer failed to start.
This failure is usually caused when TCP/IP port 10002 is not free. Agent
Controller listens on this port by default. Another process running on the
system may be using this port when Agent Controller is started or perhaps
Agent Controller was just stopped and then restarted before the port could
be released.
If Agent Controller failed to start, you can start it as follows:
- If port 10002 is being used by another process, you can change the port
number by editing the serviceconfig.xml file. This is described in the documentation.
- Note:
- If the communication port number that is configured in the serviceconfig.xml
file has been changed, then the property INSTANCE_RAC_PORT_NUM_ID that is
defined in the WebSphere Application
Server configuration needs to be changed to the same port number.
- If Agent Controller was just stopped, wait a few minutes and try to start
it again.
Other errors during installation and uninstallation
If you encounter errors during installation or uninstallation, this may
be due to the fact that the object files of Agent Controller are loaded by
running processes. To ensure the object files can be modified, do the following:
- Shut down your Eclipse workbench.
- Terminate all java.exe processes that contain either the Java Profiling
Agent or the J2EE Request Profiler.
Installing ClearCase LT
Rational ClearCase LT
is a configuration management tool for small project teams. ClearCase LT
is part of the IBM Rational ClearCase product
family that can scale from small project workgroups to the distributed, global
enterprise.
Your installation media includes Rational ClearCase LT Version 7.0.0.0 It is
installed separately from Rational Application Developer.
If
you already have ClearCase LT installed on your workstation, then
you might be able to upgrade it to the current version. Refer to the installation
documentation for ClearCase LT for information on upgrading from
previous versions.
To
enable Rational Application Developer to
work with ClearCase LT,
you must install the Rational ClearCase SCM Adapter feature. By
default, this feature is selected when you install Rational Application Developer;
however, if you did not include it, you can install it later using the Modify
Packages wizard in IBM Installation Manager. For details, refer to Modifying installations.
You
must enable the Rational ClearCase SCM
adapter before you can work with it. Refer to the online help for details
on enabling and working with the adapter.
Locating the ClearCase LT installation instructions and release
notes
For complete instructions on installing Rational ClearCase LT, refer to the installation
documentation provided with the ClearCase LT installation media. It
also strongly recommended that you read the ClearCase LT release notes before
you install the product.
Some documentation is in Acrobat PDF files. To open the files, you
require the Adobe Reader software, which you can download from http://www.adobe.com/products/acrobat/readstep2.html.
The
installation instructions and release notes can be viewed from the ClearCase LT
installation launch pad. Refer to Starting an installation of Rational ClearCase LT.
- To open the installation instructions:
-
From
the first ClearCase LT
installation CD (or disk directory for an electronic image), open doc\books\install.pdf. IBM Rational ClearCase, ClearCase
MultiSite(R), and ClearCase LT Installation and Upgrade Guide, Version
7.0 (Windows) opens.
-
Go to http://www-1.ibm.com/support/docview.wss?uid=pub1gi11636 for instructions to download IBM Rational ClearCase,
ClearCase MultiSite, and ClearCase LT Installation Guide, 7.0, Linux and UNIX.
-
IBM Rational ClearCase, ClearCase MultiSite, and ClearCase LT
Installation and Upgrade Guide, Version 7.0 (Linux) opens.
Getting documentation from the IBM Publications Center
You can also download the installation instructions and release
notes for Rational ClearCase LT
from the IBM Publications
Center.
- Go to http:http://www.ibm.com/shop/publications/order.
- Select your country/region on the Welcome page of the Publications
Center.
- Click Search for Publications.
- Enter either the document title or publication number in the appropriate
search field.
- To search for a document by its title, enter the title in the Search
on field.
- To search for a document by its publication (Material ID) number,
enter the number in the Publication number field.
Table 1. ClearCase publication numbers
Document |
Publication number |
IBM Rational ClearCase, ClearCase MultiSite, and ClearCase LT
Installation and Upgrade Guide (Windows) |
GI11-6365-00 |
IBM Rational ClearCase, ClearCase MultiSite, and ClearCase LT
Installation and Upgrade Guide (UNIX) |
GI11-6366-00 |
IBM Rational ClearCase LT Release Notes(R) |
GI11-6369-00 |
Starting an installation of Rational ClearCase LT
The installation instructions in this section are to help you start
the installation process for Rational ClearCase LT. You must refer to the
complete installation instructions found in the Rational ClearCase LT Installation Guide when
installing the product. Before installing, it is strongly recommended that
you read the release notes.
Starting an installation of Rational ClearCase LT on Windows
- Start the Rational ClearCase LT launchpad program using one of
the following methods:
- From the Rational Application Developer launchpad
program (see Starting the launchpad program),
click Rational ClearCase LT.
- Insert the first CD of Rational ClearCase LT. The launchpad program
should start automatically. If it does not run, run setup.exe from
the root of the first CD or disk image.
- Read the release information if you have not done
so.
- Click Install IBM Rational ClearCase LT. The Rational ClearCase LT Setup Wizard opens.
Follow the instructions in the Setup Wizard to complete the installation.
Installing Rational ClearCase LT on Linux
Complete instructions on installing Rational ClearCase LT version 7.0 on a Linux workstation
are available in the document IBM Rational ClearCase, ClearCase MultiSite,
and ClearCase LT Installation Guide, 7.0, Linux and UNIX, which you can
download at http://www-1.ibm.com/support/docview.wss?uid=pub1gi11636.
Configuring Rational ClearCase LT licensing
When you have Rational Application Developer installed
on the same computer as Rational ClearCase LT, you do not need to configure Rational ClearCase LT
licensing. However, if you install Rational ClearCase LT without Rational Application Developer, then you
will need to configure ClearCase LT Licensing.
See the ClearCase LT Installation Guide for details
about configuring licensing
Installing Crystal Reports Server XI Release 2
Crystal Reports Server XI Release 2 is a common architecture for
data access, reporting, and information delivery. It is designed to integrate
with existing data, Web, and application investments. Based on Crystal Reports,
Crystal Reports Server XI Release 2 is an effective solution for scaling information
to thousands of users.
Crystal Reports Server XI Release 2 is a centralized platform
for managing and securely distributing complex and interactive reports via
the Web or integrated into intranet, extranet, Internet, and corporate portal
applications and is available for both Windows and Linux.
As an integrated suite for
reporting, analysis, and information delivery, Crystal Reports Server XI Release
2 provides a solution for increasing end-user productivity and reducing administrative
efforts.
Installing Crystal Reports Server XI Release 2 on Windows
When
you perform this default installation, all the client and server components
are installed on your workstation. A MySQL database for the Central Management
Server (CMS) is automatically created. Default user and group accounts are
created, and sample reports are published to your system. When the installation
is complete, the server components are started as services on your workstation.
To
install all the components of Crystal Reports Server XI Release 2 on Windows:
- From the Rational Application Developer installation launchpad, click Install
Crystal Reports Server XI Release 2. If you are
installing from CD ROM, you will be prompted
to insert the first Crystal Reports Server XI Release 2 for Windows
installation disk into your CD ROM drive.
- From the Rational Application Developer installation launchpad, click Install
Crystal Reports Server XI Release 2.
- In the Setup wizard, select a setup language
and click OK. This is the language that
the installation process uses, not the language that will be installed.
- On the Welcome page, click OK.
- On the License Agreement page, read the license
agreement and, if you accept the terms and conditions, click I
accept the license agreement and click Next.
- On the Select Client or Server Installation page,
click Perform Server Installation.
Note:
This
option installs all required Crystal Reports Server components. The Perform
Client Installation option only installs client tools onto a machine
that you can use to administer your Crystal Reports Server environment remotely.
- Follow the instructions in the Setup wizard
and on the Directory Selection page, accept the default
location (C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5),
click Next, and proceed to Step 9.
- If you choose to install on a drive other
than the default location, the Setup wizard asks you
to select a drive for the installation of shared files that are also used
by Business Objects products such as Crystal Reports. To install several Business
Objects products on the same machine without installing files on the default
system drive, first install Crystal Reports Server. When you subsequently
install Crystal Reports, it will use the common file directory created by
Crystal Reports Server.
- On the Install Type page, click New and
complete the following steps:
- If you want to install the MySQL database as your CMS database, click Install
MySQL database server, click Next and proceed
to Step 10. This is the recommended installation.
- If you want to use another database for the CMS, such as Oracle or
Sybase, click Use an existing database server and click Next.
For information and instructions on how to use an existing database
server, refer to the BusinessObjects Enterprise Installation Guide. This information
can be found in the chapter called Installing BusinessObjects Enterprise on Windows under
the section named New installation.
- If you have chosen to install the MySQL database as your CMS database,
complete the following steps:
- Enter the port number.
- Enter and confirm the password that will be used by MySQL's
root user account.
- Accept the default user name to access the CMS database or enter
a new user name to override the default name.
- Enter and confirm the password that will be used to access the
CMS database.
- Click Next
- On the Choose Web Component Adapter Type page,
complete one of the following steps:
- If you want to use the Java Web component adapter only and use
your own Java application server, click Java application
server, click Use preinstalled Java application server,
clear the IIS ASP.NET check box, and click Next;
then proceed to Step 13.
- If you want to use the Java Web component adapter only and install
Tomcat, click Java application server, click Install
Tomcat application server, clear IIS ASP.NET,
and click Next; then proceed to Step 12.
- If you want to use the IIS ASP.NET Web component adapter only, clear
the Java application server check box, select the IIS
ASP.NET check box, from the Choose website list,
accept the default or select the Web site on which to deploy the WAR file,
and click Next; then proceed to Step 13.
- If you want to use both the Java and IIS ASP.NET Web component adapters,
select both Java application server and IIS
ASP.NET, from the Choose website list,
accept the default or select the Web site on which to deploy the WAR file,
click either Use preinstalled Java application server or Install
Tomcat application server, and click Next;
then proceed to Step 12 or Step 13.
- If you have chosen to install Tomcat application
server, accept the defaults or change the default installation location and
configure the Connection port, Shutdown port, and Redirect port, and click Next.
Note:
If you are installing Crystal Reports Server on the same
machine as a BusinessObjects Enterprise 6.x deployment, do not use the default
port number 8080 that may already be in use by another deployment.
- On the Start Installation page, click Next.
The installation begins. During the installation process, you may be prompted
to reboot the machine and register your product.
- On the last page of the Setup wizard, clear Launch
BusinessObjects Administration Console unless you want to publish
your own reports to Crystal Reports Server immediately and click Finish.
Uninstalling Crystal Reports Server XI Release 2 on Windows
To uninstall Crystal Reports Server XI Release 2 on Windows:
- Click Start -> Settings -> Control Panel.
- In the Control Panel window, click Add/Remove
Programs.
- In the Add or Remove Programs window, select Crystal
Reports Server XI Release 2 and click Remove.
Installing Crystal Reports Server XI Release 2 on Linux
Important: You cannot install Crystal
Reports Server if you have root privileges; you must be a non-root user in
order to install.
To install Crystal Reports Server XI Release 2 on Linux:
- Access the first Crystal Reports Server XI Release 2 for Linux installation
disk:
- Insert the first Crystal Reports Server XI Release 2 for Linux installation
disk into a CD ROM drive.
- If you are installing from an electronic image, navigate the disk
directory corresponding to the first Crystal Reports Server XI Release 2 for Linux disk
in the directory where you extracted the electronic image.
- Open the xir2_crs_quickinstall_linux_en.pdf file, which you can
find in the /docs/en subdirectory of the installation disk. This file contains
complete instructions for installing Crystal Reports Server XI Release 2 on Linux.
You will need to refer to the instructions in this file to prepare your system
and complete the installation process. You should also review the "Installation"
section of the release.pdf file, which is located in the root directory of
the installation disk, prior to installing the product.
- Review the Quick Installation Guide for Crystal Reports Server
on Linux section
of the PDF file and perform all necessary actions before proceeding with running
the installation script.
- Disable any antivirus software before installing the product.
- Follow the Beginning Your Installation instructions in the PDF
file to complete the installation process. It describes the procedure for
a user installation.
Uninstalling Crystal Reports Server XI Release 2 on Linux
To uninstall Crystal Reports Server XI Release 2 on Linux, run the
uninstall script that is in the installation directory of the software.
All the files that are installed during your original installation
are deleted.
Notices
(C) Copyright IBM Corporation 2000, 2006. All rights reserved.
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.
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 Dept. for Rational Software
IBM Corporation
3600 Steeles Avenue East
Markham, Ontario
Canada L3R 9Z7
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.
Trademarks and service marks
The following terms are trademarks of International Business Machines Corporation
in the United States, other countries, or both:
- AIX
- ClearCase
- developerWorks(R)
- IBM
- ibm.com
- iSeries
- MultiSite
- MVS(TM)
- OS/390
- OS/400
- Passport Advantage
- POWER5
- PowerPC
- pSeries
- Rational
- RS/6000
- WebSphere
- z/OS
- zSeries
Intel, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries,
or both.
Microsoft and Windows are trademarks of Microsoft Corporation
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.