Chat now with support
Chat with Support

Stat 6.0 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

Defining Command Maintenance Steps

You can define maintenance steps in the form of custom commands. These are operating system commands executed by the client server Stat is running on. All drive mappings and file paths are relative to the client server.

When defining a command, you can include predefined parameters as well as user and server-based parameters. This provides a convenient way to specify values commonly invoked by operating system commands, such as server names and download directories. Also, parameters offer a way to secure sensitive information by encrypting values that you do not want visible to users such as passwords.

<<YY>>

The current year, 2-digit format

01

<<YYYY>>

The current year, 4-digit format

2001

<<MM>>

The current month, 2-digit format

01

<<DD>>>

The current day of month, 2-digit format

31

<<DDD>>

The current day of week

Monday

<<HH>>

The current hour, 2-digit format

13

<<NN>>

The current minutes, 2-digit format

45

<<SS>>

The current seconds, 2-digit format

23

<<ENV>>

The target environment of the migration

PROD

<<SDCD>>

The service domain that the CSR belongs to

HR

<<CSRID>>

The CSR ID number

6086

<<OBJTYPE>>

The object type the maintenance step is defined for

Panel

<<<YYYY>>>-<<<MM>>>-<<<DD>>> <<<HH>>>:<<<NN>>>:<<<SS>>>
2
In the Command with parameters field, enter the command you want Stat to run.
5
Click Interpret >>.
6
7

Scheduling Maintenance Steps

When you schedule the Oracle Agent to run a maintenance step, you specify when you want the Oracle Agent to execute the step (immediately or at some later time) as well as the environment and servers you want the step executed against.

You can also ensure that the maintenance step is executed only after the patch it is associated with has been applied by designating the patch application request as a dependent event. This way, the Oracle Agent will not execute the step until it has first applied the patch.

2
In the Environment field, select the environment you want to run the step against.
The Servers field displays all the servers included in the selected environment. You can run the step against each server in an environment, or you can run it against just the servers you select. You must select at least one server, however.
3
(Optional) In the Servers field, deselect any server that you do not want to run the step against.
4
In the Run Time field select either Immediate if you want the Agent to process the request right away (or if you specify a dependent event, immediately after the Oracle Agent processes that event) or select Select Datetime if you want to the request to be processed at some future date.
5
If you selected Select Datetime, browse for the date you want. You can also specify the time you want the request processed in terms of hour and minute.
8
Click Save.

Associating Patches with CSRs

After uploading a patch to the Stat Repository, you can then associate that patch with a CSR. Associating patches with CSRs enables you to apply them to environments and perform impact analyses. In order to associate a patch to a CSR, the CSR must have the Patch tab enabled. The enabling of the Patch tab is determined by CSR type.

You associate patches with CSRs the same way you associate objects, first by selecting the Patch Inventory environment and then the type of patch you want. The patches that you can add to a CSR are all active patches in Stat’s patch inventory.

2
In the Environment field select Patch Inventory.
4
Click Add Object.
5
Select File | Save, or click the Save toolbar button.

Approving Patches

Before you can apply a patch to an Oracle Applications environment, you may need to get the patch approved by users authorized to approve patch applications to that environment. Conversely, if you have been designated as a patch approver for a particular environment by your system administrator, other users may need your approval before they can apply a patch to that environment. Patch approvals are environment-specific. They provide a way for users (typically managers and development leaders) to monitor and control patch applications to environments containing sensitive information, such as object definitions that should not be modified or overwritten.

Approval lists can be either required or optional and can include individual users, entire user classes, or a combination of the two. Although system administrators can add any user or class to an approval list, be aware that only users that have access to an environment (as determined by system administrators in the User Maintenance table) will be able to approve a patch application into that environment or receive email notifications regarding their pending approval. If an approver does not have access to the environment, the patch cannot be approved until either the user is granted access to the environment or the patch’s approval requirements are overridden by another user with proper security rights.

When you click All Patch Approvals, the tab displays all the patches that are awaiting approvals from other users. With proper security rights, you can make patch approvals for other users.
2
Click in the Status column for each patch that you want to approve and select Approved. If you do not approve the patch, select Rejected.
3
Click Save.
If you selected Rejected, the approval record stays on the My Patch Approvals tab until you change it to Approved, or the patch approval is overridden.
c
Click Save.

You can also approve patches in the Approval List for Target Environment window.

2
In the approval list, double-click your name and in the pop-up menu select Approve if you approve the patch. If you do not approve the patch, select Reject.
5
Click OK or Apply to save your changes.
NOTE: With proper security rights, you can make approvals for other users. You can also unapprove all approvals by clicking Unapprove All. This allows you to deselect Ready to Migrate for the target environment. When you override another user’s approval, Stat records you as the approver, not the user originally assigned to make the approval.

If you want to notify users about patches that are still pending their approval, you can email a message predefined by system administrators. In the tree list of approvers, select the node representing the user or class that you want to notify and click Email. An email job request is sent to the Stat Central Agent, which processes the request and sends an email to the user you selected or to each member of the selected class. A “@” sign is displayed for that approver node in the Envelope field of the Approval List tab.

NOTE: The Email button is disabled once the approval requirements of a patch have been satisfied.

System administrators can also configure the Stat Central Agent to include links in the reminder message that the recipient can click to approve or reject the patch application. This sends an email back to the Stat Central Agent, which processes the response email and changes the approval status to Approve or Reject, depending on which link the approver selected.

NOTE: When an approval status is changed by responding to a reminder message, the Update Date field in the Approval List window will be automatically populated and the Update By field will display the value, Via Email.

Approval notification reminder messages can also be sent for workflow status transfers and migrations. For more information, see the book Stat System Administration, Chapter 7, “Email Configuration”.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating