After applying PTF LU17323 OM Web Viewer 14 fails to deploy

Products

Output Management Web Viewer

Issue/Introduction

After applying PTF LU17323 WEB VIEWER: REPORT FAVORITES (NEW FEATURE), Web Viewer fails to deploy when the application server is using a Java version prior to Java 17.

If you are deploying Web Viewer to a CCS Apache Tomcat server, the following messages appear in STDERR:
SEVERE: Error deploying web application archive [/your/path/web-viewer.war]
...
Caused by: java.lang.UnsupportedClassVersionError: JVMCFRE199E bad major version 61.0 of class=org/springframework/web/SpringServletContainerInitializer, the maximum supported major version is 55.0; offset=6 (unable to load class [org.springframework.web.SpringServletContainerInitializer])

If you are deploying Web Viewer to a WebSphere Liberty server, the following messages appear in STDOUT:
Launching XXXXXXXX (Liberty Dev Use VV.V...) on IBM J9 VM, version 11.0.nn+n (XXXX)
...
CWWKZ0012I: The application web-viewer was not started.

Environment

Output Management Web Viewer™ for z/OS
CCS Apache Tomcat
WebSphere Liberty server

Cause

With PTF LU17323 the OM Web Viewer software requirements have changed, the lowest supported Java version is Java 17. Java 8 and 11 are no longer supported.

Resolution

Review changes to the OM Web Viewer software requirements as documented in the HOLDDATA for PTF LU17323.

Additional Information

HOLDDATA

This PTF includes:
- Changes to the OM Web Viewer software requirements.
- Updates to the OM Web Viewer database schema.
- Updates to OM Web Viewer sample members.

1. Review changes to the OM Web Viewer software requirements:

- The lowest supported Java version is Java 17. Java 8 and 11 are no
longer supported.
- The lowest supported CCS Apache Tomcat version is version 10.
Version 9 is no longer supported.
- The lowest supported version of IBM WebSphere Liberty server is
version 23.
- The IBM WebSphere Liberty Jakarta Servlet 6.0 feature is
required, Java Servlet 3.1 feature is no longer supported.
- IBM WebSphere Application Server is no longer supported.

If you are using an unsupported Java version or application server
version, you must migrate to a supported version.
If you are using IBM WebSphere Application Server, you must migrate
to a supported application server.
See the OM Web Viewer documentation topic Migrate from a Java 8/11
Environment for more information.

2. Backup your OM Web Viewer database:

The OM Web Viewer database schema updates are NOT compatible with
prior builds of web-viewer.war. We STRONGLY RECOMMEND that you backup
your OM Web Viewer database before you apply this PTF! This will give
you the option of reverting to the prior release if you encounter
issues after the upgrade.

If you are using an H2 database (either internal or external), see
the OM Web Viewer documentation topic Backup an H2 Database for more
information on backing up your H2 database.

If you are using a Db2 database, see the IBM Db2 documentation for
more information on backing up your Db2 database.

3. Backup previously customized members:

This PTF will create or overwrite the following sample members
in the installation data set &VIEWHLQ.CVDEJCL:
- CAHVCHCK (new)
- CAHVH2DL
- CAHVH2SV
- CAHVIAUD
- CAHVRORG (new)
- CAHVTOMX
- CAHVVARS
- CAHVWSRN (content removed)

This PTF will also create or overwrite the following sample members
in the installation data set &VIEWHLQ.CVDEOPTN:
- CAHVCENV
- CAHVDDDL
- CAHVD002 (new)
- CAHVEALL
- CAHVHCFP
- CAHVHDDL
- CAHVHERL
- CAHVHFEA
- CAHVHGRP
- CAHVHRPO (content removed)
- CAHVH002 (new)
- CAHVOPTS
- CAHVZDDL (new)
- CAHVZ020 (new)
- CAHVZ021 (new)
- CAHVZ022 (new)

If you have customized any of these members manually and you plan to
continue using those customizations, make a backup before you apply
this PTF.

This PTF includes:
- Updates to sample JCL members that are copied to the user data set
&USERHLQ.CVDEJCL during OM Web Viewer installation and
configuration.
- Updates to sample members that are copied to the user data set
&USERHLQ.CVDEOPTN during OM Web Viewer installation and
configuration.
- Updates to the OM Web Viewer database schema which are NOT
compatible with prior builds of web-viewer.war.
- Updates to the web-viewer.war file in the OM Web Viewer
installation directory.
- Changes to some aspects of generated spreadsheet documents
when using the export report action. The spreadsheet can now include
more than one worksheet in order to accomodate more than 1 million
rows. The names of the worksheets have also been adjusted to include
the report name and a sequence number when multiple worksheets are
used. For full details please refer to
"Structure of Generated Spreadsheet" in the "Export Reports" section
of the product documentation.

1. Update user data sets &USERHLQ.CVDEJCL and &USERHLQ.CVDEOPTN:

If you have not yet prepared your customized &USERHLQ.CVDEJCL
and &USERHLQ.CVDEOPTN user data sets, follow the steps documented in
OM Web Viewer documentation topic Prepare Customized Data Sets. The
user data sets &USERHLQ.CVDEJCL and &USERHLQ.CVDEOPTN created by
sample JCL CAHVIAUD will include the updates from this PTF.

If you've already created your &USERHLQ.CVDEJCL and &USERHLQ.CVDEOPTN
user data sets, use the following steps to propagate the updates
from this PTF to your existing data sets:
- Move the following members from your existing &USERHLQ.CVDEOPTN
user data set to a backup data set:
- CAHVCENV
- CAHVDDDL
- CAHVHDDL
- CAHVOPTS
- Reapply any manual customizations to the updated CAHVIAUD sample
member in the installation data set &VIEWHLQ.CVDEJCL. See the
OM Web Viewer documentation topic Create User Customized Data
Sets for more information on sample JCL CAHVIAUD.
- Run your customized CAHVIAUD member to copy the new and updated
sample members to your existing &USERHLQ.CVDEJCL and
&USERHLQ.CVDEOPTN user data sets.
- Reapply any manual customizations from your backup data set to
the updated CAHVCENV, CAHVDDDL, CAHVHDDL and CAHVOPTS sample
members in your existing &USERHLQ.CVDEOPTN user data set.

2. Upgrade your existing application database to the new database
schema:

If you have not yet created the application database, see the OM Web
Viewer documentation topic Prepare and Maintain an Application
Database. The application database will be created with the new
database schema.

If you have an existing application database created by a prior
build, you must upgrade the application database to the new database
schema. The application can upgrade the database schema automatically
during startup, or you can upgrade the database schema manually.

Details on upgrading the database schema can be found in the OM Web
Viewer documentation:
- For an H2 internal or H2 external database, see the topic Upgrade
an H2 Database.
- For a Db2 database, see the topic Upgrade a Db2 Database.

Important: Once you have upgraded your application database to the
new database schema you can NOT use prior web-viewer builds with the
application database.

3. Redeploy the OM Web Viewer WAR file:

The updated web-viewer.war must be deployed to your application
server. For more information, see the deployment section for your
application server in the OM Web Viewer documentation:
- Deploy the Product to a CCS Apache Tomcat Server
- Deploy the Product to a WebSphere Liberty Server