Stat 7.0 - System Administration Guide


Value	Description
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'. NOTE: You must stop and re-start the Oracle Agent if the value of the ping multiplier is modified.
Server Code	If you want to start/stop the Oracle Agent associated with this server from the Window's Client, you must first define a Server entry for this agent in the Maintenance \| General \| Object Types \| File Servers window. This entry must be defined with an SFTP protocol, and SSH must be running on the server running the Oracle Agent. Generally, the applmgr user should be used for the Username and Password or Key exchange authentication for logging into the Oracle Agent server. Once the Server entry is created, you may associate the Server Code with this Oracle Agent entry. NOTE: In order to source the environment when SSH logs in, you might be required to add the “./.ssh/rc” command to Post login cmd on the File Servers tab of the Object Type Maintenance window. In this case make sure that the rc file sources your Oracle E-business environment and sets your STAT_JAVA_HOME.
OA Stat Home	This is the STAT_HOME location defined for this Oracle Agent on the Oracle E-Business server.
OA Config File	If you override the default location for the OA config file with a “-s” switch, you must enter it here.
OA Stat Java Home	If you override the default STAT_JAVA_HOME of the Oracle Agent with a “-j” switch, you must enter it here.
Update Date (Read Only)	The date and time this record was last updated
Updated 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%%

•

Each of the four service partitions must be hosted on at least one active server. For a shared APPL_TOP, all four service partitions can be configured on one server.

•

For each active server, at least one of the service partition check boxes must be checked.

•

Only one active server can host the Database Service partition.

Start/Stop Oracle Applications Agents

After you install the Oracle Application Agent on each defined server, you may start/stop the agent, edit the stat.conf file, retrieve OA Agent logs, or change OA Agent log mode from the server list.

•

Oracle Agent Configuration - You may use this button to retrieve your stat.conf file from the OA Agent conf directory. At this point, you may view or edit the content of the file before saving it back to the server.

•

Start/Stop Oracle Agent - You may use this button to start/stop the OA Agent for the selected server. Once the OA agent is started, the Status column for the server will display Started along with a green check mark. Once the OA agent is stopped, the Status column for the server will display Stopped along with a red X.

•

Oracle Agent Logs - You may use this button to retrieve a list of logs from the OA Agent log directory. Once the list is retrieved, you may view the content of the log or export it.

•

Oracle Agent Log Mode - The current log mode defined for the Oracle Agent is displayed in the drop-down and can be changed while the agent is running. Select the desired mode from the drop-down and click the button beside it.

•

Refresh Oracle Agent Status - Once you attempt to start or stop the Oracle Agent, you may use this button to refresh the current status of the OA agent.

•

Show SSH logs - SSH protocol is used to run the Start/Stop commands on the Oracle Agent server. For troubleshooting purposes, you may need to view the SSH logs generated by the commands that are run on the server. Make sure to select this check box before executing the Start or Stop command.

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.


	CAUTION: Be careful inactivating environments that are part of migration paths. Objects in inactive environments cannot be archived or migrated.

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:

•

By a certain user AND at least one user in the Administrator user class

•

By at least two users in the Fin Developer user class

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

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

•

Two users, one of whom is required

AND

•

At least one user in the Administrator user class OR at least two users in the Fin Developer user class.

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


	NOTE: Migration and patch approval lists closely resemble status transfer approval lists and the procedures for defining them are much the same. For more information on migration approval lists, see Setting Up Transfer Approval Lists .

To set up a migration or patch approval list:

Do one of the following:

•

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

The operator icon is added to the approval list diagram.

Click on the AND or OR operator icon you just added.


	TIP: The icon background appears blue when selected and changes to gray when other fields or action buttons are activated. As long as the background of the operator icon is blue or gray, then approver groups and other operators can be attached to the operator.

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.

In the Approver Type field, select the approver group you want to add to the list.

Options include User and User Class.

When adding approvers, be aware of the following:

•

Although you can add any user or class to an approval list, be aware that only users that have access to an environment and the selected service domain (as defined in the User Maintenance table) will be able to approve a patch application or migration into that environment or receive email notifications regarding their pending approval. If an approver does not have access to the environment, the patch or migration cannot be approved until either the user is granted access to the environment or the approval requirements are overridden by another user with proper security rights. For this reason, it is recommended that you first verify users have access to a particular environment and service domain before adding them to an approval list.

•

Adding individual users to approval lists could create problems if those same users are later inactivated or have their service domain and environment access restricted. For this reason, it is recommended that you add user classes to approval lists rather than individual users whenever possible.

•

Users assigned to a migration or patch approval list must have the user class rights to operate in the same change management module in which the migration takes place. Also, you can assign user class rights that enable users to migrate objects or apply patches regardless of approval status and also to approve migrations and patches on the behalf of other users.

In the Approver Name field, select the name of the user or user class you want to add.

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.

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.

Click Add.

The approver is added to the tree structure under its approver group label and the initial AND or OR operator. Required approvers are displayed in bold.

At this point, how you proceed depends on the different approver groups you want to add to the list and how you want to define the relationships between these groups using AND and OR operators.

(Optional) Do the following to add additional AND or OR operators to your approval list:

Depending on the relationship between approver groups in your list, select the operator icon to which you want to attach additional operators.

Click AND or OR.

Repeat as necessary to add more operator icons to the approval diagram.

(Optional) To add additional user classes, select the appropriate operator icon in the approval diagram and repeat steps 4 through 8.

When you the first add an individual user to an approval list, Stat automatically creates the ad hoc group “users” in the approval diagram and attaches it to the appropriate operator icon. All subsequent users you add to the list must belong to this group.


	TIP: In a scenario in which you want to create approval relationships between multiple user approver groups, you may consider adding users to new user classes or queues created expressly for this purpose.

(Optional) To add additional users, select the “users” group and repeat steps 4 through 8.

(Optional) Do any of the following to edit the diagram as needed:

•

To change an operator from AND to OR or from OR to AND, right-click on the icon.

•

To change the Required status of an approver, right click on it in the diagram. This changes required user classes to optional with 1 minimum user approval.

•

To change the minimum number of user approvals in an optional user class, double-click on the group label and specify the minimum number of user approvals you want.

•

To move approver groups or entire operator relationships, click and hold on the group label or operator icon and drag and drop to a different operator icon in the diagram.

•

To delete approver groups or entire operator relationships, click and hold on the group label or operator icon and drag and drop to the Trash Can icon.

Click OK or Apply.

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.

To add users to an approval list:

Depending on the type of approval list you want, select either the Migration Approval List tab or the Patch Approval List tab.

Click New.

In the Approver Type field, select User.

In the Approver Name field, select the name of the user you want to add.

Select Required if the user’s approval is required.

If you do not select the check box, the user’s approval is optional.

Repeat steps 1 through 4 to add as many users to the list as needed.

If you added more than one optional user, enter the minimum number of optional users whose approval is required in the Min Approver (s) for Optional Users field.

This number must be equal to or less than the number of optional users.

To add user classes to an approval list:

Select the service domain for this environment.

Click New.

In the Approver Type field, select Class.

In the Approver Name field, select the user class you want to add.

Select Required if the approval of every user in the class is required.

Do not select the check box if the approval of only a certain number of users in the class is required.

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.

Seleziona il prodotto:

Per una maggiore efficacia, compilare l'Obiettivo della chat:

Soluzioni consigliate per il problema

Stat 7.0 - System Administration Guide

Defining Oracle Applications Servers

Start/Stop Oracle Applications Agents

Inactivating Oracle Applications Environments

Setting Up Migration and Patch Approval Lists