Chat now with support
Chat with Support

Stat 7.0 - Upgrade Notes

Configuring the Stat Central Agent character map

The Stat® Central Agent defaults to a character map of ISO-8859-1, which is compatible with sites that are upgrading from older versions of Stat. If desirable, the agent can be configured to use UTF-8.

1
Open <STAT_HOME>\app\bin\standalone.conf.bat.

Setting up support for AES256 ciphers for SFTP

The configuration of your SSH server determines which ciphers are used when connecting to the Stat™ Central Agent. The Stat Central Agent currently supports the following cipher configurations:

To configure J2SE 1.8 to support AES256, you need to download and apply the Java® Cryptography Extension (JCE).

NOTE: As JDK 9 and later offers the stronger cryptographic algorithms by default, you can skip the following steps if you are using JDK 9 or above.
3
Browse to the JAVA_HOME/jre/lib/security directory under your installation of JAVA_HOME.
4
Rename local_policy.jar to local_policy.jar.strong.
5
Rename US_export_policy.jar to US_export_policy.jar.strong.
6
Go to the temp folder where you unzipped the jce_policy file and copy local_policy.jar and US_export_policy.jar.
7
Paste both files into the JAVA_HOME/jre/lib/security folder.

Configuring the Web Client to use HTTPS

2
Delete /app/standalone/tmp and /app/standalone/data if one exists.
4
Once you have the keystore, move it to <STAT_HOME>/ app/standalone/configuration.
5
Go to <STAT_HOME>/ app/ standalone/standalone-full-https.xml to point to your keystore.
7
Search for this block in <STAT_HOME>/app/standalone/standalone-full-https.xml
<key-manager key-store="StatSSLKeyStore" name="StatSSLKeyManager">
<credential-reference clear-text=" keystorepassword"/>
</key-manager>
9
Go to the <STAT_HOME>/app/bin directory and locate the run.bat (for Unix, run.sh) file.

After configuring the Stat Central agent to run in https mode, http protocol is completely removed from the Wildfly configuration file. This means that the messaging protocol used between the Stat Central agent and all Stat Oracle Agents must use secure messaging over https. This means that the certificate stored in your keystore file must be imported into the JAVA_HOME installation of your Stat Oracle Agents.

3
Finally you need to tell the Stat Oracle Agent to use https protocol for its communications. Edit the <STAT_HOME>/conf/stat.conf file and uncomment the following property:

Modifying connection pool idle time

This feature allows the site to define the length of time before the Stat™ Central Agent connection pool times out database connections. The default is 15 minutes. However, Java® could take up to twice as long to actually disconnect from the environment.

IMPORTANT: Shorter times could adversely affect agent performance.
1
Open <STAT_HOME>/config/stat.properties.
2
Locate the parameter CONNECTION_IDLE_TIME=15, and modify the time.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating