Post-Installation Steps

This section covers steps that must be or can be performed after installation, but before logging into the system or importing data into the system. Each step is described separately.

Database Maintenance Plan

Honeywell recommends setting up regular database maintenance jobs to maintain optimal system performance.

  • Schedule a database transaction log backup job to run. This should run regularly between full backups, typically once per day. For higher volume systems or if performance begins to degrade, schedule this job to run more frequently. It will not greatly impact performance of the system, but will improve it over a long duration of time.
  • Rebuilding and reorganizing indexes regularly can increase performance in higher volume systems as the indexes on the tables may become fragmented. Schedule these jobs for SQL Server anywhere every 4 to 24 hours depending on your system. For Oracle, once a day should be sufficient

Initial Database Connection Pool Settings

Performance optimizations for installations supporting many devices

The connection pool for database connectivity can be adjusted, if necessary, in the database.properties file. The property and default value are:

Connection.maxPoolSize=20

Listed below are the recommended initial settings, which may be tuned as needed. Other factors may influence performance and require connection pool optimization, such as the number of client browsers that will be connected.

  • For up to 1000 devices, maintain the default value of 20
  • For 1001 to 1500 devices, set to 30
  • For 1501 to 2000 devices, set to 40
  • For 2001 to 2500 devices, set to 50
  • For each additional 500 devices, add 10 connections

Warning: Increase the connection pool value only when absolutely necessary. Setting this value too high may cause database deadlocks.

Apache Tomcat Performance Tuning

Depending on the number of device and browser connections expected, you may need to configure Tomcat.

In a text editor, open the server.xml file found in: <installation path>\tomcat\conf.

In the connector definitions (for HTTP and HTTPS) add or adjust the following properties.

  • maxThreads: The number of actual worker threads should be in the range of 20% of total connections expected. The default is 150. If, for example, you expect a typical load of 1000 workers and 500 browsers, then set this property value to 20% of 1500, or 300.
  • acceptCount: The number of threads that Tomcat will accept and hold until a worker thread is available. This value can be a large number close to total connections possible, but cannot exceed your machine’s limitations in memory and threads allowed. Various operating systems are different; for example Windows 64-bit architecture allows a much larger threshold than Windows 32-bit systems.

Refer to Apache Tomcat documentation for other performance settings.

Java Virtual Machine Settings

The default memory settings for the Tomcat application server Java Virtual Machine start at 256 MB and can grow up to 1024 MB. A setting of 1GB (1024 MB) is sufficient for most installations, but this will vary by the type and amount of data you intend to view unfiltered in your VoiceCheck system. To size this yourself, open the window in the application with the data you expect to view and check the Mem Usage on Windows Task Manager.

To change JVM settings in Windows, do the following:

  1. Run the VocollectWebApplicationsVoiceCheckw.exe file in the bin folder of the Tomcat install under the Vocollect directory.
  2. Click on the Java tab.
  3. If using the internal transcription engine, add the following parameters in the Java Options input box.

    -XX:MaxPermSize=512m

    -XX:PermSize=256m
  4. Change the Maximum Memory Pool setting to your desired value.

    1024 MB recommended for small load implementations

    2048 MB recommended for up to 2500 workers

    Add an extra 1024 MB for the internal transcription engine

  5. change the Initial Memory Pool setting as needed.

    512 MB recommended for small load implementations

    1024 MB recommended for up to 2500 workers

  6. Set Thread stack size. (1024 KB recommended)
  7. Click OK to save the settings and close the window.
  8. Restart the webservice.