Stat 5.7.2 Patch App Instructions

Stat 5.7.
2
Patch Application Instructions

2014 Dell Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a
software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the
applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording for any purpose other than the purchasers personal use without the written
permission of Dell Software Inc.
The information in this document is provided in connection with Dell Software products. No license, express or implied, by
estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Dell
Software products. EXCEPT AS SET FORTH IN DELL SOFTWARES TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE
AGREEMENT FOR THIS PRODUCT, DELL SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED
OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL DELL BE LIABLE FOR ANY
DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES
FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS
DOCUMENT, EVEN IF DELL SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Dell Software makes no
representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the
right to make changes to specifications and product descriptions at any time without notice. Dell Software does not make any
commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Dell Software Inc.
Attn: LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
Refer to our web site (www.software.dell.com) for regional and international office information.
Trademarks
Dell, the Dell logo, Stat and Toad are trademarks of Dell Inc. and/or its affiliates. Other trademarks and trade names may be
used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims any
proprietary interest in the marks and names of others.
Legend
CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.
WARNING: A WARNING icon indicates a potential for property damage, personal injury, or death.
IMPORTANT NOTE, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.
Stat Patch Application Instructions
Updated - October 2014
Software Version - 5.7.2
Contents
Patch Application Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Overview of the Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Unpack the 5.7.2 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Upgrade the Stat Database . . . . . . . . . . . . . . . . . . .
Oracle (9i, 10g, 11g, and 12c) . . . . . . . . . . . . . .
Microsoft SQL Server (2005, 2008, 2012, and 2014)
Staging Database Scripts . . . . . . . . . . . . . . . . . .
...
...
...
...
....
....
....
....
....
....
....
....
...
...
...
...
....
....
....
....
...
...
...
...
..
..
..
..
5
5
6
6
Install the Stat Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Use the Stat INI Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Obtain the Stat License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Upgrade Password Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Upgrade CSR Description and Resolution Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Update PeopleSoft ObjectMover Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Upgrade the Stat Central Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Upgrading the Stat Central Agent on the Standalone Platform . . . . . . . . . . . . . . . . 9
Configuring the Stat Central Agent on the Standalone Platform . . . . . . . . . . . . . . .11
Upgrading the Stat Central Agent on Oracle WebLogic 11g . . . . . . . . . . . . . . . . . .21
Configuring the Stat Central Agent on Oracle WebLogic 11g . . . . . . . . . . . . . . . . . .23
Testing Database and Server Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Upgrade the Stat Oracle Agent (Oracle E-Business Suite only) . . . . . . . . . . . . . . . . . . .26
Assign User Class Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Enhancements and Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Stat 5.7.2 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Stat 5.7.1 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Stat 5.7.0 Enhancements Requiring User Action . . . . . . . . . . . . . . . . . . . . . . . . . .38
Stat 5.7.0 Optional Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Upgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
About Dell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Contacting Dell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Technical support resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Stat 5.7.2
Introduction
Overview of the Upgrade Process
Unpack the 5.7.2 Upgrade
Upgrade the Stat Database
Install the Stat Client
Use the Stat INI Editor
Obtain the Stat License Key
Upgrade Password Encryption
Upgrade CSR Description and Resolution Fields
Update PeopleSoft ObjectMover Instructions
Upgrade the Stat Central Agent
Upgrade the Stat Oracle Agent (Oracle E-Business Suite only)
Assign User Class Rights
Enhancements and Modifications
Upgrade Checklist
Introduction
The Stat 5.7.2 patch release provides fixes and enhancements to Stat 5.7.0. This patch is primarily directed at
PeopleTools 8.54 support. For details, please refer to the Stat 5.7.2 Release Notes. Please review the Resolved
Issues section of the Release Notes before starting this upgrade.
This document details the steps necessary to upgrade from Stat 5.7.0 to Stat 5.7.2. The following steps will
guide you through a successful patch application. Please use the upgrade overview and the Upgrade Checklist to
assist you in completing all of the steps. Be sure to review the steps outlining changes to the product before
starting the upgrade process.
We believe that by following these directions, you will be able to upgrade your Stat Database without issue.
However, if you have questions, you can reach Dell Software Support by calling 949-754-8000, by fax at 949-7548999, or by email at support@software.dell.com.
Stat 5.7.2
Overview of the Upgrade Process

The following is a summation of the steps you will take to upgrade Stat to version 5.7.2. Use this information in
conjunction with the Upgrade Checklist on page 40 to understand the different stages of the upgrade process.
Use the detailed steps defined later in this document when performing the actual upgrade.
IMPORTANT: Before starting this upgrade, be aware of the following:
If your Stat version is not already 5.5.0 or higher, you must obtain a new Stat licensing key and site
message from Support Link at https://support.software.dell.com/licensing-assistance. You must
update the Stat license key to access the Stat client. See the section, Obtain the Stat License Key
on page 7 for more information.
You will use the Stat-supplied SYSTEM user account during this upgrade. Be sure you know the
password for SYSTEM before you start the upgrade process. If you need to reset the password, do
so before making the database copy.
To prepare for your upgrade, you will install the new executables and create a copy of your production
database. This production database copy will be the one used for your testing.
All steps are required unless noted as optional or specific to either PeopleSoft or Oracle E-Business Suite.
1
Verify that your Stat production database is at least v5.7.0.

If you starting from a pre-5.5.0 version of Stat, you need to obtain the 5.5.0 Patch and a new license.
Refer to the 5.5.5 Patch Application Instructions document, Patch Overview from pre-Stat 5.5.0
section before continuing to the 5.5.0 upgrade. You will need this license before you start your upgrade.
Be aware that it may take a few days to obtain this license. If you are on a release of Stat that is prior to
5.4.0, please contact support.
For the Stat Central Agent, verify that you have a 32-bit Java 2, Standard Edition, Java Development Kit
(aka Java SDK) 1.6.0_5 or higher or 1.7.0+ installed and a system variable called JAVA_HOME that
points to the JDK installation root directory (e.g., C:\Program Files (x86)\Java\jdk1.6.0_45). For Java
1.7, point JAVA_HOME to the bin directory (e.g., C:\Program Files (x86)\Java\jdk1.7.0_25\bin).
If you 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.
Java 1.8.x is not supported in this version of Stat.
Create an exact copy of your Stat production database.

This copy is where you will first test the upgrade scripts and the new Stat 5.7.2 functionality. Please
refer to the detailed instructions contained in the upgrade script specific to your database platform
(PORAv570-572.sql for Oracle and PMSSv570-572.sql for SQL Server).
Run the appropriate database upgrade scripts against the copied database.
Run the Stat 5.7.2 Windows Client installer.

It is not necessary to uninstall the previous version of the Stat Windows Client before installing Stat
5.7.2. The Stat Windows Client installer creates shortcuts from the Programs menu that point to the Stat
5.7.2 files.
Use the Stat INI Editor to create a new record for your upgraded database as there have been changes to
the login requirements.
See the section, Use the Stat INI Editor on page 7 for more information as there have been changes to
the login requirements.
For PeopleSoft users only, open Stat 5.7.2 and run the PeopleSoft ObjectMover Instructions Update
utility. Also, make sure you have configured your PeopleSoft environment connections properly, including
the parameters described in the section, Upgrade the Stat Central Agent on page 8.
Stat 5.7.2
Install the 5.7.2 Stat Central Agent to the <STAT_HOME> directory. Then modify the configuration
settings specified in run.conf (for Unix) and run.conf.bat (for Windows) to fit your site.
NOTE: This patch requires a new installation directory (referred to as <STAT_HOME>). Do not
attempt to overlay the 5.7.2 files into an older Stat version.
See the section, Upgrade the Stat Central Agent on page 8 for more information.
CAUTION: You may reference previous configuration settings from 5.6.x/5.7.0 files, but the changes
must be made to the new 5.7.2 files. Do not copy 5.6.x/5.7.0 files into the new agent directories
(with the exception of the <STAT_HOME>\report\custom\format folder, which contains custom
report definitions that you may want to carry over to 5.7.2).
Start the 5.7.2 Stat Central Agent.
10 For Oracle E-Business Suite users only:
Shut down each Stat Oracle Agent and create a backup/archive of each stat.conf file.
Install the 5.7.2 Stat Oracle Agent on each Oracle E-Business Suite server that Stat will manage.
Then copy the configuration setting you want to re-use from the archived stat.conf files and
paste them into the new 5.7.2 stat.conf files. Then specify additional configuration parameters
as needed.
For Oracle E-Business 12.2 review the stat.conf changes. See Upgrade the Stat Oracle Agent
(Oracle E-Business Suite only) on page 26.
Start each of the Stat Oracle Agents.
11 Assign new user class rights as needed.

Although there are not new user class rights in 5.7.2, if you are upgrading from a version earlier than
5.7.0, you should review the new rights. See the section, Assign User Class Rights on page 28 for more
information.
12 Implement the required enhancements and any optional enhancements you want.
See the section, Enhancements and Modifications on page 29 for more information.
13 Test your upgrade.
14 After verifying that you successfully upgraded the database to 5.7.2, upgrade your Stat 5.6.x/5.7.0
production database.
15 Install the Stat 5.7.2 Windows Client on all users workstations.
Unpack the 5.7.2 Upgrade

The Stat cd comes with an Autorun executable that launches the installer when the disc is inserted.
If you have downloaded the Stat 5.7.2 zip file from Supportlink, unzip the whole file into a location of your
choice. Locate the Autorun.exe in the root directory of that location and double-click it to launch the installer.
The installer Documentation menu give you access to the following documents:
Release Notes opens 5.7.2_Release_Notes.pdf. Refer to these notes for modifications that may affect
daily business processes.
Patch Application Instructions opens 5.7.2_Patch_App_Instructions.pdf (this document)
The installer Install menu give you access to the following components:
Stat Central Agent unpacks the Stat Central Agent. See the section Upgrade the Stat Central Agent on
page 8.
Stat Central Agent for Oracle E-Business Suite unpacks the Stat Oracle Agent programs. See the section
Upgrade the Stat Oracle Agent (Oracle E-Business Suite only) on page 26.
Stat 5.7.2
Scripts gives you access to the database upgrade scripts used to upgrade Stat. Older Stat versions
required the Stat client to be installed to access the scripts. This installer allows you to access the
scripts independently of the client installation.
Stat Windows Client installs the Stat 5.7.2 Client. See Install the Stat Client on page 7.
Upgrade the Stat Database

After you have created a copy of your Stat 5.7.0 production database (test database), you are ready to begin
the test upgrade:
1
Take a back up of the test database (copy of production).
Depending on your DBMS platform, do one of the following:
For Oracle, the scripts can be run using SQL Plus or Toad for Oracle.
For SQL Server, execute the appropriate upgrade scripts using Toad for MSS or SQL Query Analyzer.
Do not use other third-party tools.
Please note the following:
Refer to each of the database script sections to determine which scripts need to be run to support the
version or versions of PeopleSoft that you support.
Disable or remove any custom defined database triggers against the Stat schema
Before executing each script, read the instructions located at the beginning of each script. Each script
must be edited to replace certain variables prior to its execution. These variables include database
names, file locations, user ids and passwords.
Each script will create a log file. Oracle database scripts create a file with the same name as the script.
MS SQL Server scripts write a log to the screen. This log may be copied and pasted into Notepad or a like
program. The MSS script contains instructions on how to send the output to a log rather than the screen.
Upgrading to 5.7.2 will re-set the system values that determine the time interval between system jobs
run automatically by the Stat Central Agent. Any changes that may have been made will be reset to the
recommended values, which range between 20 to 30 seconds for more time sensitive jobs such as
archiving and migrating.
Make sure to review each log for errors before moving to the next script
Oracle (9i, 10g, 11g, and 12c)

The upgrade scripts for Stat 5.7.2 running on Oracle are located in <target directory>\Scripts\Oracle\Upgrade.
Oracle 9i, 10g, 11g, and 12c are supported in Stat 5.7.2.
To upgrade to Stat 5.7.2, you must be on Stat 5.7.0.
To upgrade to Stat 5.7.2 running on Oracle:

1
Run the script PORAv570-572.sql.
If the 5.6.4/5.7.0 version of this script was not previously run, for PeopleSoft 8.x users only, run
UORAv570ps8OP.sql.
Script history can be reviewed in the System Maintenance table.
For PeopleSoft 8.x users only, run PORAv572ps8Q.sql.
Recompile any invalid PL/SQL modules in the database by running the script, utlrp.sql located in
<ORACLE_HOME>/rdbms/admin directory.
Stat 5.7.2
Microsoft SQL Server (2005, 2008, 2012, and 2014)

The upgrade scripts for Stat 5.7.2 running on Microsoft SQL Server are located in <target
directory>\Scripts\MSSQLServer\Upgrade. SQL Server 2005, 2008, 2012, and 2014 are supported in Stat 5.7.2.
To upgrade to Stat 5.7.2, you must be on Stat 5.7.0.
To upgrade to Stat 5.7.2 running on Microsoft SQL Server:

1
Run the script, PMSSv570-572.sql.
If the 5.6.4/5.7.0 version of this script was not previously run, for PeopleSoft 8.x users only, run
UMSSv570ps8OP.sql.
Script history can be reviewed in the System Maintenance table.
NOTE: If you are running Stat on Microsoft SQL Server and your PeopleTools environment is 8.48 or
higher, Stat must be on MSS 2005, 2008, 2012, or 2014 regardless of the PeopleTools platform.
F or PeopleSoft 8.x users only, run PMSSv572ps8Q.sql.
Staging Database Scripts

Instructions for creating a PeopleSoft database that is used exclusively by Stat are available in the 5.7.0
Installation Notes. Staging databases are used when migrating archive sets from your Stat database to a
PeopleSoft database. A staging database is essentially a mini-PeopleSoft database with no application data and
minimal tools data. Once created it should be maintained and tuned the same as other PeopleSoft databases in
your environment.
If you are creating a staging database for the first time in Stat 5.7.2, or if you are upgrading your version of
PeopleTools to 8.54 and your current staging database was created on a previous version, you need to run the
staging scripts originally provided with this patch.
Those scripts are located in this package. Locate the script for your OS, modify the appropriate variables
according to the instructions in the script and apply the script to the designated staging database for Stat.
\scripts\DB2\Upgrade\Staging\PStageDB2-OS390v572.sql
\scripts\DB2\Upgrade\Staging\PStageDB2-UNIXv572.sql
\scripts\MSSQLServer\Upgrade\Staging\PStageMSSv572.sql
\scripts\Oracle\Upgrade\Staging\PStageORAv572.sql
Different versions of PeopleTools require different table modifications in the staging database to work with
Stat. The scripts have all 3 versions specified. Depending on the version of PeopleTools that the script will be
run in, do the following:
1
Open the script and modify the bracketed parameters, such as [DATABASENAME],
[OWNER/PWD@DATABASENAME] and [SPOOLPT].
Parameters vary for different rdbms
Also modify the scripts as follows:
8.54: run the script as is; no additional edits are required
8.53: comment out section 03d
8.52: comment out sections 03d and 03c
Prior to 8.52: comment out sections 03d, 03c and 03b
Prior to 8.x (ie v7 or v7.5): comment out sections 03d, 03c and 03b and follow the instructions in
section 03a
Stat 5.7.2
Install the Stat Client

Before installing the Stat client, please note that the user performing the installation or de-installation needs to
be logged in as an Administrator locally on that server/workstation due to enhanced security on Windows.
The Stat Client can be installed locally or it can be installed to a network location. In addition, the Stat Client is
now installed with an Autorun program, whereas previous versions of the Stat Client where installed with a
DemoShield program. For detailed instructions, see the Stat 5.7.0: Install Notes document. You can open this
document from the Stat Autorun program by clicking View Install Notes.
To install the Stat Client:

1
Do one of the following:
Insert the Stat CD
If you downloaded the upgrade package from Supportlink, click Autorun from the root of the
downloaded folder.
The Stat Auto program launches automatically.

2
Click Install Stat Windows Client.

This launches the InstallShield Wizard for Stat 5.7.2.
Complete the steps for installing the Stat Client either locally or to a network location.
See the Stat 5.7.0: Install Notes document for more information.
Use the Stat INI Editor

Use the Stat INI Editor to create a new record for the upgraded database. For more detailed instructions, see
the book, Stat 5.7.0: System Administration, Chapter 2, Administrative Utilities.
IMPORTANT: System administrators must enter the STATLOGIN password in the Encrypted Login Password
field, either by entering an encrypted password from another stat.ini file or by clicking Change Password
and entering the STATLOGIN password.
Obtain the Stat License Key

The Stat license key was replaced in 5.5.0. If you are upgrading anywhere from 5.5.0 to 5.6.4, then you have
already updated your Stat license and this step can be disregarded. However, if your Stat version is not already
5.5.0 or higher, you must obtain a new Stat licensing key and site message from Support Link at
https://support.software.dell.com/licensing-assistance. The procedure for activating licenses is the same for
both commercial and trial licenses.
To activate a Stat license

1
Open Stat and go to Maintenance | General | System Maintenance.
Click on the License Tab.
Paste the License Key and Site Message into the appropriate fields.
Click Verify.
The Properties of the license will be displayed if the key/message is valid.
Stat 5.7.2
Upgrade Password Encryption

Stat 5.5.x included a procedure to update password encryption. If you are able to login as any user other than
SYSTEM at this point, then your encryption has been modified and you may move to the next section. Another
method of validating password encryption is to go to Tools| Stat Upgrade| Upgrade Encryption If Upgrade
Encryption is dithered this routine has been successfully completed and you may move to the next section.
If the password encryption has not been completed, then after upgrading the Stat database to 5.7.2, log in to
Stat using the special Stat SYSTEM account and run an upgrade procedure from the Tools menu. This upgrades
all the passwords in the database using a default password key.
IMPORTANT: If there are any corrupted passwords, the routine will remove those passwords and
supply you with a list of which ones were removed. You will need to re-insert those passwords after
the routine has finished.
To upgrade the password encryption:

1
Log in to Stat as the SYSTEM user.
Select Tools | Stat Upgrade | Upgrade Encryption.

NOTE: After upgrading the password encryption, the menu option Upgrade Encryption is
deactivated.
After upgrading password encryption with the default key, you have the option of changing it periodically as a
general security precaution. It is recommended that you do not reset the encryption key until you have
completed the upgrade and validated that users can log in to Stat.
To change the encryption key (optional):

1
Log in to Stat as the SYSTEM user.
Select Tools | Update Encryption Key.
Upgrade CSR Description and Resolution

Fields
Stat 5.6.x included a routine to upgrade the CSR Description and Resolution fields of older CSRs. If you have
been actively using Stat 5.6.x, this step has been run and you may continue to the next section. Re-running this
procedure will not harm the database. If there is any question has to whether or not this was completed in the
5.4.x to 5.6.x upgrade, go to Tools | Upgrade Stat | Upgrade Description and Resolution.
Update PeopleSoft ObjectMover

Instructions
For PeopleSoft users, log into Stat 5.7.2 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 ObjectMover Instructions. For more
information, see the book, Stat 5.7.0: System Administration, Chapter 2, Administrative Utilities.

There are two procedures for upgrading the Stat Central Agent to 5.7.2, depending on whether it was originally
installed on the Stat-provided standalone platform or on WebLogic.
Stat 5.7.2
Upgrading the Stat Central Agent on the Standalone

Platform
The upgrade to 5.7.2 completely replaces the existing directory tree installed at the location defined by
<STAT_HOME>. Use the following procedure to avoid loss of existing log files and configuration. Starting with
Stat 5.6.0, some directories and files have been modified as compared to earlier versions. Do not copy files
from 5.6.x/5.7.0 or earlier installations to the new 5.7.2 installation.
For 5.7.2, you need to have a 32-bit Java 2, Standard Edition, Java Development Kit (aka Java SDK) 1.6.0_5 or
higher (Java 1.8 is not supported) installed and a system variable called JAVA_HOME that points to the JDK
installation root directory (e.g., C:\Program Files (x86)\Java\jdk1.6.0_45). For Java 1.7, point JAVA_HOME to
the bin directory (e.g., C:\Program Files (x86)\Java\jdk1.7.0_25\bin).
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 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.
NOTE: There should be no Stat Central Agent running against your 5.7.2 test database during the upgrade
process.
To upgrade the Stat Central Agent on the standalone platform:

1
Create a new <STAT_HOME> folder for the 5.7.2 agent and create an environment variable for
<STAT_HOME>.
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 this directory rather than deleting it so it is possible to refer to old log files or your
original configuration files. For example:
Windows:
c:\> move c:\stat c:\stat_old
c:\> mkdir c:\stat
Unix: (say <STAT_HOME> points to /usr/local/stat and assuming suitable file system permissions):
#> cd /usr/local
#> mv stat stat_old
#> mkdir stat
Open the Autorun program, either from the Stat cd or from the upgrade folder downloaded from
Supportlink.
Click Install Stat Central Agent.

Autorun opens the stat_server folder, which contains the subfolder, standalone.
Open the standalone folder, locate the file stat_standalone.zip and unzip to the desired location on the
host machine 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 the unzip
utility on Unix.
NOTE: Do not unzip the file stat_standalone.zip to a directory that contains an exclamation point
character (!). Also, if copying the installation files to a Unix system, be sure the file transfer
settings are set to 'binary' as opposed to 'ascii. Also, for Unix use the -a modifier to unzip the file.
The <STAT_HOME> directory should contain the following subdirectories:
Stat 5.7.2
app
config
report
stat_log
uploads
Configure the Stat Central Agent as required by your Environment.

Because this is a new installation, you will need to re-apply any configuration changes you want to retain
from your previous release of Stat. Refer to the section Configuring the Stat Central Agent on the
Standalone Platform on page 11 for more information. Note that while some configuration changes can
be made after you have completed installing the Stat Central Agent, other changes should be made
before proceeding to the next step in the installation. These particular issues are documented in the
subsection Before Starting the Stat Central Agent on page 11.
NOTE: Starting with Stat 5.6.0, the wrapper.conf and wrapper.bat files are no longer available.
Service.bat is used to start the service. It calls run.bat. See section Configuring the Stat Central
Agent as a Windows Service on page 17 for more information. Dell Software recommends that you
validate that the agent will start without the service before invoking the service operation.
Use run.bat or run.sh to start the Stat Central Agent NOT as a service.
If you have configured the Stat Central Agent to run as a Windows service, use the Windows Service
interface to start the agent. Otherwise, this is the typical command to start the server:
Windows:
<STAT_HOME>\app\bin\run.bat
Unix:
<STAT_HOME>/app/bin/run.sh
NOTE: If you have port conflicts during startup, the server will display one or more error messages.
For instructions on resolving port conflicts, see the section, Resolving Port and Firewall Conflicts on
page 13.
Wait for the Stat Central Agent startup process to complete.

In the server console, you will see the line, Stat Configuration Assistant is ready.
Do the following to configure the Stat database and the database type-mapping:
a
Open your internet browser and go to http://<stat_server_host_machine>:8080/stat-config.

This opens the Configuration Assistant which guides you through the process of configuring the
Stat database and the database type-mapping.
CAUTION: 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 the Authorize Access to the Configuration Page on page
11.
b
In the Type/Vendor field, select the database platform you are using.
Options include Oracle or SQL Server.
Enter appropriate info for the Stat database: Host Name, Port, DB/Service Name, Login ID,
Password.
For Microsoft SQL Server users who have installed multiple instances of Microsoft SQL Server,
specify which instance the Stat Central Agent is running on in the Instance field.
This field flexes to TNS entry for Oracle users.
For RAC environments, paste the TNS entry for the Stat database in this field. Remove any spaces
and any line feeds or carriage returns from the TNS string so that it is one long line.
Choose desired logging setting for the UI and for the Stat Central Agent application.
Stat 5.7.2
10
The default is INFO.

f
Optionally, specify a session timeout parameter.

The default value is 20 minutes. You can specify any value from 1 minute to 2880 minutes, but be
aware that setting higher values may negatively affect performance.
Click Save.
Stat verifies that the Stat database parameters you entered are correct.
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:
Before Starting the Stat Central Agent on page 11
Configuring the Stat Central Agent as a Windows Service on page 17
Installing DB2 Support for the Stat Central Agent on page 17
Setting up Support for AES256 Ciphers for SFTP on page 18
Configure Web Client to Use HTTPS on page 19
Connection Pool Idle Time on page 20
Installing Multiple Servers on the Same Host Machine on page 20

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>), then the modifications should
be made to run.conf (for run.sh) or run.conf.bat (for run.bat)
The wrapper.conf and wrapper.bat files are no longer available. Service.bat is used to start the
service. It calls run.bat. See section Configuring the Stat Central Agent as a Windows Service on
page 17 for more information. Dell recommends 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 on page 9.
Restore Customized Settings and Custom Reports

If there any customized settings specified in your 5.6.x/5.7.0 versions of run.conf (for Unix) and run.conf.bat
(for Windows) that you want to replicate in 5.7.2, the changes must be made to the new 5.7.2 files. Do not copy
5.6.x/5.7.0 files into the new agent directories. The one exception to this rule is if you have any custom report
definitions you want to carry over to 5.7.2. In this case, copy the <STAT_HOME>\report\Custom folder from its
5.6.x/5.7.0 location and paste it to the new 5.7.2 <STAT_HOME> directory. Then remove any files with a .jasper
extension for the Custom folder.
Authorize Access to the Configuration Page

To authorize access to the configuration page, you as a Stat administrator need to edit the statconfig.properties file in <STAT_HOME>/config. The privilege to modify the configuration is administered using
the computer's IP address. You can grant user permission to change the configuration by adding its computer's 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's IP address (e.g. 192.168.244.130) to the list. You
Stat 5.7.2
11
can add multiple IPs to the list and use a comma to separate them. After you complete editing statconfig.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 data object. This error is due to a query against a test table
which 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=OW_CUSTOMERS.
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 the section, Connection Pool Idle Time on page 20.
Adjust the Default Max_thread_proc Setting

If you have installed the Stat Central Agent on a HPUX machine, 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 HPs online documentation for max_thread_proc.
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://software.dell.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 shutdown. 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:
nohup run.sh &
JAVA_OPTS Environment Variable Error

If your environment already has a JAVA_OPTS environment variable defined, it may be incompatible with Stat,
in which case you will receive the following error message when starting the Stat Central Agent:
=1.0 was unexpected at this time.
To resolve this issue you need to edit the /run.conf.bat file.
1
Open <STAT_HOME>/app/bin/run.conf.bat.
Locate this section:

[ "x$JAVA_OPTS" = "x" ]
Insert this statement above the specified section:

JAVA_OPTS=""
Your file will now look like this:
Stat 5.7.2
12
JAVA_OPTS=""
[ "x$JAVA_OPTS" = "x" ]
4
Save run.conf.bat.
Resolving Port and Firewall Conflicts

If the Stat Central Agent will not run when started, typically this is 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: If you modified the Stat Central Agent port settings in a previous version of Stat, you need to reapply those changes. Starting with Stat 5.6.0, Stat Central Agent port settings are stored in the following
location: <STAT_HOME>\app\server\default\conf\bindingservice.beans\META-INF\bindings-jbossbeans.xml. This is not the same location as previous versions of Stat.
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
(For Oracle E-Business Suite users only) The JBoss Messaging service is opening a random port each time
the Stat Central Agent is started, creating port conflicts
If you have port conflicts, the server will display one or more error messages, such as:
Depends On Me: java.net.BindException: Address already in use: JVM_Bind]
The Stat Central Agent utilizes a set of ports as defined by the value in
<STAT_HOME>/app/server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml. These
values include:
1
ports-default
ports-01
ports-02
ports-03
The ports in use by the Stat Central Agent are listed below. The first, called ports-default, contains the
default ports used in a standard agent installation. The second, or ports01, contains a variant definition of
ports that could be used if there are conflicts with the ports defined in the default, or could be used for a
second agent. The third and fourth, or ports02 and ports-03, contain further port definitions that could be
used in a port conflict situation, or if a third or fourth agent is necessary.
Description
ports-default
ports-01
ports-02
ports-03
Naming Service
1098
1198
1298
1398
Naming Service
1099
1199
1299
1399
ejb3.RemotingConnector
(See Note)
3873
3973
4073
4173
Standard JBM bisocket connector

(See Note)
4457
4557
4657
4757
JBM bisocket secondary BindPort

(See Note)
4365
4465
4565
4665
Web HTTP connector socket
8080
8180
8280
8380
HTTP connector socket

(See Note)
8443
8543
8643
8743
NOTE: Be aware of the following:

Stat 5.7.2
13
ejb3.RemotingConnector For port number 3873, 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.
JBM bisocket Messaging between the Stat Central Agent and Oracle agents uses 2 ports:
The first port (4457/4557/4657/4757) is controlled by setting ports-default/ports-01, ports-02,
ports-03. The secondary port must be modified separately. This was previous referred to as the
anonymous port because Jboss generated a random, unknown port each time the agent was
restarted. Stat now delivers a configured secondary port, but since this configuration is only
necessary for firewalls, the file must be modified to turn it on. If the file is not modified, then a
random port will be used. See JMS Ports on page 15 below for how to turn it on.
If it is turned on, then the site administrator needs to modify this port id manually if they are
using anything other than ports-default, or if there is more than one Stat Central Agent on the
same device. If the delivered ports are already in use, you can choose any open port that will
work in your environment and modify the file. If you have already configured the secondary port
with a different port id, there is no need to change it.
HTTP connector socket This port is only necessary if the Stat Central Agent is configured to
support HTTPS. See Configure Web Client to Use HTTPS on page 19.
Port Configurations
When other applications are using the same port as the Stat Central Agent, you need to change which port
configuration is referenced in the file bindings-jboss-beans.xml.
1
Review the port configurations described above and designate which to use for this installation.
Open <STAT_HOME>\app\server\default\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml
with notepad or other text editor.
Search for the setting, 
<parameter>${jboss.service.binding.set:ports-default}</parameter>

<bean name="ServiceBindingManagementObject"
class="org.jboss.services.binding.managed.ServiceBindingManagementObject">
<constructor>

Change the setting to jboss.service.binding.set:ports-default>ports-01, or ports-02, or ports-03.

NOTE: As always, when you modify an .xml file, be sure that there is only one copy of it in the directory
when you are finished. Do not rename the old copy and leave it in that directory.
Firewall Configuration
After you have selected the ports, they need to be opened on existing firewalls.
The following are examples using the ports-default configuration:
Client to Central agent: 1098, 1099, 3873, 8080, 4457, 4365 (secondary port for Oracle E-Business
support)
Central Agent to Oracle agent: 1098, 1099, 8080, 4457, 4365 (secondary port for Oracle E-Business
support)
NOTE: The 4457 and 4365 only need to be opened for Oracle e-Business support. See JMS Ports on page
15 for more information.
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)

Stat 5.7.2
14
PeopleSoft databases
E-Business databases
FTP/SFTP (default = 21/22)
Email: SMTP/POP3/IMAP4 (default= 25/995/993)
The Stat client will need the same ports opened if there is a firewall between the client and any of the above
items.
JMS Ports
Stat uses JMS to communicate between the Stat Central Agent, the Stat Oracle Agents, and the Stat Client.
In addition, communication between the Stat Client and Stat Central Agent for test connecting and reporting is
done through EBJ3 calls on port 3873. All customers need 3873 open.
JMS is done over port 4457 (ports-default). An additional secondary port is utilized. Stat delivers the secondary
port as 4365. But it must be turned on as indicated below; otherwise the port will be randomly generated.
NOTE: If you are already using a different secondary port there is no need to change it.
1
Open the file <STAT_HOME>\app\server\default\deploy\messaging\remoting-bisocket-service.xml.
Find the following segment near the bottom of the file:


This segment is commented out as designated by the arrows .
Uncomment the line specifying the secondary BindPort by moving the  as shown below.
You should not uncomment the secondary ConnectPort line.

<attribute name="secondaryBindPort">4365</attribute>

NOTE: If your site has more than one Stat Central Agent running on the same server, when you change
from ports-default to ports-01/02/03 for the second server, you must designate a different
secondaryBindPort for the second server.
Firewall Timeout
For a firewall that closes the idle JMS Connections after x amount of time (for example, 1 hour), you need to
modify two xml files. The first file is the remoting-bisocket-service.xml file that you edited in the step above.
There are 2 separate sections of this code to edit. One is the ping/pong frequency and the other is continue
after timeout parameter which is near the end of the file.
1
Open the file <STAT_HOME>/app/server/default/deploy/messaging/remoting-bisocket-service.xml.
Select the following code:

<attribute name="numberOfCallRetries" isParam="true">1</attribute>
<attribute name="pingFrequency" isParam="true">214748364</attribute>
<attribute name="pingWindowFactor" isParam="true">10</attribute>
Modify the values to look like this:

<attribute name="numberOfCallRetries" isParam="true">5</attribute>
Stat 5.7.2
15
<attribute name="pingFrequency" isParam="true">1200000</attribute>

<attribute name="pingWindowFactor" isParam="true">2</attribute>
NOTE: The ping frequency is in milliseconds and 1200000 represents 20 minutes. You may need to
modify this frequency based on the timeout period set on your firewall ports. The ping frequency
should always be something slightly shorter than the timeout frequency.
4
Select the following code (near the end of the file):

<attribute name="timeout" isParam="true">0</attribute>


Modify the values to look like this:

NOTE: Notice that  have been removed from the continueAfterRimeout line.
<attribute name="timeout" isParam="true">1800000</attribute>
<attribute name="continueAfterTimeout" isParam="true" >false</attribute>
Save <STAT_HOME>/app/server/default/deploy/messaging/remoting-bisocket-service.xml.
Open <STAT_HOME>/app/server/default/deploy/messaging/connectionfactories-service.xml.
Uncomment all occurrences of DisableRemotingChecks for ping/pong frequency.

