H2 Database Version 2.1.214 Upgrade Migration for Web Viewer 14.0

Products

• Output Management Web Viewer

Issue/Introduction

The current H2 database version 1.x has found to be vulnerable. An upgrade and migration procedure to 2.1.214 is now available.

Environment

Web Viewer 14.0

VIEW 14.0

H2 Database

Cause

Required to mitigate vulnerabilities in H2 1.x versions

Resolution

Required to mitigate vulnerabilities in H2 1.x versions

H2 2.x database format not compatible with 1.x format

• Requires manual migration while the database is not in use
• Export data using 1.x library; create new database using 2.x library; import data

There are two steps. Can be performed separately:

SET UP FOR MIGRATION

1. Apply Maintenance
   LU08230 SAMPLE JCL FOR MAINTENANCE OF PRODUCT H2 DATABASE for View 14.0 
   LU08231 SAMPLE JCL FOR MAINTENANCE OF PRODUCT H2 DATABASE for Web Viewer (14.0.60)
   These supply new CVDEJCL members to create, maintain and upgrade the H2 database.  This also provides a new Web Viewer war file.  14.0.03 build 14.0.60 
   The Web Viewer USS files need to be mounted or the receive, apply and accept of these fixes will fail.
   These PTF's maintain backward compatibility. There is support for both H2 1.x and 2.x library versions
   Will be part of the PRE chain for updates to product war, ear and utilities jar
   Update read write permissions on the USS files to 777; Update ownership
   
   See details in Customize the CAHVVARS Member

MIGRATE

1. Before applying the H2 new version PTF, run CAHVH2CP job to copy your current H2 file.  
2. Apply Follow-up PTF LU08416 SECURITY OR INTEGRITY PROBLEM - updates H2 new jar file to 2.1.214
3. Update read write permissions on the new jar file
   Requires performing database migration BEFORE APPLY (then APPLY and then cleanup)
   NOTE: Will not be a Prerequisite for a while to give customers time to choose when to migrate

See On Line documentation below for step by step instructions.

Also included in this update:

New approach to JCL sample customization

Modular approach to allow separation of customer modifications from the executed logic
Customer modification modules should be copied from installation CVDEJCL library to customer library
Reusable environment variables are specified in CAHVVARS
Top level JCL members for given operation are modified
specify JOB card
specify JCLLIB ORDER to prefer modified members
Execution logic is kept in unmodified INCLUDE members
Currently focused on H2 maintenance operations, to be extended to other samples later

Example job:

CAHVH2CR (modified)
CAHVVARS (modified)
CAHV#HCR
CAHV$ISH
CAHV$ENV
CAHV$HCR

Additional Information

On Line documentation:  Migrate an H2 Database 

New JCL Samples Delivered

Prepare and Maintain an Application Database
CAHVH2CR - Create an H2 database
CAHVH2BK - Backup an H2 database.
CAHVH2RS - Restore an H2 database backup archive to a new H2 database
Migrate an H2 Database
CAHVH2CP - Copy the H2 JAR file
CAHVH2MG - Migrate the H2 database from the previous H2 version to the current H2 version
CAHVH2DL - Delete the copied H2 JAR file
Miscellaneous
CAHVH2PV - Backup a database created by the previous H2 version
CAHVH2DT - Delete an H2 database
CAHV$$$$ readme member in CVDEJCL