stat 5.6.0 install notes

8/18/2019 Stat 5.6.0 Install Notes

1/74

5.6.0

Install Notes


2/74

© 2011 Quest Software, 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 Quest Software, Inc.

The information in this document is provided in connection with Quest 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

Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THELICENSE AGREEMENT FOR THIS PRODUCT, QUEST 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 QUEST 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 QUEST HAS

BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with

respect to the accuracy or completeness of the contents of this document and reserves the right to make changesto specifications and product descriptions at any time without notice. Quest 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:

Quest Software World Headquarters

LEGAL Dept

5 Polaris Way

Aliso Viejo, CA 92656

email: [email protected]

Refer to our web site (www.quest.com) for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, Stat, and Toad are trademarks and registered trademarks of Quest

Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used

in this guide are property of their respective owners.

mailto:[email protected]://www.quest.com/http://www.quest.com/mailto:[email protected]


3/74

Table of Contents

Preface ..................................................................................................................................................................v

About This Guide..............................................................................................................................................................vi

Additional Information ......................................................................................................................................................vi

Online Help..............................................................................................................................................................vi

Release Notes.........................................................................................................................................................viAbout Quest Software, Inc. ..................... .................. .................. ................. ................. ................... .................. ............ vii

Contact Quest Software .................. ................. ................. .................. ................... ................. ................. .................. .... vii

Contact Quest Support ................ ................. ................... .................. ................. ................. .................... ................. ...... vii

Installing Stat........................................................................................................................................................1

Introduction....................................................................................................................................................................... 2

Before Proceeding with the Installation: .................. .................. ................. ................. ................... .................. ....... 2

Installation Checklist................................................................................................................................................ 3

Unpacking the 5.6.0 Installer ........................................................................................................................................... 4

Installing the Stat Database ........ ................. ................... .................. ................. ................. .................... .............. .......... 5

Stat on Oracle.......................................................................................................................................................... 5

Running Stat with Multiple Oracle Versions ............................................................................................................ 8

Stat on MS SQL Server (2005 or 2008) .................................................................................................................. 9

Creating a Staging Database (PeopleSoft Only) ........................................................................................................... 11

PeopleSoft on Oracle ............................................................................................................................................ 12

PeopleSoft on Sybase........................................................................................................................................... 13

PeopleSoft on MS SQL Server.............................................................................................................................. 13

PeopleSoft on DB2................................................................................................................................................ 13

Installing the Stat Client ................................................................................................................................................. 14Local Installation.................................................................................................................................................... 14

Network Installation ................. ................. ................. .................. ................... ................. ................. .................. ... 19

Oracle Developer Object Compare Support: Stat Client ................ .................. .................. .................. ................. 19

http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/


4/74

iv Stat 5.6.0Install Notes

Configuring the Stat Database ............... ................... ................. .................. ................. ................... .................. ............ 20

Edit the INI File ................. ................... ................. ................. .................. ................... ................. ................. ......... 20

Update the System Table ................ ................. ................... .................. ................. ................. .................... .......... 21

Installing the Stat Central Agent .................. ................. ................. .................. ................... ................. ................. ......... 22

Installing the Stat Central Agent on the Standalone Platform.......... ................. ................. ................... ................. 22

Configuring the Stat Central Agent on the Standalone Platform............................................................................28

InstallingUpgrading the Stat Central Agent on Oracle WebLogic 11g .................. .................. ................ ............... 41

Configuring the Stat Central Agent on on Oracle WebLogic 11g...................... .................. .................. ................. 43

Testing Database and Server Connections ................ ................. .................. .................. .................. ................. ... 46

Installing the Stat Oracle Agent (Oracle E-Business Suite only) ................ ................... ................. .................. .............. 48

Configuration................... ................. ................. ................... ................. .................. ................. ................... ........... 49

Administration ................. ................. ................. ................... .................. ................. ................. ................. ............. 59

Dynamically Changing Log Level........... ................. ................... .................. ................ ................... .................. ..... 61

Stat Oracle Agent Version ................... ................. ................. .................. ................... ................. ................. ......... 61Custom Products and File Locations ................. .................. .................. ................. ................. .................... .......... 61

Object Compare Support for Form Library Files .................. .................. ................. ................. .................... .......... 64

Base Directory Codes................ ................. ................... .................. ................. ................. ................... ................. 64

Verifying the Stat Oracle Agent............ ................. ................. .................. ................... ................. ................. ......... 64

Implementing Stat................ .................. .................. .................. ................. ................... ................. ................. ............... 65

Update the PS Object Mover Instructions (PeopleSoft Only) .................. ................... ................. ................. ......... 65Configure Stat........................................................................................................................................................65

Users and User Classes ............... .................. ................. .................. ................... ................. .................. .............. 66

http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/http://stat%205.6.0%20-%20install%20notes.pdf/


5/74

Preface

Contents

About This Guide

Additional Information

About Quest Software, Inc.

Contact Quest Software

Contact Quest Support


6/74

vi Stat 5.6.0

Install Notes

About This GuideThis guide describes how to install Stat version 5.6.0.

Additional Information

In addition to this guide, there are a number of options available for quickly finding theinformation you need.

Online Help

There are several ways to access online help topics.

Release Notes

To access the release notes, please visit SupportLink at: http://support.quest.com. Therelease notes are also available on the installation CD.

To... Do This...

Display the table of contents for help

topics

Select Help | Contents. If required, in

the Help window, select the Contents

tab.

Search for a specific help topic Select the Search tab in an open Help

window.

Display the index for help topics Select Help | Index. If required, in the

Help window, select the Index tab.

Display help for a specific window or

dialog

In the window or dialog, do one of the

following:

• Click Help

• Press F1

Note Not all windows and dialogs are linked

to specific help topics.

http://support.quest.com/http://support.quest.com/


7/74

Preface vii

About Quest Software, Inc.Quest Software simplifies and reduces the cost of managing IT for more than 100,000

customers worldwide. Our innovative solutions make solving the toughest IT

management problems easier, enabling customers to save time and money across

physical, virtual and cloud environments. For more information about Quest go to

www.quest.com.

Contact Quest Software

Please refer to our web site for regional and international office information.

Contact Quest SupportQuest Support is available to customers who have a trial version of a Quest product or

who have purchased a Quest product and have a valid maintenance contract. Quest

Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit

SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

• Retrieve thousands of solutions from our online Knowledgebase

• Download the latest releases and service packs

Phone 949.754.8000 (United States and Canada)

Email [email protected]

Mail Quest Software, Inc.

World Headquarters

5 Polaris Way

Aliso Viejo, CA 92656

USA

Web site www.quest.com

Stat Community http://communities.quest.com/community/stat

http://www.quest.com/http://support.quest.com/mailto:[email protected]://www.quest.com/http://communities.quest.com/community/stathttp://support.quest.com/http://communities.quest.com/community/stathttp://www.quest.com/mailto:[email protected]://www.quest.com/


8/74

viii Stat 5.6.0

Install Notes

• Create, update and review Support cases

View the Global Support Guide for a detailed explanation of support programs, online

services, contact information, and policy and procedures. The guide is available at http:/

/support.quest.com/pdfs/Global Support Guide.pdf .

http://support.quest.com/pdfs/Global%20Support%20Guide.pdfhttp://support.quest.com/pdfs/Global%20Support%20Guide.pdfhttp://support.quest.com/pdfs/Global%20Support%20Guide.pdfhttp://support.quest.com/pdfs/Global%20Support%20Guide.pdf


9/74

Installing Stat

Contents

Introduction

Unpacking the 5.6.0 Installer

Installing the Stat Database

Creating a Staging Database (PeopleSoft Only)

Installing the Stat Client

Configuring the Stat Database

Installing the Stat Central Agent

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

Implementing Stat


10/74

2 Stat 5.6.0

Install Notes

IntroductionThis guide documents the steps necessary to install Stat version 5.6.0 on either an

Oracle or a Microsoft SQL Server database. The guide is divided into eight sections.

Section 1: Unpacking the 5.6.0 Installer

Section 2: Installing the Stat Database

Section 3: Creating a Staging Database (PeopleSoft Only)

Section 4: Installing the Stat Client

Section 5: Configuring the Stat Database

Section 6: Installing the Stat Central Agent

Section 7: Installing the Stat Oracle Agent (Oracle E-Business Suite only)

Section 8: Implementing Stat

The sections are listed in the order that they need to be performed. The Stat Installation

CD contains the scripts that are used to build the Stat database. The database must exist

in order to do configurations.

This document assumes the user has a working knowledge of Stat and access to the user

manuals, especially the book, Stat 5.6.0: System Administration. The section

“Configuring the Stat Database” on page 20 assumes that data is being created in thenew Stat database. However, the instructions could be applied to any Stat database.

Before Proceeding with the Installation:

• The Stat client can be installed as a local installation or a network installation. If

the network installation is chosen, each workstation must have a ‘net install’ of

Stat performed on that workstation.

• The user installing or uninstalling the Stat client must be logged in as an

“Administrator” locally on that server/workstation due to enhanced security on

Windows XP/Vista/7/2003 server/2008 server.

• Verify the location of the database directories on the server and the instance

names (check with your DBA for this information).

• Depending on available resources, the Stat database can reside on the same serveras the current PeopleSoft, Oracle E-Business Suite, or generic application

database, or on a stand-alone server.


11/74

Stat 5.6.0 3

Install Notes

• Verify connectivity to the database that was created for Stat:

• Oracle: Oracle client connectivity, compatible to the database version, on all

workstations.

• MS SQL Server: MS SQL Server client connectivity, compatible to the

database version, on all workstations.

• Ensure that the new Stat databases are included in the Maintenance, Backup and

Recovery Strategy for this organization before continuing.

Installation Checklist

The following checklist summarizes the main steps of a complete Stat installation. After

you have performed each task, see the last section in this document, “Implementing

Stat” on page 65 for information on the additional configuration tasks that you will

perform to customize your copy of Stat to fit your particular business needs.

Step DB 1 DB 2 DB 3

1. Verify the location of the database directories on the

server and the instance names

2. Verify connectivity to the database created for Stat

3. Verify that the Stat database backup is defined

4. Modify and execute the appropriate database scripts

(Oracle/MSS)

5. Install the Stat client application, either locally or over

the network

6. For PeopleSoft users only, modify and execute the

required database scripts and staging database script

7. Add a record for the new database to the Stat INI file

8. Login in to Stat and update the System table with

appropriate values including license information

9. Install and configure the Stat Central Agent

10. For Oracle E-Business Suite users only, install andconfigure the Stat Agent for Oracle E-Business Suite


12/74

4 Stat 5.6.0

Install Notes

Unpacking the 5.6.0 Installer The Stat cd comes with an Autorun executable that launches the installer when the disc

is inserted.

If you have downloaded the Stat 5.6.0 zip file from Supportlink, unzip the whole file

into a location of your choice. Locate the Autorun.exe in the root directory of that

location and doubleclick it to launch the installer.

The menu buttons give you access to the various components of this upgrade:

• View Install Notes opens 5.6.0_Install_Notes.pdf

• View Upgrade Notes opens 5.6.0_Upgrade_Notes.pdf

• View Release Notes opens the Stat 5.6.0 Release notes in your Browser. Refer to

these notes for modifications that may affect daily business process.

• View Upgrade Scripts gives you access to the database upgrade scripts used toupgrade Stat. Does not apply to new installations.


13/74

Stat 5.6.0 5

Install Notes

• Install the Stat Central Agent unpacks the Stat Central Agent. See the section

“Installing the Stat Central Agent” on page 22.

• Install Stat Agent for Oracle E-Business Suite unpacks the Stat Oracle Agent

programs. See the section “Installing the Stat Oracle Agent (Oracle E-Business

Suite only)” on page 48.

• Install Stat Windows Client installs the Stat 5.6.0 Client. See “Installing the Stat

Client” on page 14.

• More Information provides copyright information about Stat and has links to

Quest and Quest Supportlink.

Installing the Stat Database

This section contains instructions for the scripts that need to be run against the client’s

Demo, Development (optional), and Production databases. The scripts are located under

a “scripts” directory on the Stat cd. Each script, which is supplied with the Stat

Installation cd, must be edited to replace certain variables prior to its execution. Because

they perform actions such as granting access to the Stat ID and creating database

objects, the path information supplied in the scripts is critical.

Read all instructions included within the scripts before proceeding with script

execution.

Note The Stat user password is set in the first new install script. This password can be modified AFTER the installation is completed. At least one administrative user needs to be logged

into the Stat application at the time. For more information, see the section “Changing the

Database Password” in the book, Stat 5.6.0: System Administration, Chapter 3, “Stat

Security.”

Stat on Oracle

1 Locate the necessary scripts.

Oracle install scripts are located in \Scripts\Oracle\Install . The

first three scripts need to be run to create the Stat database regardless of your

change management module. See the comments in each script for a complete

description of its purpose.

• NORAv560-1.sql


14/74

6 Stat 5.6.0

Install Notes

• NORAv560-2.sql

• NORAv560-3.sql

• NORAv560oa.sql

• NORAv560ps7x.sql

• NORAv560ps8x.sql

2 Modify the scripts as noted below.

3 Execute the appropriate scripts for your development environment using SQLPlus or Toad for Oracle only (Do not use other third-party tools).

Caution Each script should be run one-time only.

4 Recompile any invalid PL/SQL modules in the database by running the script,

utlrp.sql located in /rdms/admin directory.

NORAv560-1.sql

1 Locate the script NORAv560-1.sql.

2 Find and replace the bracketed variables with the appropriate values from the

database pages of the Pre-Installation Checklist completed by the customer:

• Replace [DATABASENAME] with the name of the database.

• Replace [SYSTEMPWD] with the password of the Oracle user SYSTEM.

• Replace [SPOOLPT] with the directory for the Session Log.

• Replace [MOUNTPT] with the directory path for the datafile. If possible,

spread MOUNTPT over multiple disks.

Notes:

• Oracle 7.x and Oracle 8.x are not supported

• We recommend the use of locally managed tablespaces and, if running Oracle

10g or 11g, Automatic Segment Space Management as included in the script.

• You must have Automatic Undo Management enabled on your database

• Auto-extensibility is enabled by default in this script. The Database

Administrator may choose to alter the Tablespace create statements to disable

Auto-extensibility.

NORAv560-2.sql

1 Locate the script NORAv560-2.sql .

2 Find and replace the bracketed variables with the appropriate values.

Replace [DATABASENAME] with the name of the database.


15/74

Stat 5.6.0 7

Install Notes

Replace [SPOOLPT] with the directory for the Session Log.

NORAv560-3.sql

1 Locate the script NORAv560-3.sql .


Replace [DATABASENAME] with the name of database.

Replace [SPOOLPT] with the directory for the Session Log.

Execute the Scripts

The Stat database scripts are run via Oracle SQL*Plus (or Toad for Oracle).

1 For SQL Plus, at the prompt, type: @ \

then press “Enter.”

2 Execute NORAv560-1.sql



5 For PeopleSoft users only, execute the appropriate archive table create scripts as

documented below.

6 Review the database logs and validate that the scripts ran without error.

7 Recompile invalid PL/SQL modules in the database by running the script, utlrp.sql located in the /rdms/admin directory.

Execute Required PeopleSoft Scripts (PeopleSoft Only)

For PeopleSoft users only, execute the appropriate archive table create script (shown

below) for the PeopleSoft releases at this site. Modify the bracketed variables in a

similar manner to the prior mandatory scripts.

Script PS 7 and 7.5 PS 8 and higher,Unicode and Non-Unicode

NORAv560ps7x.sql X

NORAv560ps8x.sql X


16/74

8 Stat 5.6.0

Install Notes

Enabling MercOAEvent System Job (Oracle E-Business Suite Only)

To enable event logs to be sent to the Stat Oracle Agent, execute the script,

NORAv560oa.sql , located in the \Scripts\Oracle\Install directory.

Oracle Object Compare Support: Stat Database (Oracle E-Business SuiteOnly)

If you are running Oracle E-Business Suite and plan to use the object compare feature

for developer objects (form, form libraries and reports) in patches, the Oracle JVM must

be installed with your Stat Repository. Refer to the Oracle Metalink document

appropriate for the Oracle release of your Stat Repository:

• Oracle Note: 202914.1 (9.0.1.x)

• Oracle Note: 209870.1 (9.2.0.x)

• Oracle Note: 276554.1 (10g)

• Oracle Note: 457279.1 (11g)

After installing the Oracle JVM, you need to install the stat_db.jar file, located in the

directory, \Scripts\Oracle\JSP . To do this, execute the following

command, adding the appropriate connection parameters:

$>loadjava –user [username]/[password]@[database] –force –resolvestat_db.jar

After loading the Java classes, you need to recompile invalid PL/SQL modules in the

database by running the script, utlrp.sql located in the /rdms/admin

directory.

Note Each Stat client that will use the object compare feature for developer objects must beproperly configured. For more information, see the section, “Oracle Developer Object

Compare Support: Stat Client” on page 19. Also, for users that plan to compare form library

files that have attached libraries, there are special configuration steps that must beperformed. For more information, see the section, “Object Compare Support for Form

Library Files” on page 64.

Running Stat with Multiple Oracle Versions

If you have more than one version of Oracle installed on the same machine, Stat

connects by default to the client that is defined by ORACLE_HOME.


17/74

Stat 5.6.0 9

Install Notes

However, you may select an alternative Oracle client by creating a batch file, for

example:

set path=D:\oracle\non_default_oracle_client\BIN;%path%

start stat.exe

This configures Stat to connect to the non-default Oracle client and allows other

applications to connect to the version that is defined by ORACLE_HOME, even if that

version is not supported by Stat, such as Oracle 8.

Stat on MS SQL Server (2005 or 2008)

1 Locate the necessary scripts.

MSS SQL Server install scripts are located in \Scripts\

MSSSQLServer\Install . The following scripts need to be run to create the Stat

database regardless of your change management module:

• NMSSv560-1.sql

• NMSSv560-2.sql

• NMSSv560-3.sql

These scripts are designed to run on either MS SQL Server 2005 or 2008. See the

comments in each script for a complete description of its purpose.

2 Check the MS SQL Server setting (see below).3 Execute the appropriate scripts for your development environment using SQL

Query Analyzer only (Do not use third-party tools).

Caution Each script should be run one-time only.

MS SQL Server Settings

These scripts are designed to run on either MS SQL Server 2005 or 2008.

Each script is divided into functions with a summary at the beginning of each individual

script. To quickly go to the function in the script, do a find on Function xx where xx is

the function number of interest.

Verify that the server is installed with BINARY collation.

Each new Stat database will require the tempdb to increase data by 75 MB and log by 25

MB (this is coded into the script by modifying the FILEGROWTH parameters).


18/74

10 Stat 5.6.0

Install Notes

NMSSv560-1.sql

1 Locate the NMSSv560-1.sql script.


• Replace [DATABASENAME] with the name of the database (the name used

on the system that connects to the database).

• Replace [DBdirectory] with the entire path information for the database

(Example: ‘D:\Mssql\data’).

• Replace [LOGdirectory] with the entire path information for the log

(Example: ‘E:\Mssql\log’)

Note If the Stat database is being installed on MS SQL Server and the script syntax is checkedbefore running script #1 (before the database is created), error messages will appear that

can be ignored. This is because the database is being created in the same script as the

“USE [DATABASENAME]” statements.

NMSSv560-2.sql



Replace [DATABASENAME] with the name of the database (the name used on

the system that connects to the database).

NMSSv560-3.sql



Replace [DATABASENAME] with the name of the database (the name used on

the system that connects to the database).

Execute the Scripts

1 Using SQL Server Management Studio or Toad for SQL Server, load and execute

the scripts in order.

2 Copy the output of the script results to a file and save the file for review.

3 Execute NMSSv560-1.sql




19/74

Stat 5.6.0 11

Install Notes

6 For PeopleSoft users only, execute the appropriate archive table create scripts as

documented below.

7 Review and save the script output to validate that the scripts ran without error.

Execute Required PeopleSoft Scripts (PeopleSoft Only)

If running PeopleSoft, execute the appropriate archive table create script (shown below)

for the PeopleSoft releases at this site. Modify the bracketed variables in a similar

manner to the prior mandatory scripts.

Creating a Staging Database (PeopleSoft Only)

Staging databases are used when migrating archive sets from your Stat database to a

PeopleSoft database. A staging database is essentially a mini-PeopleSoft database with

no application data and minimal tools data. Once created it should be maintained and

tuned the same as other PeopleSoft databases in your environment.

Depending on the volume of objects moved or number of PeopleSoft tools versions you

are supporting, you may decide to have multiple staging databases. This section

describes how to create a staging database in Stat.

• For PS version 7.x – The staging database needs to be a PeopleSoft Application

Update (AUD) database. This requires you to run the AUD DataMover script

when creating the PeopleSoft database (e.g. AUSYSORA.dms if your platform isOracle).

• For PS version 8.x and higher – The staging database can either be a PeopleSoft

demo (DEMO) or system (SYS) database. For detailed instructions on creating

this database, please see your PeopleSoft Installation and Administration Guide.

Financial databases in particular have a large number of tables used for sorting

data. These can be dropped from the staging database.

Once you have created your AUD, Demo, or System database, execute the appropriate

script

Script PS 7 and 7.5 PS 8 and higher,Unicode and Non-Unicode

NMSSv560ps7x.sql X

NMSSv560ps8x.sql X


20/74

12 Stat 5.6.0

Install Notes

• If running on Oracle, execute NStageORAv560.sql

• If running on MS SQL Server, execute NStageMSSv560.sql

• If running on DB2 execute NStageDB2-OS390v560.sql (for mainframe), or

NStageDB2-UNIXv560.sql (for Aix/Unix)

• If running on Sybase, execute NStageSYBv560.sql

These scripts complete the creation of a staging database. It is recommended that you

create at least 2 staging databases. You may need to alter this script to match your platform.

It is necessary to alter an existing table after running PeopleSoft staging database scripts

if the database is PS v7 or v7.5. See comments in the scripts for further information.

Note Be aware of the following:

• For each staging database you define in Stat, make sure the Reload Last Project at

Startup option is deselected for that database in PeopleSoft App Designer. Stat mayhave difficulty auto-migrating objects from the staging database if this option is selected.

• When migrating archive sets, the base language of the staging database must be the

same as the base language of the environment that the archive set came from (i.e., the

source). The base language option is specified in the PeopleSoft Environment

Connection Maintenance table. For more information, see Stat 5.6.0: System

Administration, Chapter 4, ”General Maintenance Tables.”

PeopleSoft on Oracle

1 Locate the NStageORAv560.sql script.

2 Replace the following variables:

• [OWNER/PWD@DATABASENAME] Replace with the correct values for

the PeopleSoft schema owner/password and staging database.• [SPOOLPT] Replace with the directory for the session log.

• [PTAPP] Replace with the tablespace for the staging table

• [PSINDEX] Replace with the tablespace for the staging table indexes

• [VIEWTEXT] If you are running PeopleSoft version 7.x please

UNCOMMENT the command ALTER TABLE PSVIEWTEXT MODIFY

(VIEWTEXT NULL)

3 Run the modified script via Sql*Plusor Toad in the PeopleSoft staging database as

the PeopleSoft schema owner


21/74

Stat 5.6.0 13

Install Notes

PeopleSoft on Sybase1 Locate the NStageSYBv560.sql script.

2 Replace the following variables:

• [DATABASE] Replace with the database name

• [VIEWTEXT] If you are running PeopleSoft version 7.x please

UNCOMMENT the command ALTER TABLE PSVIEWTEXT MODIFY

(VIEWTEXT NULL)3 Run the modified script in the PeopleSoft staging database as the PeopleSoft

schema owner

PeopleSoft on MS SQL Server

1 Locate the NStageMSSv560.sql script.

2 Find and replace the variable [DATABASENAME] with the name of the

database.

3 Using Enterprise Manager, go into SQL Server Analyzer from Tools on the menu

bar. Log in as sa with SYSTEM-level access and open the modified scripts. After

running each script, copy the output of the script results to a file and save the file

for review.

PeopleSoft on DB2

Execute the script corresponding to your DB2 platform.

Mainframe

1 Locate the NStageDB2-OS390v560.sql script.2 Find and replace the following variables:

• [DATABASENAME] Replace with the name of the database (the name used

on the system that connects to the database)

• [USERID] Replace with the correct user access id. Must be a valid RACF id.

• [PASSWORD] Replace with the correct access password

• [TABLETBSPC1] Replace with tablespace for the new table. Usually use anexisting tablespace, so DB2 utilities (that run at the tablespace level) do not

have to be modified for the new tablespace (example: image copy).


22/74

14 Stat 5.6.0

Install Notes

• [TABLETBSPC2] Replace with tablespace for the existing table. Usually

currently defined in tablespace PSIMAGE (only used for PS versions prior to8).

• [CREATORID] Replace with the creator/owner id. Requires the [USERID]

to be able to set current sqlid to this [CREATORID] secondary authorization

RACF group. Would need to connect [USERID] to the RACF group

[CREATORID].

• [STOGRPNAME] Replace with the Stogroup name for the index. Requires

the grant “GRANT USE OF STOGROUP [STOGRPNAME] TO

[CREATORID]”

• [PEOPLESOFTID] Replace with PeopleSoft login id

Aix/Unix

1 Locate the NStageDB2-UNIXv560.sql script.

2 Find and replace the following variables:

• [DATABASENAME] Replace with the name of the database

• [USERID] Replace with the correct user access id

• [PASSWORD] Replace with the correct access password

• [TABLETBSPC] Replace with tablespace for the table

• [CREATORID] Replace with the creator/owner ID of the tables

• [PEOPLESOFTID] Replace with PeopleSoft login ID

Installing the Stat Client

Before installing the Stat client, please note if installing on Windows XP, Vista, or 7 the

user performing the installation or de-installation needs to be logged in as an“Administrator” locally on that server/workstation due to enhanced security on

Windows XP/Vista/7.

Local Installation

1 Unpack the Stat Installer.

See “Unpacking the 5.6.0 Installer” on page 4.


23/74

Stat 5.6.0 15

Install Notes

2 Click Install Stat Windows Client.

Note Users installing on Vista/7 may receive security warnings stating that the softwarepublisher cannot be identified or verified. These warnings can be disregarded.

This launches the InstallShield Wizard for Stat 5.6.0.


24/74

16 Stat 5.6.0

Install Notes

3 Click Next>.

4 Read the license agreement and select the I accept checkbox.

5 Click Next>.

6 Specify where you want to install the application.

You can keep the default location (C:\Program Files\Quest Software\Stat 5.6 ), or

if you want to install to a different location. click Change... and specify the

location you want. When finished click Next. The Setup Type window appears.

Note FDCC regulations stipulate that only administrators be allowed to write to theProgram Files folder. For this reason, the Stat installer creates an additionaldocuments folder. On Windows XP, this is C:\Documents and Settings\All

Users\Application Data\Quest Software\Stat\5.6.0. On Windows 7 and 2008, this is

C:\ProgramData\Quest Software\Stat\5.6.0 . This is also where the user-editable file

stat.ini is installed, as well as the dictionary files userdic.tlx and correct.tlx .

7 Click Next.

The Setup Type window appears

8 Select the type of installation you want.


25/74

Stat 5.6.0 17

Install Notes

Options include Complete or Custom. Complete installs all of the Stat

application components. Custom allows you to choose from a list of optionalcomponents the ones you want to install. Complete is recommended for the

initial installation. Custom is recommended on individual workstations where

certain components might not be needed.

9 Click Next.

If you selected Custom, the next window has the User’s Guide pre-selected.

The following components are deselected by default in a custom installation:

• Network Installation (network installations only) – This option creates thefolder under the Stat install directory that contains the setup program users

must run for their workstations to connect to a network installation. For more

information, see the section, “Network Installation” on page 19.

• System Administrators Guide – If the user should have access to the System

Administration Guide, select this option.

• Change Management Guides – Depending on the change management

module you plan to use, select the corresponding change management guide.

• PS ObjectMover Instructions ( PeopleSoft users only) – The PS

ObjectMover instructions must be selected on at least one workstation in order

18 St t 5 6 0


26/74

18 Stat 5.6.0

Install Notes

to update the Stat object that archives PeopleSoft objects. These instructions

are required in order for this object to operate. The instructions are loadedusing the Update PS Object Mover utility available under the General

Maintenance menu. Deselect on workstations where the user will not have the

security to run these instructions.

10 If performing a custom installation, select or deselect components, depending on

the type of install you want. Then click Continue.

11 In the next window, do one of the following:• Click Next to install the Stat shortcuts in the default Start menu folder, Quest

Software\Stat 5.6 .

• Modify the folder name and click Next to install the shortcuts in a different

Start menu folder.

12 In the next window, click Install to begin the installation.

13 When prompted, click Finish to complete the installation.

Stat 5 6 0 19


27/74

Stat 5.6.0 19

Install Notes

Network Installation

Stat can be installed in one primary network location that users can access remotely.

Remote users must install certain files on their individual workstations to run Stat from

the primary location.

Note Both the network installation of Stat and the installation of files on the workstations ofremote users must be performed by an administrator.

To install Stat on a network, run the Stat client install program at the designated network

location and select either the Complete installation option, or select the Custom install

option with the Network Installation component.

After the Stat client has been installed on the primary network location (referred to as

), do the following on the workstation of each remote user:

1 Map a drive to the primary location of Stat.

2 Navigate to /netinstall on the primary location.

3 Run Setup.exe.

Required third party OCX files are loaded to the user's workstation with a

shortcut to Stat on the primary location.

The stat.ini file and spelling dictionaries are loaded to individual user's

workstations:• For Windows XP - C:\Documents and Settings\All Users\Application

Data\Quest Software\Stat\5.x.x (where 5.x.x is the version being installed)

• For Windows Vista and higher - C:\Program Data\Quest Software\Stat\5.x.x.

A blank stat.ini is loaded to this location, or, if Stat was previously installed on a

lower version, a copy of that stat.ini is moved here.

Oracle Developer Object Compare Support: Stat Client

If you plan to use the object compare feature for Oracle developer objects (form, form

libraries and reports), it is necessary to install Oracle Developer.

The CLASSPATH for the Stat client must include one of the following directories to

compare forms and form libraries:

• For Oracle E-Business Suite 11i: $ORACLE_HOME/forms60/java/f60jdapi.jar

• For Oracle E-Business Suite R12: $ORACLE_HOME/forms/java/frmjdapi.jar

20 Stat 5 6 0


28/74

20 Stat 5.6.0

Install Notes

The PATH must include $ORACLE_HOME/bin to compare reports. The version of

Oracle Developer should be compatible with the version of objects being compared. Forexample, with Oracle E-Business Suite, Oracle Developer 6i should be used with at

least patchset 15. Please note that the Forms Applet Jar Files component of the Oracle

Forms product must be installed. This component is not included with the “typical”

installation.

Note In addition to configuring the Stat client, Oracle E-Business Suite users must set up the Stat

Database to support the compare feature for developer objects in patches. For moreinformation, see the section, “Oracle Object Compare Support: Stat Database (Oracle E-

Business Suite Only)” on page 8. Also, for users that plan to compare form library files that

have attached libraries, there are special configuration steps that must be performed. For

more information, see the section, “Object Compare Support for Form Library Files” on

page 64.

Configuring the Stat Database

The new Stat database needs to be configured with basic data before the installation can

be verified. For the purposes of an installation, Stat database configuration includes

adding the new databases to the Stat INI file and updating the System table with client

specific information including the license code.

Edit the INI File

The INI Editor displays all the database profile records contained in the Stat.ini file. For

more detailed instructions, see the book, Stat 5.6.0: System Administration, Chapter 2,

“Administrative Utilities.”

To edit the Stat INI file:

1 Run the Ini Editor from the Startup menu or your Desktop.

2 To add a new profile, select Edit | New Record. In the Add New Profile window,

enter a name for the new database then click OK . The Editor adds a new database

profile to the record sheet.

3 Specify remaining values as needed.

Stat 5 6 0 21


29/74

Stat 5.6.0 21

Install Notes

Update the System Table

The System table defines global operating parameters for your installed copy of Stat.

For more information, see the book, Stat 5.6.0: System Administration, Chapter 4,

“General Maintenance Tables.”

1 Login into the Stat application using the Stat SYSTEM user and no password.

2 When prompted enter a password that is easily remembered.

This SYSTEM account is critical to getting into the application until other usersare defined. It is suggested that you use “system” as the password until additional

administrative users have been defined later in the installation. At that time a

more secure password can be defined.

Full access to Stat 5.6.0 requires a license key. Until the license key is entered,

you can only access the System Maintenance window in the client application.

3 Select Maintenance | General | System Maintenance.

4 In the General tab, enter the site name, address, phone number, etc.

5 In the License tab, do the following to enter the Stat license key:

a Enter the License Key and Site Message.

b Test the key by clicking Verify.

A valid key will include the following License Properties:

• The type of license. Options include Commercial (permanent), Trial

(temporary) and Term (a temporary enhancement of licensing rights for

commercial users

• Number of Technical Licenses

• Number of Functional Licenses

• Licensed Modules - a check mark denotes the module is licensed; an X

indicates the module is not licensed.6 (Optional) Change the default Country on the Other Options tab.

The default is USA.

7 When finished, click OK and exit the Stat application.

22 Stat 5.6.0


30/74

Install Notes

Installing the Stat Central AgentThe Stat Central Agent is a Java-based application that contains the business logic for

Stat and the UI for Stat Web client.

The following instructions apply to both Windows and Unix platforms. Be sure to adjust

your path and environment settings to suit your platform. After installation, the startup

may report errors. These are often caused by port conflicts. To resolve such conflicts,

see the subsections below, “Resolving Port Conflicts.”Before you install the Stat Central Agent, you may want to log in to the Stat client and

perform certain configuration tasks, such as setting up service domains, defining users,

and establishing connections between Stat and your native application environments

and ftp file servers. It is not necessary that you configure Stat before installing the Stat

Central Agent, but if installing on Windows, this will allow you to test connectivity

parameters. For PeopleSoft users running on any platform except DB2, this entails

specifying the appropriate values in the Host Name, DB Listener Port, and (if runningPeopleSoft on Oracle) Service Name fields in the PeopleSoft Environment Connection

Maintenance table. For more information, see the section “Implementing Stat” on

page 65 and the book, Stat 5.6.0: System Administration, Chapter 4, “General

Maintenance Tables.”

Note If you are running PeopleSoft on a DB2 platform, see the section, “Installing DB2 Supportfor the Stat Central Agent” on page 36 for additional information.

Installing the Stat Central Agent on the Standalone Platform

Stat provides a platform on which you can install the Stat Central Agent, referred to as

the standalone platform.

To install the Stat Central Agent:

You should already have a Java 2, Standard Edition, Java Development Kit (aka Java

SDK) v1.5.x or 1.6 (1.60_5 and higher) installed and a system variable called

“JAVA_HOME” that points to the JDK installation root directory (e.g., “C:\j2sdk1.5”).

Caution If running on a 64-bit environment, make sure the JDK installation root directory does notinclude spaces. The Stat Central Agent cannot run if it does.

Stat 5.6.0 23


31/74

Install Notes

1 If Java is not installed and you are running Windows or Solaris, go to http://

www.oracle.com/technetwork/java/javase/downloads/index.html and downloadan appropriate version of Java SDK. If running HPUX, go to http://www.hp.com/

go/java/.

2 Insert the Stat CD.

The Stat Autorun program launches automatically.

3 Click Install Stat Central Agent.

Autorun opens the stat_server folder, which contains the subfolder, standalone.

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

5 Create a system environment variable called STAT_HOME with a value of

from the above step.

Note Do not add a backslash character (\) to the end of the STAT_HOME variable.

To run the Stat Central Agent as a Windows Service instead, see “Configuring the

Stat Central Agent as a Windows Service” on page 35. We recommend that you

first configure and test the agent before creating the service.

6 Preview and implement any configuration changes required by your enviornment.

These issues are documented in the section “Configuring the Stat Central Agent

on the Standalone Platform” on page 28. Note that while you can address someconfiguration issues after you have completed installing the Stat Central Agent,

you should address others before you proceed to the next step in the installation.

These particular issues are documented in the subsection “Before Starting the Stat

Central Agent”.

7 Start the Stat Central Agent:

Windows:

\app\bin\run.bat

24 Stat 5.6.0

I t ll N t

http://java.sun.com/http://www.hp.com/go/java/http://www.hp.com/go/java/http://www.hp.com/go/java/http://www.hp.com/go/java/http://www.oracle.com/technetwork/java/javase/downloads/index.htmlhttp://www.oracle.com/technetwork/java/javase/downloads/index.htmlhttp://java.sun.com/javase/downloads/index_jdk5.jsphttp://java.sun.com/


32/74

Install Notes

Unix:

/app/bin/run.sh

Note If you have port conflicts during startup, the server will display one or more errormessages. For instructions on resolving port conflicts, see the section, “Resolving

Port and Firewall Conflicts” on page 31.

8 Wait for the Stat Central Agent startup process to complete

In the server console, you will see the line, “Stat Configuration Assistant is

ready”.

9 Open your internet browser and go to http://:8080/

stat-config.

This opens the Configuration Assistant which guides you through the process of

configuring the Stat database and the database type-mapping.

Caution If you are not running the agent from the local machine (i.e. “Telnet” session), youmust add the IP address to /config/stat-config.properties or you

will not have access to the Configuration Assistant. See the section “Authorize Access to the Configuration Page” on page 29.

Stat 5.6.0 25

Install Notes


33/74

Install Notes

10 In the Type/Vendor field, select the database platform you are using.

Options include Oracle or SQL Server.

11 Enter appropriate info for the Stat database: Host Name, Port, Service Name,

Login ID, Password.

12 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 is inactive for Oracle users.

13 Choose desired logging setting for the UI and for the Stat Central Agent

application.

26 Stat 5.6.0

Install Notes


34/74

Install Notes

The default is INFO.

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

15 Click Save.

Stat verifies that the Stat database parameters you entered are correct.

The next step is the last step in the installation procedure and applies only to users

installing the Stat Central Agent on Oracle RAC environments. All other users

have at this point completed the installation of the Stat Central Agent.

16 For users installing the Stat Central Agent on Oracle RAC environments, do the

following to edit the file stat-ds.xml located in /app/server/

default/deploy:

a If you haven’t already done so, stop the Stat Central Agent.

b Open /app/server/default/deploy/stat-ds.xml .

The beginning of the file will look like this but with your database

information:

StatDataSource

jdbc:oracle:thin:@//alvsupl04v.quest.com:1521/st560

oracle.jdbc.driver.OracleDriver

EncryptedDBPassword

Stat 5.6.0 27

Install Notes


35/74

Install Notes

SELECT STAT_DB_VERSION FROM SYSTEM_TBL

Stat-Agent

2

50

Oracle9i

c Edit this line only:

jdbc:oracle:thin:@//alvsupl04v.quest.com:1521/st560

d Starting from the @ symbol, paste the TNS entry without carriage returns or

line feeds.

It will look something like this:

jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL =

TCP)(HOST = alvsupl04v.quest.com)(PORT = 1521))(ADDRESS = (PROTOCOL =TCP)(HOST = Alvsupl11v.quest.com)(PORT = 1521))(LOAD_BALANCE =

no)(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = st560)))

In context, the file will look like this:

StatDataSource

jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL

= TCP)(HOST = alvsupl04v.quest.com)(PORT = 1521))(ADDRESS = (PROTOCOL =

TCP)(HOST = Alvsupl11v.quest.com)(PORT = 1521))(LOAD_BALANCE =

no)(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = st542)))

oracle.jdbc.driver.OracleDriver

28 Stat 5.6.0

Install Notes


36/74

Install Notes

EncryptedDBPassword

SELECT STAT_DB_VERSION FROM SYSTEM_TBL

Stat-Agent

2

50

Oracle9i

e Save and close the file.

Configuring the Stat Central Agent on the Standalone Platform

Refer to the following sections for information on the number of ways you can

configure the Stat Central Agent on the standalone platform:

• “Before Starting the Stat Central Agent” on page 29

• “Configuring the Stat Central Agent as a Windows Service” on page 35• “Installing DB2 Support for the Stat Central Agent” on page 36

• “Setting up Support for AES256 Ciphers for SFTP” on page 37

• “Connection Pool Idle Time” on page 39

• “Installing Multiple Servers on the Same Host Machine” on page 39

Caution Before making any configuration changes, be aware of the following:

• Modifications should not be made to either run.sh or run.bat . Instead, if

customizations are needed (such as hard coding the location of JAVA_HOME or

), 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 35 for more information. Quest recommends that

you validate that the agent will start without the service before invoking the service

operation.

Stat 5.6.0 29

Install Notes


37/74

Before Starting the Stat Central Agent

The following are configuration issues you may need to address while installing the Stat

Central Agent but before starting it for the first time. After reviewing and addressing

these issues, you can resume the installation as documented in the section “Installing the

Stat Central Agent on the Standalone Platform” on page 22.

Authorize Access to the Configuration Page

To authorize access to the configuration page, you as a Stat administrator need to edit

the stat-config.properties file in /config . The privilege to modify theconfiguration is administered using the computer's IP address. You can grant user

permission to change the configuration by adding its computer's IP address to the list of

the property auth.user.ip (IPV4 and IPV6 formats are supported). For example, you can

grant user John the permission by appending his computer's IP address (e.g.

192.168.244.130) to the list. You can add multiple IPs to the list and use a comma to

separate them. After you complete editing stat-config.properties file, change its

permission so no other users can view or edit it.

Table or View Does Not Exist Error

Generic applications and Oracle E-Business Suite users may see a “table or view does

not exist” error message in the Stat Central Agent log file after migrating a data object.

This error is due to a query against a test table which is normally present in PeopleSoft

installations, and while it does not affect the migration, to avoid receiving this message,

open the stat.properties file in /config and locate the following

variable, TestTableName=PSOBJGROUP. Set this variable to the name of a table in the

database you are working in, for example, TestTableName=OW_CUSTOMERS.

Change the Default Timeout Setting

The default timeout setting for connections between the Stat Central Agent and your

environments is 15 minutes. If you want to increase or decease the time amount, open

the stat.properties file, locate the variable “CONNECTION_IDLE_TIME=15”, and change the

setting to the number of minutes you want. For more information, see the section,“Connection Pool Idle Time” on page 39.

Adjust the Default Max_thread_proc Setting

If you have installed the Stat Central Agent on a HPUX machine, you may need to

adjust the default max_thread_proc setting to allow for Java processing. For more

information, go to: http://www.hp.com/go/java/ or search HP’s online documentation

for ‘max_thread_proc’.

30 Stat 5.6.0

Install Notes

http://www.hp.com/go/java/http://www.hp.com/go/java/


38/74

Display Graphical Objects

If you have installed the Stat Central Agent on Unix, you may experience problems

displaying graphical objects (such as workflow diagrams and reports) in the Stat Web

client. These errors are generated because the graphics libraries installed with the Stat

