|
|
|
Soft - is your software and documentation |
ClearCase Remote Client (CCRC, Rational ClearCase web and CM Server “How do I” covers: (Last updated 13-Nov-09)
- General – General things affecting CCRC, CM Server, ClearCase web, etc...
- Remote Client – getting started, trace, creating template config
spec for, etc..
- CM Server – configuration and setup, etc...
Table of contents
3. How do I - determine
login credentials for CCWeb and CCRC
5. How do I – understand
about the .copyarea.dat and .copyarea.db files
7. How do I – understand
the availability of CCRC Version 7.0.1 Client Update 7.0.1.D090928
8. How do I – understand
about Multiple ClearCase Region Support for CCRC
9. How do I – understand
the CCRC .Net Update Site
10. How do I – understand
that CCRC posted delivery hangs with Solaris 7.1.0.2 CM Server
11. How do I – install
ClearCase Remote Client 7.1 and previous versions on the same host
12. How do I – understand
CCRC customization at install time for deployment is no longer available
13. How do I – understand
about the ccweb.conf file
14. How do I - understand the CCRC 7.1 plug-in support for
Ubuntu 8.0.4 LTS Desktop
17. How do I – get started
with the ClearCase Remote Client
18. How do I – understand
the CCRC support for the UCM integration with ClearQuest
19. How do I - change the
language settings in the ClearCase Remote Client
21. How do I - uninstall the
ClearCase Remote Client from a Linux system
23. How do I – understand
about Multiple ClearCase Region Support on CCRC 7.0.1 Servers
25. How do I – understand
the Configuration guidelines for CM Server for CCRC in version 7.1
26. How do I – understand about
the Web Server URL for CCRC version 7.1
27. How do I – understand
the System Requirements for the ClearCase Remote Client
28. How do I – understand
the SCM Server configuration guidelines for CCRC in ClearCase version 7.1
29. How do I – install the
ClearCase Remote Client Extension 7.1.0.01
32. How do I – understand
the problems when uninstalling CCRC IDE from Eclipse
34. How do I – understand
being unable to authenticate using PAM from CCWeb, MSWeb or CCRC clients
37. How do I - attempt to
checkout a locked element from CCRC silently fails
38. How do I – understand
IHS not restarting after httpd.conf and ssl.conf files were modified
41. How do I – understand
why active views missing from CCRC client
46. How do I – understand
why the CM server does not automatically restart
47. How do I – understand
why CCRC views are not visible from CCWeb after upgrade to 7.0
53. How do I – understand
why the CCRC 7.1.x view load hangs on attrib.exe
54. How do I – understand
that after updating ClearCase Remote Client, the ccrc.ini is blank
58. How do I – understand
why checkin of an unreserved file hangs in CCRC 7.1.x
64. How do I - enable region
mapping on UNIX or Linux CM server blocks login
65. How do I - customize
context menus in ClearCase Remote Client
66. How do I – understand
about removing elements from CCRC
68. How do I - synchronize a
CCRC view with a shared UCM stream
69. How do I – understand
the rcleartool and version extended paths
70. How do I - add existing
Web views to ClearCase Navigator in CCRC
71. How do I – use the
WebSphere collector tool to gather logs for a RWP installation
72. How do I - create a
batch file to restart IBM Rational CM Server
73. How do I - manually
remove a ClearCase Web view
74. How do I – understand
checkout/checkin within CCRC 7.0.1
75. How do I – understand
how to create a config spec templates for remote users of ClearCase
78. How do I - customize
context menus in ClearCase Remote Client
79. How do I – understand
about pathnames that exceed 256 characters and CCRC on Windows
81. How do I - write
triggers for the ClearCase Remote Client
82. How do I – change the
file association behavior in CCRC
83. How do I - change the
config spec of a CCRC view from an RWP server
84. How do I – understand
about clearfsimport capability in CCRC.
85. How do I – understand
the sample response files for IBM Rational ClearCase Remote Client
86. How do I – understand
about Multiple ClearCase Region Support on CCRC 7.0.1 Servers
87. How do I - trace CCRC
client operations on Windows
88. How do I – create config
spec templates for remote users of ClearCase
89. How do I - remove
elements from CCRC
90. How do I - access
previous versions of an element from CCRC
91. How do I – understand
about the discordance state in CCRC
92. How do I - stop the ClearQuest
Web 7.1 cmprofile service in Windows Task Manager
93. How do I - obtaining the
Edge component for use with ClearQuest and ClearCase on CM Server
95. How do I – understand
the CM Server configuration guidelines for CCRC in ClearCase version 7.1
97. How do I – why enabling
region mapping on Linux CM server blocks login
98. How do I – understand
change Management (CM) Server Administrative Security
99. How do I – why enabling
region mapping on Linux CM server blocks login
100. How do I – understand
server versions used by the Rational Web Platform and CM Server
101. How do I – understand
about the ccweb.conf file
102. How do I – understand
about Java Runtime (JRE) and ClearCase Web
103. How do I - trace
CCWeb client operations on Windows using Internet Explorer
General
1. How do I - update the IBM WebSphere Application Server components in Rational ClearCase and Rational ClearQuest 7.1
Updating
WebSphere Application Server
Unlike the version 7.0.n
releases of IBM Rational ClearCase and Rational ClearQuest, the Change
Management (CM) Server 7.1 ships with full IBM WebSphere Application Server
(WAS) version 6.1. One of the many advantages of the full version of WebSphere
Application Server is that you can apply updates as these become available.
WebSphere Application Server updates might improve the overall performance and
availability of ClearCase Remote Client (CCRC) and ClearQuest Web 7.1.
There are four main steps
to updating the WebSphere Application Server software:
1. Download the WebSphere
Application Server software updates.
2. Stop the ClearCase
Remote Client and the ClearQuest Web 7.1 services, which include the CM Server
WebSphere Application Server services and the IBM HTTP Server services.
3. Update WebSphere
Application Server.
4. Restart the ClearCase
Remote Client and ClearQuest Web 7.1 services, including the CM Server
WebSphere Application Server services and the IBM HTTP Server services.
Step 1:
Download the WebSphere Application Server software updates
Updates to WebSphere
Application Server are called fix packs. For CM Server 7.1, you need the latest
fix packs for WebSphere Application Server V6.1. The following location
contains information about the latest fix packs:
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27009661
You can also use the
Maintenance Download Wizard for WebSphere Application Server V6.1 to determine
if new fix packs are available:http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27009393
Use the following
guidelines when downloading the WebSphere Application Server software updates:
- Select the appropriate platform and
architecture/chipset for your server.
- On some UNIX system platforms, WebSphere
Application Server is available in both 32-bit and 64-bit. Always select
the 32-bit fix pack when given a choice.
- Update the AppServer (Application Server)
component, the IBM HTTP Server component, and the JavaTM SDK
component. These components require separate downloads. Copy the
downloaded files to the server you want to upgrade. Make a note of the
download location.
- The ClearCase and ClearQuest 7.1 Installation
Manager installs the IBM Update Installer for WebSphere Software. Upgrade
the Update Installer for WebSphere Software to the latest version. Consult
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24012718 and http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24020212.
Step 2: Stop the ClearCase Remote Client and ClearQuest Web 7.1 services
On
Windows:
Issue the following commands at the command prompt:
> cd <install-directory>\common\CM\profiles\cmprofile\bin
> stopserver.bat server1
> cd <install-directory>\common\IHS\bin
> apache.exe -w -n "IBM HTTP Server 6.1" -k stop
On the
UNIX system and Linux:
Issue the following commands at the command prompt:
$ cd <install-directory>/common/CM/bin/
$ cmserver_shutdown
Step 3:
Update WebSphere Application Server
The ClearCase and
ClearQuest 7.1 Installation Manager installs the IBM Update Installer for
WebSphere Software.
1. Navigate
to the directory where the IBM Update Installer for WebSphere Software is
installed.
On Windows:
Issue the following command at the command prompt:
> cd <install directory>\common\IHS_updateinstaller\
On the UNIX system and Linux:
Issue the following command at the command prompt:
$ cd <install-directory>/common/IHS_updateinstaller/
2. Run the
Update Installer.
On Windows:
Issue the following command at the command prompt:
> update.bat
On the UNIX system and Linux:
Issue the following command at the command prompt:
$ ./update.sh
3. Follow
the WebSphere Application Server Information Center instructions on how to
install a WebSphere Application Server fix pack: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tins_updi_install.html
Use the following guidelines when installing the fix pack:
·
You are prompted for the location of the product to update. You
can only update one product at a time. WebSphere Application Server and IBM
HTTP Server are considered separate products. Here are the default locations of
these products:
WebSphere Application Server:
On Windows: <install-directory>\common\eWAS
On the UNIX system and Linux: <install-directory>/common/eWAS
IBM HTTP Server:
On Windows: <install-directory>\common\IHS
On the UNIX system and Linux: <install-directory>/common/IHS
·
Next you are prompted for the location of the corresponding fix
packs.
·
The same Java SDK fix pack file is used for both the WebSphere
Application Server and IBM HTTP Server update.
·
Follow the on-screen instructions to complete the installation.
·
Restart the Update Installer to update another product. For
example, if you updated WebSphere Application Server first, then you must
restart the Update Installer to update the IBM HTTP Server.
Step 4:
Restart the ClearCase Remote Client and ClearQuest Web 7.1 services
1. On
Windows:
Issue the following commands at the command prompt:
> cd <install-directory>\common\IHS\bin
> apache.exe -w -n "IBM HTTP Server 6.1" -k start
> cd <install-directory>\common\CM\profiles\cmprofile\bin
> startserver.bat server1
On the UNIX system and Linux:
Issue the following commands at the command prompt:
$ cd <install-directory>/common/CM/bin/
$ cmserver_startup
2. Validate
that the ClearCase Remote Client and ClearQuest Web 7.1 are functioning
properly by looking at the log file:
<install-directory>\common\CM\profiles\cmprofile\logs\server1\SystemOut.log
The top of the file shows the version of WebSphere Application Server that is
running. For example, if you updated to Fix Pack 6.1.0.23, the log file will
look similar to this:
************ Start Display Current Environment ************
WebSphere Platform 6.1 [BASE 6.1.0.23 cf230910.10] running with process
name ....
Also, the file <install directory>\common\IHS\logs\error.log.[timestamp]
has the version of IBM HTTP Server that is running. For example, if you updated
to Fix pack 6.1.0.23, the file will contain information similar to this:
[Tue May 05 12:24:09 2009] [notice] IBM_HTTP_Server/6.1.0.23 Apache/2.0.47
(Win32) configured -- resuming normal operations
[Tue May 05 12:24:09 2009] [notice] Server built: Dec 4 2008 16:52:28
2. How do I – understand the feature Comparison Matrix for CCRC, CCWeb, Native ClearCase and SCM Adapter
IMPORTANT: ClearCase Remote Client (CCRC) provides a
stand-alone client based on Eclipse RCP (Rich Client Platform) technology
(supported on Windows and Linux only) and an Eclipse plug-in (supported on
Windows, UNIX and Linux). The features below relate to both CCRC types.
|
Capability |
Native ClearCase UNIX & Windows |
SCM Adapter for Eclipse 3.x.x |
CC Web |
CCRC 6.0 |
CCRC 7.0 |
CCRC 7.0.1 |
CCRC 7.1 |
Notes |
Supported
view types (create & access)
|
||||||||
|
Dynamic
views |
Yes |
Yes |
N/A |
N/A |
N/A |
N/A |
N/A |
|
|
Snapshot
views |
Yes |
Yes |
N/A |
N/A |
N/A |
N/A |
N/A |
|
|
Web
views |
N/A |
N/A |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Basic View
Management
|
||||||||
|
Create
View |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Remove
view |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
View
update |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Find
files (checkout, hijack, view private) |
Yes* |
Yes* |
Yes |
Yes** |
Yes** |
Yes** |
Yes** |
*Find
view private files from the command line only. |
|
Display/Modify
view properties (config spec & load rules) |
Yes |
Yes |
Yes |
Yes * |
Yes * |
Yes * |
Yes* |
* CCRC
doesn’t display the UCM generated config spec rules. It can only display the
“custom” rules for UCM controlled views. |
|
Pending
Changes |
No |
No |
No |
No |
No |
No |
Yes |
|
|
Copy
View Configuration |
No |
No |
No |
No |
No |
No |
Yes |
|
|
Scheduling
polling and dynamic notification of pending view updates |
No |
No |
No |
No |
No |
No |
Yes |
|
|
Capability |
Native ClearCase UNIX & Windows |
SCM Adapter for Eclipse 3.x.x |
CC Web |
CCRC 6.0 |
CCRC 7.0 |
CCRC 7.0.1 |
CCRC 7.1 |
Notes |
Basic
Version Control operations
|
||||||||
|
Add to
source |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes** |
|
|
Checkout
(reserved & unreserved) |
Yes |
Yes |
Yes* |
Yes |
Yes |
Yes |
Yes** |
*
Reserved only |
|
Checkin |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes* |
|
|
Aggregated
Checkin |
No |
No |
No |
No |
No |
No |
Yes* |
*
Perform checkin from anywhere in the hierarchy to checkin files below |
|
Uncheckout |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Aggregated
Uncheckout |
No |
No |
No |
No |
No |
No |
Yes* |
*
Perform uncheckout from anywhere in the hierarchy to checkin files below |
|
Hijack |
Yes |
Yes |
No * |
Yes |
Yes |
Yes |
Yes |
* No
specific GUI support, but can modify the file attributes |
|
Unhijack |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Aggregated
Unhijack |
No |
No |
No |
No |
No |
No |
Yes* |
*
Perform unhijack from anywhere in the hierarchy to checkin files below |
|
View
Element History |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
View
read only copy of another version in element history |
Yes* |
Yes* |
Yes |
No |
No** |
No** |
No** |
* From
command line only |
|
File/directory
namespace operations (Move, Rename,Copy,Delete/Remove (rmname)) |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Graphical
version tree browser |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
|
|
Draw a
merge arrow & arbitrary merge |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
Remove
versions and branches |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Capability |
Native ClearCase UNIX & Windows |
SCM Adapter for Eclipse 3.x.x |
CC Web |
CCRC 6.0 |
CCRC 7.0 |
CCRC 7.0.1 |
CCRC 7.1 |
Notes |
ClearCase
UCM and CQ-enabled UCM, unless otherwise noted
|
||||||||
|
Developer
Use capabilities |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
All
Non-Admin functionality |
|
Join
Multi-stream Project |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Join
Single-stream Project |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Scheduling
polling and dynamic notification of pending new baselines |
No |
No |
No |
No |
No |
No |
Yes |
|
|
Create
an Activity |
Yes |
Yes |
Yes* |
Yes** |
Yes** |
Yes** |
Yes |
*
ClearCase UCM only (not from CQ) |
|
Work-on
Activity |
Yes |
Yes |
No |
Yes* |
Yes* |
Yes* |
Yes |
* From
CCRC only (Support for filling required field upon transition to active state
via CQ Web form on Windows/Linux), you cannot choose a CCRC view when
initiating a work-on from CQ |
|
Find
Activities |
Yes* |
Yes* |
No |
Yes** |
Yes* |
Yes* |
Yes |
*
Cannot run arbitrary CQ query (for example "Browse") for CQ-enabled
UCM on UNIX |
|
Deliver/Rebase |
Yes |
Yes |
Yes* |
Yes** |
Yes** |
Yes** |
Yes |
* CQ
enabled deliver/rebase not supported |
|
Streamlined
Deliver/Rebase |
No |
No |
No |
No |
No |
No |
Yes* |
*
Allows single button deliver, start to completion if no manual merges are
required. Also include prompt to make baseline at completion of deliver. |
|
Rebase
to Non-recommended Baseline in Parent Stream |
Yes |
Yes |
No |
No |
Yes* |
Yes* |
Yes* |
* In
parent stream only |
|
Rebase
to Baselines in Non-Parent Stream |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Deliver
Baseline |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Alternate
Target Deliver |
Yes |
Yes |
No |
No |
No |
Yes |
Yes* |
|
|
Finish
Activity |
Yes |
Yes |
No |
Yes* |
Yes** |
Yes*** |
Yes |
*
Operation will fail if there are mandatory fields not completed |
|
Unset
Current Activity |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
Delete
Activities |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
View
Activity Properties |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
|
|
View
Change Set Versions |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Move
versions between Change Sets |
Yes |
Yes |
No |
No |
No |
No |
Yes |
The
ability to perform operations from the change set GUI |
|
View
Project Properties |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
View
Stream Properties |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
|
|
View
Baseline Properties |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
|
|
View
Component Properties |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
View
Contributing Activities |
Yes |
Yes |
No |
No |
No |
No |
Yes* |
|
|
Supports
ClearQuest-enabled UCM |
Yes |
Yes |
No |
Yes* |
Yes* |
Yes* |
Yes |
* With
restrictions: no new CQ-enabled activity |
|
Create
new CQ-enabled UCM activity |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
Browse
query |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
CC/CQ
single sign-on |
Yes |
Yes |
No |
No |
No |
No |
Yes* |
|
|
Display
CQ Forms (from activity properties, for entering mandatory fields) |
Yes |
Yes |
No |
No |
Yes* |
Yes** |
Yes*** |
* On
Windows/Linux only |
|
Project
Lead (Project Explorer) capabilities |
Yes |
Yes |
No |
No |
Yes* |
Yes* |
Yes* |
*Partial
capabilities |
|
UCM
Project Navigator View |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
|
|
Create
and Modify UCM Projects (including policies) |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Create
& Modify UCM Streams (including policies) |
Yes |
Yes |
No |
No |
No |
No |
Yes* |
|
|
Delete
Streams |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Create
Read-only Streams |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
Create
& Recommend Baselines |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
|
|
Create
UCM Components |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
View
Baseline Graphs |
Yes* |
Yes* |
No |
No |
No |
No |
No** |
* On
UNIX there is no graphical component tree browser available, but this can be
done textually |
|
Diff
Baselines |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Edit
Baseline Dependencies (including overrides) |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Capability |
Native ClearCase UNIX & Windows |
SCM Adapter for Eclipse 3.x.x |
CCWeb |
CCRC 6.0 |
CCRC 7.0 |
CCRC 7.0.1 |
CCRC 7.1 |
Notes |
Compare/Merge
|
||||||||
|
Compare
Versions |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Merge
Versions |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Merge
Manager |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Support
for all element types |
Yes |
Yes |
No |
Yes |
Yes* |
Yes* |
Yes |
*
'Never' & 'User' type is supported, New 'Copy' type is not supported |
|
Support
for Comparing/Merging UML Models (xtools2) |
Yes* |
Yes* |
No |
Yes |
Yes |
Yes |
Yes |
* Also
with ClearCase SCM Adapter |
|
Support
for Comparing/Merging UTF-8 |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
Capability |
Native ClearCase UNIX & Windows |
SCM Adapter for Eclipse 3.x.x |
CC Web |
CCRC 6.0 |
CCRC 7.0 |
CCRC 7.0.1 |
CCRC 7.1 |
Notes |
View/Edit
Properties of ClearCase Objects
|
||||||||
|
VOB
Properties |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
|
|
View
Properties |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Element
Properties |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Version
Properties |
Yes |
Yes |
Yes* |
Yes |
Yes |
Yes |
Yes |
*Limited
properties display |
|
Capability |
Native ClearCase UNIX & Windows |
SCM Adapter for Eclipse 3.x.x |
CC Web |
CCRC 6.0 |
CCRC 7.0 |
CCRC 7.0.1 |
CCRC 7.1 |
Notes |
Metadata
Capabilities
|
||||||||
|
Ability
to Create Branch Types |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
|
|
Ability
to Create Label Types |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
|
|
Ability
to Apply Labels |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
|
|
Ability
to Remove Labels |
Yes |
Yes |
No |
No |
No* |
No* |
No* |
* RFE for CCRC |
|
Ability
to Create Attribute Types |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Ability
to Apply & Modify Attributes |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Create
Trigger Types |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Create
hyperlinks (including symbolic links) |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Long
running tasks can be run in the background |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Findmerge |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
|
View
Update |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Load
Resources |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Checkin/Checkout/Add
to Source |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Progress
view allows users to view status of background jobs as well as cancel them |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Capability |
Native ClearCase UNIX & Windows |
SCM Adapter for Eclipse 3.x.x |
CC Web |
CCRC 6.0 |
CCRC 7.0 |
CCRC 7.0.1 |
CCRC 7.1 |
Notes |
|
“Cheat
Sheets” provide getting started information in a task-oriented approach |
No |
No |
No |
Yes* |
Yes* |
Yes* |
Yes* |
*
Cheatsheets are an Eclipse mechanism for developing embedded tutorials and
help systems, this support is part of the Eclipse platform. Creating custom
cheatsheets is not supported in the RCP version of CCRC |
|
Comprehensive
on-line help, including tutorials |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
|
|
Administration
capabilities |
Yes |
Yes |
No |
No |
No |
No |
No |
|
Installation
& Upgrades
|
||||||||
|
Zero
install client |
No |
No |
Yes |
No |
No |
No |
No |
|
|
Easy
install client |
No |
No |
N/A |
Yes |
Yes |
Yes |
Yes |
|
|
Support
for Automatic Client Updates |
No |
No |
N/A |
Yes |
Yes |
Yes |
Yes |
|
Integrations
|
||||||||
|
Base
ClearCase -ClearQuest Integration |
Yes |
Yes |
No |
No |
No |
Yes |
Yes |
|
|
Eclipse |
Yes* |
Yes* |
No |
Yes |
Yes |
Yes |
Yes |
* With
ClearCase SCM Adapter |
|
Rational
Software Development Platform |
Yes* |
Yes* |
No |
Yes |
Yes |
Yes |
Yes |
* With
ClearCase SCM Adapter |
|
.NET |
Yes |
No |
No |
Yes |
Yes |
Yes |
Yes |
.NET
2005 and later supported. Review Release Notes. |
|
Other
SCC |
Yes |
No |
No |
No |
No |
No |
No |
|
|
Capability |
Native ClearCase UNIX & Windows |
SCM Adapter for Eclipse 3.x.x |
CC Web |
CCRC 6.0 |
CCRC 7.0 |
CCRC 7.0.1 |
CCRC 7.1 |
Notes |
Client
Platform Support
|
||||||||
|
Windows |
-- |
-- |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Linux |
-- |
-- |
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
Solaris®,
HP-UX®, AIX® |
-- |
-- |
Yes |
No |
Yes * |
Yes * |
Yes * |
*
Plug-in version only, Stand-alone version is not supported. |
|
Mac
OSX™ |
-- |
No |
Yes* |
No |
No |
No |
No |
*
English only |
MultiSite
Support
|
||||||||
|
Support
for non-mastered, unreserved check-out |
Yes |
Yes |
No |
No |
No |
Yes |
Yes |
|
|
Posted
delivery |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
Yes* |
|
|
Find
(and complete) Posted Deliveries |
Yes |
Yes |
No |
No |
No |
No |
Yes |
|
|
Change
Mastership of ClearCase Objects |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Request
for Mastership Support for ClearCase Objects |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Change
Mastership of UCM Objects (including streams) |
Yes |
Yes |
No |
No |
No |
No |
No |
|
|
Request
for Mastership Support for UCM Objects |
No |
No |
No |
No |
No |
No |
No |
|
|
Element
creation using mkelem -master functionality |
Yes |
Yes |
No |
No |
No* |
No* |
No* |
* RFE
for CCRC RATLC01007906 |
Miscellaneous
Support
|
||||||||
|
Support
for Multiple Primary Groups |
Yes |
Yes |
No |
Yes |
Yes* |
Yes** |
Yes** |
*
Windows server only |
|
Support
for multiple region on the server |
N/A |
N/A |
No |
No |
No |
Yes* |
Yes* |
Review
technote 1264782 for
more information. |
|
Server-side
trigger support |
N/A |
N/A |
No |
No |
Yes* |
Yes** |
Yes ** |
*
Interactive triggers supported |
|
Command
Line Interface support |
Yes |
Yes |
No |
No |
No |
No |
Yes |
Review
document 4021929 for
version 7.1 information |
|
Public
API |
Yes* |
Yes* |
No |
No |
No |
No |
Yes ** |
* COM
and Perl |
* In new Pending Changes interfaceFootnote
1: Support for posted deliveries
- If the UCM integration stream is not
mastered at the CCRC server site, you can now do post deliveries from the
CCRC client.
- The deliver preview dialog detects
and indicates a post deliver is required. No integration view is required
for post deliveries.
- Once the delivery is posted, no
integration is done at the non-mastered site. The integrator picks up the
deliver at the master site and performs and completes the deliver.
Related
information
Differences between ClearCase and ClearCase LT
Getting started with the ClearCase Remote Client
Feature differences between ClearCase Eclipse plug-ins
TOC: ClearCase Family Table of Contents
Eclipse plug-in compatibility for CCRC
CCRC Community Space on developerWorks
Rational RFE Community
ClearCase 2003.06 System Requirements
ClearCase 7.0.x.x System Requirements
ClearCase 7.1 System Requirements
3. How do I - determine login credentials for CCWeb and CCRC
How to determine the
credentials used for authentication when using the IBM® Rational® ClearCase®
Web (CCWeb) Interface or the ClearCase Remote Client (CCRC) on Microsoft®
Windows®, UNIX® or Linux®.
There are two
undocumented commands that can be used to provide more verbose account
information from a CCWeb or CCRC client perspective:
1. creds
2. dump
Using your web
browser, type in the address bar the following URL (substituting the
appropriate server name and port number) to view the information on screen.
Note: You will be asked to re-enter your login information as the user
you are inquiring about.
For ClearCase version 7.0 and 2003.06, use:
- Windows Server creds:
http://host.domain.com:port_num/ccweb/bin/ccweb.exe?cmd=creds - Windows Server dump:
http://host.domain.com:port_num/ccweb/bin/ccweb.exe?cmd=dump - UNIX and Linux Server dump:
http://host.domain.com:port_num/ccweb/bin/ccweb?cmd=dump
For ClearCase version 2002.05, use:
- Windows Server creds:
http://host.domain.com:port_num/ccase/bin/ccweb.exe?cmd=creds - Windows Server dump:
http://host.domain.com:port_num/ccase/bin/ccweb.exe?cmd=dump - UNIX and Linux Server dump:
http://host.domain.com:port_num/ccase/bin/ccweb?cmd=dump
Note: The creds command will only work with Windows
RWP server whereas dump will work on both UNIX, Linux and Windows (and
provides much more information than just the users credentials.)
Examples
Output from a creds
URL will be similar to the following:
Login name: MyDomain\myuser
USID:
NT:S-1-5-21-1453292567-1645505489-561332275-11019
Primary group:
MyDomain\Domain Users (NT:S-1-5-21-1453292567-1645505489-561332275-513)
Groups: (8)
Everyone
(NT:S-1-1-0)
BC-W2K-SVR2\user (NT:S-1-5-21-606747145-507921405-1801674531-1008)
BUILTIN\Administrators (NT:S-1-5-32-544)
BUILTIN\Users (NT:S-1-5-32-545)
NT
AUTHORITY\INTERACTIVE (NT:S-1-5-4)
NT
AUTHORITY\Authenticated Users (NT:S-1-5-11)
LOCAL
(NT:S-1-2-0)
MyDomain\CC_CUP_USERS (NT:S-1-5-21-1453292567-1645505489-561332275-5265)
You do not have
ClearCase administrative privileges.
You are logged onto
Administrative-mode Terminal Server (Console)
Output from a dump URL will contain a "User credentials"
section near the bottom.
This section will look similar to:
User credentials
Login ID:
myuser(UNIX:UID-500)
Group ID:
cc_grp(UNIX:GID-54329)
Additional groups:
cc_web(UNIX:GID-54328)
Figure 1. Example single-server A deployment extended with additional
ClearQuest Server B
The first test was a 16-hour ClearQuest Web application load
performance test using an example customer schema. The hardware configuration
used was the same as the above single-server A deployment without Computer B.
The hardware consisted of dual Intel 2.4 Gigahertz Xeon processors and 2
gigabytes of memory. There were 50 concurrent users for a total of 750
transactions per hour. The transactions executed during the load tests
consisted of 70% database reads and 30% database writes. The transaction types
were:
- Login and Logout
- Create, modify, and view records.
- Create and run queries
Performance tests showed that approximately 7 megabytes of
memory per user was required for the ClearQuest Request Manager Server. This
value varied dramatically depending on the schema tested, as well as the
quantity and types of transactions. The Request Manager server was not CPU
bound. The ClearQuest Request Manager steady-state memory usage without any
users was approximately 60 megabytes. The Request Manager memory usage is the
hardware resource constraint for the ClearQuest Web application. Average
response times for this customer example schema were less than 6 seconds per
transaction.
The second test was also a 16-hour ClearQuest Web
application load performance test using an example customer schema, but the
deployment configuration was a single-server A with two additional servers,
Request Manager Servers B and C. There were 100 concurrent users, each
performing 15 transactions per hour. One server had the ClearQuest Web
Application deployed with a Request Manager similar to Computer A in Figure 1.
Two additional servers each had a Request Manager deployed. The single
ClearQuest Web application was able to support these three Request Managers
while maintaining an average response time of less than 6 seconds per
transaction. Each server in this test had dual Intel 2.4 Gigahertz Xeon
processors with 2 gigabytes of memory. The transactions executed during the
load tests consisted of 70% database reads and 30% database writes. The
transaction types were:
- Login and logout
- Create, modify, and view records.
- Create and run queries
Table 7. Hardware Requirements Using an Example Customer
Schema
|
Number Concurrent Users |
Process |
Memory |
Number CPUs |
Number of Transactions |
|
50 |
Tomcat |
60 Megabytes |
2 |
750/hr |
|
100 |
Tomcat |
80 Megabytes |
2 shared |
1500/hr |
Depending on the nature of your environment, you can use a
combination of the monitoring, tuning, and sizing methods described in this
paper not only to optimize the performance of IBM Rational ClearQuest Web, but
also other web-based applications and web server processes
4. How do I – understand why the ClearCase Remote Client command line does not cache login credentials
The CCRC
CLI command rcleartool login does not cache the user's login credentials.
After
running the command rcleartool login using the ClearCase Remote Client command line interface, and a
successful login occurs, the login credentials are not cached and subsequent rcleartool commands will prompt for a login again.
For
example:
C:\Documents and Settings\user\user_view\vob>rcleartool
login
Please enter the missing credentials:
Server URL:http://server:12080/TeamWeb/services/Team
User name:DOMAIN\user
Password:
You are successfully logged in.
Then immediately run the "ls" command:
C:\Documents and Settings\user\user_view\vob>rcleartool
ls
Please enter the missing credentials:
Cause
This is
currently working as designed.
Request
for Enhancement (RFE) RATLC01278706 has been submitted to allow for caching of
these credentials in the future.
Resolving
the problem
There is
currently no resolution for this RFE which is still under investigation.
You can view and post comments for RFE RATLC01278706 on the
RFE Community Web site.
Related
information
Rational ClearCase Remote Client Command Line Interface
5. How do I – understand about the .copyarea.dat and .copyarea.db files
How are the .copyarea.dat and .copyarea.db files are used in an
IBM® Rational® ClearCase® Remote Client (CCRC) or ClearCase Web (CCWeb) view.
Each CCRC or CCWeb view root directory (the directory tree where
the files from the VOB are downloaded into the local view workspace) contains a
.copyarea.dat and a .copyarea.db file. Below is a brief
explanation of how these files are used.
.COPYAREA.DAT
The .copyarea.dat file is used to detect if changes have been made
to the loaded files to determine is hijacked state.
The .copyarea.dat file stores information like:
- When a view was
created
- What http
server the view was originally connecting to
- The view's
Operating System platform
- CCRC remote
view tag
The contents of a .copyarea.dat file looks similar to the following:
ClearCase CopyArea|222|ed364ca8f7ee468185bfa528784055ed|a:Windows
XP|1c:Thu Mar 10 12:24:08 EST
2005|base|1f:htp://host1/ccase/bin/ccweb.exe|b:user1_host1|20
.COPYAREA.DB
The .copyarea.db file is created in each directory of a CCRC or
CCWeb view which contains a list of files that are loaded in the view as well
as metadata about the files.
If this file is missing or corrupt, you will notice that all or
some of the loaded files will appear to be hijacked.
Also, CCRC and CCWeb keep a record of both the timestamp and a
checksum for each element version downloaded. This information is stored in the
.copyarea.db file in each directory.
The contents resemble something like:
ClearCase
CopyAreaDB|4my_test_vob217:foo.doc|1|1028d7f8806|6000|89a7d530|cc22d419b775452ea0da8bf1b807c616|0
or
ClearCase CopyAreaDB|4
.
2
1
5:testvob|2|0|0|0|cb9bf50026fe43ef96160518044e8c93|0
The CCRC and the ClearCase Web use the following algorithm to detect if a file
has been changed:
1.
First, the file size is checked. If the file size has changed, then
the file has been hijacked.
Next, the file's timestamp is checked. If the timestamp has
changed, then the CRC of the file is checked. If the timestamp AND the CRC of
the file have changed, then the file has been hijacked. If only the timestamp
changed, but the CRC is still the same, then the new timestamp is updated in
the copyarea.db.
6. How do I – understand the backup considerations for ClearCase, CaseCase Remote Client and ClearCaseWeb
As far as ClearCase is concerned, backing up a ClearCase RWP Web server
is very similar to normal ClearCase backup procedures. Refer to the IBM
Rational ClearCase Administrators Guide under the topic of Backing
up Critical Rational ClearCase Data for further details.
However, there are a few additional considerations:
1. A
snapshot or Web view may have a view storage directory that is in a different
location, perhaps on a separate host, from the directory where the downloaded
files are stored.
Web views almost always have this configuration, as do snapshot views on
Rational ClearCase LT. You must back up both directories. Refer to technote
1150413 Moving the view storage location of a web view for
information about the location of the web view directory on the web server.
2. The
ccweb.conf configuration file as described in technote
1125332 About the ccweb.conf file should be backed up as well. This
file should be preserved since it makes changes to the RWP server for all
clients to use and allows a ClearCase administrator to enforce certain policies
when clients connect to the server. A list of the options that can be
configured on the RWP host can be found in the ccweb.conf file.
If you have customized the RWP server to use secured sockets, you
should backup the ssl.conf configuration file. Refer to the IBM Rational
ClearCase Administrators Guide under the topic of Configuring
secure access to RWP for further information about this file.
Remote Client
Installation & configuration
7. How do I – understand the availability of CCRC Version 7.0.1 Client Update 7.0.1.D090928
This
news alert is meant to inform you about the availability of IBM Rational
ClearCase Remote Client (CCRC) version 7.0.1 client update 7.0.1.D090928 which
is available for download.
Content
IBM
Rational Remote Client version 7.0.1 client update 7.0.1.D090928 is available
for download.
Download the 7.0.1.D090928 zip file here: 7.0.1.D090928
All CCRC 7.0.1 client updates are here: CCRC 7.0.1 Client update site
Refer to technote 1224586 System Requirements for the ClearCase
Remote Client for further details regarding CCRC system
requirements.