Previous Topic: How to Prepare for the Web Interface UpgradeNext Topic: Configuring the Database

Upgrading the Web Interface › Upgrade the Web Interface (Windows, UNIX, and Linux)

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.

Important! Before upgrading the Web Interface, verify that you have access rights to create directories and files in this location.

Follow these steps:

  1. Start or stop your application server.
  2. (Optional) If you have customized any CA Harvest SCM JSP pages in your existing Web Interface installation, back them up to a different location.

    Note: Do not copy the previously customized JSP pages back into your upgraded product installation. You should only use these JSP pages as a reference to customize the upgraded versions.

  3. Uninstall the previous version of the product client.
  4. Verify that the current version product client is installed.
  5. (WebSphere only) 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>
  6. Start the installation by inserting the installation media in your drive.
  7. Click Upgrade to start the upgrade.
  8. Read the Release Notes to 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.
  9. Deploy the harweb.war file to the application server.

    Important! 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.

  10. (WebSphere only) 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:

    The Web Interface installation is upgraded.