Regarding Pre and Post Migration Steps windows:
Unlike the Pre Migration Steps window, the Post Migration Steps window is not opened automatically. Instead, post migration steps have a default status of Pending, which means that until the user changes the status of a post migration step to either Complete or N/A (Not Applicable), the migration will have a status of Wait for Post Step in the Migration Console. This is how Stat prompts users to complete post migration steps as intended. Once all the post migration steps have been marked as Complete or N/A, the status of the migration will change to Complete.
Automatic steps consist of custom commands defined by your system administrator. For more information on automatic steps, see the Stat System Administration Guide, Chapter 5, “Service Domain-Specific Maintenance.”
To execute an automatic step, click Run. Depending on the step, Stat may prompt you to specify additional parameters.
Predefined parameters specify values used to login to a target environment during a migration (database name, user name and password), whereas user and server-based parameters generally invoke values specific to the users and file servers defined in Stat. Also, certain parameters may be defined so that their values are different depending on which user or server they are being applied to. For more information on pre and post migration step parameters, see the book, Stat System Administration, Chapter 4, “General Maintenance Tables”.
1 |
In the Command with parameters field, enter the command you want Stat to run. |
NOTE: System administrators can restrict user access to certain servers at the service domain level. The servers displayed in the Server field drop-down list may be limited if the server access of the current user has been restricted. For more information, see Stat System Administration, Chapter 3, “Stat Security.” |
3 |
Click Interpret >>. |
4 |
5 |
Click OK. |
To view the history of any automatic step, select it and click History. This opens the Migration Step History window, which displays a record of each time Stat successfully executed the command. These records display the date and time the step was run, the user who ran it, and what parameters were used.
To view the log for the step, click Log. To print the history table, click Print. To export it to a file format, click Export.
2 |
Select Complete for each step that Stat performs successfully. |
3 |
(Optional) Complete any manual steps, or perform them at a later time as required. Then select Complete for each step you perform. |
NOTE: Until a post migration step has been marked as either Complete or N/A (non-applicable or not applied), the migration will have a status of Wait for Post Step in the Migration Console. Once all the post migration steps have been marked as Complete or N/A, the status of migration will change to Complete. |
4 |
Click OK. |
The process is the same for migration of all types of archive sets.
When you want to perform a migration that requires approval, or you want to flag an archive set for a mass migration, the first step is to mark the archive set for migration. This is done either by individually selecting the Ready to Migrate option on the Archive Sets tab of the CSR window, and then selecting the environment(s) that you want to target, or by marking multiple archive sets in the Ready to Migrate window.
2 |
3 |
Click Migration Target. |
4 |
In the table on the right side of the window, select Migrate for each environment that you want to designate as a target environment. |
NOTE: In the table displayed in the right section of the Target environments window, distribution environments and their associated distributed environments are designated by small blue and yellow icons, respectively. When you select Migrate for a distribution environment, all the environments on its distribution list are selected as well. Also, you cannot select a distributed environment without selecting its distribution environment as well. |
5 |
Click Premigration List to view a checklist of any actions you should take before migrating the archive set. |
7 |
TIP: If you later decide you do not want to migrate to a particular environment, deselect it in the Target Environments window. When you click OK or Apply, any approval requests that were generated the first time are deleted. |
1 |
Select Migration Management | Archive Sets - Ready to Migrate. |
2 |
In Module field, select the change management module you are using. |
3 |
In Service Domain field, select the service domain of the archive sets. |
4 |
In Environment field, select the migration target environment of the archive sets. |
5 |
In Release field, select a release label. Stat retrieves archive sets that have been assigned to that release. |
6 |
(Optional) Deselect Ready to Migrate for any archive set that you do not want to be marked for migration. |
7 |
Click OK to save the archive sets as Ready to Migrate. |
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 transfer, select Rejected. |
3 |
c |
You can also approve the migration of an archive set in the Target Environments window of the CSR.
2 |
4 |
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 (Generic Applications) .
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 and Oracle Apps patch applications. For more information, see the book Stat System Administration, Chapter 7, “Email Configuration”.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center