Chatta subito con l'assistenza
Chat con il supporto

Stat 7.0 - 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 Enabling Web Client to perform PeopleSoft migrations 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: Oracle Agent: Stat.conf and log4j2.xml configuration Appendix: Custom Report Files

Pre and Post Migration Steps

The Pre and Post Migration Steps Maintenance table defines the actions to be taken on certain types of objects in an archive set before or after it has been migrated. Pre and Post migration steps are either manual or automatic, i.e., they are triggered either manually by users or automatically during Stat migration.

The Pre and Post Migration Steps Maintenance table defines actions that should be taken before an archive set is migrated.

Pre and post migration steps security is controlled by the following user class rights:

•
Migration Steps - Add
•
Migration Steps - Edit

The Pre and Post Migration Steps Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Pre and Post Migration Steps.

Value
Description

Active

If selected, activates the value in Stat

Step Type

Defines whether step is Pre or Post

Migration Step
(Required Value)

The type of step. Options include Custom Command, Run DMS, Create Project Build Script, Compile Cobol, and Manual Step.

Auto

If this check box is selected, the step will be triggered automatically. Only Custom Command steps can be set to run automatically.

Description
(Required Value)

The name of the step

Object Class
(Key Value)

The class of object for which the step is defined. Options include data objects and file object for all three change management modules supported by Stat, as well as PeopleSoft Proprietary objects.

Object Type
(Key Value)

The object type the step is associated with (if any)

Run Order
(Required Value)

A number that determines the sort order for the step on the pre and post migration checklist. Steps with a lower number are executed first.

Target Environment

The target environment the step is associated with (if any)

Include Distributed

If this check box is selected, the step is also propagated to each distributed environment.

Run Once Per Env

If this check box is selected, the step will be deselected by default when it was already executed in the past.

User would still be able to add such step to the migration

Last Update
(Read Only)

The date and time that this record was last updated

Updated By
(Read Only)

The user that who updated this record

Step Types

Stat offers the following types of steps:

Custom Command

User can define custom command

 

Run DMS

Run PeopleSoft Data Mover script

PeopleSoft only

Manual Step

Step that is run outside of Stat

 

Create Project Build Script

Generate/execute PeopleTools Project Build script

PeopleSoft only

Compile Cobol

 

PeopleSoft only

Custom Command steps can be triggered automatically by Stat or manually. Other steps types are triggered manually.

Predefined Steps

Stat has three predefined PeopleSoft pre and post migration steps: Create Project Build Script, Compile COBOL, and Run DataMover Script. These steps are triggered manually by the migrator.

Create Project Build Script

When this step is triggered, Stat logs into the target PeopleSoft environment of the migration and creates the project build script for the project used during the migration. Stat uses the command line statement to launch PeopleSoft. It uses the PeopleSoft build settings from the Windows registry to generate the SQL script for create or alter.

Compile COBOL

When this step is triggered, Stat launches the PeopleSoft COBOL Compile program, either CBLBLD for NT or pscbl.mak for Unix. When executing this step, Stat uses the following file server variables:

•
The definition of the file server operating system (NT, Unix, or Mainframe).
•
The location of the COBOL Compiler for each file server that PeopleSoft COBOLs reside on. This location is defined in the File Servers tab of the Object Type Maintenance window.
•
The %PS_HOME% location for the COBOLs to be compiled. This value is taken from the Windows registry entry for PS_HOME. All the COBOL source programs residing in %PS_HOME%\src\cbl are compiled.
•
For NT servers, The location where the compile is to take place. By default, C:\temp\compile.
•
For Mainframe servers, the name and location of the JCL file used to upload cobols

Except for the definition of the operating system, all of these settings can be changed at the time of execution.

Run DataMover Script

When this step is triggered, Stat logs in to the PeopleSoft environment (by default, the target environment of the migration) using the user’s PS operator ID and password and runs the selected Data Mover script. By default, Stat uses the .dms file in the subdirectory “\script,” which is appended to the PeopleSoft Home Directory (PS_HOME) defined in the PeopleSoft Configuration Manager. All of these settings can be changed at the time of execution.

Defining a Custom Command

You can define custom commands for pre and post migration steps. These are operating system commands executed by the Stat Central Agent. Commands can be executed locally where the Central Agent is running or remotely on a migration target server via SSH. All drive mappings and file paths are relative to the server where the Central Agent is running. Commands can be triggered automatically during the migration or manually by the migrator.

To define a custom command:
1
In the Pre and Post Migration Step Maintenance window, click New and specify the object class and object type of the step you want to create.
2
Select the type of executed step: Pre or Post.
3
In the Migration Step drop-down list, select Custom Command.
4
Select Auto if you want the step to trigger automatically.
5
Specify a name for the step in the Description field.
6
Select Object Class and Object Type.
7
Select Default Run Order. The step execution order can be changed later during migration initialization.
8
(Optional) Add Target Environment to trigger a migration step for a specific environment.
9
Click Apply to save your work.
10
Click Define Command.
Stat opens the Pre/Post Migration Step Command Editor window.
Pre and Post migration steps can be run locally on the Stat Central Agent machine. Some steps can also be configured to run remotely via an SSH connection.
•
For PeopleSoft and Generic file objects, the step can be run on all defined file locations or on the default file location.
•
For Oracle E-Business objects, the step can be run on all target servers. Note, for each Server, the file server entry has to be defined in Object Type - Server.
Note that in order to run the step remotely, SSH must be configured for the target server.
When defining a command, you can include predefined parameters as well as user and server-based parameters that have been defined in Stat. This provides a convenient way to specify values commonly invoked by operating system commands, such as server names and download directories. In addition, parameters offer a way to secure sensitive information by encrypting values that you do not want visible to users such as passwords.
Predefined parameters specify values used to login into an environment during a migration (database name, user name and password) or to invoke Stat web services (service domain and CSR ID). User and server-based parameters, on the other hand, generally invoke values associated with 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, see the section, Pre/Post Migration Steps Parameters .
* 
NOTE: In the case of Oracle-based environments, predefined parameters also include host name, service name, DB listener port, and TNS entry, and for Oracle Applications environments, APPL_SYS_USERNAME and APPL_SYS_PASSWORD.
11
In the Command field, enter the command you want Stat to run.
If you want to include parameters in the definition of the command, click the location in the command line where you want to insert the parameter. Then select parameter type and double-click the parameter you want to insert. When included in a command, the parameter name is enclosed by two percent symbols (%%), for example, “%%GL_PWD%%.”
Certain users and file servers may have parameters that have been defined specifically for them, or the value of a particular parameter may be different depending on which user or server it is being applied to. When the Stat Command Editor is first opened, the parameters are listed as they have been defined for the local client server and the current user. If you want to include parameters defined for a different server, click the Server defined option. Click the User defined option to insert a user-specific parameter.
12
Stat includes a predefined TARGET_OBJECT_NAME parameter that you can use in custom run commands for objects. When this parameter is present in a command, the step will be executed as many times as the number of migrated objects of that type.
13
To run multiple commands on Unix, separate the commands with a semicolon. To run multiple commands on Windows, separate the commands with “&&”. To run commands on Windows, use “cmd /c” before the command.
14
If the command is still running when the connection times out, no log is attached to Stat. However, you can adjust the 5 second default SSH connection timeout setting. A longer connection timeout setting allows the SSH session to stay connected the entire time the command is being processed, in which case the SSH session log will be attached to Stat.
15
(Optional) In the SSH time-out in seconds field, specify a longer connection timeout amount.
16
(Optional) Specify the command return code condition on which migration will be stopped. When a pre-migration step completes with an error, the entire migration will halt with status “Waiting for Pre-Step.” When a post-migration step completes with an error, then migration will halt with status “Waiting for Post-Step.” To continue migration, a migrator can manually trigger that step or change the status of that step to Completed or Canceled.
17
Click Apply.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione