Chat now with support
Chat with Support

Stat 6.0 - Upgrade Notes

Upgrading Stat Upgrade the Stat Central Agent Upgrade the Stat Oracle Agent (Oracle E- Business Suite only) Additional changes Appendix: Upgrade Checklist

Upgrading the Stat Central Agent on the standalone platform

The upgrade to Stat® 6.0.0 completely replaces the existing directory tree installed at the location defined by <STAT_HOME>. Starting with Stat 6.0.0, a new agent is installed.

IMPORTANT: Do not copy files from 5.8.x or earlier installations to the new 6.0.0 installation.

For Stat 6.0.0, you need to have Java Development Kit (aka Java SDK) 7 or 8 installed, and optionally a system variable called JAVA_HOME that points to the JDK installation root directory (e.g., C:\Program Files (x86)\Java\jdk1.7.0_25).

If you are running Windows® or Solaris and have an older version of Java installed, go to http://www.oracle.com/technetwork/java/javase/downloads/index.html and upgrade to the appropriate version. If you are running HPUX, go to http://www.hp.com/go/java/. The previous service wrapper has been replaced with a delivered server.bat. You will need to re-apply custom modifications.

IMPORTANT: There should be no Stat Central Agent running against your 5.8.x test database during the upgrade process.
1
Create a new <STAT_HOME> folder for the Stat 6.0.0 agent and optionally create an environment variable for <STAT_HOME>.
Instead of creating a system variable for <JAVA_HOME> and <STAT_HOME>, enter these values directly in <STAT_HOME>/app/bin/standalone.conf (for Unix) or <STAT_HOME>\app\bin\standalone.conf.bat (for Windows).
For Windows, uncomment and change these 2 lines in <STAT_HOME>\app\bin\standalone.conf.bat.
For Unix, uncomment and change these 2 lines in <STAT_HOME>\app\bin\standalone.conf.
2
Backup your previous <STAT_HOME> if you are planning on using the same name.
NOTE: The new folder must be empty.
For example, if you installed the Stat Central Agent in C:\Stat, move that directory to C:\stat_old, and create a new directory for C:\Stat (<STAT_HOME> will still point to the correct location).
We suggest making a backup of C:\Stat rather than deleting it so it is possible to refer to old log files or your original configuration files. For example:
Unix: (assuming <STAT_HOME> points to /usr/local/stat and suitable file system permissions):
4
Click Install Stat Central Agent.
Autorun opens the stat_server folder, which contains the subfolder, standalone.
5
Open the standalone folder, locate the file stat_standalone.zip and unzip it to the desired location on the host computer where you want to install the Stat Central Agent.
An example for Windows might be c:\stat; on Unix®, this might be /usr/local. The location you choose for the installation is referred to as <STAT_HOME>. Use Winzip® to unpack the file on Windows or use the unzip utility on Unix.
IMPORTANT: Do not unzip the file stat_standalone.zip to a directory that contains an exclamation point character (!).

If copying the installation files to a Unix system, be sure the file transfer settings are set to binary and not ascii. Use the -a modifier to unzip the file.

The <STAT_HOME> directory should contain the following subdirectories:
NOTE: 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. Quest® Software recommends that you validate that the agent will start without the service before invoking the service operation.
7
Use run.bat or run.sh to start the Stat Central Agent not as a service.
Windows: <STAT_HOME>\app\bin\run.bat
Unix: <STAT_HOME>/app/bin/run.sh
NOTE: If you have port conflicts during startup, the server displays one or more error messages. For instructions on resolving port conflicts, see Resolving Port and Firewall Conflicts.
In the server console, you will see the line, Stat Configuration Assistant is ready.
9
Open your internet browser and go to http://<stat_server_host_machine>:8080/stat-config.
IMPORTANT: If you are not running the agent from the local machine (i.e. Telnet session), you must add the IP address to <STAT_HOME>/config/stat-config.properties or you will not have access to the Configuration Assistant. See Authorize Access to the Configuration Page.
10
In the Type/Vendor field, select the database platform you are using. Options include Oracle or SQL Server.
11
Enter the appropriate information for the Stat database: Host Name, Port, DB/Service Name, Login ID, Password.
This field flexes to TNS Entry for Oracle users.
13
Choose the logging setting for the UI Logging Level and for the Stat Central Agent application. The default is INFO.
15
Click Save.

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.0.0, copy the <STAT_HOME>\report\custom\format folder from its 5.8.x location and paste it to the new 6.0.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: Starting with Stat 6.0.0, 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.

HTTP socket binding

8080

8081

8082

8180

HTTPS socket binding (See Note)

8443

8444

8445

8543

Management socket binding

9990

9991

9992

10090

Management socket binding https (See Note)

9993

9994

9995

10093

Transaction sockets

4712

4713

4713

4714

4714

4715

4812

4813

NOTE: Be aware of the following:
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.

2
Open <STAT_HOME>\app\bin\standalone.conf.bat with Notepad or another text editor. For Stat Central Agent on Unix®, you need to open <STAT_HOME>/app/bin/standalone.conf.
3
Search for the setting -Djboss.socket.binding.port-offset=0
4
Change the setting to a proper offset. For example: -Djboss.socket.binding.port-offset=10

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

Related Documents