Central Agent on Unix are implemented using XWindows/Motif graphics libraries,

which require access to an X server. To resolve this issue, you need to download and

install the X Virtual Frame Buffer (Xvfb), a free virtual server that provides the same

graphical resources as a X11 Windows Server. Installing the Xvfb is platform-specific.

For more information, please contact Quest Support.

Keep the Telnet Session Open

If the Stat Central Agent was started on Unix with telnet, closing the telnet session may

cause the Stat Central Agent to shutdown. To keep the Stat Central Agent running after

closing Telnet, go to /app/bin and execute the following command to

run the process in the background:

nohup run.sh &

JAVA_OPTS Environment Variable Error

If your environment already has a JAVA_OPTS environment variable defined, it may be

incompatible with Stat, in which case you will receive the following error message

when starting the Stat Central Agent:

=1.0 was unexpected at this time.

To resolve this issue you need to edit the Stat.conf.bat file.

1 Open /app/bin/run.conf.bat .

Locate this section:

if "x%JAVA_OPTS%" == "x-Xrs" goto JAVA_OPTS_SET_RS

if not "x%JAVA_OPTS%" == "x" goto JAVA_OPTS_SET

:JAVA_OPTS_SET_RS2 Insert this statement above the specified section:

set JAVA_OPTS=

Your file will now look like this:

set JAVA_OPTS=

if "x%JAVA_OPTS%" == "x-Xrs" goto JAVA_OPTS_SET_RS

if not "x%JAVA_OPTS%" == "x" goto JAVA_OPTS_SET :JAVA_OPTS_SET_RS

3 Save run.conf.bat .

Stat 5.6.0 31

Install Notes


39/74

Resolving Port and Firewall Conflicts

If the Stat Central Agent will not run when started, typically this is because either the

port assigned to it is already in use by a different program or there are firewalls that

need to have ports opened for the Stat Client to communicate with the database or with

the Stat Central Agent.

Note If you modified the Stat Central Agent port settings in a previous version of Stat, you need tore-apply those changes. Starring with Stat 5.6.0, Stat Central Agent port settings are stored

in the following location:\Stat560agent\app\server\default\conf\bindingservice.beans\META-

INF\bindings-jboss-beans.xml. This is not the same location as previous versions of Stat.

Typical port and firewall conflicts include:

• Other applications are using the same port as the Stat Central Agent

• You are running multiple Stat Central Agents on the same host machine and the

installations are trying to access the same ports

• The default timeout setting on a firewall prevents the Stat Central Agent from

opening properly

• (For Oracle E-Business Suite users only) The JBoss Messaging service is opening

a random port each time the Stat Central Agent is started, creating port conflicts

If you have port conflicts, the server will display one or more error messages, such as:

Depends On Me: java.net.BindException: Address already in use: JVM_Bind]

The Stat Central Agent utilizes a set of ports as defined by the value in

/app/server/default/conf/bindingservice.beans/META-INF/bindings-

jboss-beans.xml . These values include:

1 ports-default

2 ports-01

3 ports-02

4 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

“ports–01”, 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

32 Stat 5.6.0

Install Notes


40/74

fourth, or “ports–02” 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.

Note For Oracle E-Business Suite users, communication between the Stat Central Agent and theStat Oracle Agents is conducted through JBoss Messaging. This may lead to port conflicts

on the 4457 series of ports (4457,4557, 4657, 4757). See “JBoss Messaging Ports” below

for more information.

Port Configurations

ports-default ports-01 ports-02 ports-03

1098 1198 1298 1398

1099 1199 1299 1399

1100 1200 1300 14001162 1262 1362 1462

1701 1801 1901 2001

3528 3628 3728 3828

3873 3973 4073 4173

4444 4544 4644 4744

4445 4545 4645 4745

4457 (see note) 4557 (see note) 4657 (see note) 4757 (see note)

8080 8180 8280 8380

8083 8183 8283 8383

8089 8189 8289 8389

8090 8190 8290 8390

8092 8192 8292 8392

8093 8193 8293 8393

19001 19101 19201 19301

Stat 5.6.0 33

Install Notes


41/74

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 \app\server\default\conf\bindingservice.beans\META-

INF\bindings-jboss-beans.xml with notepad or other text editor.

3 Search for the setting,

${jboss.service.binding.set:ports-default}

${jboss.service.binding.set:ports-default}

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 thedirectory when you are finished. Do not rename the old copy and leave it in that directory.

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:

1 Open the file /server/default/deploy/messaging.sar/remoting-

bisocket-service.xml .

2 Select the following code:1

214748364

10

…

0

34 Stat 5.6.0

Install Notes


42/74

3 Replace it with the following:

5

1200000

2

…

1800000

false

4 Open /server/default/deploy/messaging.sar/connection-

factories-service.xml .

5 Uncomment all occurrences of DisableRemotingChecks.

Look for the three occurrences of:

And change them to:

true

JBoss Messaging Ports

Stat uses JBoss Messaging to communicate between the Stat Central Agent and the Stat

Oracle Agents.

Communication between the Stat Client and Stat Central Agent for test connecting and

reporting is done through EBJ3 messages on port 3873. All customers need 3873 open.

Only Oracle E-Business customers need to be concerned with the 4457 series of ports

(4457,4557, 4657, 4857).

JBoss messaging is done over port 4457 (ports-default). JBoss also creates one

additional random “anonymous” port which will be different every time the agent is

Stat 5.6.0 35

Install Notes


43/74

started. JBoss uses anything in the range between 1001 and 65000+ for this random

port.

The anonymous port will cause issues for customers with firewalls. But it is possible to

designate a fixed port.

1 Open the file \app\server\default\deploy\messaging\remoting-

bisocket-service.xml.

2 Find the following segment near the bottom of the file:

This segment is commented out as designated by the arrows .

3 Designate a specific port number to expose the secondaryBindPort.

If designating port 12345, for example, your modified segment should look like

this:

12345

Note If your site has more than one Stat Central Agent running on the same server, when youchange from ports-default to ports-01/02/03 for the second server, you should designate a

different secondaryBindPort for the second server.

Configuring the Stat Central Agent as a Windows ServiceOptionally, you can run the Stat Central Agent as a Windows service using the wrapper

that is provided with Stat. This is done using the service.bat shell command located in

the /app/bin folder.

If you previously used Wrapper.conf and other associated files to run the Stat Central

Agent functionality of the Stat Central Agent as a Windows service, you must replace

them with the wrapper that is provided with the Stat standalone agent. This is done

using the service.bat shell command located in the /app/bin folder.

To configure the Stat Central Agent as a Windows service:

36 Stat 5.6.0

Install Notes


44/74

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

Note This was optional before, but is now required for running the Stat Central Agent as aservice.

2 (Optional) In /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: \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 both the Windows service applet or the service.bat command to

start the service.

5 To start JBoss AS service, run \app\bin>service start

JBAS50SVC.

This creates a run.log file in \app\bin (replaces wrapper.log) and

also creates a lock file called .r.lock in the bin directory which is removed whenservice is stopped.

Note The run.log file is persistent. You should monitor the size of this file while running asa service.

To modify the service.bat file, you need to stop the service, uninstall it, make the

changes you want, and then reinstall the service.

• To stop the service, run “service stop JBAS50SVC”• To remove the service, run “service uninstall”

Installing DB2 Support for the Stat Central Agent

To connect with PeopleSoft databases running on DB2, the system running the Agent

must already have the DB2 client-side libraries installed. This setup process installs files

and creates environment settings which allow DB2 client applications to run.

Stat 5.6.0 37

Install Notes


45/74

NoteFor connectivity to DB2 databases on AIX, the Stat Central Agent requires that you install

the 32-bit version of the driver, as opposed to the mixed 32/64-bit driver.

When DB2 connectivity is installed and has been verified for the system which will be

running the Agent, you need to install a library to a location in so the

Stat Central Agent can connect to DB2 and perform object archives and migrations.

The Stat Central Agent must already be installed and otherwise setup in

. The default DB2 installation directory for a Win32 system isC:\Program Files\SQLLIB (referred to as %DB2HOME%). Copy the file

%DB2HOME%\java\db2java.zip to \app\server\default\lib.

For PeopleSoft users running on early versions of DB2, verify that you are running

JDBC2 for DB2, which is required to successfully migrate certain object types such as

Records and Components.

Setting up Support for AES256 Ciphers for SFTPThe 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 .

38 Stat 5.6.0

Install Notes

http://www.oracle.com/technetwork/java/javase/downloads/index.htmlhttp://www.oracle.com/technetwork/java/javase/downloads/index.html


46/74

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 copylocal_policy.jar and US_export_policy.jar .

7 Paste both files into the JAVA_HOME/jre/lib/security folder.

Configure Web Client to Use HTTPS

This functionality is supported for the Standalone platform only.

It is recommended that you first configure the Stat Central Agent without https andvalidate that it can be started and is functional before switching to https.

1 Shut down the agent.

2 Delete /app/server/default/tmp and /app/

server/default/work.

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

4 Once you have the keystore, move it to /app/server/default/conf .

5 Do the following to turn on SSL:

a Go to /app/server/default/deploy/jbossweb.sar/server.xml

and turn on SSL.

b Modify the keystoreFile to match the keystore file name (in the exampleabove, change only the chap8.keystore to the appropriate name. Leave the

directory as is).

c Modify the keystorePass to equal the password written in the keystore.

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 to8443 when logging into the web client:

a Stop the agent

b Move app/server/default/deploy/stat-agent.ear to a location

outside of the folder for backup purposes

c Locate the stat-agent.ear file in stat-agent-https.zip from this distribution

package and copy it into app/server/default/deploy.

7 Restart your agent.

Stat 5.6.0 39

Install Notes


47/74

8 Access the web client as before.

If you input http:servername:8080/stat, you will automatically be directed to thesecure location of https:servername:8443/stat.

Connection Pool Idle Time

This feature allows the site to define the length of time before the Stat Central Agent

connection pool times out database connections. The default is 15 minutes. However,

Java could take up to 2x as long to actually disconnect from the environment.

1 Open /conf/stat.properties.

2 Locate the parameter CONNECTION_IDLE_TIME=15 and modify the time.

3 Stop and restart the agent.

Caution Shorter times could adversely affect agent performance.

Installing Multiple Servers on the Same Host MachineStat currently supports installing up to four Stat Central Agents on the same host

machine (provided there are no port conflicts). Additional Stat Central Agents are

installed basically the same way as the first server, except you will need to install the

additional servers to separate directories, define separate system variables, modify the

startup files, and assign the servers to different port profiles.

If you need to install more than four servers on the same machine, contact Technical

Support.

Note You can install only one Stat Central Agent per Stat Repository.

To install an additional Stat Central Agent on the same machine:

1 Unzip the contents of stat_standalone.zip to a location on the host machine that is

different from the location where the first Stat Central Agent is installed.

This location will be referred to as .

2 Create a environment system variable called STAT_HOME2 with a value of

from the above step.

3 Do one of the following, depending on your platform:

• For Windows, go to \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%" -

40 Stat 5.6.0

Install Notes


48/74

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 /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 \app\server\default\conf\

bindingservice.beans\META-INF and open the file bindings-jboss-beans.xml .

Then locate the line:

${jboss.service.binding.set:default}

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 otherapplications running on the host machine. See “Resolving Port and Firewall

Conflicts” on page 31 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, thedefault 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, , 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, , 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.6.0 41

Install Notes


49/74

InstallingUpgrading the Stat Central Agent on Oracle WebLogic

11gIf you do not want to install the Stat Central Agent on the default, standalone platform,

Stat supports installations on Oracle WebLogic 11g (WebLogic v10.3.3 and higher).

To install the Stat Central Agent on Oracle WebLogic 11g:

1 If you have not already done so, install Oracle WebLogic 11g.

The following configuration settings are recommended:• Select custom installation

• Uncheck WebLogic Workshop

• Uncheck Web Server Plug-ins and Server Examples

• Uncheck Mercury Profiling tools

• Click No for Node Manager Service

The directory where you install Oracle WebLogic 11g will be referred to in thisdocument as . You do not need to set this variable.

2 Create a directory for Stat 5.6.0 in user_projects/domains/ .

For a second Stat Central Agent, against a test repository you may create a new

folder called /user_projects/domains/stat2 (or stat560).

Note If you have port conflicts, see “Resolving Port Conflicts (WebLogic)” on page 44

below.

3 Create a variable named $STAT_HOME and set it to /

user_projects/domains/stat .

4 Create a variable named $STAT_HOME2 and set it to /

user_projects/domains/stat2.

5 On the installation media, go to the \stat_server\weblogic folder and unzip the file

stat_weblogic.zip to /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

so that it references the correct wlserver folder name and

(optionally) a different JDK version.

You will need to modify /user_projects/domains/stat/

startweblogic.cmd (or startweblogic.sh for unix) to point to this

new location or to the variable described in step 4.

6 Edit startWebLogic.cmd as follows:

42 Stat 5.6.0

Install Notes


50/74

a Locate the wlserver_10x folder under and then edit the line

set WL_HOME = %STAT_HOME%\..\..\..wlserver10 so that it specifies the exactfolder name (e.g., wlserver_10.3).

Note WebLogic 10 names its wlserver folder based on the minor release installed.

b (Optional) If you want to use a different 1.5.x or 1.6.0 JDK version, replace

the line JAVA_HOME=..\..\..\jdk150_11 with the path for the new version (e.g.,

JAVA_HOME=C:\j2sdk1.5.0_14).

7 Locate the files wlclient.jar , wljmsclient.jar , and wlthint3client.jar in

/wlserver_10.x/server/lib and copy them to the Stat install folder

on EACH WORKSTATION where Stat is installed.

Note For Oracle Applications only, wlclient.jar , wljmsclient.jar, and one additional file, weblogic.jar , must also be copied to each Oracle Agent. For more information, see

“Installing the Stat Oracle Agent (Oracle E-Business Suite only)” on page 48 .

8 Do one of the following:

• If on Windows, run the script startWebLogic.cmd .• If on Unix, run the script, startweblogic.sh.

The first time you start the WebLogic server, the Stat Connection is not properly

defined; therefore the server will start with errors.

9 Configure Oracle WebLogic 11g as follows:

a Start the WebLogic console from the following url:

http://hostname:8081/console

b Login with the following credentials:

• Username = weblogic

• Password = irv200038stat

c Click Services and then Data Sources on the Domain Structure tree on the left

side of the screen.

d Click StatDataSource on the configuration tab.

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:

Stat 5.