Stat 6.1 - System Administration Guide

Oracle Apps Base Directories

For Oracle Applications, you need to specify file locations only for custom file types (Custom, Custom with Product or Custom with Product and Language). The locations of the proprietary file types (forms, reports, etc.) are managed by Stat automatically. The base directories are defined on the OraApps Base Directory tab, while the file “pathways” are defined on the file type window.

The agent must be able to resolve the server environment variable into a known file location. For all non-R12.2 environments, this is done via the stat.conf file. For example, if in the Object Type 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 custom objects using this base directory code:

The syntax for the parameter is <EnvCode>.env.<BaseDirectory>=<value>. The value should be an absolute (i.e., fully qualified) directory with read/write privileges for the Oracle agent. The parameter in this example is added to the Oracle agent for the “Dev” environment. The parameter can be set to a different directory for each agent.

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. The Context Pattern field in Stat 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: //OA_HTML[@oa_var="s_oahtml"].

Note that if these Base Directories are not under the Edition-based File System, then the value for the Base Directory is defined in stat.conf.

Also Note that in general if a value is defined for any parameter in stat.conf, it always overrides the value read from the context file.

NOTE: Be aware of the following: • Custom objects in Stat are specially affected by R12.2 file system. For Custom and Generic custom objects, OA Base Directory values should exist in the Environment's Context File, or it should come from a location outside the AppsTier File System. In the latter case, the values are defined in the stat.conf file as before. • Context patterns may be used be all releases of R12, in which case you don’t need to define the base directory as a parameter in the stat.conf file.

Testing File Locations, Servers, and Default Directory Locations

You can test the connection between Stat and any file location, server, directory or change management environment by selecting the row and clicking Test Connection. This directs Stat to test its connectivity to the selected file location, file server, directory or environment. If successful, Stat displays a “Connection Successful” message box. If Stat is unable to connect, it displays a message box stating the cause of the failure, for example, “User ID or Password is not defined.” The connection between Stat and the file server is always established by the Stat Central Agent. For this reason, ensure that the Stat Central Agent is up and running before testing any connections.

PeopleSoft Environment Connection Maintenance

The PeopleSoft Environment Connections Maintenance table defines the PeopleSoft environments to which Stat can connect. These are the environments available for selection on CSRs and the various PeopleSoft wizards. Within the definition for each environment is the information Stat needs to connect to it.

PeopleSoft environment connection security is controlled by the following user class rights:

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

Stat provides change management support for PeopleSoft running on a several different platforms, including Oracle, SQL Server, and UDB (both OS/390 and AIX/Unix). Although most of the values that you specify in the PeopleSoft Environment Connection Maintenance table are the same regardless of which platform you are running on, some values are DBMS-specific. For this reason, the following sections describe each value in the maintenance table for each platform supported by Stat, along with any special considerations you should bear in mind when defining connections between Stat and your PeopleSoft environments.

Oracle 10g, 11i, and 12c

The PeopleSoft Environment Connections Maintenance table defines the PeopleSoft environments to which Stat can connect. These are the environments available for selection on CSRs and the various PeopleSoft wizards. Within the definition for each environment is the information Stat needs to connect to it.

PeopleSoft environment connection security is controlled by the following user class rights:

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

Stat provides change management support for PeopleSoft running on a several different platforms, including Oracle, SQL Server, and UDB (both OS/390 and AIX/Unix). Although most of the values that you specify in the PeopleSoft Environment Connection Maintenance table are the same regardless of which platform you are running on, some values are DBMS-specific. For this reason, the following sections describe each value in the maintenance table for each platform supported by Stat, along with any special considerations you should bear in mind when defining connections between Stat and your PeopleSoft environments.