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 - Upgrade Notes

Update PeopleSoft Object Mover instructions

For PeopleSoft® users, log into Stat® 6.3.0 using the special Stat SYSTEM account to update the PeopleSoft Object Mover instructions. The Stat object that archives PeopleSoft objects requires a set of instructions in order to operate. To do this, select Maintenance | General | Update PS Object Mover Instructions. For more information, see the Stat System Administration Guide, Chapter 2, Administrative Utilities.

Upgrade the Stat Central Agent

Topics:

Upgrading the Stat Central Agent

The upgrade to Stat® 6.3.0 completely replaces the existing directory tree installed at the location defined by <STAT_HOME>.

IMPORTANT: Do not copy files from earlier installations to the new 6.3.0 installation.

For Stat 6.3.0, you need to have Java Development Kit installed, and optionally a system variable called JAVA_HOME that points to the JDK installation root directory (e.g., C:\Program Files\Java\jdk1.8.0_191).

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. 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 previous test database during the upgrade process.
1
Create a new <STAT_HOME> folder for the Stat 6.3.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.
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.
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

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:
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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating