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

Testing Environment Connections

Active

If selected, indicates that this environment is active in Stat

Environment Cd
(Key Value)

A 1-10 character code which uniquely identifies the environment. This is the code that must be used in the Stat Oracle Agent configuration file.

Description
(Required Value)

A 1-35 character description of the environment

OraApps Version
(Required Value)

The version number of the Oracle Applications environment. Options include 11i and R12.

Data Obj
Version

The Oracle Applications version number, as defined in the Data Objects Maintenance table. Select a value in this field only if you plan on using Stat to manage data objects within this environment.

Req. Mgr. Approval

If selected, indicates that archive sets cannot be migrated to the environment without approval

Req. Patch Approval

If selected, indicates that patches cannot be applied to the environment without approval

DBMS
(Required Value)

The Oracle database management system that the environment is running on

Database Name

TNSNAMES.ORA entry on all Stat users’ workstations. Used by Stat Client for Oracle Net connections to the Oracle Applications database.

APPS User

Name of the APPS database account holder

APPLSYS User

Name of the APPLSYS database account holder

SYSTEM Pwd

SYSTEM database account password

APPS Pwd

APPS database account password

WebLogic Password

For R12.2 environments, the WebLogic server password

Host Name

Name of the machine hosting the database. Used by the Stat Central Agent and the Stat Oracle Agent for JDBC connections to the Oracle Applications database.

Required value for the Stat Central Agent.

Service Name

For Oracle, the listener service of the database. Used by the Stat Central Agent and the Stat Oracle Agent to establish JDBC connections to the Oracle database.

DB Listener Port

Port number for the database listener. Used by the Stat Central Agent and the Stat Oracle Agent for JDBC connections to the Oracle Applications database.

Required value for the Stat Central Agent.

Use Tns

For RAC Oracle databases, configures Stat to invoke TNS

Tns Entry

The full description as it appears in the tnsnames.ora file with no line breaks or carriage returns

Other Database Parameters

Additional environment-specific parameters, if needed

Last Update
(Read Only)

The date and time this record was last updated

Update By
(Read Only)

The user who last updated this record

After defining an environment in the maintenance table, you can make sure that you have entered all the information correctly by clicking Test Connection. This makes Stat establish a connection to the newly defined environment. If successful, Stat immediately disconnects from the environment and displays a “Connection Successful” message. If Stat is unable to connect, it displays an error message. Test Connect verifies that APPS and SYSTEM passwords. For R12.2 it also verifies the WebLogic password.

You can also test connections to multiple databases simultaneously. To test multiple connections, hold the <Ctrl> or <Shift> keys and select the databases you want to test. Then click Test Selected. Stat attempts to establish a connection to each database and reports its results in the Database Test Connect window

Note that when you test a single environment, Stat does not validate the values specified in the fields Host Name, Service Name, or DB Listener Port. If any of these fields are not configured properly, the Stat Central Agent will log an error when the user attempts to migrate an object to or from the environment. When you test multiple connections, however, Stat does test both client and agent connections, including Host Name, Service Name, DB Listener Port or (in the case of Oracle-based environments) TNS Entry.

Defining Oracle Applications Servers

In the Oracle Apps Environment Servers table, you define one or more servers that host the four service partitions required for each Oracle Applications environment. These service partitions include Web Service, Forms Service, Concurrent Manager Service, and Admin Service. To open the table, select the environment you want and click Servers.

Active

If selected, indicates that the server is active

Server Name
(Required Value)

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

Server Host
(Required Value)

The physical hostname (as opposed to the value in the Server Name field, which is user defined). This must be the server’s exact name (i.e., the value returned by hostname).

Platform
(Required Value)

The server’s operating system

Working Directory
(Required Value)

The location where the Stat Oracle Agent temporarily unzips patch files. A patch file is only stored in the directory while Stat is applying the patch with AutoPatch. After the patch has been applied, the patch file is removed.

Autobatch Size

Batch size parameter for AutoPatch

Autoparallel Workers

The number of parallel workers used by autopatch

Web Srv

Indicates if the server hosts a Web Service

Forms Srv

Indicates if the server hosts a Forms Service

Concurrent Srv

Indicates if the server hosts a Concurrent Manager Service

Admin Srv

Indicates if the server hosts the Database Service, also known as the “Administration Server” in Oracle documentation

Start Concurrent Cmd

Command run by the Stat Oracle Agent to start Concurrent Manager Service

Stop Concurrent Cmd