Look for the three occurrences of:

Change the lines to look like this (remove  from the attribute name line):
<attribute name="DisableRemotingChecks">true</attribute>
10 Save <STAT_HOME>/app/server/default/deploy/messaging/connectionfactories-service.xml.
Natted Firewall between the Stat Central Agent and Stat Oracle Agents
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.
################################################################################
# Stat Repository
################################################################################
stat.db.jdbc_driver:oracle.jdbc.driver.OracleDriver
stat.db.server:<stat repository server name/ip> <-- Natted IP Address
NOTE: The natted addresses must also be set up appropriately in you DNS server or individual Hosts files
on both sides of the natted firewall.
Stat 5.7.2
16
Configuring the Stat Central Agent as a Windows Service

If you previously used Wrapper.conf and other associated files to run the Stat Central Agent functionality of the
Stat Central Agent as a Windows service, you must replace them with the wrapper that is provided with the Stat
standalone agent. This is done using the service.bat command located in the <STAT_HOME>/app/bin folder.
To configure the Stat Central Agent as a Windows service:

1
Set JAVA_HOME and <STAT_HOME> in run.conf.bat to the full physical path.

NOTE: This was optional before, but is now required for running the Stat Central Agent as a
service.
(Optional) In <STAT_HOME>/app/bin/service.bat, modify the following values if you want the service
name to reflect Stat:
Set SVCNAME=JBAS50SVC
Set SVCDISP=JBoss Application Server 5.1
Set SVCDESC=JBoss Application Server 5.1.0 GA/Platform: Windows x86
Specify one of the following parameters to run service.bat commands:

install|uninstall|start|stop|restart|signal
Launch: <STAT_HOME>\app\bin>service install.

This installs JBoss AS as Windows service by creating a manual service called JBAS50SVC (unless you
changed the name in step 2). Now JBoss AS should be enlisted in the Windows Service List, which is
found in the Control Panel.
Now you can use either the Windows service applet or the service.bat command to start the service.
To start JBoss AS service, run <STAT_HOME>\app\bin>service start JBAS50SVC.

This creates a run.log file in <STAT_HOME>\app\bin (replaces wrapper.log) and also creates a lock file
called .r.lock in the bin directory which is removed when service is stopped.
NOTE: The run.log file is persistent. You should monitor the size of this file while running as a
service.
To modify the service.bat file, you need to stop the service, uninstall it, make the changes you want,
and then reinstall the service.
To stop the service, run service stop JBAS50SVC
To remove the service, run service uninstall
Installing DB2 Support for the Stat Central Agent

The requirements have changed since 5.6.3. The DB2 Client connect does not need to be installed on the Stat
Central Agent machine, however the agent does need the jdbc drivers provided in DB2 connect.
The Stat Central Agent uses the IBM JDBC type 4 driver. The required files can be found in C:\Program
Files\IBM\SQLLIB\java of the DB2 client installation. Note that Stat requires a 32 bit version of these files.
Copy db2jcc.jar and db2jcc_license_%%.jar from C:\Program Files\IBM\SQLLIB\java to
<STAT_HOME>\app\server\default\lib. The location of required drivers may vary on your site due to DB2
installation preferences.
Also note that the Stat Central Agent requires 3 columns filled in to connect to a PeopleSoft database that were
not required before.
Host The IP address or Server name where the database resides
Service The UDB/DB2 database Name. This is database name as defined during installation, not an
alias.
Stat 5.7.2
17
Port The port that is listening for requests against the UDB/DB2 database.
Additionally, the Other Database Parameters field is now case sensitive for UDB/DB2 databases. The correct
format is:
currentSQLID=The implicit qualifier of all table, view, alias, and index names specified in dynamic SQL
statements (Mainframe).
Or
currentSchema=Specifies the default schema name that is used to qualify unqualified database objects
in dynamically prepared SQL statements-also case sensitive (Aix).
Configure the Stat Central Agent Character Map

The Stat Central Agent defaults to a character map of ISO-8859-1 which is compatible with sites that are
upgrading from older versions of Stat. If desirable, the agent can be configured to use UTF-8.
If the Stat Central Agent is running on Windows:

1
Open <STAT_HOME>\app\bin\run.conf.bat.
Locate the following:

set "JAVA_OPTS=%JAVA_OPTS% -Dstat.home="%STAT_HOME%" -Dmail.mime.charset=ISO8859-1 -Duser.language=en -Duser.region=US -Doracle.jdbc.V8Compatible=true"
At the end of the line and included inside the final quote mark, add:
-Dweb.charset=UTF-8
The final edit will look like this:
set "JAVA_OPTS=%JAVA_OPTS% -Dstat.home="%STAT_HOME%" -Dmail.mime.charset=ISO8859-1 -Duser.language=en -Duser.region=US -Doracle.jdbc.V8Compatible=true
-Dweb.charset=UTF-8"
Restart the Stat Central Agent.
If the Stat Central Agent is running on Unix:

1
Open <STAT_HOME>/app/bin/run.conf.
Locate the following:

JAVA_OPTS="$JAVA_OPTS -Dstat.home=$STAT_HOME -Djboss.bind.address=0.0.0.0 Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US Doracle.jdbc.V8Compatible=true"
At the end of the line and included inside the final quote mark, add:
Add -Dweb.charset=UTF-8
The final edit will look like this:
JAVA_OPTS="$JAVA_OPTS -Dstat.home=$STAT_HOME -Djboss.bind.address=0.0.0.0 Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US Doracle.jdbc.V8Compatible=true -Dweb.charset=UTF-8"
Restart the Stat Central Agent.
Setting up Support for AES256 Ciphers for SFTP

The configuration of your SSH server determines which ciphers are used when connecting to the Stat Central
Agent. The Stat Central Agent currently supports the following cipher configurations:
Blowfish
Triple DES
Stat 5.7.2
18
AES128
AES192
AES256
To configure J2SE 1.5 or 1.6 to support AES256, you need to download and apply the Java Cryptography
Extension (JCE). To do this:
1
Go to the following url:

http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download the Java Cryptography Extension (JCE), which is contained in the appropriate zip file
(jce_policy-1_5_0.zip or jce_policy-6.zip) to a temp folder and unzip the file
Browse to the JAVA_HOME/jre/lib/security directory under your installation of JAVA_HOME.
Rename local_policy.jar to local_policy.jar.strong.
Rename US_export_policy.jar to US_export_policy.jar.strong.
Go to the temp folder where you unzipped the jce_policy file and copy local_policy.jar and
US_export_policy.jar.
Paste both files into the JAVA_HOME/jre/lib/security folder.
Configure Web Client to Use HTTPS

This functionality is supported for the Standalone platform only.
It is recommended that you first configure the Stat Central Agent without https and validate that it can be
started and is functional before switching to https.
1
Shut down the agent.
Delete <STAT_HOME>/app/server/default/tmp and <STAT_HOME>/app/server/default/work.
Obtain a keystore with a self-signed certificate from your security group or build it yourself, if
authorized.
You need to know the keystore file name and the password that opens it.
Once you have the keystore, move it to <STAT_HOME>/app/server/default/conf.
Do the following to turn on SSL:

a
Go to <STAT_HOME>/app/server/default/deploy/jbossweb.sar/server.xml and turn on SSL.
Look for this block in the file:


Move the trailing --> to the end of this line:

Modify the keystorePass to equal the password written in the keystore.
Modify the keystoreFile to match the keystore file name (in the example above, change only the
chap8.keystore to the appropriate name. Leave the directory as is).
The edits will now look like this:
Stat 5.7.2
19
-->
<Connector protocol="HTTP/1.1" SSLEnabled="true"
port="8443" address="${jboss.bind.address}"
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/statagent.keystore"
keystorePass="password" sslProtocol = "TLS" />
At this point users can log in as http:servername:8080/stat or as https:servername:8443.
6
Do the following to have the port location automatically change from 8080 to 8443 when logging into the
Stat Web Client:
a
Stop the agent
Move <STAT_HOME>app/server/default/deploy/stat-agent.ear to a location outside of the

<STAT_HOME> folder for backup purposes
Locate the stat-agent.ear file in stat-agent-https.zip from this distribution package and copy it
into <STAT_HOME>app/server/default/deploy.
Restart your agent.
Access the Stat Web Client as before.

If you input http:servername:8080/stat, you will automatically be directed to the secure location of
https:servername:8443/stat.
If you have a firewall, open port 8443 (8443/8543/8643/8743) on the firewall.
Connection Pool Idle Time

This feature allows the site to define the length of time before the Stat Central Agent connection pool times out
database connections. The default is 15 minutes. However, Java could take up to 2x as long to actually
disconnect from the environment.
1
Open <STAT_HOME>/conf/stat.properties.
Locate the parameter CONNECTION_IDLE_TIME=15 and modify the time.
Stop and restart the agent.

CAUTION: Shorter times could adversely affect agent performance
Installing Multiple Servers on the Same Host Machine

Stat currently supports installing up to four Stat Central Agents on the same host machine (provided there are
no port conflicts). Additional Stat Central Agents are installed basically the same way as the first server, except
you will need to install the additional servers to separate directories, define separate system variables, modify
the startup files, and assign the servers to different port profiles.
If you need to install more than four servers on the same machine, contact Technical Support.
NOTE: You can install only one Stat Central Agent per Stat Repository.
To install an additional Stat Central Agent on the same machine:

1
Unzip the contents of stat_standalone.zip to a location on the host machine that is different from the
location where the first Stat Central Agent is installed.
This location will be referred to as <STAT_HOME2>.
Create an environment system variable called STAT_HOME2 with a value of <STAT_HOME2> from the
above step.
Stat 5.7.2
20
Do one of the following, depending on your platform:
For Windows, go to <STAT_HOME2>\app\bin and open the file run.conf.bat in a text editor. Then
locate the line:
set "JAVA_OPTS=%JAVA_OPTS% -Dstat.home="%STAT_HOME%" -Dmail.mime.charset=ISO-8859-1 Duser.language=en -Duser.region=US -Doracle.jdbc.V8Compatible=true"
and change the value "%STAT_HOME%" to "%STAT_HOME2%".
For Unix, go to <STAT_HOME2>/app/bin and open the file run.conf in a text editor. Then locate
the line:
JAVA_OPTS="$JAVA_OPTS -Dstat.home=$STAT_HOME -Djboss.bind.address=0.0.0.0 Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US Doracle.jdbc.V8Compatible=true"
and change the value $STAT_HOME to $STAT_HOME2.
Go to <STAT_HOME2>\app\server\default\conf\
bindingservice.beans\META-INF and open the file bindings-jboss-beans.xml. Then locate the line:
and change the value ports-default to ports-01.
This assigns the second Stat Central Agent to a different port profile than the first Stat Central Agent.
However, you may still experience port conflicts with other applications running on the host machine.
See Resolving Port and Firewall Conflicts on page 13 for information on resolving port conflicts.
Continue installing the second Stat Central Agent the same way you did the first using the Configuration
Assistant.
Remember that the URL address for the Configuration Assistant will be different for the second Stat
Central Agent. After changing the port profile to ports-01, the default URL for the second Stat Central
Agent is http://localhost:8180/stat-config.
(Optional) If you want to install a third server, repeat steps 1 through 5, substituting the value 3 for the
value 2 where appropriate, for example, <install location3>, STAT_HOME3, etc. Also, when assigning the
third server to a different port profile, specify the value ports-02. The default URL for the third Stat
Central Agent is http://localhost:8280/stat-config.
(Optional) If you want to install a fourth server, repeat steps 1 through 5, substituting the value 4 for the
value 3 where appropriate, for example, <install location4>, STAT_HOME4, etc. Also, when assigning the
fourth server to a different port profile, specify the value ports-03. The default URL for the fourth Stat
Central Agent is http://localhost:8380/stat-config.
NOTE: If you have port conflicts you may not be able to install 3 additional agents as you may need to use
the settings to resolve the port conflicts.
Upgrading the Stat Central Agent on Oracle WebLogic

11g
As an alternative to the recommended Stat Standalone platform, the Stat Central Agent can be installed on
Weblogic 11g (WebLogic v10.3.3-10.3.6).
To install the Stat Central Agent on Oracle WebLogic 11g:

1
If you have not already done so, install Oracle WebLogic 11g.
The directory where you install Oracle WebLogic 11g will be referred to in this document as <WL_HOME>.
You do not need to set this variable.
Create a directory for Stat 5.7.2 in <WL_HOME>user_projects/domains/.

For a second Stat Central Agent, against a test repository you may create a new folder called
<WL_HOME>/user_projects/domains/stat2 (or stat570).
NOTE: If you have port conflicts, see Resolving Port Conflicts (WebLogic) on page 24 below.
Stat 5.7.2
21
Create a variable named $STAT_HOME and set it to <WL_HOME>/user_projects/domains/stat.
Create a variable named $STAT_HOME2 and set it to <WL_HOME>/user_projects/domains/stat2.
On the installation media, go to the \stat_server\weblogic folder and unzip the file stat_weblogic.zip to
<WL_HOME>/user_projects/domains/stat.
NOTE: For Unix, use the -a modifier to unzip the file.
Next, you need to edit the startup script, startWebLogic.cmd located in <STAT_HOME> so that it
references the correct wlserver folder name and (optionally) a different JDK version.
You will need to modify <WL_HOME>/user_projects/domains/stat/startweblogic.cmd (or
startweblogic.sh for Unix) to point <STAT_HOME> to this new location or to the variable described in step
4.
Edit startWebLogic.cmd as follows:

a
Locate the wlserver_10x folder under <WL_HOME> and then edit the line:
set WL_HOME = %STAT_HOME%%\..\..\..wlserver10 so that it specifies the exact folder name (e.g.,
wlserver_10.3).
NOTE: WebLogic names its wlserver folder based on the minor release installed.
(Optional) If you want to use a different 1.6.x or 1.7.x JDK version, replace the line
JAVA_HOME=..\..\..\jdk160_45 with the path for the new version (e.g.,
JAVA_HOME=C:\j2sdk170_25).
Locate the files wlclient.jar, wljmsclient.jar, and wlthint3client.jar and copy them to the Stat install
folder on EACH WORKSTATION where Stat is installed.
These files are located in <WL_HOME>/wlserver_10.x/server/lib.
NOTE: For Oracle Applications only, wlclient.jar and wljmsclient.jar must also be copied to each
Stat Oracle Agent. For more information, see Upgrade the Stat Oracle Agent (Oracle E-Business
Suite only) on page 26.
Do one of the following:
If on Windows, run the script startWebLogic.cmd.
If on Unix, run the script, startweblogic.sh.
The first time you start the WebLogic server, the Stat Connection is not properly defined; therefore the
server will start with errors.
9
Configure Oracle WebLogic 11g as follows:

a
Start the WebLogic console from the following url:

http://hostname:8081/console
Login with the following credentials:
Username = weblogic
Password = irv200038stat
Click Services and then Data Sources on the Domain Structure tree on the left side of the screen.
Click StatDataSource on the configuration tab.

Additional tabs are displayed.
Click the Connection Pool tab.
Click Lock & Edit on the upper left portion of the screen.
Depending on whether your Stat Database is on Oracle or SQL Server, update the DriverName,
Properties and URL.
For Oracle:
Stat 5.7.2
22
Update the URL with your Stat Database information :@hostname:port:sid
DriverName="oracle.jdbc.driver.OracleDriver"
Properties=v$session.program=STAT
Set the user name to STAT and set the password for Stat user.
For SQL Server:
Update the URL with your Stat repository information: //hostname:port/databasename.
DriverName="net.sourceforge.jtds.jdbc.Driver"
Properties="user=STAT
appName=Stat Central Agent on WebLogic"
URL="jdbc:jtds:sqlserver://hostname:port/databasename"
If you are running the Stat Database as an instance, append the instance name to the
Properties value, for example:
Properties="appName=Stat Central Agent on WebLogic;instance=instance name"
Click Save on the Connection Pool Tab.

NOTE: If you do not receive a green check mark with the message Settings Updated
Successfully, edit your savings and try again.
Click Activate Changes under Lock & Edit.

You should receive a green check mark with the message All Changes have been activated. No
restarts are necessary.
Log out of the console.
10 Restart the Stat Central Agent.

11 Open a browser and go http://hostname:8081/stat (host name is the name of the machine where
weblogic is installed).
Configuring the Stat Central Agent on Oracle

WebLogic 11g
Refer to the following sections for information on the number of ways you can configure the Stat Central Agent
on Oracle WebLogic 11g:
Configuring the Stat Central Agent as a Windows Service (WebLogic) on page 23
Installing DB2 Support for the Stat Central Agent (WebLogic) on page 24
Resolving Port Conflicts (WebLogic) on page 24
Deleting Data Sources and Connection Pools (WebLogic) on page 24
Support IMAP via TLS on page 25
Configuring the Stat Central Agent as a Windows Service

(WebLogic)
Optionally, you can configure the Stat Central Agent as a Windows service. For more information, see the
section, Setting Up a WebLogic Server Instance as a Windows Service, currently located at the following URL:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13708/winservice.htm#i1186180
Stat 5.7.2
23
Installing DB2 Support for the Stat Central Agent (WebLogic)

The requirements have changed since 5.6.3. The DB2 Client connect does not need to be installed on the Stat
Central Agent machine, however the agent does need the jdbc drivers provided in DB2 connect.
The Stat Central agent will now use the IBM JDBC type 4 driver. The required files can be found in C:\Program
Files\IBM\SQLLIB\java of the DB2 client installation. Note that Stat requires a 32 bit version of these files.
Copy db2jcc.jar and db2jcc_license_%%.jar from C:\Program Files\IBM\SQLLIB\java to <STAT_HOME>\lib. The
location of required drivers may vary on your site due to DB2 installation preferences.
Also note that in the PeopleSoft Environment Connection Maintenance table, the Stat Central agent needs 3
columns filled in for connection to a PeopleSoft database that were not required before.
Host Name The IP address or Server name where the database resides
Service Name The UDB/DB2 database Name. This is database name as defined during installation, not
an alias.
DB Listener Port The port that is listening for requests against the UDB/DB2 database.
Additionally, the Other Database Parameters field is now case sensitive for UDB/DB2 databases. The correct
format is:
currentSQLID=The implicit qualifier of all table, view, alias, and index names specified in dynamic SQL
statements (Mainframe).
Or
currentSchema=Specifies the default schema name that is used to qualify unqualified database objects
in dynamically prepared SQL statements-also case sensitive (Aix).
Resolving Port Conflicts (WebLogic)

On many server installations, standard ports are often already occupied by various systems. By default, the Stat
Central Agent uses port number 8081. If you have port conflicts, the server will display one or more error
messages, such as:
java.net.BindException: Address already in use:
To resolve this conflict you may need to change the default service port, 8081.
1
Change this port setting as follows:

- cd <WL_HOME>/user_projects/domains/stat/config
Open the file config.xml.
Locate the line with this structure:

<server>
<name>myserver</name>
<listen-port>8081</listen-port>
<listen-address></listen-address>
</server
Modify the ListenPort="8081" setting to a suitable port for your system.
Deleting Data Sources and Connection Pools (WebLogic)

Data sources and connection pools are automatically deleted from your environments by default each time you
first access the datasource upon a new re-start. This allows the agent to re-connect to an environment even if
its connection configuration (such as usernames, encrypted passwords, and port numbers) has been changed, or
if the environment has been moved to a new location.
Clearing connection information is controlled by a parameter in the stat.properties file. If for any reason you
want to persist connection information after re-starting the agent, open the stat.properties file in
<STAT_HOME>/config and change the value of the parameter ClearWeblogicDatasource to No.
Stat 5.7.2
24
If you change this setting, it is your responsibility to manually delete the datasources if you make any
configuration changes (such as usernames, encrypted passwords, and port numbers). To resolve this issue you
need to log in to WebLogic's web console interface and manually remove the unwanted data source and its
corresponding connection pool from the WebLogic configuration file. After deleting the unwanted data source
and connection pool, the Stat Central Agent will re-create the data source and connection pool with the
updated connection information the next time the data source is accessed.
To delete Oracle WebLogic 11g data sources and connection pools:

1
Go to http://localhost:8081/console, where local host is the name of the machine the agent is running
on and login using the same username and password used to start WebLogic.
Click Services and then Data Sources on the Domain Structure tree on the left side of the screen.
Click Lock and Edit on the Change Center box in the upper left of the screen.
Select the Data Source to be deleted.

NOTE: Do not remove StatDataSource. This is the Stat Repository configuration.
Click Delete.
You will be prompted to validate the datasource you have selected for deletion. Click Yes.
Click Activate Changes on the Change Center box in the upper left of the screen.
Validate that you receive a message with a green check mark: All changes have been activated. No
restarts are necessary.
Support IMAP via TLS

In order to support Imap via TLS, the Stat Central Agent needs at least version 1.4.5 of Java Mail.jar.
This can be obtained from Oracle at: http://www.oracle.com/technetwork/java/javamail/index-138643.html.
Extract mail.jar from the .zip file and place it at \WL_Home\jdk160_21\jre\lib\ext (jdk162_21 may be different
on your site).
Restart the Stat Central Agent if it is running.
Testing Database and Server Connections

If you have already defined any database and server connections in the Stat Repository, you can test the
connections in the Stat Web Client after installing the Stat Central Agent.
TIP: You can also test connections in the Stat Windows Client. See the book, Stat 5.7.0: System
Administration, Chapter 4, General Maintenance Tables for more information.
You can validate the connections between the Stat Central Agent and all the databases, ftp file servers, email
servers, and VCM repositories currently defined in the Stat Repository.
NOTE: To test connections in Stat Web, you must be assigned the user class right, Agent Test Connect.
To test database and server connections:

1
Open your internet browser and go to the URL address for Stat Web.
On the standalone platform: http://localhost:8080/stat
On Weblogic: http://localhost:8081/stat
Enter your assigned user name and password and click Login or press <Enter>.
This logs you into the Stat Web Console.
Click Menu in the Stat Web Console menu bar.

Stat 5.7.2
25
This opens the Stat Menu window.

4
Click Test Connect.

This opens the Stat Test Connect window.
Select the tab for the type of database or server you want to test.
Select the checkbox for each database or server you want to test.
Click Test Connect.

The Stat Central Agent attempts to connect to each database or server you selected and then reports the
results in the Status column. Connection errors are reported with a brief description of the problem.
Upgrade the Stat Oracle Agent (Oracle EBusiness Suite only)

The following upgrade must be performed on each Oracle E-Business Suite server that will be managed by Stat.
You must re-install each Stat Oracle Agent defined on each server before you can upgrade them from
5.6.x/5.7.0 to 5.7.2. To save time, however, it is recommended that you first create a backup of each agents
stat.conf file. This way, after installing a Stat Oracle Agent from the 5.7.2installation cd, you can reuse your
5.6.x/5.7.0 configurations by copying configuration data from the archived stat.conf file to the new stat.conf
file you just installed.
To use the Oracle E-Business Suite functionality supported by Stat, install and run the Stat Oracle Agent after
you have installed and run the Stat Central Agent.
To upgrade a Stat Oracle Agent:

1
Stop all instances of the agent. Execute the following command for each environment:
statctl.sh -e <envCode> -e stop
Backup/archive the stat.conf file for each Stat Oracle Agent you want to upgrade.
Create a user to own the Stat Oracle Agent files. All Oracle E-Business Suite OS accounts on the server
must have read and execute permissions for these files.
Stat 5.7.2
26
The new Stat user account should exist in the same group as the Oracle E-Business Suite accounts (e.g.
"dba"). The Stat Oracle Agent can also be installed under a different directory with the existing Stat user
account.
4
Locate the stat installation directory: <stat installation cd>/stat_agent_ora_apps.
Copy the stat_ora.zip from the Stat installation CD to the Oracle E-Business Suite server.
Unzip stat_ora.zip in the home directory of the new user created for the Stat Oracle Agent files, or the
new directory if the existing user is being used.
This directory is referred to below as STAT_HOME.
Set the <STAT_HOME> and PATH in the profile of each Oracle E-Business Suite user (e.g. applmgr) on the
server.
Example:
$>STAT_HOME=/home/stat
$>export STAT_HOME
$>PATH=$PATH:$STAT_HOME/bin
Set the STAT_JAVA_HOME to the JVM that should be used by the Stat Oracle Agent.
Example:
$>STAT_JAVA_HOME=/opt/java/15
The Stat Oracle Agent requires 32 bit Java 1.6.0_5+ or later (Java 1.8.x is not supported). It will be
necessary to install a suitable version if one is not already available.
TIP: You can also use the Java version supplied in your E-Business environment. The version used by
Stat should be equal to or greater than the one in the E-Business environment.
For users migrating file and schema objects that include diacritic marks (umlauts, tildes, breves, etc.),
do the following to change the character set to ISO-8859-1:
a
Open Statctl.sh.
Locate the line:

-Dfile.encoding=UTF-8 \
Modify it to:
-Dfile.encoding=ISO8859-1 \
10 For users that have installed the Stat Central Agent on Weblogic, locate the files wlclient.jar,
wljmsclient.jar, and wlthint3client.jar in <WL_HOME>/weblogic10.x/server/lib and copy them to the
~/lib/weblogic directory for each Oracle Agent that you have set up.
11 For each Stat Oracle Agent that you are upgrading, open the stat.conf file that you backed up/archived
in step 2, copy the configuration settings you want to re-use, and paste them in the corresponding 5.7.2
stat.conf file located in <STAT_HOME>/conf.
12 If you are running a Release 12 Oracle E-Business Suite environment, do the following:
a
Open the stat.conf file located in <STAT_HOME>/conf and add the parameter
<env>.env.CONTEXT_NAME:<sid_hostname>
NOTE: The <env>.CONTEXT_NAME parameter is required for Release 12 support. See Edit
the Stat.Conf File on page 32 for information on new Stat 5.7.2 configuration parameters.
The following parameters are no longer required in the stat.conf file for 12.x and are
automatically read from the Context File. If they are present in stat.conf, they will override the
values read from the Context File.
<env>.env.APPL_TOP
<env>.env.ORACLE_HOME
<env>.env.TWO_TASK
<env>.env.APPLFENV
<env>.env.CONTEXT_FILE
Stat 5.7.2
27
<env>.env.APPLTMP
<env>.env.APPLREP
<env>.env.LD_LIBRARY_PATH
b
(Optionally) If you experience issues with compiling RDF Report File, you may need to patch the
reports.sh file located in $ORACLE_HOME/bin directory:
a
Open the reports.sh file located in $ORACLE_HOME/bin/ and locate the following:
TNS_ADMIN=$ORACLE_HOME/network/admin
export TNS_ADMIN
Replace with the following:

#TNS_ADMIN=$ORACLE_HOME/network/admin
#export TNS_ADMIN
TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}
export TNS_ADMIN
(Optionally) If you experience issues with compiling Form File, you may need to patch the
frmcmp_batch.sh file located in $ORACLE_HOME/bin directory:
a
Open the frmcmp_batch.sh file located in $ORACLE_HOME/bin/ and locate the following:
TNS_ADMIN=$ORACLE_HOME/network/admin
export TNS_ADMIN
Replace with the following:

#TNS_ADMIN=$ORACLE_HOME/network/admin
#export TNS_ADMIN
TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}
export TNS_ADMIN
NOTE: For R12.2, make sure to change these values on both Run and Patch Editions.
d
Remove xmlparserv2.jar from <STAT_HOME>/lib/oracle directory.
13 If your Stat database is running on Oracle 12c, open the SQLNET.ORA file and add the following SQLNET
parameter:
SQLNET.ALLOWED_LOGON_VERSION=8
14 Review Appendix F of the System Administrator Guide if you have a firewall between your Stat Oracle
Agents and your Stat Central Agent.
The location of the configuration files have changed. You will need to review the settings on these files.
Assign User Class Rights

The table below describes the new user class rights defined in Stat 5.7.0. You may need to assign certain rights
to implement some 5.7.0/5.7.1/5.7.2 enhancements.
Rights Group
Right
Description
Security
LDAP Connection - Add
Enables the user to add new LDAP

Connection definitions
Security
LDAP Connection - Edit
Enables the user to edit existing LDAP

Connection definitions
Security
Access Stat Web Client
Enables the user to access the Stat Web

Client
Security
Access Stat Windows Client
Enables the user to access the Stat

Windows Client
Stat 5.7.2
28
Rights Group
Right
Description
CSR Tasks
Tasks - Edit Task on Closed CSR
Enables the user to edit a Task after the

associated CSR has been closed
CSR Tasks
Tasks - Edit Own Tasks
Enables the user to edit a Task owned by

them
CSR Tasks
Tasks - Edit Other User
Enables the user to edit a Task that is not

assigned to them
CSR Tasks
Tasks - View Billed Hours
Enables the user to view the actual Billed

Hours on a Task
CSR Tasks
Tasks - View Billable Rate
Enables the user to change the Billable

Rate on a Task
PS Migration Mgmt
Allow to skip Restage
Enables the migrator to indicate that

restaging the PeopleSoft project is not
necessary
PS Migration Mgmt
PS Audit Flags - Edit
Enables the user to change the

PeopleSoft Project audit flags during a
migration
PS Migration Mgmt
Allow partial migration
Allows the user to choose which objects

in an Archive Set will be migrated,
effectively creating a partial Archive Set
migration
PS Migration Mgmt
PS Migration status change-Override
Enables the user who is not a migrator to

change migration status to Cancel or
Complete
OraApps Migration Mgmt
OA Migration status change-Override

Complete
Generic App Migration Mgmt GA Migration status change-Override

Complete
Enhancements and Modifications

The change requests listed below are for enhancements and fixes that either require a configuration
modification, or have an optional modification.
For a complete list of enhancements, see the Release Notes.
Stat 5.7.2 Enhancements

Support for PeopleTools 8.54 (Stat-768)
PeopleTools 8.54 introduces 1 new object type and modifies 33 other object types.
New object type:
MAP Admin
Object types that have been renamed in 8.54:
Object Security Group is the same as Definition Security
Objects that have been modified in 8.54:
Activity
Stat 5.7.2
29
Application Data Set
Application Engine Section
Component
Composite Query
Definition Security (Object Security Group)
HTML
Job Definition
Map Layout
Map Template
Message Node
Page
Permission List
Portal Registry Structure
Process Definition
PS/Query
Record
Related Content Definition
Search Category
Search Definition
Service Operation Version
Style Sheet
Test
Before starting the Stat Central Agent, log on as a Stat administrator and update the Object Mover Instructions:
Maintenance | General | Update PS Object mover instructions. This inserts 1453 new rows into the tools
table.
The new PeopleTools version is 8Q in Stat. One of the following two scripts should have been run as part of the
Stat database upgrade, as described in Upgrade the Stat Database on page 5:
PORAv572ps8Q.sql for Oracle
PMSSv572ps8Q.sql for MSSQL Server
In addition, the following staging scripts are necessary against a PeopleSoft 8.54 database for a Stat staging
database, as described in Staging Database Scripts on page 6:
PStageDB2-OS390v572.sql
PStageDB2-UNIXv572.sql
PStageORAv572.sql
PStageMSSv572.sql
Go to Maintenance | General | PeopleSoft Connect and update the PS Version on the appropriate PeopleSoft
databases to 8.54+.
Go to Maintenance | Domain Specific |PeopleSoft Migration Paths and create migration paths for the 8.54
databases. You cannot migrate objects between databases of different tools versions.
The definition of the object may be different (see above) and be stored in different Stat tables.
Application Designer Project Copy does not allow the target to be a different version from the Source.
PeopleTools Physical Locking

Stat 5.7.2
30
Definition Security has changed in PeopleTools 8.54. While it is still possible to define it using the two tier
Application Designer function (GO | Definition Security), PeopleSoft recommends defining it with the PIA client
(Main Menu | PeopleTools | Security | Definition Security | Definition Groups). This allows for additional
object types to be locked: Analytic Model and Optimization Model.
Definition Security setup is defined in PeopleTools 8.54: Security Administration, a pdf available from Oracle at
http://docs.oracle.com/cd/E55244_01/psft/acrobat/pt854tsec-b0714.pdf.
Also see the book, Stat 5.7.0: Stat System Administration, Chapter 8, Object Security.
The setup is essentially the same as previous PeopleTools release with a couple of differences from Stat.
You still need to associate PeopleSoft Operid's with Stat ID's in Stat using one of the following:
User Options | PeopleSoft Options
User Options | User Maintenance
Maintenance | Security Settings | User Maintenance
Maintenance | General | PeopleSoft Connect | PS Options
You do not need to define a ZZSTATDONOTDEL object as a place holder in PeopleTools in the 8.54
PeopleTools database
Run the PSLockSync job against the appropriate 8.54 database. The PSLockSync job automatically
creates and populates Definition Security Groups in the tables (PSPTDEFSEC_GRP and PSPTDEFSEC_GRPS)
in the specified 8.54 database, including STAT_READ and STAT_EXCLUD.
IMPORTANT: Do NOT define inclusion rules for STAT_READ, STAT_EXCLUD or any STAT_operid group
in PIA
You still need to associated the STAT_* groups to the primary permission list of the user. Use PIA| Main
Menu | PeopleTools | Security | Permissions & Roles| Permission Lists | Definition Security Tab and
Mark STAT_READ as display only in each Permission List assigned.
Unable to open document links from web client after 5.7.1

upgrade (Stat-870)
Three additional buttons have been added to the Description/Resolution Editor on the Stat Web Client:
Insert/Edit Link
Unlink
Preview
To enter a link, type a link name and select it. The Insert/Edit and Unlink buttons are enabled. Click Insert/Edit
and fill in the appropriate information
To remove a link, highlight the link and click Unlink. The text will remain, but the url is removed.
To open the link, right click on it and select one of the following options:
Open Link in New Tab
Open Link in IE
Open Link in New Window
Open Link in New Private Window

IMPORTANT: This functionality is browser specific and is controlled by security rules enforced by that
browser. You may need to highlight the link and click Preview. From the Preview popup, right click on the
url to get the options.
If the link is to a file on local server, Chrome prompts you to copy the link and paste it into another
tab/window.
Stat 5.7.2
31
Stat 5.7.1 Enhancements

Support for Oracle E-Business 12.2 (Stat-736)
Stat 5.7.1 is primarily directed at support for Oracle 12.2 E-Business environments. This enhancement affects
many areas of Stat, as described in the following sections. The configuration changes you make to support R12.2
will also work with lower versions of 12.x, except where noted.
Regarding Stat support for R12.2:
R12.2 features a Weblogic Server that replaces the OC4J Application server used in previous Oracle EBusiness versions. One instance of the Weblogic Server is installed on the Admin server. Stat tests
connections to this server in the Oracle Apps Connection Maintenance window.
In R12.2, the Application Tier file system maintains 2 copies of all files: a Run Edition File System, and a
Patch Edition File System. These 2 file systems are used in the new Online Patching feature. Stat
archives files from the current Run Edition, and migrates to both editions.
A few of the parameters in the stat.conf configuration file are specific to each Edition and are
eliminated from stat.conf for R12.2. Instead, they are automatically read from the Context File in the
Oracle E-Business environment.
Configuring R12.2 Support

The following sections are listed in the order they should be performed.
NOTE: Before configuring R12.2 support, stop all instances of the agent. Execute the following command
for each environment: statctl.sh -e <envCode> -e stop
Add WebLogic Server Password

R12.2 relies on a WebLogic Server in place of the OC4J Application server used in previous versions. This means
when configuring your new R12.2 environment in Stat you must specify the WebLogic Server password.
1
Launch Stat 5.7.1 and go to Maintenance | General | Oracle Applications Environment Connection
Maintenance.
Define any new R12.2 environments as needed.

For more information on defining environments, see the book Stat 5.7.0: System Administration,
Chapter 4, General Maintenance Tables.
For each R12.2 environment, click Enter Password in the WebLogic Password field and enter the
WebLogic Server password.
The Weblogic Server password is required along with the APPS and SYSTEM passwords. Do not yet
attempt to test the connection to any R12.2 environments.
Edit the Stat.Conf File

Stat 5.7.2
32
As described in the section, Upgrade the Stat Oracle Agent (Oracle E-Business Suite only) on page 26, all R12
(not required for 11i) Oracle E-Business suite versions must have the CONTEXT_NAME parameter defined in the
stat.conf file. There are also new optional parameters you can add for R12.2 and several parameters you should
remove for R12.2.
Table 1. Required parameter for all R12 Oracle E-Business Suite versions
<env>.env.CONTEXT_NAME:<sid_hostname>
sid_hostname is the usually configuration for this value. Yours

may be different. Ask your DBA
Table 2. Optional parameters for R12.2

<env>.env.CUSTOM_PRODUCTS
For R12.2, when a custom top is created using adsplice, a new

Product's status is not set to 'L'. This parameter keeps track of
custom products. Value is a comma separated list of custom
products, for example (XXDELL,XXQUEST).
<env>.env.ADOP_LOG_PATTERN
Default pattern for capturing Patch logs is "(.*\\.log)|(.*\\.lgi),

meaning all files with .log and .lgi extensions.
Users may add other extension by changing the regular
expression. For example to additionally capture files with .out
extension change the pattern to (.*\\.log)|(.*\\.lgi)|(.*\\.out)
<env>.env.ssh_disabled
In a Multi-node environment, by default, Stat assumes that the

ssh utility is running between the Admin node and all other
nodes. To override this, set this parameter to 'n'.
Table 3. Optional parameters not used for R12.2

<env>.env.JAVA_TOP
Optional for R12 and R12.1; not used in R12.2
<env>.env.CUSTOM_OAF_ROOT_PATH
Deprecated for R12. OAF files are assumed to be under

JAVA_TOP
<env>.env.APPL_TOP
Optional for R12 and R12.1
<env>.env.ORACLE_HOME
<env>.env.TWO_TASK
<env>.env.APPLFENV
<env>.env.CONTEXT_FILE
<env>.env.APPLTMP
<env>.env.APPLREP
<env>.env.LD_LIBRARY_PATH
NOTE: In general Stat reads the values for these parameters from the Context File of the environment. If
these parameters are present in stat.conf, they override the values in the Context File.
Update Product List

Many new features in Stat supporting R12.2 rely on the Release Level of the AD record in the list of products for
each environment. After successfully starting the Oracle agent, the next step is to update the product list for
each R12.2 environment. This is done in the Oracle Applications Configuration maintenance table.
1
Launch Stat 5.7.1 and go to Maintenance | General | Oracle Application Configuration.
For each R12.2 environment, select the environment and click Update Products.
The code level for Release R12.2 is C. (Note that R12.1 has code level B and R12 has code level A).
Stat 5.7.2
33
NOTE: After updating the product list, you can test your connections to R12.2 environments in the Oracle
Applications Environment Connection Maintenance window.
Configure Support for Custom Products

If custom objects are defined, then the base directories for those object locations are defined in the OraApps
Base Directories tab of the Object Type Maintenance window. Prior to 5.7.1, these directories were required to
be defined in the stat.conf file. For R12.2 environments, if these base directories are under the Edition-based
File System, then the value for each Base Directory must come from the Context File. An example of these
types of Base Directories would be OA_HTML. This parameter is defined in the Context file with a value for both
the fs1 and fs2 file system. To retrieve values from the Context File, you always need an XPath expression. A
new column called Context Pattern is defined in Stat which stores the XPath expression for retrieving the value
from the Context File. (You may need to consult with your DBA and refer to documentation for EXTRACTVALUE
command). For example the expression for retrieving OA_HTML from the Context file is:
//OA_HTML[@oa_var="s_oahtml"].
Note that if these Base Directories are not under the Edition-based File System, then the value for the Base
Directory is defined in stat.conf as before.
Also Note that in general if a value is defined for any parameter in stat.conf, it always overrides the value read
from the Context File.
Patching and Migrating in R12.2 Environments

Patching for R12.2 environments is done through a patching cycle. There are 5 phases in a patching cycle:
prepare, apply, finalize, cutover, and cleanup. After the cutover stage is run, the Run Edition and Patch Edition
file systems are swapped.
Oracle Apps Management Console window
Stat 5.7.2
34
If there is at least one active R12.2 environment or higher (meaning that there is an AD record in the list of
imported products with code level of C or higher), a Patch Cycle button is displayed on the Patch Inventory
tab on the Oracle Apps Management Console window.
For R12.2 environments, patching is done through a patch cycle on the Patch Edition of the environment. A new
utility called adop is used to manage patch cycle phases, apply patches, and run impact analyses. The Patch
Cycle button is used to schedule any phase of a patch cycle but cannot be used to schedule Apply Patch or Patch
Impact requests (which are scheduled through the Schedule button.)
New Oracle App Patch window

Clicking New in the Patch Inventory tab opens the New Oracle App Patch window. A new adop Options field has
been added to this window for R12.2 patches. Here you can specify adop options which are additional default
parameters passed to the adop utility during the Patch Apply process (users can override these parameters at
runtime). The syntax for adop options is name=value pairs separated by spaces. Refer to your Oracle
documentation for a list of valid adop parameters.
Patching Multi-Node Instances

For a multi-node instance, there are 2 ways to apply the patch to all nodes.
The preferred way is by having ssh enabled between the Admin node and all other nodes. If this is the
case, we only need to apply the patch on the Admin node. All changes for other nodes will be applied by
Admin node.
If ssh is not enabled between the Admin node and other nodes, the patch will be applied to each node
separately
NOTE: For multi-node environments with shared appl_tops, Stat always starts only one agent on the
Admin node; therefore it is mandatory to have the ssh utility enabled and thereby enabling adop to be run
remotely on other nodes via adop remote invocation.
In a Multi-node environment, by default we assume that ssh utility is running between the Admin node and all
other nodes. To override this use the following stat.conf parameter: <env>.env.ssh_disabled:n
Schedule Request Window
Stat 5.7.2
35
In the Oracle Apps Management Console, both the Patch Cycle button and the Schedule button open the
Schedule Request window. The Patch Cycle button is only displayed if there is at least one active R12.2 or
higher environment.
In the Schedule Request window, the Environment field lists all active environments. If you select a R12.2
environment, the Process Type field includes the patch cycle options prepare, finalize, cutover, and cleanup.
Depending on whether the window was opened from the Patch Cycle button or the Schedule button, The
Process Type field displays additional options:
If opened from the Patch Cycle button, the Process Type field displays additional phases including
Abort, fs_clone, and actualize_all.
If opened from the Schedule button, the Process Type field displays the Apply patch and Impact Patch
options, as well as the patch cycle options prepare, finalize, cutover, and cleanup.
The window displays different input fields based on the option selected in the Process Type field.The
Dependent Event fields allows scheduling the patch cycle request as a dependent event. In the adop options
field, you can overwrite any adop parameters specified in the New Patch window.
NOTE: The Maintenance Mode option is not supported for R12.2 and higher and is not displayed if the
environment is R12.2 or higher.
IMPORTANT: You must have OraApp Patch - Apply security right to schedule a Patch Cycle event
For more information on the Schedule Request window, see the book Stat 5.7.0: User Guide, Chapter 12,
Change Management for Oracle Applications.
View Logs from the Process Request Tab

For R12.2, a large number of log files may be generated at the end of each cycle. Typically the following
directory is created $NE_BASE/EBSapps/log/adop/<session id> and log files for each phase of the Patch Cycle
are placed there. Stat by default captures all *.log and *.lgi files. You can configure the following new
environment variable to control this pattern:
Stat 5.7.2
36
<env>.env.ADOP_LOG_PATTERN defaults to "(.*\\.log)|(.*\\.lgi)". This is a regular expression that captures all

*.log and *.lgi file extensions. If you also need to capture *.out files, override the pattern like so:
<env>.env.ADOP_LOG_PATTERN: (.*\\.log)|(.*\\.lgi)|(.*\\.out).
Migration
Migration Window
R12.2 application tier file system has 2 copies of all files. A Run File System where all the services are
currently running from, and a Patch File System where all patches are applied in a patch cycle. A patch cycle
starts when the prepare phase of adop is run and the Run File System is copied to the Patch File System.
To keep both file systems in synch during a Patch Cycle, Stat migrates file objects to both the Run Edition and
Patch Edition File Systems.
Stat archives file objects from the current Run Edition.
If the target environment is version R12.2, the Maintenance Mode option is not used and is not displayed in the
Migration window.
If the target environment is version R12.2, the Migration window displays an Edition field, allowing users to
migrate to both editions or to a specific edition (Run or Patch).
Migration History Window
New columns are added to the Migration History window to track Maintenance Mode, Migration Exit Option and
Edition. These values are forwarded from the Migration window.
Stat 5.7.2
37
Custom Objects
Stat's custom objects are specially affected by R12.2 file system. For Custom and Generic custom objects, OA
Base Directory values should exist in the Environment's Context File, or it should come from a location outside
the AppsTier File System. In the latter case, the values are defined in the stat.conf file as before. Refer to the
Maintenance changes above to see how you can define a Context Pattern in order to extract the OA Base
Directory from the Environment's Context File.
Stat 5.7.0 Enhancements Requiring User Action

1
(STAT-509) Reset password using a temporary password through email

Outbound mail is required for creating users and resetting Stat User passwords (not LDAP). When an
administrator resets a user's password, the user will receive an email notifying him/her of the change
and providing an encrypted password to log into Stat. This message can be configured in the Reset
Password tab of the Electronic Mail Interface Setup window under Maintenance | Stat Central Agent |
Email Settings. When users logs in, they are immediately be prompted to change their password.
Stat 5.7.0 Optional Enhancements

The change requests listed below describe enhancements featured in Stat 5.7.0 which you can implement as
needed.
1
(STAT-14) Purge system generated logs purges data that should be retained
The purge job that removes old system generated logs has been modified so that it no longer purges
email logs. Review the retention days set on Purge-System Generated Log jobs (one per service domain)
and shorten the retention days if the retention days are higher than one to two weeks.
(STAT-178) A workflow rejection should trump an approval

Part of this approval modification was to change the method of defining Approvals to allow for 'OR'
operands in addition or instead of 'AND' operands. All three approval types (Status Transfer, Migration,
Patch Apply) are affected by this change. The upgrade leaves your approvals as defined, but you should
review the approvals and evaluate where changes may be needed. The approval list is present in a tree
view. Emails can be sent to the whole tree, branches of the tree, or individual approvers. This may
affect how you choose to define your approvals. Where you previously could only define 'AND' operands
between classes/queues/users, you may now specify something like 1 user from Class A or 2 from Class
B. In a given situation you may only want to send the emails to the members of Class A. Note that the
email indicator is now an '@' sign.
(STAT-251) Stat.ini is not where documentation indicates for Windows 7/Windows 8

Stat.ini is installed in ProgramData/Dell/Stat/570 by default.
Some sites have extra security programs loaded on to their workstations/laptops which disguises the
location of the Stat.ini file from the user. That made it difficult to set the trace mode on for Stat.
In Stat.ini editor now allows the user to set trace on individual environments with a checkbox so it is no
longer necessary to open the stat.ini file manually.
Stat 5.7.2
38
(STAT-136) Prevent user access to the Stat Web Client

Two new user rights have been added: one for Stat Windows Client access and One for Stat Web Client
access. (See the table of new User rights listed above). The rights have been added to all user classes by
default. Review the user classes and remove one or the other right if appropriate.
(STAT-321) Allow for multiple LDAP domains

Multiple LDAP servers may be defined in Stat and associated to different users. Each user is only
associated to one server. LDAP setup has been moved to Maintenance | Security | LDAP Connect. The
servers, Domain Names and users can all be configured before turning the feature on. LDAP is turned on
in the Other Options tab in the System Maintenance table. See System Administration Guide for details.
(STAT-82) Audit Stat Security Tables USER_SVC_DOMAINS and USER_CLASS_RIGHTS

Stat is automatically auditing all transactions against the following tables:
STAT.PS_DB_OPRID, STAT.QUEUE_ASSIGNMENT, STAT.STAT_FILE_LOCATE, STAT.STAT_FILE_SERVERS,
STAT.STAT_LDAP_CONFIG, STAT.STAT_LOGIN, STAT.STAT_PSDB_CONFIG, STAT.STAT_VC_PARAMS,
STAT.STATUSER, STAT.SYSTEM_TBL,
STAT.USER_APPLICATIONS, STAT.USER_CLASS_RIGHTS, STAT.USER_CLASS, STAT.USER_ENVIRONMENTS,
STAT.USER_OBJECT_TYPES, STAT.USER_SERVERS, STAT.USER_SVC_DOMAINS
An audit report is available in the Compliance category.
It is recommended that any custom triggers previously created to audit these tables be turned off.
(STAT-88) Filter approval lists based on environment access profiles

Migration Approval lists are now filtered based on Environment Access as defined in User Maintenance. If
you have indicated Environment Restrictions for users, and have defined Migration approvals, review the
approval definitions to validate that there are sufficient users defined after filters are applied.
User Maintenance modifications

A number of enhancements have been made to the User Maintenance table. See the System
Administration Guide for details.
(STAT-120) Ability to clone a user

The Stat administrator can synchronize user access information (Service Domain/User Class,
Queue, Application, Objects, Environments and Servers) between one selected user and many
other users. Users can be imported into Stat using minimal information and then synchronized to
another user who was previously setup. Or, if a new user class, queue, etc. is added, it can be
added to one user and then synchronized to many other users.
(STAT-411) Ability to assign queues to users via User Maintenance

An additional tab has been added to User Maintenance to allow queues to be assigned to a user.
The traditional method of adding users to a queue still exists.
Workflow modifications
A number of changes have been made to workflow functionality. These are listed here and documented
in the System Administration Guide.
(STAT-84) Cannot inactivate workflows used in open CSRs

Workflows can now be inactivated even though they may be used on existing CSRs. Be sure that
you still have an active Default workflow for each CSR type previously defined with workflow.
(STAT-32) Workflow should dynamically auto advance to the next workflow step when a task
is completed
Status transfer rules that contain Approvals can be designated to automatically transfer once the
approval rule has been satisfied. If the user has the CSR open this will not occur until the user
saves the CSR. If the CSR window is not open, the agent will update the status. There is typically
a 1 - 2 minute delay between the last approval and the status update, depending on network
performance. To update a transfer rule, right click on the arrow and select Auto Advance. If Auto
Advance is not available, this transfer rule does not qualify. To update existing CSRs with the new
Stat 5.7.2
39
Auto Transfer rules, logon as SYSTEM and run Tools | Stat Upgrade | Upgrade Workflow Auto
Transfer. This job may be run more than once.
(STAT-128) Restrict Archive Set Source Location based on workflow status and source of
migrations
Open a workflow status rule to indicate which environments can be a source of an archive while a
CSR is in this status. [none] indicates that no archives can be taken at all. Multiple environments
can be selected. If no rows are highlighted, then archives can be taken from any environment on
the migration path.
(STAT-138) Resolution tab needs to be configured to tie to any Workflow Status

Any status in a workflow can be set to require a resolution be entered while the CSR is in that
Status. The status transfer cannot occur until the resolution is entered. Closed statuses still
require resolutions and user whatever is already in the resolution tab. To update existing CSRs
with the new Resolution Status rules, logon as SYSTEM and run Tools | Stat Upgrade | Upgrade
Workflow Status Resolution. This job may be run more than once.
(STAT-112) Enhancement Request: Filter Approvals based on Application

Approval requests will be filtered based on Application Access as defined in User Maintenance. If
you currently have restricted application access, review your approval requests to validate that
you will always have appropriate users available when the lists are generated. Conversely, you
may want to consider adding application access restrictions to filter your approval lists.
Upgrade Checklist
The following checklist, combined with the previous sections of this document, will guide you through the
entire upgrade process.
Make a copy of this checklist for each database you will be upgrading.
Step
Description
Verify that your Stat production database is version 5.7.0.
De-install or back up old version of Stat
Create an exact copy of your Stat production database
Run the appropriate upgrade scripts against the database to be upgraded.
Install the Stat Windows Client
Use the INI Editor to create a new record for that database
If not done prior to the 5.7.1 upgrade, do the following:
Update the Stat license key
Upgrade the Stat password encryption
Upgrade the CSR Description and Resolution fields
Update the PeopleSoft Object Mover instructions (PeopleSoft users only)
10
Upgrade the Stat Oracle Agent (Oracle E-Business Suite users only)
11
Verify the installation directories modified during the upgrade
12
Assign new user class rights
13
Configure Oracle E-Business R12.2 support as needed
13
Implement required Stat 5.7.1 enhancements and optional enhancements as needed
14
Upgrade the original Stat production database
15
Install Stat on any remaining workstations
Stat 5.7.2
40
About Dell
Dell listens to customers and delivers worldwide innovative technology, business solutions and services they
trust and value. For more information, visit www.software.dell.com.
Contacting Dell
Technical support:
Online support
Product questions and sales:
(800) 306-9329
Email:
info@software.dell.com
Technical support resources

Technical support is available to customers who have purchased Dell software with a valid maintenance
contract and to customers who have trial versions. To access the Support Portal, go to
http://software.dell.com/support/.
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a
day, 365 days a year. In addition, the portal provides direct access to product support engineers through an
online Service Request system.
The site enables you to:
Create, update, and manage Service Requests (cases)
View Knowledge Base articles
Obtain product notifications
Download software. For trial software, go to Trial Downloads.
View how-to videos
Engage in community discussions
Chat with a support engineer
Stat 5.7.2
41

Stat 5.7.2 Patch App Instructions

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Stat 5.7.2 Patch App Instructions

Hochgeladen von

Copyright:

Verfügbare Formate

Stat 5.7.

Install the Stat Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Patch Application Instructions

Overview of the Upgrade Process

Unpack the 5.7.2 Upgrade

Upgrade the Stat Database

Install the Stat Client

Use the Stat INI Editor

Obtain the Stat License Key

Upgrade Password Encryption

Upgrade CSR Description and Resolution Fields

Update PeopleSoft ObjectMover Instructions

Upgrade the Stat Central Agent

Upgrade the Stat Oracle Agent (Oracle E-Business Suite only)

Assign User Class Rights

Enhancements and Modifications

Overview of the Upgrade Process

Verify that your Stat production database is at least v5.7.0.

Create an exact copy of your Stat production database.

Run the Stat 5.7.2 Windows Client installer.

Start the 5.7.2 Stat Central Agent.

10 For Oracle E-Business Suite users only:

Start each of the Stat Oracle Agents.

11 Assign new user class rights as needed.

Unpack the 5.7.2 Upgrade

Patch Application Instructions opens 5.7.2_Patch_App_Instructions.pdf (this document)

Upgrade the Stat Database

Take a back up of the test database (copy of production).

Depending on your DBMS platform, do one of the following:

Please note the following:

Oracle (9i, 10g, 11g, and 12c)

To upgrade to Stat 5.7.2 running on Oracle:

Run the script PORAv570-572.sql.

For PeopleSoft 8.x users only, run PORAv572ps8Q.sql.

Microsoft SQL Server (2005, 2008, 2012, and 2014)

To upgrade to Stat 5.7.2 running on Microsoft SQL Server:

Run the script, PMSSv570-572.sql.

F or PeopleSoft 8.x users only, run PMSSv572ps8Q.sql.

Staging Database Scripts

Also modify the scripts as follows:

8.54: run the script as is; no additional edits are required

8.53: comment out section 03d

8.52: comment out sections 03d and 03c

Prior to 8.52: comment out sections 03d, 03c and 03b

Install the Stat Client

To install the Stat Client:

Do one of the following:

Insert the Stat CD

The Stat Auto program launches automatically.

Click Install Stat Windows Client.

Use the Stat INI Editor

Obtain the Stat License Key

To activate a Stat license

Open Stat and go to Maintenance | General | System Maintenance.

Click on the License Tab.

The Properties of the license will be displayed if the key/message is valid.

Upgrade Password Encryption

To upgrade the password encryption:

Log in to Stat as the SYSTEM user.

Select Tools | Stat Upgrade | Upgrade Encryption.

To change the encryption key (optional):

Log in to Stat as the SYSTEM user.

Select Tools | Update Encryption Key.

Upgrade CSR Description and Resolution