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

How to inform Stat about the available PT servers

We will have to configure this from Windows client.

•
We have added new user rights to work with PT servers. You should find these two new rights under the PS Migration Mgmt group
•
Right to edit a PT server
•
Right to add a PT server
•
In the Stat Object Type Maintenance window, we have added another tab called PT Servers.

How does the test connection of PT servers work?

The Stat Central Agent tries to establish a SSH connection the to PT server. If the connection is successful, then Stat tries to establish if there's a PeopleTools installation present in this PT server. This is done by checking the HKEY_CURRENT_USER\SOFTWARE\PeopleSoft\PeopleTools\Release8.40 registry key.

If Stat is able to find this key, then you should see the below message.

“Successful connection to server PT Server1, with path PT installation server status: Verified”

The status would have been UNABLE TO VERIFY if the registry key was missing.

An untested or unverified PT server can still be used for migration. The testing feature is only available for the Stat Admin to verify the usability of the configured PT server.

How to map PT servers with individual users

1
This information will be configured in User Access Information at Maintenance > Security Settings > User Maintenance > Select user > User Access Information.
2
We have created another tab PT server assignment. Here users will have the option to inform Stat about which PT server the user wishes to perform the migration for a particular version.
3
This tab will contain a table with the following columns
 
Value
Description

Active

Indicates if this server is activated in Stat

Server name

The PT server that you want to add for this user

Directory

The directory in the PT server remote machine where PeopleTool utilities like Application Designer (pside.exe) and Data Mover (psdmt.exe) are present. The admin needs to give the canonical path in this directory. Do not use relative path or environment variables while using providing the path here.

Avoid adding any trailing forward or backward slash here.

Directory Log

This is where all the logs related to different PeopleTools CLI operations will be stored.

Avoid adding any trailing forward or backward slash here.

PS Config File

This is the.cfg file which will be imported during the migration. This file should reside in the PT server which is mapped to this user.

Updated By

The user who updated this entry

Last Update

Date of the last update operation performed

A single user will not be able to have multiple active PT servers for the same version.

Using same PT server for migration of multiple PT environments

Typically you cannot use PeopleTool utilities belonging to different versions on the same machine as all PeopleTools installations, regardless of their version, store their metadata in the same registry keys. You can find these keys in HKEY_CURRENT_USER\SOFTWARE\PeopleSoft\PeopleTools\Release8.40

Similarly, PeopleTools Configuration Manager also fetches its metadata from a centralized location which is not specific to its version.

Windows Client mitigates this by asking for the version specific .cfg file from the Stat Admin. This cfg file is imported during the migration by the windows client using the pscfg.exe utility of that specific version. Once the migration is over, Windows Client reverts back the PeopleTools configuration to its original configuration.

When a user is migrating using the Web Client, the same workflow is replicated by the Stat Central Agent. The Stat Central Agent also gets the .cfg file which is provided by the user in PT Server Assignment tab. This file is them imported by the Central Agent using the pscfg utility. Once the migration is concluded, the original cfg file is restored.

 

* 
NOTE: A PT server can be any windows machine that has PeopleTool utilities like Application designer. This machine must have SSH enabled with support for either SSH-1 or SSH-2.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione