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

New Setup Objects Interface

Stat facilitates the creation of new Setup object types. In the following section, the interface is used to configure Stat support for the Setup object type, Advanced Benefits Startup Action Types. The R12 version of the .lct file is located under BEN_TOP/patch/115/admin/benstact.lct.

A quick examination of the .lct file shows that it is a good candidate for Stat:

DOWNLOAD ACTION <----- Entity Name
"select v.TYPE_CD,<----- Entity Column Name
v.DESCRIPTION <----- Additional parameter to identify the row
(v.TYPE_CD like :TYPE_CD)))" <----- Parameter which uniquely identifies the row

The view BEN_STARTUP_ACTN_TYP_VL is the source for data, and each row is uniquely identified by TYPE_CD column.

1
In the Object Class field, select Oracle Apps Setup Objects.
2
Click New.
4
Click Apply.
5
Click Setup.
7
In the Lct Filename field, enter benstact.lct.
8
In the Entity Name field, enter ACTION.
10
In the Lov Partial Sql field, enter
FROM BEN_STARTUP_ACTN_TYP_VL v.
11
Click Update to save your changes.
TIP: If you need to modify an existing row, click Update again. Click Export to export the sql script for the new created object type. Click Delete to delete the object type definition.
13
In the Environment field, select an environment.
14
Click Fetch.

File Servers

The File Servers tab defines the servers that Stat accesses when archiving file objects for a specified environment or a user’s working directory. For Oracle Applications, the file servers defined here are used only for working directories. Servers for Oracle Applications environments require a different configuration and are defined in the Oracle Application Environment Connection Maintenance table, as described in the section, Oracle Applications Connection Maintenance .

You can check the connection between Stat and a file server by selecting the server and clicking Test Connection. This works the same way as testing connections to change management environments. For more information, see Testing File Locations, Servers, and Default Directory Locations .

The following table defines the value types on the File Server tab of the Object Type Maintenance window. Some of the value types, although not required, are necessary for archiving by Stat.

Active

Indicates if this server is activated in Stat

Server Name
(Key Value)

A user defined character code which uniquely identifies the server in Stat

Description

A description of the server. 35 character maximum.

Host
(Required Value)

The actual FTP host name or IP address (as opposed to the value in the Server Name field, which is user defined)

OS
(Required Value)

The operating system the server runs on. Options include Unix, NT, and MVS.

Directory

The FTP server directory where Stat accesses file objects. Make sure you use the proper syntax when specifying server directories. For more information, see File Path Syntax .

User
(Required Value)

The ID Stat uses to connect to the file server. 50 character maximum.

Auth Type

The type of user ID authentication you want for Stat on this server. options include Password and (for SFTP servers only) Public Key. You can also select None if you do not want to use authentication.

Authentication

If you selected the value “Password” in the Auth Type field, this field displays the Enter Password button, which opens the Change Password dialog box. Enter the password in the Password and Confirm Password fields. Then click OK. 50 character maximum.

If for an SFTP server you selected the value Public Key in the Auth Type field, this field displays the Public Key Config button, which opens the Public key Maintenance window. Here you can import/export key files and generate keys.

Port

The port number that the FTP server is running on. Default is 21.

Passive

FTP setting used with firewalls. The default value for ftp in Stat is passive. Uncheck this option for active mode.

Post login cmd

Any commands you want Stat to run after connecting to the FTP server. Must begin with the prefix “cd.”

File Case
Sensitive

If selected, Stat handles file names on a case sensitive basis when migrating files to this server

FTP Protocol
(Required Value)

The security protocol used by the server when archiving or migrating objects. Options include FTP and SFTP. Default is FTP.

Unix File
Permission

For Unix File Servers Only.

If selected, Stat automatically executes the Unix command, chmod 666, after users migrate file objects to their working directories. This command gives all users that have access to the specified working directory read-write access to the migrated file objects.

NOTE: You can specify file permission settings for individual file types in the Object Types tab. Selecting Unix File Permission, however, overrides any file type-specific setting.

Cobol Compiler Location: Drive and Root Directory

Location of the Cobol Compiler used to compile PS cobol programs that reside on this server

JCL File Location

The file name and location (local or network) of the jcl file that users can invoke to run the Compile Cobol post migration command on mainframe servers only.

Last Update
(Read Only)

The date and time this record was last updated

Update By
(Read Only)

