Before you can install or upgrade to ClearCase CCRC WAN
server and ClearQuest Web server V8.0.1, you must install or upgrade
the WebSphere Application Server environment where you plan to deploy
the web server components.
About this task
Before you install or upgrade Rational web components,
you might need to upgrade the existing WebSphere Application Server
installation or install a new instance. You can use WebSphere Application
Server V8.0 or V8.5.x.
Install a new instance of WebSphere Application
Server in any of the following cases:
- You are installing Rational web components such as ClearCase CCRC
WAN server or ClearQuest web server for the first time, and the environment
does not have a supported version of WebSphere Application Server
installed.
- You are upgrading from ClearCase or ClearQuest V7.1.1.x, V7.1.2.x
to V8.0.1.
- An existing ClearCase or ClearQuest V8.0 or V8.0.0.1 installation
is deployed to WebSphere Application Server V7.0.x.
If you are upgrading to ClearCase or ClearQuest V8.0.1 from a
V8.0.0.x installation that is deployed to WebSphere Application Server
V8.0.0.x, you can upgrade the existing WebSphere Application Server
to version 8.5.x or continue with WebSphere Application Server V8.0.0.x.
If you continue using WebSphere Application Server V8.0.0.x, the WebSphere
Application Server environment has already been prepared. You can
skip this procedure and go directly to installing or upgrading the
product web components.
For more detailed information about installation and upgrade tasks, see
Technote
1572830, which includes the following information:
- Matrix of supported installation, upgrade, and rollback scenarios
- Information about upgrading an existing installation of WebSphere Application Server, and IBM
HTTP Server components.
- Instructions for upgrading ClearCase and ClearQuest Web components, deploying, or redeploying
them to the WebSphere Application Server.
WebSphere Application Server and IBM HTTP Server
are installed by using IBM Installation Manager.
Note: WebSphere
Application Server version 8 is not compatible with Rational ClearCase
or ClearQuest version 8.0 or earlier.
You can obtain WebSphere Application Server and HTTP Server from IBM Passport Advantage.
Fix packs are available from IBM Support Fix Central.
- Restrictions
Before you begin an installation of WebSphere Application
Server, review the following information.
- Prepare the operating system for product installation in the WebSphere Application
Server documentation ( V8.0.x, V8.5.x).
- See the ClearCase or ClearQuest release information on the IBM
Support website for current information about using these products
with WebSphere Application Server and IBM HTTP Server:
- On UNIX systems, do not use symbolic links as the destination
directory. Symbolic links are not supported.
- Do not use a semicolon in the directory name. WebSphere Application
Server cannot install properly if the target directory includes a
semicolon. A semicolon is the character that is used to construct
the class path on Windows systems.
- The maximum path length for the installation location on the Windows
Server 2008, Windows Vista, and Windows 7 operating systems is 60
characters.
- Deleting the default target location and leaving an installation-directory
field empty prevents you from continuing.
Use the following procedure to install WebSphere
Application Server V8.0.x components. For information on installing
WebSphere Application Server version 8.5.x, see Technote 1634430 Upgrading to ClearCase and ClearQuest
V8.0.1 with WebSphere Application Server and IBM HTTP Server V8.5.
- Start Installation Manager.
- Select . Then, add the installation repository for WebSphere
Application Server from the Repositories section
of the Preferences panel.
Tip: In Installation Manager, select Search service
repositories during installation and updates on the Installation
Manager Repository preference page. Then, if you have
an Internet connection, you can click Check for Other Versions
and Extensions to search for updates in the default update
repositories for the selected packages. In this case, you do not need
to add the specific service-repository URL to the Installation
Manager Repository preference page. Select the fixes to
install. Any recommended fixes are selected by default. If there are
recommended fixes, you can select the option to show only recommended
fixes, and hide non-recommended fixes.
- Click Install on the main Installation
Manager screen.
- On the Install Packages panel, select
the following packages to install, and then click Next to
continue the installation.
- IBM HTTP Server for WebSphere Application Server, Version
8.0.0.0 (or later)
- IBM WebSphere Application Server, Version 8.0.0.0 (or later)
- Web Server Plug-ins for IBM WebSphere Application Server,
Version 8.0.0.0 (or later)
- WebSphere Customization Toolbox, Version 8.0.0.0 (or later)
- If you want to install a fix pack for WebSphere Application
Server and IBM HTTP Server, such as version 8.0.0.1, select the Check
all versions and Check for Other Versions and
Extensions check boxes. The fix pack versions are displayed
in the list of packages. If they do not appear, then the repository
for the WebSphere Application Server software is not included in the
preferences. In this case, see Installation Manager tip in step 2.
If the package list is correct, click Next.
- If there are any fixes available, select all listed fixes.
Then, click Next.
Note: If you
have not authenticated to the IBM server, you are prompted to enter
an IBM user name and password authorized to access the service repositories.
- Accept the license agreement. Then, click Next.
- On the Shared Resources Directory panel,
review any installation warnings and instructions.
- At the next panel, you can change the default installation
directory by selecting a package group name and specifying a new path
name in the Installation Directory field. Click Next.
Note: If you change the installation location of either the
AppServer, Plug-ins, or Toolbox, you might need to make the same change
for the others. Do not use locations that are already in use by another
version of WebSphere Application Server and IBM HTTP Server on the
same system.
- Select your translation choices. Then, click Next.
- At the Select the features to install panel,
verify that IBM HTTP Server, IBM WebSphere Application Server, Web
Server Plug-ins, and WebSphere Customization Toolbox are selected.
Accept default selections. Click Next.
- On the Configuration for IBM HTTP Server panel,
specify your web server configuration.
- Specify the port number for IBM HTTP Server communication. Use the default port 80, unless that port is already in use.
In that case, specify an different port number.
- Optional: On Windows systems, choose whether
to run the IBM HTTP Server as a Windows service. You can
configure the service to run as local system account, or a user ID
that you specify. The user ID requires the following advanced user
rights:
- Act as part of the operating system.
- Log on as a service.
- Accept the default startup type, Automatic.
Important: If you do not select Run IBM
HTTP Server as a Windows Service, this instance of IBM
HTTP Server cannot be stopped or started by the WebSphere Application
Server administrative console. At any time after installation, you
can create a new service by running the following command: ihs_root/bin/httpd.exe
-n new_service_name -k install, and then update the web
server definition in the administrative console to reflect the new
service name.
- Click Next to review the summary
information. Then, click Install.
If the installation fails, or you see error messages in the summary panel, review the
installation log file. For troubleshooting information, see Technote
1573966.
When the installation completes successfully, you typically
see a choice of post-installation tools: - Optional: You can start installed components from
the Start program list in the Installation
Manager, or start them from the program shortcuts that are created
during the WebSphere Application Server installation process.
- WebSphere Customization Toolbox. You need this tool to configure
the HTTP plug-ins. This tool must be run on Windows as built-in Administrator
or as a local user in the Administrator group.
- Profile Management Tool. You can use this tool to create a WebSphere
Application Server profile if you plan to deploy a web component into
an existing profile. See WebSphere Application Server profiles for web feature deployment.
- Select the WebSphere Customization Toolbox to configure
the plug-in, and click Finish. If
you selected an application to start, the application starts after
the Installation Manager exits.
Note: If you do not see an option to
run the WebSphere Customization Toolbox on Windows operating systems,
click .
What to do next
The post-installation steps to complete the plug-in configuration
include:
- Optional: Configure a Web plug-in:
If you have
not already run the Web Server Plug-ins Configuration Tool to configure
the web server to communicate with the application server, see Configuring a web plug-in for IBM HTTP Server. On Windows, this tool requires user credentials
for a built-in Administrator or a local user in the Administrator
group.
- Optional: Create a WebSphere Application Server application profile
When you
install Rational ClearCase and ClearQuest web components to a WebSphere Application Server
application profile, you can choose the Profile Deployment Type: new profile,
or existing profile. To determine which type of profile to use, see WebSphere Application Server profiles for web feature deployment.
If you plan to deploy the product web components into an
existing WebSphere Application Server profile, the profile must exist before you begin installing or
upgrading. To create a profile, run the WebSphere Application Server Profile Management Tool, or use
the manage profiles script. For instructions, see Managing profiles on non-z/OS operating
systems in the WebSphere Application Server documentation (V8.0.x, V8.5.x)
.
- Upgrade Rational ClearCase CCRC WAN server and ClearQuest Web Server to V8.0.1. See Technote 1572830.
For more information about the WebSphere Application Server,
see the following references: