Upgrade the Web Interface
This article details about how to upgrade your Web Interface on Windows, UNIX, and Linux.
cahscm101
This article details about how to upgrade your Web Interface on Windows, UNIX, and Linux.
How to Prepare for the Web Interface Upgrade
Follow these steps:
- If you have not already done so, review the Release Information. Do not upgrade the Web Interface until you have reviewed the release notes. For more information, see Release Notes.
- Determine the Web application server type.
- Determine the full path to the existing Web Interface installation (that is, Harweb home).For WebSphere, this is the directory where the harweb.war file is deployed.For example, Tomcat on Windows:C:\Program Files\Apache Software Foundation\Tomcat 6\webapps\harwebFor example, Websphere on Windows:C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\computer-nameNode01Cell\harweb.ear\harweb.warFor example, Tomcat on Linux/UNIX:.../Tomcat/apache-tomcat-6.0.2For example, Websphere on Linux/UNIX:.../IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/computer-nameNode01Cell/harweb.ear/harweb.war
- Determine the temporary directory to be used by the installation (a default is provided by the wizard).
- Determine the deployment directory (that is, the full path to the web application server's home directory).
Upgrade the Web Interface (Windows, UNIX, and Linux)
You upgrade the Web Interface so that the new product features can be used. Users who need to upgrade their Web Application servers to meet the system requirements of this
CA Harvest SCM
release cannot upgrade. Instead, they must uninstall the existing Web Interface and then do a new installation.Before upgrading the Web Interface, verify that you have access rights to create directories and files in this location.
Follow these steps:
- Start or stop your application server.
- (WebSphere) This application server must be running during the upgrade.
- (Apache Tomcat and JBoss) These application servers must be shut down during the upgrade.
- (Optional) If you have customized anyCA Harvest SCMJSP pages in your existing Web Interface installation, back them up to a different location.Do not copy the previously customized JSP pages back into your upgraded product installation. You shouldonlyuse these JSP pages as a reference to customize the upgraded versions.
- Uninstall the previous version of the product client.
- Verify that the current version product client is installed.
- (WebSphereonly) Open <harweb-home>/WEB-INF/harweb.cfg and manually add the entries for SCM Database user and password as follows and then restart the WebSphere application server:User=<SCM-Database-User>Password=<SCM-Database-Password>
- Start the installation by inserting the installation media in your drive.
- Click Upgrade to start the upgrade.
- Read theRelease Informationto help ensure that the application server you are using is supported by the product. If necessary, uninstall your existing application server and install a supported version.
- Deploy the harweb.war file to the application server.When you install the Web Interface, you can enter non-English characters (such as Japanese or accented characters) when specifying the name of the context root (.war file name). However, if you use non-English characters in the name of the .war file, your application server may encounter errors, and may not be able to generate a context with a matching name, because of system limitations in some servlet containers. Therefore, we strongly recommend that you only use single-byte, English characters when naming the .war file.
- (WebSphereonly) Open <harweb-home>/WEB-INF/harweb.cfg and remove the SCM Database user and password as follows, execute svrenc to create harweb.dfo file, and then restart WebSphere application server:
- Windows:svrenc - f harweb.dfo - dir “<harweb-home>\WEB-INF”
- UNIX, Linux:svrenc - f .harweb.dfo - dir “<harweb-home>/WEB-INF”