Using CM Server with an existing installation of IBM WebSphere Application Server

You can use CM Server with an existing installation of IBM® WebSphere® Application Server rather than with WebSphere Application Server version 6.1 that is included with CM Server.

If you have already installed Rational® ClearCase® or Rational ClearQuest® with CM Server (with WebSphere Application Server version 6.1 installed and running CM Server), or if you have also installed WebSphere Application Server and want CM Server to run within a different version of WebSphere Application Server instead of the supplied WebSphere Application Server version 6.1, the following instructions apply.

Note that the ports may be different for WebSphere Application Server profiles that you have created than the defaults for the WebSphere Application Server version 6.1 that is included with CM Server. For example: See Configuring CM Server for more information.

For information on WebSphere Application Server see http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp

Deploy CM Server for the UNIX® system

The following script deploys an existing CM Server installation into WebSphere Application Server. Copy the following content into a shell script file, change the permissions so the file is an executable, and then run it:
#!/bin/sh
WAS_BIN=/opt/IBM/WebSphere/AppServer/bin
export WAS_BIN; 

cd /opt/IBM/RationalSDLC/common/CM/scripts
$WAS_BIN/wsadmin.sh -f installAll.jacl -rationalDir /opt/rational
$WAS_BIN/stopServer.sh server1 
$WAS_BIN/startServer.sh server1 
Note: For Linux, the install path is /opt/ibm/RationalSDLC/.

Disabling existing WebSphere Application Server

To disable the existing version of WebSphere Application Server, you stop it with this command:
/opt/IBM/RationalSDLC/common/eWAS/bin/stopServer.sh server1 cmprofile
cd /etc
find . -name '*ewas*' -print 
The output lists WebSphere Application Server startup and shutdown files:
./init.d/ewas_startup
./init.d/ewas_shutdown
./rc0.d/K30ewas_shutdown
./rc3.d/S99ewas_startup 
Remove all the startup and shutdown files.

Redirecting IBM HTTP Server to WebSphere Application Server

By default, IBM HTTP Server redirects some URLs to WebSphere Application Server ports. To make IBM HTTP Server redirect to your WebSphere Application Server installation, edit plugin-cfg.xml (/opt/rational/common/eWAS/profiles/plugin-cfg.xml). This file is referenced from /opt/rational/common/IHS/conf/httpd.conf. If you want the plugin file to be elsewhere, you can move it and then update httpd.conf.

Modify plugin-cfg.xml by updating the port numbers to match the ports you selected when you created your WebSphere Application Server profile. Afterward, reset IBM HTTP Server to make the changes take effect with this command:
/opt/IBM/RationalSDLC/common/IHS/bin/ihs_restart
You can verify the updates with this URL: http://localhost/TeamWeb/services/Team

Deploy CM Server for Windows

The following script deploys an existing CM Server installation into WebSphere Application Server. Copy the following content into a batch file and then run it:
set WAS_BIN=C:\Progra~1\IBM\WebSphere\AppServer\bin
c:
cd "Program Files\IBM\RationalSDLC\common\CM\scripts"
call %WAS_BIN%/wsadmin.bat -f installAll.jacl -rationalDir "C:/Program Files/IBM/RationalSDLC"
call %WAS_BIN%/stopServer.bat server1 
call %WAS_BIN%/startServer.bat server1 

Optionally, server1 can be restarted from Windows® Services Control Panel.

Disabling existing WebSphere Application Server

To disable WebSphere Application Server , use the Windows Services Control Panel to stop and disable the WebSphere Application Server profile (named cmserver). You can stop and disable the service or delete it.

Redirecting IBM HTTP Server to WebSphere Application Server

By default, IBM HTTP Server redirects some URLs to WebSphere Application Server ports. To make IBM HTTP Server redirect to your WebSphere Application Server installation, edit plugin-cfg.xml (C:\Program Files\IBM\RationalSDLC\ common\eWAS\profiles\plugin-cfg.xml). This file is referenced from httpd.conf (for example, C:\Program Files\IBM\RationalSDLC\ common\IHS\conf\httpd.conf). If you want the plugin file to be elsewhere, you can move it and then update httpd.conf.

Modify plugin-cfg.xml by updating the port numbers to match the ports you selected when you created your WebSphere Application Server profile. Afterward, reset IBM HTTP Server to make the changes take effect with this command:
C:\Program Files\IBM\RationalSDLC\common\IHS\bin\ihs_restart
You can verify the updates with this URL: http://localhost/TeamWeb/services/Team
Related concepts
CM Server architecture
CM Server deployment models
Configuring CM Server
Monitoring CM Server
Related reference
CM Server hardware and software requirements
CM Server installation directory

Feedback