Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Stat 6.3 - Install Notes

Installing Stat
Prepare for installation Unpack the 6.3.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 Web Client to use HTTPS

2
Delete <STAT_HOME>/app/standalone/tmp and <STAT_HOME>/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
Go to the <STAT_HOME>/app/bin directory and locate the standalone.conf.bat (for Unix, standalone.conf) 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:

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.

CAUTION: Shorter times could adversely affect agent performance.

Configure Web Client and Web Services to use custom URL

Installing multiple servers on one host computer

Stat® currently supports installing up to four Stat Central Agents on the same host computer (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 server, 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 on the host computer 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 and open the standalone.conf.bat file in a text editor. 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 and open the standalone.conf file in a text editor. 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

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating