Professional Documents
Culture Documents
1
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 purchaser’s 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 SOFTWARE’S 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 5.7.1
1
Patch Application Instructions
Patch Application Instructions
• Introduction
• Overview of the Upgrade Process
• Unpack the 5.7.1 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.1 patch release provides fixes and enhancements to Stat 5.7.0. This patch is primarily directed at
Oracle E-Business 12.2 support. For details, please refer to the Stat 5.7.1 Release Notes. Please review the
Resolved Issues section of the Release Notes before starting this upgrade.
IMPORTANT: This is a re-packaged version of Stat 5.7.1. It includes a modified upgrade script for MSS to
prevent data loss and it includes Stat 5.7.1HF-a and Stat 5.7.1HF-b previously released against the June
2014 version of Stat 5.7.1. The documentation of the scripts includes a date stamp to indicate which
version of the scripts have been run.
This document details the steps necessary to upgrade from Stat 5.7.0 to Stat 5.7.1. 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-754-
8999, or by email at support@software.dell.com.
Stat 5.7.1
2
Patch Application Instructions
Overview of the Upgrade Process
The following is a summation of the steps you will take to upgrade Stat to version 5.7.1. Use this information in
conjunction with the Upgrade Checklist on page 37 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 6 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.
2 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.
3 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.1 functionality. Please
refer to the detailed instructions contained in the upgrade script specific to your database platform
(PORAv570-571.sql for Oracle and PMSSv570-571.sql for SQL Server).
4 Run the appropriate database upgrade scripts against the copied database.
5 Run the Stat 5.7.1 Windows Client installer.
It is not necessary to uninstall the previous version of the Stat Windows Client before installing Stat
5.7.1. The Stat Windows Client installer creates shortcuts from the Programs menu that point to the Stat
5.7.1 files.
6 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 6 for more information as there have been changes to
the login requirements.
7 For PeopleSoft users only, open Stat 5.7.1 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.
NOTE: This patch requires a new installation directory (referred to as <STAT_HOME>). Do not
attempt to overlay the 5.7.1 files into an older Stat version.
Stat 5.7.1
3
Patch Application Instructions
8 Install the 5.7.1 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.
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.1 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.1).
Stat 5.7.1
4
Patch Application Instructions
• Stat Windows Client installs the Stat 5.7.1 Client. See Install the Stat Client on page 6.
Stat 5.7.1
5
Patch Application Instructions
To upgrade to Stat 5.7.1 running on Microsoft SQL Server:
1 Run the script, PMSSv570-571.sql.
2 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.
Stat 5.7.1
6
Patch Application Instructions
2 Click on the License Tab.
3 Paste the License Key and Site Message into the appropriate fields.
4 Click Verify.
5 The Properties of the license will be displayed if the key/message is valid.
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.
Stat 5.7.1
7
Patch Application Instructions
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.”
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
3 Open the Autorun program, either from the Stat cd or from the upgrade folder downloaded from
Supportlink.
4 Click Install Stat Central Agent.
Autorun opens the stat_server folder, which contains the subfolder, standalone.
Stat 5.7.1
8
Patch Application Instructions
5 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.
7 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 12.
b In the Type/Vendor field, select the database platform you are using.
Options include Oracle or SQL Server.
Stat 5.7.1
9
Patch Application Instructions
c Enter appropriate info for the Stat database: Host Name, Port, DB/Service Name, Login ID,
Password.
d 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.
e Choose desired logging setting for the UI and for the Stat Central Agent application.
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.
g Click Save.
Stat verifies that the Stat database parameters you entered are correct.
Stat 5.7.1
10
Patch Application Instructions
definitions you want to carry over to 5.7.1. In this case, copy the <STAT_HOME>\report\Custom folder from it’s
5.6.x/5.7.0 location and paste it to the new 5.7.1 <STAT_HOME> directory. Then remove any files with a .jasper
extension for the Custom folder.
Stat 5.7.1
11
Patch Application Instructions
1 Open <STAT_HOME>/app/bin/run.conf.bat.
2 Locate this section:
[ "x$JAVA_OPTS" = "x" ]
3 Insert this statement above the specified section:
JAVA_OPTS=""
Your file will now look like this:
JAVA_OPTS=""
[ "x$JAVA_OPTS" = "x" ]
4 Save run.conf.bat.
Stat 5.7.1
12
Patch Application Instructions
Description ports-default ports-01 ports-02 ports-03
JBM bisocket secondary BindPort 4365 4465 4565 4665
(See Note)
Web HTTP connector socket 8080 8180 8280 8380
HTTP connector socket 8443 8543 8643 8743
(See Note)
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.
2 Open <STAT_HOME>\app\server\default\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml
with notepad or other text editor.
3 Search for the setting, <!-- The name of the set of bindings to use for this server -->
<parameter>${jboss.service.binding.set:ports-default}</parameter>
<!-- Provides management tools with a ProfileService ManagementView
interface to the SBM and its components -->
<bean name="ServiceBindingManagementObject"
class="org.jboss.services.binding.managed.ServiceBindingManagementObject">
<constructor>
<!-- The name of the set of bindings to use for this server -->
<parameter>${jboss.service.binding.set:ports-default}</parameter>
4 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:
Stat 5.7.1
13
Patch Application Instructions
• 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
14 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)
• 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.
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.
Stat 5.7.1
14
Patch Application Instructions
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.
2 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>
3 Modify the values to look like this:
<attribute name="numberOfCallRetries" isParam="true">5</attribute>
<attribute name="pingFrequency" isParam="true">1200000</attribute>
<attribute name="pingWindowFactor" isParam="true">2</attribute>
4 Select the following code (near the end of the file):
<attribute name="timeout" isParam="true">0</attribute>
<!-- Uncomment for adjusting firewall ping/pong frequency -->
<!-- <attribute name="continueAfterTimeout" isParam="true" >false</
attribute> -->
5 Modify the values to look like this:
NOTE: Notice that <!-- and --> have been removed from the continueAfterRimeout line.
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 5.7.1
15
Patch Application Instructions
################################################################################
stat.db.jdbc_driver:oracle.jdbc.driver.OracleDriver
stat.db.server:<stat repository server name/ip> <-- Natted IP Address
2 (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
3 Specify one of the following parameters to run service.bat commands:
install|uninstall|start|stop|restart|signal
4 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.
5 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”
Stat 5.7.1
16
Patch Application Instructions
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.
• 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).
Stat 5.7.1
17
Patch Application Instructions
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
• 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
2 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
3 Browse to the JAVA_HOME/jre/lib/security directory under your installation of JAVA_HOME.
4 Rename local_policy.jar to local_policy.jar.strong.
5 Rename US_export_policy.jar to US_export_policy.jar.strong.
6 Go to the temp folder where you unzipped the jce_policy file and copy local_policy.jar and
US_export_policy.jar.
7 Paste both files into the JAVA_HOME/jre/lib/security folder.
Stat 5.7.1
18
Patch Application Instructions
c Move the trailing --> to the end of this line:
<!-- SSL/TLS Connector configuration using the admin devl guide keystore
d Modify the keystorePass to equal the password written in the keystore.
e 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:
<!-- SSL/TLS Connector configuration using the admin devl guide keystore
-->
<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
b Move <STAT_HOME>app/server/default/deploy/stat-agent.ear to a location outside of the
<STAT_HOME> folder for backup purposes
c 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.
7 Restart your agent.
8 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.
9 If you have a firewall, open port 8443 (8443/8543/8643/8743) on the firewall.
Stat 5.7.1
19
Patch Application Instructions
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>.
2 Create an environment system variable called STAT_HOME2 with a value of <STAT_HOME2> from the
above step.
3 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.
4 Go to <STAT_HOME2>\app\server\default\conf\
bindingservice.beans\META-INF and open the file bindings-jboss-beans.xml. Then locate the line:
<parameter>${jboss.service.binding.set:ports-default}</parameter>
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 12 for information on resolving port conflicts.
5 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.
6 (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.
7 (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.
Stat 5.7.1
20
Patch Application Instructions
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.
2 Create a directory for Stat 5.7.1 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 23 below.
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.
6 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.
b (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).
7 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.
Stat 5.7.1
21
Patch Application Instructions
Additional tabs are displayed.
e Click the Connection Pool tab.
f Click Lock & Edit on the upper left portion of the screen.
g Depending on whether your Stat Database is on Oracle or SQL Server, update the DriverName,
Properties and URL.
For Oracle:
• 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"
h 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.
Stat 5.7.1
22
Patch Application Instructions
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.1
23
Patch Application Instructions
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.
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.
5 Click Delete.
You will be prompted to validate the datasource you have selected for deletion. Click Yes.
6 Click Activate Changes on the Change Center box in the upper left of the screen.
7 Validate that you receive a message with a green check mark: “All changes have been activated. No
restarts are necessary”.
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.
Stat 5.7.1
24
Patch Application Instructions
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
2 Enter your assigned user name and password and click Login or press <Enter>.
This logs you into the Stat Web Console.
3 Click Menu in the Stat Web Console menu bar.
This opens the Stat Menu window.
4 Click Test Connect.
This opens the Stat Test Connect window.
5 Select the tab for the type of database or server you want to test.
6 Select the checkbox for each database or server you want to test.
7 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.
Stat 5.7.1
25
Patch Application Instructions
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
2 Backup/archive the stat.conf file for each Stat Oracle Agent you want to upgrade.
3 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.
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.
5 Copy the stat_ora.zip from the Stat installation CD to the Oracle E-Business Suite server.
6 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.
7 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
8 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.
9 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.
b Locate the line:
-Dfile.encoding=UTF-8 \
c 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.1
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 29 for information on new Stat 5.7.1 configuration parameters.
Stat 5.7.1
26
Patch Application Instructions
The following parameters are no longer required in the stat.conf file for 12.x and are
automatically read from the Context File. They should be removed from, or commented out of
the stat.conf 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
<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
b Replace with the following:
#TNS_ADMIN=$ORACLE_HOME/network/admin
#export TNS_ADMIN
TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}
export TNS_ADMIN
c (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
b 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.
Stat 5.7.1
27
Patch Application Instructions
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 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
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 Enables the user who is not a migrator to
change migration status to Cancel or
Complete
Generic App Migration Mgmt GA Migration status change-Override Enables the user who is not a migrator to
change migration status to Cancel or
Complete
Stat 5.7.1
28
Patch Application Instructions
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 E-
Business 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.
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.
Stat 5.7.1
29
Patch Application Instructions
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.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'.
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.
Stat 5.7.1
30
Patch Application Instructions
NOTE: After updating the product list, you can test your connections to R12.2 environments in the Oracle
Applications Environment Connection Maintenance window.
Stat 5.7.1
31
Patch Application Instructions
Oracle Apps Management Console window
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.)
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
Stat 5.7.1
32
Patch Application Instructions
Schedule Request Window
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.”
Stat 5.7.1
33
Patch Application Instructions
are placed there. Stat by default captures all *.log and *.lgi files. You can configure the following new
environment variable to control this pattern:
<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).
Stat 5.7.1
34
Patch Application Instructions
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.1
35
Patch Application Instructions
4 (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.
5 (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.
6 (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.
7 (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.
8 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.
9 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.1
36
Patch Application Instructions
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
1 Verify that your Stat production database is version 5.7.0.
2 De-install or back up old version of Stat
3 Create an exact copy of your Stat production database
4 Run the appropriate upgrade scripts against the database to be upgraded.
5 Install the Stat Windows Client
6 Use the INI Editor to create a new record for that database
7 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
8 Update the PeopleSoft Object Mover instructions (PeopleSoft users only)
9 Upgrade the Stat Central Agent
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.1
37
Patch Application Instructions
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
Stat 5.7.1
38
Patch Application Instructions