Chat now with support
Chat with Support

Stat 6.0 - Upgrade Notes

Upgrading Stat Upgrade the Stat Central Agent Upgrade the Stat Oracle Agent (Oracle E- Business Suite only) Additional changes Appendix: Upgrade Checklist

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.7 or 1.8 to support AES256, you need to download and apply the Java® Cryptography Extension (JCE).

2
Download the Java Cryptography Extension (JCE), which is contained in the appropriate zip file (jce_policy-7.zip or jce_policy-8.zip) to a temp folder and unzip the file.
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

This functionality is supported for the standalone platform only. It is recommended that you first configure the Stat™ Central Agent without https and validate that it can be started and is functional before switching to https.

2
Delete <STAT_HOME>/app/standalone/tmp.
4
Once you have the keystore, move it to <STAT_HOME>/app/standalone.
a
Go to <STAT_HOME>/app/ standalone/ standalone-full.xml and turn on SSL.
c
g
Uncomment the block by moving the trailing --> to the end of this line:
At this point users can log in as http://servername:8080/stat or as https://servername:8443.
b
Move <STAT_HOME>/app/standalone/deployments/stat-agent.ear to a location outside of the <STAT_HOME> folder for backup purposes.
c
Locate the stat-agent.ear file in stat-agent-https.zip from this distribution package and copy it into <STAT_HOME>/app/standalone/deployments.

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.

Installing multiple servers on the same host

Stat™ currently supports installing up to four Stat Central Agents on the same host machine (provided there are no port conflicts). Additional Stat Central Agents are installed basically the same way as the first server, except you will need to install the additional servers to separate directories, define separate system variables, modify the startup files, and assign the servers to different port profiles.

If you need to install more than four servers on the same computer, contact Technical Support.

NOTE: You can install only one Stat Central Agent per Stat Repository.
1
Unzip the contents of stat_standalone.zip to a location on the host computer that is different from the location where the first Stat Central Agent is installed. This location will be referred to as <STAT_HOME2>.
2
Create an environment system variable called STAT_HOME2 with a value of <STAT_HOME2> from the above step.
For Windows, go to <STAT_HOME2>\app\bin, open the file standalone.conf.bat in a text editor, and locate the line:
Change the value "%STAT_HOME%" to "%STAT_HOME2%".
Change the value for –Djboss.socket.binding.port-offset from zero to a proper value.
For Unix, go to <STAT_HOME2>/app/bin, open the file standalone.conf in a text editor, and locate the line:
Change the value $STAT_HOME to $STAT_HOME2.
Change the value for –Djboss.socket.binding.port-offset from zero to a proper value.
The value for port-offset assigns a new offset of ports to the second Stat Central Agent. See Resolving port and firewall conflicts for information on choosing the proper value for port-offset and resolving port conflicts.
Related Documents