Stat 6.3 - Install Notes

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.

Table or View Does Not Exist error

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.

Change the default timeout setting

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.

Display graphical objects

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

Keep the telnet session open

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:

•

Other applications are using the same port as the Stat Central Agent

•

You are running multiple Stat Central Agents on the same host machine and the installations are trying to access the same ports

•

The default timeout setting on a firewall prevents the Stat Central Agent from opening properly

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

java.net.BindException: Address already in use: Bind

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:

•

if offset is zero, ports 8080, 8443, 9990, 9993, 4712, and 4713 are used.

•

If offset is one, ports 8081, 8444, 9991, 9994, 4713, and 4714 are used.

•

If offset is two, ports 8082, 8445, 9992, 9995, 4714, and 4715 are used.

•

If offset is 100, ports 8180, 8543, 10090, 10093, 4812, and 4813 are used.

Table 4. Ports

Description	Ports
HTTP socket binding	8080
HTTPS socket binding (See Note)	8443
Management socket binding	9990
Management socket binding https (See Note)	9993
Transaction sockets	4712 4713

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.

Port configurations

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.

Review the port configurations described above and decide on a proper offset.

Open <STAT_HOME>\app\bin\standalone.conf.bat with Notepad or other text editor. For Stat Central Agent on Unix, you need to open the <STAT_HOME>/app/bin/standalone.conf file.

Search for the setting: -Djboss.socket.binding.port-offset=0

Change the setting to a proper offset. For example, -Djboss.socket.binding.port-offset=10

Firewall configuration

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

•

Client to Central agent: 8080 (If port-offset has changed, add the value to 8080)

•

Central Agent to Oracle agent: 8080 (If port-offset has changed, add the value to 8080)

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

•

Stat database (Oracle® default=1521; MSS default = 1433)

•