Chat now with support
Chat with Support

Stat 6.1 - 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: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Platforms

When users upload a patch to the Stat Repository, they are prompted to specify the target platform. The list of available platforms is defined in the Platform tab.

Stat uses the value displayed in the Description field to identify the platform that an uploaded patch targets by matching the text to the patch file name.

Stat comes pre-configured to support AIX, SunOS, Windows, HP-UX, Linux, and generic platforms. You cannot define new platforms, but you can deactivate existing ones to reduce the number of options in other fields. Deselect Active to deactivate a platform.

Updating Products

Each of your Oracle Applications environments may feature a different set of Oracle Applications products. In order to utilize Stat’s change management support for the proprietary file objects in your Oracle Applications environments, as well as apply product-specific Oracle patches to the appropriate environments, you need to specify the products that each environment contains. For Oracle Apps Setup objects, each environment may have a different list of active products. To retrieve the proper list of Setup Objects in Stat, it is imperative that the list of products are updated. This is done in the Products tab.

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 along with their release level. When you first define an environment, install new Oracle Applications products to a particular environment, create a custom product, or apply a maintenance pack, you should update the environment’s product list. To do this, select the environment you want to retrieve the product list for and 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 for the selected environment. To deactivate a product, deselect Active.

* 
NOTE: You can also update the products list of an environment in the Products tab of the Application Options window, which you open from the Oracle Application Environment Connection Maintenance table.

When updating products, be aware of the following considerations:

•
For Stat to recognize a custom product, the product must have a record created in the FND_PRODUCT_INSTALATIONS table. To create this record, select System | Installations in the Oracle Alert Manager responsibility and use the form to define the custom product. It will be necessary to re-start the Stat Oracle Agent after this record is created. Also, custom products may need to be defined in the stat.conf file before they can be updated in Stat. For Release 12.2, Stat reads the values for custom product locations from the Context File of the environment. If these parameters are present in stat.conf, they override the values in the Context File.
•
Oracle stores all form FMB files in the same directory ($AU_TOP/forms/<lang>). When getting a list of forms for a user to assign to a CSR, Stat uses two sources to determine the FMBs associated with the product selected by the user: All FMBs registered for the product are considered and all FMBS with a corresponding FMX file in the product top are considered. If a form is not registered or does not have an FMX file, Stat will not include it when displaying a list of forms. This limitation does not affect forms for custom applications since Stat also considered FMBs in the product top for custom applications.

Languages

In the Languages tab you configure Stat to support change management for language-specific, proprietary Oracle Applications file objects as well as translation patches. The Language tab is read-only. It displays a list of all the languages enabled for all environments. The default language is American English. You can update the list for any Oracle Application environment first by selecting an environment in the dropdown list and then clicking Update Languages.

To deactivate a language, deselect Active.

If you need to migrate AOL objects in multiple language versions, do the following to configure language support AOL object in Stat.

1
Select the Oracle Application environment containing the AOL objects you want to migrate in the drop-down list and click Update Languages.
2
Verify that the languages you want supported are installed.
3
Add the AOL objects you want to migrate to a CSR.
When you select the AOL object in a multi-lingual environment, you are prompted to select a language.
* 
NOTE: The following objects are exceptions: XDO Templates, XDO Translations, OAF Component XML, and XDF Editioning View (R12.2). Also, no prompt is displayed if only American English is installed.
After adding the objects to the CSR, each object’s description will have the language appended to the end. Also, after an archive set has been created successfully, you can view and verify the content of the archive set.
4
Open the archive set in the Objects tab, select an object, and click View.
A View Archive window is displayed showing specifics about the object, including the language.

Patch Prerequisites

In the Patch Prerequisites tab you specify the default environment against which Stat will process patch prerequisite requests whenever users upload and save a patch. Specifying a default environment is optional.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating