We reviewed the zip file documents from the link we received for the internal Derby to DB2 conversion:
NEED CONVERSION FROM INTERNAL DATABASE TO DB2, RO74120.
We see there is a JAR file to migrate Web Viewer data from the internal Derby database to a DB2 database. However, it doesn’t contain any instructions on how to re-configure the Apache Tomcat/Web Viewer to use the new DB2 database after the data migration.
Pointing Web Viewer 12.1 to the newly created and populating the Web Viewer DB2 database, is not a part of the database migration tool. When you are finished running the migration tool, Web Viewer 12.1 will still be using the internal Derby database.
To get off of Internal Derby, you have to run the Web Viewer configTool and point to the new DB2 database. After you've saved that change and recycled Tomcat, Web Viewer should come up using the new DB2 database.
If you're running Web Viewer on a Windows Server, and you took the defaults when installing, you should find the ConfigTool in the C:\Program Files\CA\CA_OM_Web_Viewer\util folder. For other environments, the path to the configTool will be similar.