Command run by the Stat Oracle Agent to stop Concurrent Manager Service

Start Forms Cmd

Command run by the Stat Oracle Agent to start Forms Service

Stop Forms Cmd

Command run by the Stat Oracle Agent to stop Forms Service

Start Web Cmd

Command run by the Stat Oracle Agent to start Web Service

Stop Web Cmd

Command line run by the Stat Oracle Agent to stop Web Service

Ping Multiplier

The rate in 30 second increments at which the Oracle Agent updates the MEC_WAKE table and reports its status in Oracle Agent Status window (opened from the Tools menu). The default value is 1, meaning every 30 seconds. To increase the time amount, enter a higher value, e.g., meaning 120 seconds (4x30=120 seconds). The default value is 1.

If the value is set to 0, the agent does not report its status and will always be shown as 'Not Responding'.

Update Dt
(Read Only)

The date and time this record was last updated

Update By
(Read Only)

The user who last updated this record

When defining servers for an Oracle Applications environment, be aware of the following:

When specifying commands that start and stop any of the Oracle Apps services, you can use the appsusername and appspwd parameters to pass the user name and password values specified in the Apps User and Apps Pwd columns in the Oracle Applications Environment Connection Maintenance table. For example, to start a Concurrent Manager in R12, you would specify:
$INST_TOP/admin/scripts %%appsusername%%/%%appspwd%%

Inactivating Oracle Applications Environments

To inactivate an environment, de-select Active. Stat displays a warning message if the environment is currently part of a migration path.

Setting Up Migration and Patch Approval Lists

If an environment requires the approval of certain users before an archive set can be migrated into it or a patch can be applied, you can specify who these users are in the Migration Approval List and Patch Approval List tabs of the Application Options window. To open this window, select the environment you want and click App Options in the Oracle Application Environment Connection Maintenance table.

When setting up a migration or patch approval list, you can include different approver groups, including individual users and entire user classes or a combination of the two. The approval of any user or user class that you add to a list can be either required or optional.

Approval requirements that involve multiple approver groups or that can be satisfied in more than one way are defined using AND and OR operators. As you add approver groups using AND and OR operators, Stat displays the list as a tree structure and in the form of a SQL statement at the bottom of the window.

For example, let’s say a migration to a particular environment in the Financial Services service domain can be approved in one of two ways:

In this case, your approval list would look like this:

To further illustrate, let’s say that the migration must be approved by:

In this case, the approval list would look like this:

It is recommended that before setting up a migration or patch approval list, you have a basic idea of what approver groups (users and user classes) you want involved in the approval process as well as the relationships between these groups, which you define using AND and OR operators. For example, if the approval of one or more approver groups are required, you would begin the approval list with the AND operator. If, however, the approval of only one of two or more approver groups is required, you would begin the list with the OR operator.

Click AND if the approval of one or more approver groups are required
Click OR if the approval of one of two or more approver groups are required
3
In the Service Domain field, select the service domain that you plan to associate the environment with in the Oracle Applications Migration Path Maintenance table.
4
In the Approver Type field, select the approver group you want to add to the list.
Options include User and User Class.
5
In the Approver Name field, select the name of the user or user class you want to add.
6
In the Required field, select Required if the approval is required or Optional if it is not required.
The Required option means that the individual user and every member of the user class must approve the migration or patch. Optional means that the individual user’s approval is not required, whereas for user classes, it means that the approval of only a specified minimum number of users within that class is required.
7
If you selected User Class in the Approver Type field and Optional in the Required field, specify the minimum number of users in that class who must approve the migration or patch in the Number field.
8
Click Add.
b
Click AND or OR.
13
Click OK or Apply.

If an environment requires the approval of certain users before an archive set can be migrated into it or a patch can be applied, you can specify who these users are in the Migration Approval List and Patch Approval List tabs of the Application Options window. To open this window, select the environment you want and click App Options in the Oracle Application Environment Connection Maintenance table.

When setting up an approval list, you can include individual users, entire user classes, or a combination of the two. Also, the approval of any user or user class that you add to a list can be either required or optional.

2
Click New.
3
In the Approver Type field, select User.
4
In the Approver Name field, select the name of the user you want to add.
5
Select Required if the user’s approval is required.
2
Click New.
3
In the Approver Type field, select Class.
4
In the Approver Name field, select the user class you want to add.
5
Select Required if the approval of every user in the class is required.
6
If you did not Required, enter the number of users belonging to the class whose approval is required in the Min Approver (s) for Optional Classes field.
Related Documents