Stat 7.0 - Install Notes

Installing the Stat Central Agent

Stat® provides a platform on which you can install the Stat Central Agent.

NOTE: Stat 7.0 Central Agent works with Java 21.

You need to have a Java® Development Kit (Java SDK) installed and a system variable called JAVA_HOME
that points to the JDK installation root directory (e.g., C:\Program Files\Java\jdk-21.0.3).

If you are running Windows® or Solaris and Java® is not installed, or if you have an older version of Java installed, go to http://www.oracle.com/technetwork/java/javase/downloads/index.html and download the appropriate version.

NOTE: Do not unzip the file stat_standalone.zip file to a directory that contains an exclamation point character (!). For Unix, use the -a modifier to unzip the file. If copying the installation files to a Unix system, be sure the file transfer settings are set to binary as opposed to ascii.

NOTE: Do not add a backslash character (\) to the end of the STAT_HOME variable.

NOTE: If you have port conflicts during startup, the server will display one or more error messages. For instructions on resolving port conflicts, see Resolving Port and Firewall Conflicts. Optionally you may set the STAT_HOME and JAVA_HOME variables in standalone.conf.bat or standalone.conf file instead of defining system environment variables.

NOTE: If you receive a Connection Refused error when your Stat Windows Client is trying to access the Stat Central Agent, you may need to start your Stat Central Agent with a -b parameter to specify the hostname of the agent. In this case, edit your run.bat (run.sh for Unix) and add -b=<hostname>, where <hostname> is the hostname for the machine running the Stat Central Agent. For example, in run.bat: standalone.bat -b=ALVWindows For example, in run.sh: ./standalone.sh -b=ALVLinux

Configuring the Stat Central Agent

Refer to the following sections for information on the number of ways you can configure the Stat Central Agent.

NOTE: Before making any configuration changes, be aware of the following: • If customizations are needed (such as hard coding the location of JAVA_HOME or <STAT_HOME>), then the modifications should be made to standalone.conf or standalone.conf.bat • <STAT_HOME>/app/bin/service/service.bat is used to start the service. It calls run.bat. See section Configuring the Stat Central Agent as a Windows Service for more information. It is recommended that you validate that the agent will start without the service before invoking the service operation.

Before starting the Stat Central Agent

The following are configuration issues you may need to address while installing the Stat® Central Agent but before starting it for the first time. After reviewing and addressing these issues, you can resume the installation as documented in the section Install the Stat Oracle Agent (Oracle E-Business Suite only).

To authorize access to the configuration page, you as a Stat administrator need to edit the stat-config.properties file in <STAT_HOME>/config. The privilege to modify the configuration is administered using the IP address of the computer. You can grant user permission to change the configuration by adding the computer IP address to the list of the property auth.user.ip (IPV4 and IPV6 formats are supported). For example, you can grant user John the permission by appending his computer IP address (e.g. 192.168.244.130) to the list. You can add multiple IPs to the list and use a comma to separate them. After you complete editing the stat-config.properties file, change its permission so no other users can view or edit it.

Generic applications and Oracle E-Business Suite users may see a table or view does not exist error message in the Stat Central Agent log file after migrating a database object. This error is due to a query against a test table that is normally present in PeopleSoft® installations, and while it does not affect the migration, to avoid receiving this message, open the stat.properties file in <STAT_HOME>/config and locate the following variable, TestTableName=PSOBJGROUP. Set this variable to the name of a table in the database you are working in, for example, TestTableName=DUAL.

The default timeout setting for connections between the Stat Central Agent and your environments is 15 minutes. If you want to increase or decrease the time amount, open the stat.properties file, locate the variable CONNECTION_IDLE_TIME=15, and change the setting to the number of minutes you want. For more information, see Connection Pool Idle Time.

If you have installed the Stat Central Agent on Unix®, you may experience problems displaying graphical objects (such as workflow diagrams, reports and email) in the Stat Web Client. These errors are generated because the graphics libraries installed with the Stat Central Agent on Unix are implemented using XWindows/Motif graphics libraries, which require access to an X server. To resolve this issue, you need to download and install the X Virtual Frame Buffer (Xvfb), a free virtual server that provides the same graphical resources as a X11 Windows Server®. Installing the Xvfb is platform-specific. For more information, please contact the Support Portal at http://quest.com/support/.

If the Stat Central Agent was started on Unix with telnet, closing the telnet session may cause the Stat Central Agent to shut down. To keep the Stat Central Agent running after closing Telnet, go to <STAT_HOME>/app/bin and execute nohup run.sh & to run the process in the background.

Resolving port and firewall conflicts

If the Stat® Central Agent will not run when started, the port assigned to it may already in use by a different program or there are firewalls that need to have ports opened for the Stat Central Agent to communicate with the database or with the Stat Client.

Typical port and firewall conflicts include:

If you have port conflicts, the server will display one or more error messages, such as:

The Stat Central Agent utilizes a set of ports that are already defined.

These values are defined for a default port offset of zero which is set in a variable called jboss.socket.binding.port-offset in standalone.conf.bat or standalone.conf file. If there is a conflict situation or a second or third agent is necessary, you may change the jboss.socket.binding.port-offset in standalone.conf.bat or standalone.conf file. The value for offset is added to all the default values.

For example:

NOTE: Be aware of the following: • Stat invokes the DNS server to resolve the fully qualified server name when communicating between the client and the central agent. When server hostname is not registered on the DNS server, use etc/hosts file to map hostname and its IP address. • HTTPS connector socket and Management socket — These ports are only necessary if the Stat Central Agent is configured to support HTTPS. See Configure Web Client to Use HTTPS.

When other applications are using the same port as the Stat Central Agent, you need to change the port offset in your standalone.conf.bat or standalone.conf file.

The http port is the only port that needs to be opened on existing firewalls.

Other ports used by the Stat Central Agent include the following (the actual port numbers will vary according to your site specifications):

The Stat Client will need the same ports opened if there is a firewall between the client and any of the above items.

If there is a natted firewall between the Stat Central Agent and the Stat Oracle Agents, the following options must be configured in the stat.conf file for the Stat Oracle Agents. Older versions of Stat always required the fields to be filled in, but since 5.7.0, the Stat Oracle Agents query the Stat Central Agent for the secure Stat database information. You need only change the stat.db.server: value and indicate the natted ip address. For this scenario, they are not optional.