The user who last updated this record

File Path Syntax

In Stat, there are syntactical rules for specifying file paths. These rules vary somewhat depending on whether you are defining paths on Unix and NT servers or on mainframe servers.

The full path of a source file location or working directory on a Unix or NT server can be composed of up to three separate elements, the topmost being the Stat home directory defined on the server, followed by the directory of the server that hosts the source file location or working directory (as specified in the Directory field of the File Servers tab), and lastly the source file location or working directory itself.

NOTE: When a file archive or migration request is made in Stat, Stat opens a FTP/SFTP connection to the server, logging in with the username specified in the User field of the File Server tab, for example, “StatFTP.” This means whenever particular Stat users archive or migrate files, they log into the server using Stat’s login credentials rather than their own. Like all users, however, Stat has a default home directory assigned to it on the file server as part of its account setup. This Stat home directory in turn serves as the topmost element in any file path defined in Stat.

File paths starting with “/” or “\” are assumed to be absolute paths, and are not concatenated with or relative to the element that directly precedes them, which can be either the server directory or the Stat home directory.

File paths that do not start with “/” or “\” are assumed to be relative, and are concatenated with the element that directly precedes them. See the table below for examples.

Note that Stat ignores slashes at the end of file paths.

Also, if you do not define either a source file location or a working directory, Stat assumes the path at the server directory level. Likewise, if no server directory is defined, the path is assumed at the level of the Stat home directory.

The table below illustrates the how Stat processes the syntactical combinations of the three path elements.

/usr/local/statftp

/p701dp01

/SQR

/SQR

/usr/local/statftp

p701dp01

/SQR

/SQR

/usr/local/statftp

/p701dp01

SQR

/p701dp01/SQR

/usr/local/statftp

p701dp01

SQR

/usr/local/statftp/p701dp01/SQR

/usr/local/statftp

Blank

/SQR

/SQR

/usr/local/statftp

Blank

SQR

/usr/local/statftp/SQR

/usr/local/statftp

p701dp01

Blank

/usr/local/statftp/p701dp01

/usr/local/statftp

/p701dp01

Blank

/p701dp01

/usr/local/statftp

Blank

Blank

/usr/local/statftp

Stat supports archiving and migrating file objects that reside on DB2 for z/OS mainframes. Mainframe file servers are defined much the same way as NT or Unix-based servers, except source file locations for mainframe servers are defined as datasets.

Access to a dataset is granted through its owner. You only need to specify the dataset in the File Path field if the login user (as specified in the File Servers tab) is the dataset owner. However, if the dataset owner is not the login user, you must fully qualify the dataset by appending the owner name and enclosing it in single quotes (‘owner.dataset’).

For example, in the table below, STATTAB is the login user specified in the File Servers tab and the owner of the first dataset. The second dataset, however, is owned by STATSYS, which means the file path must be fully qualified with the owner name and enclosed in single quotes.

STATTAB

QA.STATSOFF.PARMLIB

STATTAB.QA.STATSOFF.PARMLIB

STATTAB

‘STATSYS.QA.STATSON.PARMLIB’

STATSYS.QA.STATSON.PARMLIB

Case Sensitivity and File Name Conversion

You can configure Stat to conform to the case sensitivity requirements of your file servers. For example, certain file servers may be case insensitive when handling the names of file objects, but because Stat is case sensitive by default, this can result in Stat not recognizing file objects that exist on a file server as being the same objects that exist in the Stat Repository. You can resolve this issue on a per server basis by deactivating case sensitivity in Stat. Also, if a file server requires that the names of files of a specific type be all uppercase or lowercase, you can configure Stat to convert the case of file names when migrating to that server.

You can deactivate case sensitivity in Stat for file servers that are case insensitive. This way, when archiving or migrating file objects, Stat can locate objects in the file server’s source locations, even if the names of the files are in a different case.

1
In the File Servers tab, deselect File Case Sensitive for the file server you want.
2

A file server may require that the names or the extensions of certain types of objects be all in uppercase or lowercase. You can configure Stat to convert the names or extensions of these types of file objects into the required case when they are migrated to that server.

These include options for the conversion of both the name of the file and the extension. For example, if you select the option Lower File Name - Upper Extension, Stat converts the name of the file into lower case and the extension into uppercase. To deactivate file name conversion for a file type, select None in the field.
3
Related Documents