Cora Knowledge Center

Support

Post-Migration Procedures and Considerations

V9.0

Overview

After you migrate the database, you can run additional SQL scripts to optimize the database, verify that links to custom files are not broken, and remove redundancy from specific jobs. 

Download scripts from this location.

NOTE
Any changes to configuration, shared resources, web pages, or other types of customization, require building a customized application.
For more information on building customized applications, see this article.  

This article covers the following procedures:

  • Remove unused tables
  • Map jobs to hosts
  • Ensure custom files are located in the correct Shared Resources folder

Remove unused tables

Cora SeQuence V9.0, data from USL and UWF tables have been consolidated for efficiency and improved system performance. 

  • USL tables: Hot Operations solution tables, previously known as USL tables, have been consolidated into global tables, and an archiving mechanism has been created to store data from closed tasks and cases into a separate table.
  • UWF tables: The UWF table, which stores the values of each workflow instance variables, now stores data related to an entire workflow space, including all workflow versions.

After migration, run the following SQL scripts to remove the old USL and UWF tables: 

NOTE
Before you run the scripts, remove any custom references to the old tables from database views, stored procedures, or functions.

  1. Run the following scripts: 
    • 09 - Optional - Drop all USL tables.sql 
    • 10 - Optional - Drop Obsolete UWF tables.sql

Map jobs to hosts

After migration, all jobs are configured as redundant by default. 

If certain jobs need to run on a specific host, run the following SQL script to map a job to a host: 

  1. Stop all JES instances.
  2. Open script Optional - Make job non redundant.sql, and edit the following parameters:
    • JOBHOSTNAME: Change to the name of the required job host (JES) that should run the job.
    • JOBNAME: Change to the name of the relevant job.
  3. Run the script for each job that you need to allocate to a specific host.
  4. Start all JES instances.

Ensure custom files are located in the correct Shared Resources folder and referenced correctly

In previous versions, the Shared Resources folder was located, by default, under Program File\PNMsoft\Shared Resources.
In Cora SeQuence V9.x, every deployed application has its own Shared Resources folder. 

If your implementation includes custom files, such as JavaScript, CSS, and image files, you need to move these files to the new Shared Resources location.

TIP

You can run the following script to get a list of all the activities that use the Shared Resources folder:
11 - Optional - Find activities with Shared Resources.sql.

  • Check the results to make sure that links included in the source code are not broken, and the references are set correctly.
  • The script can take several minutes to run.

NOTE
Flowtime and Administration applications are deployed as sites (IIS root level). Make sure that your references are set correctly.