Stat 6.1 - Upgrade Notes

Configuring the Stat Central Agent on the standalone platform

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

NOTE: Before making any configuration changes, be aware of the following: • Modifications should not be made to either run.sh or run.bat. Instead, if customizations are needed (such as hard coding the location of JAVA_HOME or <STAT_HOME>), make the modifications to standalone.conf (for run.sh) or standalone.conf.bat (for run.bat). • <STAT_HOME>/app/bin/service/service.bat is used to start the service by calling run.bat. See 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 Upgrading the Stat Central Agent on the standalone platform.

If you have any custom report definitions you want to carry over to 6.1.0, copy the <STAT_HOME>\report\custom\format folder from its previous location and paste it to the new 6.1.0 <STAT_HOME> directory, and remove any files with a .jasper extension for the Custom folder.

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 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 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 data 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 variable TestTableName=PSOBJGROUP. Set this variable to the name of a table in the database you are working in, for example, TestTableName=OW_CUSTOMERS.

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. For more information, see Modifying connection pool idle time.

If you have installed the Stat Central Agent on a HPUX computer, you may need to adjust the default max_thread_proc setting to allow for Java processing. For more information, go to http://www.hp.com/go/java/ or search the HP online documentation for max_thread_proc.

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 an X11 Windows® Server. Installing the Xvfb is platform-specific. For more information, please contact the Support Portal at https://support.quest.com.

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 the following command to run the process in the background:

Resolving port and firewall conflicts

If the Stat® Central Agent will not run when started, it may be because either the port assigned to it is 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.

NOTE: Stat Central Agent port settings are stored in the following location: <STAT_HOME>/app/standalone/configuration/standalone-full.xml, which is not the same location as previous versions of Stat.

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 uses a set of ports as defined by the value in <STAT_HOME>/app/standalone/configuration/standalone-full.xml. These values are defined for a default port offset of zero which is set in the jboss.socket.binding.port-offset variable 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.

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 the 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 Configuring the 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 6.1.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.

Stopping the Stat Central Agent

To stop the Stat Central Agent on either a Windows or a Unix platform, do one of the following:

You can also create a desktop shortcut which sends the appropriate command-line shut down argument to the Stat Central Agent.

If you have modified your port offset from the default value of zero due to conflicts with other systems, etc., then you must supply the modified port information to the shutdown command so that it can find the server to shut it down.

For example, if you modified the port offset to one, you need to edit %STAT_HOME%\app\bin\shutdown.bat and modify it as below:

For Unix installations, you need to edit $STAT_HOME/app/bin/shutdown.sh and modify it as below.

Also, if you running more than one Stat Central Agent on the same host machine, you must specify the port offset. In this case, you must also specify the port number when executing the shutdown command. The port numbers for a port offset of one is 9991 and for a port offset of 100 is 9990+100=10090. Again, these numbers may be modified if they conflict with other applications.