Converse agora com nosso suporte
Chat com o suporte

Stat 6.3 - 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: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

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.

Updating Products per Environment

Each Oracle Applications environment you define may feature a different set of Oracle Applications products. In order to utilize Stat’s change management support for proprietary Oracle Applications file objects, 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 of the Application Options window.

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. When you first define an environment, or when you install new Oracle Applications products to a particular environment, you should update the environment’s product list. To do this, 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.

Copying Oracle Applications Environments

If you need to define an Oracle Applications environment that closely resembles an existing Oracle Applications environment, you can save time by copying the definition of the existing environment and editing the copy as needed. When you copy an Oracle Applications environment, all the information gets copied over, including server definitions and approval lists.

Generic Application Connection Maintenance

The GenApps Environment Connection Maintenance table defines the generic (non-PeopleSoft and non-Oracle Applications) application environments connected to Stat. The table closely resembles the connection maintenance tables for PeopleSoft and Oracle Applications, and many of the maintenance procedures are the same. Within the definition for each environment is the information Stat needs to connect to it.

Connection security for generic applications is controlled by the following user class rights:

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

Active

If selected, indicates that this environment is available for selection

Environment Cd
(Key Value)

A 1-10 character code which uniquely identifies the environment

Description
(Required Value)

A 1-35 character description of the environment.

Data Obj Version

The version number of the generic application, 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. Migr. Approval

If selected, indicates that Archive sets cannot be migrated into the environment without migration approval

DBMS

Name of the APPS database account holder

Database Name

The name of the environment (database instance). Options include Oracle, Microsoft SQL Server, and N/A.

DB User ID
(SQL Server Only)

The SQL Server user ID for the schema owner. The default is “sysadm.”

DB Password
(SQL Server Only)

The password for the DB User ID

Database Server

The name of the database server housing the generic application repository. Format for this entry is DBMS-specific.

Srv Login ID

The login ID used for Stat login to the environment. Not used by ODBC.

Server Password

The password associated with the Srv Logon ID

Host Name

Name of the machine hosting the database

Service Name

For generic applications running on Oracle, the listener service of the database. Used by the Stat Central Agent to establish JDBC connections to the Oracle database.

DB Listener Port

Port number for the database listener.

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

Unicode DB

If selected, indicates the database is Unicode

Last Update
(Read Only)

The date and time this record was last updated

Update By
(Read Only)

The user who last updated this record

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação