Skip to main content
View as Markdown

Other Recommended Settings

There are a number of recommended settings for running kanoaMES.

For this training, you will need to change the following settings via the Gateway Console page...

Hands-on
  1. Enable Include Schema in table Name for the kanoaCore database connection.
  2. Set Max Active to -1 for the kanoaCore database connection.
  3. Adjust the User Inactivity timeout to -1 under Config → Security → General (Ignition 8.1), Platform → Security → General Settings (Ignition 8.3). This will keep you from having to login every 10 minutes.
View All Recommended Settings

Every implementation is different — some sites have a couple of production lines, others have hundreds. You may only make one product or thousands. Regardless, here are some settings we recommend starting with.

Set WebSocket max memory size to 4096​

Perspective views pass data to popups via web sockets and asset imports and analyzing large Quality SPC datasets can contain a lot of data. You'll need to increase the web socket max memory setting in order to not run into any errors.

Increase websocket size
  1. Open the ignition.conf file that is located in the data folder that’s found in your Ignition installation path
  2. Open the ignition.conf with any text editor
  3. Within the ignition.conf file, scroll down to where it says # Java Additional Parameters; This is the location where JVM parameters are added into Ignition and where we will be adding our web socket max message size parameter
  4. Copy/Paste the following line in the # Java Additional Parameters section of the ignition.conf file:
wrapper.java.additional.X=-Dperspective.websocket.max-message-size=#
  1. Replace X in the line with the next sequential parameter number that is seen in the file.
  2. Replace # in the line with the websocket max message size value in KB; The default size is 2048 KB when no value is specified
  3. Save changes to the ignition.conf file; A restart of the Ignition gateway service will be required for the changes to take effect. This can be done by following the instructions that are provided in the following link: Gateway Command-line Utility - gwcmd - Ignition User Manual 8.1 - Ignition Documentation

Here is an example of how the JVM parameter entry would look like :

WebSocket Setting

Enable “Include Schema in Table Name” for the kanoaCore database connection​

In the kanoaCore database connection configuration (Advanced Properties), we recommend enabling:

  • Set Include Schema in Table Name to true
  • Set Max Active to -1 in the advanced options

Adjust the User Inactivity Timeout​

In the Gateway settings, we recommend reviewing and adjusting the User Inactivity Timeout to keep you from having to login every 10 minutes:

  • Config → Security → General (Ignition 8.1)
  • Platform → Security → General Settings (Ignition 8.3)

Enable Database Concurrency​

We recommend switching on READ COMMITTED SNAPSHOT ISOLATION (RCSI) in Microsoft SQL Server.

Enabling this feature:

  • Helps avoid Reader/Writer blocking - In default mode, a SELECT can block or be blocked by an UPDATE, INSERT, or DELETE. With RCSI, readers get a consistent snapshot without locking the table.
  • Reduces Deadlocks - Because RCSI avoids shared locks, there's much less lock contention, and fewer deadlocks in high-concurrency environments.
  • Improves Read Scalability - Excellent for reporting queries, dashboards, APIs, or UIs that only need committed data and can tolerate a slight delay in seeing updates.

To enable RCSI, log into SQL Management Studio as a user with dbOwner permission on the Kanoa Core database and run the following:

SELECT is_read_committed_snapshot_on 
FROM sys.databases 
WHERE name = 'kanoaCore';

--USE master;
--GO

--ALTER DATABASE kanoaCore...
--SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
--GO

--ALTER DATABASE kanoaCore...
--SET READ_COMMITTED_SNAPSHOT ON;
--GO

--ALTER DATABASE kanoaCore...
--SET MULTI_USER;
--GO

From Other Recommended Settings →

Last updated on