In the left panel, click System Settings. Click Save.

1-4 Oracle Fusion Middleware Integration Guide for Oracle Enterprise Repository 2 ClearCase Integration 2-1 2 ClearCase Integration This chapter describes how to set up a ClearCase repository and integrate it with Oracle Enterprise Repository. This chapter contains the following sections: ■ Section 2.1, ClearCase Web Interface ■ Section 2.2, File Stores ■ Section 2.3, ClearQuest Integration

2.1 ClearCase Web Interface

This section explains the procedure to follow to setup a ClearCase repository, which allows ClearCase files to be linked to assets for future usedownload. This section contains the following topics: ■ Section 2.1.1, Overview ■ Section 2.1.2, Prerequisites ■ Section 2.1.3, Creating and Configuring Repository and Assets

2.1.1 Overview

This section contains the following topics: ■ Webshpere 5.x Apache Plug-In ■ WebLogic 8.1 Tuxedo Plug-In Webshpere 5.x Apache Plug-In When using an HTTP server such as Apache, IIS, IBM HTTP Server 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 servers the Config element contains a value of AcceptAllContent=false, by default. This parameter must 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. 2-2 Oracle Fusion Middleware Integration Guide for Oracle Enterprise Repository 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.

2.1.2 Prerequisites

Before using ClearCase, you must perform the following prerequisites: ■ The application server must support the UTF-8 character set to allow ClearCase and Oracle Enterprise Repository to function properly together. ■ Ensure the application server has access to the ClearCase server. ■ CCWeb andor ClearTool must be installed and enabled on the application server computer. For more information, see the ClearCase documentation. Enabling UTF-8 Support Enabling the UTF-8 character set is accomplished in the following manners based on the server employed. ■ Weblogic 7.x8.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 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_HOMEconf directory: Connector port=8080 URIEncoding=UTF-8 ... 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.

Note: The ability to browse into the ClearCase server and view filesdirectory structure from within the Oracle Enterprise Repository application is provided through Files Stores integration.