Chat now with support
Chat with Support

Stat 6.1 - Install Notes

Installing Stat
Prepare for installation Unpack the 6.1.0 installer Install the Stat database Create a staging database (PeopleSoft Only) Install the Stat Client Configure the Stat database Update the System Maintenance table Install the Stat Central Agent Install the Stat Oracle Agent (Oracle E- Business Suite only) Configure the SYSTEM user account Update the PS Object Mover Instructions (PeopleSoft Only) Implement Stat

Configure 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.

If the Stat Central Agent is running on Windows®:
1
Open <STAT_HOME>\app\bin\standalone.conf.bat.
2
Locate the following:
set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M -Dstat.home="%STAT_HOME%" -Djboss.socket.binding.port-offset=0 -Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US -Dcom.microsoft.tfs.jni.native.base-directory="%STAT_HOME%/tfs-native-dlls" -Doracle.jdbc.V8Compatible=true"
3
At the end of the line and included inside the final quote mark, add:
-Dweb.charset=UTF-8
The final edit will look like this:
set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M -Dstat.home="%STAT_HOME%" -Djboss.socket.binding.port-offset=0 -Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US -Dcom.microsoft.tfs.jni.native.base-directory="%STAT_HOME%/tfs-native-dlls" -Doracle.jdbc.V8Compatible=true -Dweb.charset=UTF-8"
4
Restart the Stat Central Agent.
If the Stat Central Agent is running on UNIX®:
1
Open <STAT_HOME>/app/bin/run.conf.
2
Locate the following:
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Stack=true -Dstat.home=$STAT_HOME -Djboss.socket.binding.port-offset=0 -Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US -Dcom.microsoft.tfs.jni.native.base-directory=$STAT_HOME/tfs-native-dlls -Doracle.jdbc.V8Compatible=true"
3
At the end of the line and included inside the final quote mark, add:
Add -Dweb.charset=UTF-8
The final edit will look like this:
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Stack=true -Dstat.home=$STAT_HOME -Djboss.socket.binding.port-offset=0 -Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US -Dcom.microsoft.tfs.jni.native.base-directory=$STAT_HOME/tfs-native-dlls -Doracle.jdbc.V8Compatible=true -Dweb.charset=UTF-8"
4
Restart the Stat Central Agent.

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:

•
Blowfish
•
Triple DES
•
AES128
•
AES192
•
AES256

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

1
Go to the following url: http://www.oracle.com/technetwork/java/javase/downloads/index.html
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.

Configure 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.

To configure Web Client to use HTTPS:
1
Shut down the agent.
2
Delete <STAT_HOME>/app/standalone/tmp.
3
Obtain a keystore with a self-signed certificate from your security group or build it yourself, if authorized.
You need to know the keystore file name and the password that opens it.
4
Once you have the keystore, move it to <STAT_HOME>/app/standalone.
5
Do the following to turn on SSL:
a
Go to <STAT_HOME>/app/ standalone/standalone-full.xml and turn on SSL.
b
Look for this block in the file:
<!--
<security-realm name="SslRealm">
<server-identities>
<ssl>
<keystore path="keystore.jks"
relative-to="jboss.server.config.dir"
keystore-password="changeme"/>
</ssl>
</server-identities>
</security-realm>
-->
c
Uncomment the block by moving the trailing --> to the end of this line:
<!--
d
Modify the keystore-password to equal the password written in the keystore.
e
Modify the path to match the keystore file name (in the example above, change only the keystore.jks to the appropriate name).
The edits will now look like this:
<!-- -->
<security-realm name="SslRealm">
<server-identities>
<ssl>
<keystore path="statagent.keystore"
relative-to="jboss.server.config.dir"
keystore-password="password"/>
</ssl>
</server-identities>
</security-realm>
f
Look for this block in the file:
<!--
<https-listener name="default-ssl" socket-binding="https" security-realm="SslRealm" max-post-size="999999999"/>
-->
g
Uncomment the block by moving the trailing --> to the end of this line:
<!--
The edits will now look like this:
<!-- -->
<https-listener name="default-ssl" socket-binding="https" security-realm="SslRealm" max-post-size="999999999"/>
At this point users can log in as http:servername:8080/stat or as https:servername:8443.
6
Do the following to have the port location automatically change from 8080 to 8443 when logging into the Stat Web Client:
a
Stop the agent
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.
7
Restart your agent.
8
Access the Stat Web Client as before.
If you input http://<servername>:8080/stat, you will automatically be directed to the secure location of https://<servername>:8443/stat.
9
If you have a firewall, make sure that port 8443 is open on the firewall.

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 2x as long to actually disconnect from the environment.

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

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating