Oracle® Enterprise Repository IBM® Rational® ClearCase® and IBM Rational ClearQuest® Integration Guide 10g Release 3 (10.3)
July 2009
Copyright (c) 2008, 2009, Oracle and/or its affiliates. All rights reserved. 1 of 21 Oracle Enterprise Repository IBM Rational ClearCase and IBM Rational ClearQuest Integration Guide, 10g Release 3 (10.3)
Copyright © 2008, 2009, Oracle. All rights reserved.
Primary Author: Vimmika Dinesh
Contributing Author: Jeff Schieli, Sharon Fay, Dennis Chin, Scott Spieker, Phil Reed, Adam Wallace The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
Copyright (c) 2008, 2009, Oracle and/or its affiliates. All rights reserved. 2 of 21 Oracle Enterprise Repository
Connector for IBM Rational ClearCase and IBM Rational ClearQuest
● ClearCase Integration: ClearCase Web Interface ● ClearCase Integration: File Stores ❍ Using File Stores ● ClearQuest Integration
Copyright (c) 2008, 2009, Oracle and/or its affiliates. All rights reserved. 3 of 21 ClearCase Integration: ClearCase Web Interface
Overview
This document explains the proper procedure to follow in order to setup a ClearCase repository, which will allow ClearCase files to be linked to assets for future use/download.
Important Note
Webshpere 5.x Apache Plug-In
When using an HTTP server (such as Apache, IIS, IBM HTTP Server, etc.) to connect to a Websphere 5.x server using the mod_was_ap20_http.so or mod_was_ap20_http.dll plug-in, a configuration change must be applied to the plugin-cfg.xml document used with this connector:
● Each time the crtplugininst application is run to regenerate the plugin-cfg.xml document for use on the HTTP server(s) the Config element will contain a value of AcceptAllContent="false" by default. This parameter will need to be changed to true to allow deltaV requests to be passed between the HTTP Server and the Websphere application server hosting the Oracle Enterprise Repository. This restriction only applies to an HTTP server using the Websphere plug-in to connect the two servers.
WebLogic 8.1 Tuxedo Plug-In
When using the Weblogic Tuxedo Plugin, there is a requirement of 8.1 SP3 being applied to both the application server as well as the Tuxedo Plug-In on the Apache server. This required feature was applied with change request #CR084303.
Prerequisites/Requirements
● The application server must support the UTF-8 character set to allow ClearCase and Oracle Enterprise Repository to function properly together. ● Make sure the application server has access to the ClearCase server. ● CCWeb and/or ClearTool must be installed and enabled on the application server machine (see your ClearCase documentation for details).
Enabling UTF-8 Support
Enabling the UTF-8 character set is accomplished in the following manners based on the server employed.
● Weblogic 7.x/8.x ❍ You may specify the character set for all deployed Weblogic Web applications deployed on a Weblogic Server instance by setting the system properties client.encoding.override and file.encoding equal to the
Copyright (c) 2008, 2009, Oracle and/or its affiliates. All rights reserved. 4 of 21 name of the character set. Set this system property in the environment variable called JAVA_OPTIONS. For example: JAVA_OPTIONS=-Dclient.encoding.override=UTF-8 -Dfile.encoding=UTF-8 These values can also be supplied as part of the startup options for the domain.
● Websphere 5.x ❍ Change the Generic JVM Arguments for the server to include the following parameter: -Dclient.encoding. override=UTF-8
● Tomcat 5.0.25 ❍ Change the URIEncoding value in the Connector element within the server.xml file in the CATALINA_HOME/ conf directory:
Note: The ability to browse into the ClearCase server and view files/directory structure/etc. from within the Oracle Enterprise Repository application is provided via Files Stores integration. Important Notes 1. Construct a view in CCWeb. 2. Create the link based on that view constructed in CCWeb. 3. Add the link within the File Information section of the asset within the Asset Editor. 4. Select the Test button to verify that the link is valid. 5. It should also be possible to access the link by pasting the URL into a browser address window. If this is not possible the link itself may be in error, or there may be a problem with the network connection to the ClearCase server. Creating and Configuring Repository and Assets Configure an Artifact Store This procedure is performed in the Oracle Enterprise Repository Asset Editor screen. 1. Open the Actions menu. 2. Click Configure Artifact Store 3. Click Add 4. Fill in the appropriate information. Copyright (c) 2008, 2009, Oracle and/or its affiliates. All rights reserved. 5 of 21 5. Click OK Set the artifact store from which to extract files This procedure is performed on the Oracle Enterprise Repository Admin screen. 1. Click System Settings. 2. Enter cmee.server.paths.upload-repository in the Search box. The Upload Area group within the Server Settings section will open. 3. Use the Submission Upload Artifact Store drop-down menu to select the ClearCase repository. 4. Click Save when finished. Create an asset for the ClearCase file(s) 1. Click Submit an Asset on the Oracle Enterprise Repository Assets screen. Copyright (c) 2008, 2009, Oracle and/or its affiliates. All rights reserved. 6 of 21 ❍ New assets may also be created via the File menu in the Asset Editor. 2. Select an Asset Type from the drop-down menu. 3. Enter a name for the new asset in the Name text box. 4. Enter a brief description in the Description field. Note: The asset detail will not appear on Oracle Enterprise Repository Assets screen until the registration process is completed. Link the ClearCase file to the asset 1. Open the asset in the Asset Editor. 2. Locate the File Information section (typically on the General tab). 3. Click Add. 4. Create a name and/or description. 5. Click Edit. 6. Select the Repository File radio button. Copyright (c) 2008, 2009, Oracle and/or its affiliates. All rights reserved. 7 of 21 7. Select ClearCase in the Host drop-down.