Chatta subito con l'assistenza
Chat con il supporto

Stat 6.2 - 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

Approving Migrations

Before you can migrate an archive set into a PeopleSoft environment, you may need to get the migration approved by users authorized to approve migrations into that environment. Conversely, if you have been designated as a migration approver for a particular environment by your system administrator, other users may need your approval before they can migrate archive sets into that environment. Migration approvals are environment-specific. They provide a way for users (typically managers and development leaders) to monitor and control migrations into 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 migration into that environment or receive email notifications regarding their pending approval. If an approver does not have access to the environment, the migration cannot be approved until either the user is granted access to the environment or the migration’s approval requirements are overridden by another user with proper security rights.

For more information on migration approvals, see the Stat System Administration Guide, Chapter 4, “General Maintenance Tables.”

1
Select Migration Management | Migration Approvals.
2
In the My Open Approvals tab, select Approved in the Status column for each migration that you want to approve. If you do not approve the migration, select Rejected.
3
Click OK or Apply to save your changes.
If you selected Rejected, the approval record stays on the My Open Approvals tab until you change it to Approved, or the migration approval is overridden, or the archive set is changed so that it is no longer ready to migrate.
c
Click OK or Apply to save your changes.

You can also approve the migration of an archive set in the Target Environments window of the CSR.

4
Click OK or Apply.
TIP: 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 the Ready to Migrate check box 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.

You can view records of migration approvals from the Migration Details window. For more information, see Documenting Migrations (PeopleSoft) .

If you want to notify users about migrations 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 migration 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 migration. 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. For more information, see the book Stat System Administration, Chapter 7, “Email Configuration”.

Mass Migrating Objects

If you need to migrate several archive sets to the same environment, rather than migrate them one at a time, you can perform a mass migration. There are two types of mass migration supported by Stat:

Because mass migrations can include objects assigned to different users and belonging to different CSRs, it is recommended that a limited number of users be allowed to perform mass migrations. With proper security, users can perform mass migrations that override workflow rules and approval requirements. In addition, Stat features the Release Recovery window, which allows users to perform application release mass migrations that override workflow rules, approval requirements, and object locks. For more information, see Release Recovery Window .

2
Select Migration Management | Mass Migration.
4
(Optional) In the Description field, enter a unique description of the migration.
5
(Optional) Select the Stop on Error option if you want the Stat Central Agent to terminate the migration at the first error it encounters.
6
In the Module field select PeopleSoft.
TIP: You can set a default value to be displayed in the Module field. To do this, select User Options | Stat Options. Then in the Stat User Options window, select the value you want in the Default Module field.
7
In the Service Domain field, select the service domain associated with the migration path containing the target environment you want.
8
In the Target field select the environment to which you want to migrate the archive sets.
9
In the Type field select one of the following:
Select Ready to Migrate if you want to mass migrate archive sets that have been individually marked for migration
Select Migration by Release if you want to mass migrate archive sets that have been assigned the same application release label. When you select this option, the Release field is displayed. Then in the Release field select the release label you want. Release labels can be minor or major and are defined by system administrators. After you select a release label, Stat displays a list of archive sets that have been assigned that label.
10
(Optional) In the Sources section, deselect Migrate for each archive set that you do not want to include in the mass migration.
11
(Optional) In the Archive Migr Order column, change the order in which selected archive sets will be migrated.
13
(Optional) In the Migrate column, deselect the individual objects you do not want to migrate.
16
Click Migrate>.

The following considerations apply to mass migrating to distribution environments:

The mass migration cannot proceed for the following situations:

If any archive set is causing errors when mass migrating, you can opt not to include that archive set in the mass migration. You can then mass migrate the other archive sets and resolve the issue at a later time.

Documenting Migrations (PeopleSoft)

After creating and migrating a base, interim, and final archive set, a typical migration path may look like this:

The sample migration path above shows:

Flag Indicators

Flags appear to the right of environment graphics and indicate that an archive set was created in that environment. Flags include ‘B’ for base, ‘I’ for interim, and ‘F’ for final. If multiple interim archive sets were created in an environment, only one ‘I’ flag is shown.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione