The default logging level for an instance of the Stat® Oracle Agent is determined by the <ENV>.log.level parameter. You can change the logging level for a running agent using the <STAT_HOME>/app/bin/setLogLevel.sh utility.
The build (i.e., version) for the Stat Oracle Agent is included with header block in the log file when starting an instance of the agent. A listing of the build is displayed with the <STAT_HOME>/app/bin/getversion.sh utility.
Stat® Agents for Oracle® Apps use the stat.conf file and the Oracle E-Business Suite environment file to resolve the top-level directory for each product. In the case of custom products, you may need to add an entry in the stat.conf file for each Agent. For example, if you created an application named XXXGL for customizations to GL, you would add the following entry to utilize Stat functionality for these custom objects:
NOTE: 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 Object Compare Support for Form Library Files. |
NOTE: A typical installation of Stat comes with a number of Setup objects. These objects are referred to as AOL objects. These objects support archiving and migration of data from the FND (Application Object Library) product top. In addition, Stat provides Oracle Apps Resource Kit, which gives customers the option of adding support for object types from 10 other product tops, including ALR, AP, AR, BOM, FA, FF, GL, INV, ONT, and PA. |
After defining a new base directory or editing an existing one in the File Object Maintenance table, you need to update the configuration file of the Stat® Oracle® Agent. The Stat Oracle Agent must be able to resolve the base directory codes when processing generic file objects. For example, if in the File Object Maintenance table you defined a base directory code COMMON_TOP, you must add the following parameter to all the Oracle Agents that will process the generic objects using this base directory code:
For R12.2 environments, if these base directories are under the Edition-based File System, then the value for each Base Directory must come from the Context File. An example of these types of Base Directories would be OA_HTML. This parameter is defined in the Context file with a value for both the fs1 and fs2 file system. To retrieve values from the Context File, you always need an XPath expression. A new column called Context Pattern is defined in Stat which stores the XPath expression for retrieving the value from the Context File. (You may need to consult with your DBA and refer to documentation for EXTRACTVALUE command). For example the expression for retrieving OA_HTML from the Context file is:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center