Cumulative Build Remains the Same after Applying Maintenance to Web Viewer 12.1 for Windows
search cancel

Cumulative Build Remains the Same after Applying Maintenance to Web Viewer 12.1 for Windows

book

Article ID: 253664

calendar_today

Updated On:

Products

Output Management Web Viewer

Issue/Introduction

After applying a cumulative build to Web Viewer for Windows and starting the service and clicking on ABOUT, the previous build number is still displayed.

During the install, the Pre Installation Summary states the wrong Tomcat Build

On the Install Complete Page the wrong Tomcat Build is Displayed

Environment

  • Output Management Web Viewer 12.1 for Windows
  • Apache Tomcat®

Cause

During the application of a CUMULATIVE BUILD you will be prompted to "Select an Update Target, Update Web Viewer running on an Apache Tomcat Server.......

However if you click Next to accept the default is not correct and your upgrade will not work

Resolution

This problem is resolved with LU09689 Security or Integrity Problem (Cumulative Build 239) Apply the Latest cumulative maintenance for Web Viewer
Note: the maintenance is the same for each platform.

This is the workaround if you are not at that build:

To recover: Install the build again:

  1. Verify what version of Tomcat you are running.  Check the version of Tomcat in the Services.
  2. When installing the build you will be prompted to:
    "Select an Update Target"
  3. Select the top Button, which says Update Web Viewer running on an Apache Tomcat Server, Select the Web Viewer unzipped web application folder, Choose"

 

4. Click in the path and go to the end and verify that the path specifies the Tomcat you are running.  For example

             C:\Program Files\CA\CA_OM_Web_Viewer\apache-tomcat-9.0.62\webapps\CAOMWebViewer12

5. If not correct, 

    • In the path you will see webapps, select down arrow
    • Select CA_OM_Web_Viewer
    • Select the Tomcat you are running 
    • Select webapps again
    • Select CAOMWebViewer12 again
    • Click OK
    • Select Next and Complete the install.

Additional Information

The above resolution is a workaround.  The fix will be in build 244 or later.