This chapter describes ClearCase support for the ToolTalk™ integrated software development environment. ClearCase can broadcast ToolTalk messages whenever ClearCase performs a configuration management operation, no matter how that operation was requested: from a ToolTalk tool, from the ClearCase graphical user interface, from the ClearCase command line interface, from the ClearCase API, and so on. This flexibility accommodates a variety of working styles without sacrificing tool integration.
ToolTalk tools communicate with ClearCase through the ToolTalk Session Server, ttsession, and two ClearCase processes:
After ToolTalk has been configured to work with ClearCase, certain ToolTalk commands automatically invoke ClearCase operations. When a ToolTalk tool makes a configuration management request, such as CM-Checkin-File, the ToolTalk Session Server receives the message and passes it on to clearencap_tt. (The Session Server starts an encapsulator process if one is not already running.) clearencap_tt evaluates the message and invokes the appropriate ClearCase tool, such as cleartool checkout.
If the operation succeeds, the ClearCase tool returns a success exit status to clearencap_tt, which sends a success reply back to the Session Server.
If the operation fails (non-zero exit status), the encapsulator returns a failure status to the Session Server.
In both cases, the Session Server passes the final status message back to the requesting ToolTalk tool.
On SunOS systems, do not start any ToolTalk program from a shell that is set to a view. As you work, use view-extended pathnames to indicate the desired view context(s).
On IRIX systems, you can work as described in the preceding paragraph. Alternatively, you can start a ToolTalk program from within a view; the program will be able to communicate only with other programs that were also started from within that view. You can use standard (non-view-extended) pathnames with such programs.
A ClearCase tool can send a success message even if the operation was not initiated by a ToolTalk tool:
Make sure that the ClearCase tool and the Session Server both have the environment variable DISPLAY set to the same value.
Run the ClearCase tool in an environment with CLEARCASE_MSG_PROTO set to ToolTalk.
(An error occurs in a ClearCase tool that has CLEARCASE_MSG_PROTO set correctly, but not DISPLAY.) In this environment, the Notice Forwarder generates a success message on each applicable ClearCase operation that succeeds.
The notice forwarder process logs errors, warnings, and other messages in file /usr/adm/atria/ti_server_log.