Professional Documents
Culture Documents
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
Stat 5.7.2
Patch Application Instructions
Introduction
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
Patch Application Instructions
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
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.
Run the appropriate database upgrade scripts against the copied database.
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
Patch Application Instructions
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).
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.
Release Notes opens 5.7.2_Release_Notes.pdf. Refer to these notes for modifications that may affect
daily business processes.
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
Patch Application Instructions
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.
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.
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
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.
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
Patch Application Instructions
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.
\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
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
Patch Application Instructions
If you downloaded the upgrade package from Supportlink, click Autorun from the root of the
downloaded folder.
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.
Paste the License Key and Site Message into the appropriate fields.
Click Verify.
Stat 5.7.2
Patch Application Instructions
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.
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.
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
Patch Application Instructions
app
config
report
stat_log
uploads
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.
Do the following to configure the Stat database and the database type-mapping:
a
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
Patch Application Instructions
10
Click Save.
Stat verifies that the Stat database parameters you entered are correct.
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.
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.
Open <STAT_HOME>/app/bin/run.conf.bat.
Stat 5.7.2
Patch Application Instructions
12
JAVA_OPTS=""
[ "x$JAVA_OPTS" = "x" ]
4
Save run.conf.bat.
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
4457
4557
4657
4757
4365
4465
4565
4665
8080
8180
8280
8380
8443
8543
8643
8743
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, <!-- 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>
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):
14
PeopleSoft databases
E-Business databases
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
Uncomment the line specifying the secondary BindPort by moving the <!-- and --> as shown below.
You should not uncomment the secondary ConnectPort line.
<!-- Use these parameters to specify values for binding and connecting control
connections to work with your firewall/NAT configuration
-->
<attribute name="secondaryBindPort">4365</attribute>
<!-- <attribute name="secondaryConnectPort">abc</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
15
Save <STAT_HOME>/app/server/default/deploy/messaging/remoting-bisocket-service.xml.
Open <STAT_HOME>/app/server/default/deploy/messaging/connectionfactories-service.xml.
Change the lines to look like this (remove <!-- and --> from the attribute name line):
<!-- Uncomment for adjusting firewall ping/pong frequency -->
<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
Patch Application Instructions
16
(Optional) In <STAT_HOME>/app/bin/service.bat, modify the following values if you want the service
name to reflect Stat:
Set SVCNAME=JBAS50SVC
Service The UDB/DB2 database Name. This is database name as defined during installation, not an
alias.
Stat 5.7.2
Patch Application Instructions
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).
Open <STAT_HOME>\app\bin\run.conf.bat.
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"
Open <STAT_HOME>/app/bin/run.conf.
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"
Blowfish
Triple DES
Stat 5.7.2
Patch Application Instructions
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
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
Go to the temp folder where you unzipped the jce_policy file and copy local_policy.jar and
US_export_policy.jar.
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.
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
Patch Application Instructions
19
<!-- 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
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.
Open <STAT_HOME>/conf/stat.properties.
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
Patch Application Instructions
20
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:
<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 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.
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.
Stat 5.7.2
Patch Application Instructions
21
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.
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.
The first time you start the WebLogic server, the Stat Connection is not properly defined; therefore the
server will start with errors.
9
Username = weblogic
Password = irv200038stat
Click Services and then Data Sources on the Domain Structure tree on the left side of the screen.
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
Patch Application Instructions
22
DriverName="oracle.jdbc.driver.OracleDriver"
Properties=v$session.program=STAT
Set the user name to STAT and set the password for Stat user.
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"
Installing DB2 Support for the Stat Central Agent (WebLogic) on page 24
Stat 5.7.2
Patch Application Instructions
23
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).
Stat 5.7.2
Patch Application Instructions
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.
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.
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.
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.
25
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.
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
Patch Application Instructions
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
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.
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
Patch Application Instructions
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
(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
NOTE: For R12.2, make sure to change these values on both Run and Patch Editions.
d
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.
Right
Description
Security
Security
Security
Security
Stat 5.7.2
Patch Application Instructions
28
Rights Group
Right
Description
CSR Tasks
CSR Tasks
CSR Tasks
CSR Tasks
CSR Tasks
PS Migration Mgmt
PS Migration Mgmt
PS Migration Mgmt
PS Migration Mgmt
MAP Admin
Activity
Stat 5.7.2
Patch Application Instructions
29
Component
Composite Query
HTML
Job Definition
Map Layout
Map Template
Message Node
Page
Permission List
Process Definition
PS/Query
Record
Search Category
Search Definition
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:
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.
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:
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.
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 IE
Stat 5.7.2
Patch Application Instructions
31
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.
Launch Stat 5.7.1 and go to Maintenance | General | Oracle Applications Environment Connection
Maintenance.
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.
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>
<env>.env.ADOP_LOG_PATTERN
<env>.env.ssh_disabled
<env>.env.CUSTOM_OAF_ROOT_PATH
<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
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.
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
Patch Application Instructions
33
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.2
Patch Application Instructions
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.)
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
Stat 5.7.2
Patch Application Instructions
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.
36
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
Patch Application Instructions
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-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.
38
Workflow modifications
A number of changes have been made to workflow functionality. These are listed here and documented
in the System Administration Guide.
(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
Patch Application Instructions
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.
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
Use the INI Editor to create a new record for that database
10
Upgrade the Stat Oracle Agent (Oracle E-Business Suite users only)
11
12
13
13
14
15
Stat 5.7.2
Patch Application Instructions
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
Stat 5.7.2
Patch Application Instructions
41