After you install WebSphere Application
Server and IBM HTTP Server, you can deploy the Rational web server
components you need into the WebSphere Application Server environment
using profiles.
These instructions apply to version 7 of
WebSphere Application Server and IBM HTTP Server. For information
on installing and configuring WebSphere Application Server and IBM
HTTP server version 8, see
Technote #1569987, For information on supported
configurations, see
Installing WebSphere Application Server and IBM HTTP Server.
Rational web server features can be deployed to existing WebSphere
Application Server profiles or to new profiles created during the
installation process. The port used to access a web server is the
port number configured for the host profile. You select the profile
during the web feature installation process.
- Install into a new profile
- This option is the default selection in the Rational ClearCase
and Rational ClearQuest installation programs. When this option is
selected, applications are deployed to these installation directory
and ports:
- For the CCRC WAN server:
- Windows 32-bit Installation directory: C:\Program
Files\IBM\RationalSDLC\common\ccrcprofile
- Windows 64-bit Installation directory: C:\Program
Files (x86)\IBM\RationalSDLC\common\ccrcprofile
- UNIX/Linux installation directory:/opt/IBM/RationalSDLC/common/ccrcprofile
- Port number: 16080
- For the ClearQuest Web server:
- Windows 32-bit Installation directory: C:\Program
Files\IBM\RationalSDLC\ClearQuest\cqweb\cqwebprofile
- Windows 64-bit Installation directory: C:\Program
Files (x86)\IBM\RationalSDLC\ClearQuest\cqweb\cqwebprofile
- UNIX/Linux installation directory:/opt/IBM/RationalSDLC/ClearQuest/cqweb/cqwebprofile
- Port number: 12080
These default file paths and port numbers are referenced in the
user instructions provided in the Rational ClearCase and ClearQuest
product information
- Install into an existing profile
- You can choose to deploy one or more Rational web servers to an
existing WebSphere Application Server profile. This option supports
flexible deployment of web servers-- for example, deploying multiple
servers to one profile (not recommended for scalability) or to create
a profile that would run as a non-root user on UNIX or Linux machine.
Note: If
you create a non-root user profile, confirm that the start-up command
in your /etc/init.d script is preceded by su <non-root
user>, where non-root user is
the same identity as the identity under which the profile was created.
If
you deploy to an existing profile, the web feature is deployed to
the installation directory location and port number associated with
the selected profile.
For information on the default directory conventions,
finding profile information, and other profile management tasks, see
these topics: