Chat now with support
Chat with Support

Stat 6.0 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Updating Products per Environment

Each Oracle Applications environment you define may feature a different set of Oracle Applications products. In order to utilize Stat’s change management support for proprietary Oracle Applications file objects, as well as apply product-specific Oracle patches to the appropriate environments, you need to specify the products that each environment contains. This is done in the Products tab of the Application Options window.

Except for the Active check box, the Products tab is read-only. It displays a list of all the products contained in the selected environment. When you first define an environment, or when you install new Oracle Applications products to a particular environment, you should update the environment’s product list. To do this, click Update Products. This sends a request to the Stat Oracle Agent, which updates the list with any fully installed, shared, or custom products it finds.

Copying Oracle Applications Environments

If you need to define an Oracle Applications environment that closely resembles an existing Oracle Applications environment, you can save time by copying the definition of the existing environment and editing the copy as needed. When you copy an Oracle Applications environment, all the information gets copied over, including server definitions and approval lists.

Generic Application Connection Maintenance

The GenApps Environment Connection Maintenance table defines the generic (non-PeopleSoft and non-Oracle Applications) application environments connected to Stat. The table closely resembles the connection maintenance tables for PeopleSoft and Oracle Applications, and many of the maintenance procedures are the same. Within the definition for each environment is the information Stat needs to connect to it.

Connection security for generic applications is controlled by the following user class rights:

The GenApps Environment Connection Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | General | Generic Application Connect.


If selected, indicates that this environment is available for selection

Environment Cd
(Key Value)

A 1-10 character code which uniquely identifies the environment

(Required Value)

A 1-35 character description of the environment.

Data Obj Version

The version number of the generic application, as defined in the Data Objects Maintenance table. Select a value in this field only if you plan on using Stat to manage data objects within this environment.

Req. Migr. Approval

If selected, indicates that Archive sets cannot be migrated into the environment without migration approval


Name of the APPS database account holder

Database Name

The name of the environment (database instance). Options include Oracle, Microsoft SQL Server, and N/A.

DB User ID
(SQL Server Only)

The SQL Server user ID for the schema owner. The default is “sysadm.”

DB Password
(SQL Server Only)

The password for the DB User ID

Database Server

The name of the database server housing the generic application repository. Format for this entry is DBMS-specific.

Srv Logon ID

The login ID used for Stat login to the environment. Not used by ODBC.

Server Password

The password associated with the Srv Logon ID

Host Name

Name of the machine hosting the database

Service Name

For generic applications running on Oracle, the listener service of the database. Used by the Stat Central Agent to establish JDBC connections to the Oracle database.

DB Listener Port

Port number for the database listener.

Use Tns

For RAC Oracle databases, configures Stat to invoke TNS

Tns Entry

The full description as it appears in the tnsnames.ora file with no line breaks or carriage returns

Other Database Parameters

Additional environment-specific parameters, if needed

Unicode DB

If selected, indicates the database is Unicode

Last Update
(Read Only)

The date and time this record was last updated

Update By
(Read Only)

The user who last updated this record

Testing Environment Connections

After defining an environment in the maintenance table, you can make sure that you have entered all the information correctly by clicking Test Connection. This makes Stat establish a connection to the newly defined environment. If successful, Stat immediately disconnects from the environment and displays a “Connection Successful” message. If Stat is unable to connect, it displays an error message.

You can also test connections to multiple databases simultaneously. To test multiple connections, hold the <Ctrl> or <Shift> keys and select the databases you want to test. Then click Test Selected. Stat attempts to establish a connection to each database and reports its results in the Database Test Connect window

Note that when you test a single environment, Stat does not validate the values specified in the fields Host Name, Service Name, or DB Listener Port. If any of these fields are not configured properly, the Stat Central Agent will log an error when the user attempts to migrate an object to or from the environment. When you test multiple connections, however, Stat does test both client and agent connections, including Host Name, Service Name, DB Listener Port or (in the case of Oracle-based environments) TNS Entry.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating