Deploying OM Web Viewer 14.0 with Tomcat 10 STDOUT info missing CAHVS9000E

Products

• Output Management Web Viewer

Issue/Introduction

1. After deploying the web-viewer.war file by following Procedure 2 as defined in the documentation, after start up under the STC the STDOUT DD there is no output available. Usually the STDOUT would contain web-viewer information if the start up was successful. What is missing?
2. After resolving that, the following error is displayed:

   CAHVS9000E Internal Server Error. HTTP status: 500 INTERNAL_SERVER_ERROR, Exception: com.broadcom.msd.om.contentviewer.common.exception.DatabaseException, Error: CAHVS0203E Cannot connect to external database No JDBC URL available

Environment

• Output Management Web Viewer™ for z/OS
• Apache Tomcat® 10

Cause

1. Not following HOLDDATA
2. Incorrect configuration
3. Old build of Web Viewer

Resolution

1. LU15712 TOMCAT 10 Support must be applied
2. Moving web-viewer.war to ../webapps-javaee/ fixed the startup issue.

Additional Information

The Web Viewer build version 14.0.97 you are trying to install on Tomcat 10 requires a slightly different deployment procedure. The DOC HOLDDATA for the LU15712 contains important information about how to install an older version of Web Viewer 14 to Tomcat 10. That procedure is required for all builds between 14.0.97 and 14.0.107. Here is the information provided by the LU15712 DOC HOLDDATA:

Note that if you are using a custom procedure for deploying the product 
WAR file instead of the CCS deployment sample JCL (TOMWAR) you will have
to adjust your procedure when transitioning to CCS Apache Tomcat 10.    
With CCS Apache Tomcat 10 the product WAR file must be currently        
deployed into the 'webapps-javaee' directory instead of the 'webapps'   
directory.                                                              

You may simply try deploying your WAR into 'webapps-javaee' Tomcat folder to see if it helps. But would still suggest you apply LU15712 and follow the HOLDDATA to get the new installation samples in place.

Another option would be to install a newer version of the product (>= 14.0.107) where the special procedure of deploying into webapp-javaee is no longer needed.

Deploy the product to a CCS Tomcat Server

2. At the very top of the uploaded "external db error.txt" file. It says you have the CAWVHOME environment variable set to "/u/tomcat1f/CAWVHOME". The product searches for the configuration file in "config" subfolder but could not find it.

2025-11-11 15:49:51.019 E (*init) CAHVS0021E Parameter configuration file /u/tomcat1f/CAWVHOME/config/ConfigFile.cfg not found

Since the configuration file was not found, the JDBC URL is not fetched.

The JDBC URL can also be set through WV_DATABASE_JDBC_URL environment variable. For that I would recommend using the new installation samples provided by LU15712. The current installation guide refers to them.