Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email for assistance

Stat 6.3 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking 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: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Copying Generic Application Environments

If you need to define a generic application environment that closely resembles an existing generic application environment, you can save time by copying the definition of the existing environment and editing the copy as needed. When you copy a generic application environment, all the information gets copied over, including file locations and migration approval lists.

Schema Object Parameters Maintenance

Oracle and SQL Server database schema objects include a set of predefined true/false parameters that are executed before the definition of the object is captured in Stat. You can change the true/false values of these parameters in the Schema Object Parameters Maintenance table.

The ability to change default schema object parameter values is controlled by the following user class right:

The Schema Object Parameters Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | General | Schema Object Parameters.

The Schema Object Parameters Maintenance table lists each parameter by DDL type and name. The Default Value column indicates whether a particular parameter is true or false by default. To change the value of a parameter, select its corresponding check box in the Param Value column to make it true, or de-select it to make it false. Then click OK or Apply.

Data Object Maintenance

Data objects are user-defined or third party data sets developed for specific application environments. You can configure Stat to support data objects by defining in the Data Object Maintenance table the tables and table keys that make up the definition of these objects within their native environment. Data objects can be locked, archived, and migrated just like the proprietary objects already supported by Stat.

Data objects are specific to the change management module that they are defined for. This means that data object types supported in one change management module are not supported in the other modules. To avoid confusion, data object types for PeopleSoft, Oracle Applications, and generic applications are defined and maintained in separate tabs on the Data Objects Maintenance window. The maintenance procedures for all three are the same.

The Data Object Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | General | Data Objects.

Defining Application Version Numbers

Because data objects are directly associated with a change management module, the first step in defining a data object type is to associate it with its module, and if that module does not already have one, to assign it a version number. This allows Stat to maintain an archive of the object definition in the event you upgrade your application environments and modify your data object definitions at some point in the future. For example, let’s say you upgrade from PeopleSoft 8.14 to 8.17 and need to add a table to the definition of one of your data objects. By archiving object definitions according to application version number, you can maintain different versions of the same object and roll back to previous versions as necessary.

In the Module field, select the object type’s change management module.
Options include PeopleSoft, Oracle Applications, and Generic Applications.
In the Appl Number field type a number or code that uniquely identifies the version of the application.
(Optional) In the Description field type a brief description of the application version.
Click OK or Apply.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating