Run the Insight Data Batch Process

In-house customers can follow these steps to manually run the batch process to refresh the Insight data if necessary.

Start the Insight Data Batch Process

1. Login as the server admin - admin@d
2. Click the Manage Insight Data link on the Manage Server screen. The chart shows the following information for the last 1000 batch runs:
   1. Date and time when the batch job was Started
   2. Date and time when the batch job completed/failed/stopped or was marked abandoned.
   3. Status of the batch jobs previously run - completed/failed/stopped/abandoned.
      
      
      
      
3. Click the icon to initiate a new batch job.
4. The Start Refresh of Insight Data screen displays.
5. Select the tenant(s) for the batch job run. The choices are:
   1. All Tenants on the server
   2. A Specific Tenant
   3. If you select Specific Tenant then you must specify the tenant name. Type part of the tenant id into the search field and click the Search button. In the image, the Insight Data batch process will run for a tenant named mycompany. Notice only a partial portion of the tenant id was typed into the search box to display the list of tenants that meet the search criteria:
      
      
      
      
6. Click Submit to start the batch process. The Refresh Insight Data Batch Job Status screen redisplays with a success message, the Date and time the batch job began and the status of the batch job as Started.
   
   

Stop the Insight Data Batch Process

Once you have initiated the Insight Data Batch process, the UI allows for the job to be stopped or aborted. The batch process can be stopped if it is in the STARTING or STARTED state.

You will notice a Stop column in the row in the table for the process that was started. To stop the job:

1. Click the Stop icon .
   
   
   
   
2. Click Ok to confirm.
   
   
   
   
3. When the batch job is stopped, the status column will update.
   
   

Restarting a Stopped Insight Data Batch Process

When the batch job runs, tables that store the state of the job are created in the frevvo database. By default, if a job were to fail or be stopped, starting the job again would restart the failed/stopped job from where it failed/stopped.

To restart a Stopped/Failed batch job, simply start the batch job again with same tenant and it will resume the last stopped job. 

To prevent the last stopped job from restarting, change the status to Abandoned.

Abandoning the Insight Data Batch Process

The Insight Data Batch Process can be abandoned if it is not in the STARTING or STARTED state. The batch job must be stopped to mark it as abandoned. This prevents it from being restarted. You may want to abandon a batch job if it failed and restarting it would result in another failure. Abandoning the batch job allows you to start over again with a new process.

When you stop a batch process, you will notice Stop and Abandon columns in the row in the table for the process that was started. To abandon the job:

1. Stop the Insight Data Batch Process
2. Click the Abandon icon in the row in the Abandon column for the batch job you want to prevent from restarting.
   
   
   
   
3. Click Ok to confirm.
   
   
   
   
4. The Refresh Insight Data Batch Job Status screen will update.
   
   

Specify a Submission Start Date for the Insight Data Batch Process

If you are not interested in data before a certain date, configure the parameter index.submission.start.date  to a date in the YYYY-MM-DD format in the <frevvo-home>\tomcat\conf\catalina\localhost\insights.xml file. The batch will then exclude any submissions before this date.

Troubleshooting

Additional information, about the Insight Batch Job can be found in the <frevvo-home>\tomcat\logs\insight.log file.

Insight Batch Job displays a status of UNKNOWN

If you are using Oracle 12c as your database, you may see a batch job that displays a status of Unknown . This status indicates that the batch job did not complete.

If you see this status, you may see the following errors in the <frevvo-home>\tomcat\logs\frevvo.log:

Failed to map Submission{id:16ce6738-a62a-48b2-826c-3d65be386ca2} Caused by: java.io.IOException: 
IO Error: Unexpected packet
Rolling back with transaction in unknown state
Application exception overridden by rollback exception
Non-skippable exception during read

Solution:

The version of the Oracle thin JDBC driver must be ojdbc7. Update your existing driver to the ojdbc7.jar. in the <frevvo-home>\tomcat\lib directory.