Stat 6.1 - Install Notes

Update the System Maintenance table Install the Stat Central Agent

Installing the Stat Central Agent on the standalone platform Configuring the Stat Central Agent on the Standalone Platform

Before starting the Stat Central Agent Resolving port and firewall conflicts Stopping the Stat Central Agent Configuring the Stat Central Agent as a Windows service Installing DB2 Support for the Stat Central Agent Configure the Stat Central Agent character map Setting up support for AES256 Ciphers for SFTP Configure Web Client to use HTTPS Connection pool idle time Installing multiple servers on one host computer

Installing the Stat Central Agent on Oracle WebLogic 11g/12c Configuring the Stat Central Agent on Oracle WebLogic 11g/12c

Configuring the Stat Central Agent as a Windows Service (WebLogic) Installing DB2 Support for the Stat Central Agent (WebLogic) Resolving Port Conflicts (WebLogic) Deleting Data Sources and Connection Pools (WebLogic) Support IMAP via TLS

Testing Database and Server Connections

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

Configuration Administration Dynamically changing log level Stat Oracle Agent version Custom products and file locations Object compare support for form library files Base directory codes Verifying the Stat Oracle Agent

Configure the SYSTEM user account Update the PS Object Mover Instructions (PeopleSoft Only) Implement Stat

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

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. For example, 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 more information, see Oracle Object Compare Support: Stat Database (Oracle E-Business Suite Only). Also, for users who plan to compare form library files that have attached libraries, there are special configuration steps that must be performed. For more information, see Object Compare Support for Form Library Files.

Configure 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. See Edit the INI file.

Edit the INI file

The Stat® INI Editor is a GUI application designed to create new INI files and edit existing ones. The INI Editor displays all the database profile records contained in the Stat.ini file in an easy-to-read format. For more detailed instructions, see the book, Stat 6.1.0: System Administration Guide, Chapter 2, Administrative Utilities.

The Stat.ini file contains the information Stat needs to connect to Stat databases. Stat.ini is located in the Stat version-specific documents folders.

•

The location of the stat.ini file is C:\ProgramData\Quest Software\Stat\6.1.0.

IMPORTANT: The stat.ini file may be hidden depending on the file security settings on your computer.

The Database tab in the INI Editor lists the database(s) to which Stat can connect. From here you can edit an existing INI file entry or create a new one. The INI Editor helps edit a file by asking for the exact information it needs. For example, if the DSN field is not required for a particular database, that field is grayed out.

To create an INI file entry:

Select File | New.

Select Edit | New Record.

Enter the name of the database, and click OK.

The Stat INI Editor adds a new database profile to the record sheet.

In the DBMS field, select a DBMS.

The default is Microsoft® SQL Server®. Depending on the DBMS you select, the STAT INI Editor prompts you to define different values.

Enter the STATLOGIN password in the Encrypted Login Password field, either by entering an encrypted password from another stat.ini file or by clicking Change Password and entering the STATLOGIN password.

In the remaining fields, specify additional parameters as needed.

Select File | Save as, and specify a name for the INI file.

Click Save.

The following table contains general database connection settings for the Stat INI Editor. Each record in the Stat INI Editor represents a database in the INI file. For more general information on available DBMS settings, see any of the Environment Connection Maintenance sections in the book see the book, Stat 6.1.0: System Administration, Chapter 4, General Maintenance Tables.

Table 3. General database connection settings for the Stat INI Editor

Value	Description
DBMS	Database interface identifier. This identifier is DBMS and DBMS release specific.
ServerName (SQL Server)	The name of the database server that houses the Stat Repository.
ServerName (Oracle)	TNS entry name (NET_SERVICE_NAME)
Database (SQL Server)	Database name
LoginId	The login ID used for the Stat first-pass login. Not used by all DBMS. This entry should always be STATLOGIN.
Encrypted Login Password	The encrypted password of STATLOGIN. This value can be changed, as described below.
Connect Time Out Secs	Number of seconds to wait for a connection to the database before timing out. Not supported by all RDBMS.
OtherDbParm	Additional database connection parameters, if needed. For Oracle databases that use a comma rather than a period as a decimal separator, enter the value: DecimalSeparator=','.
Unicode	Type Y if you are running Stat on a Unicode database (in order to support PeopleSoft Unicode databases) and the DBMS is SQL Server. Otherwise leave blank.
Enable DB Trace	Configures Stat to write a trace log of all commands. Selecting this option impacts the client application’s processing speed and should only be selected if directed to by Support.

Update the System Maintenance table

After configuring the Stat® database, the next step is to login to Stat for the first time using the special SYSTEM user account and to update the System Maintenance table. The System Maintenance table is where you define global operating parameters for your installed copy of Stat and verify your license. For more information, see the book, Stat 6.1.0: System Administration Guide, Chapter 4, General Maintenance Tables.

To update the System Maintenance table:

When prompted, enter a password that is easily remembered.

CAUTION: The SYSTEM account is the only way to log into the Stat Client until other users are defined. When prompted for the initial password, enter a password that is easily remembered. A more secure password can be defined later.

Full access to Stat 6.1.0 requires a license key. Until the license key is entered, you can only access the System Maintenance window in the client application.

Select Maintenance | General | System Maintenance.

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

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

Enter the License Key and Site Message.

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

•