立即与支持人员聊天
与支持团队交流

Stat 6.2 - 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 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: stat.conf Configuration Appendix: Custom Report Files

Updating CSR Migration Paths with Additional Environments

You can add environments to existing migration paths that are already associated with CSRs. You then have the option of updating the migration path on selected CSRs to include the new environments.

* 
IMPORTANT: Be aware of the following:
•
Although you can add and remove environments from migration paths, you can only update the migration paths of existing CSRs after adding environments, not after removing them (see 2nd bullet below). Furthermore, you cannot update the migration paths of existing CSRs after replacing environments (i.e., removing one environment and adding another in its place).
•
Environments can be removed from the migration path maintenance table. However, removing an environment from a migration path will only be reflected on newly created CSRs. The environment will not be removed from existing or closed CSRs.
To add environments to CSR migration paths:
1
Open the migration path diagram you want to add an environment to.
2
Follow the instructions in the section Migration Path Diagram to add environments to the migration path.
3
Click Add new env. to CSR.
Stat displays a list of any open CSRs currently associated with the migration path. You can select the CSRs you want to update. You can also opt to copy the objects from the Base or Development environment to the newly added environments on the migration path.
4
Select the Update option for each CSR you want to update.
5
Optionally, select the Update Object List option if you want to copy the objects from either the Base or Development environment to the newly added environments. Then select Base or Dev.
6
Click OK.

PeopleSoft Migration Path Maintenance

The PeopleSoft Migration Path Maintenance table defines migration paths used in the PeopleSoft change management module. Migration paths define the progression of objects from one environment to another. When users add objects to a CSR, they must first select a migration path.

For more detailed information on migration paths, see the book, Change Management for PeopleSoft, Chapter 1, “Object Management.”

When defining migration paths, keep in mind the following:

•
Environments cannot be listed on the path more than once
•
The environments defined as Base, Development, and Distribution must also appear on the path. It is not required that they appear as environment 1, 2, and 3, but they must appear somewhere.
•
Environments connected to a distribution environment (i.e., the distributed environments) should not appear in any other migration path. This is because objects are not locked in the connected environments and overwrites could occur if the same objects exist in other environments.
•
Environments cannot exist on migration paths of different service domains. An environment cannot be shared by multiple service domains.
•
If you attempt to remove from a migration path an environment that is used in a workflow transfer rule, Stat displays a warning message. If you proceed in removing the environment, Stat automatically deletes the transfer rules from any workflow in which the environment is used.
•
An environment can exist in multiple migration paths in a service domain
•
Service domains and environments have a one-to-many correlation

PeopleSoft migration path security is controlled by the following user class rights:

•
PeopleSoft Migration Paths - Add
•
PeopleSoft Migration Paths - Edit

The PeopleSoft Migration Path Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | PeopleSoft Migration Paths

The following table defines the fields (columns) in the PeopleSoft Migration Path Maintenance window.

Value
Description

Active

If selected, activates the value in stat

Migration Cd
(Key Value)

A 1-10 character code that uniquely identifies this migration path

NOTE: Special characters are not allowed, including:
~ ‘ “ * % ( ) ,

Description
(Required Value)

A 1-35 character description of the path

Base Object Source
(Required Value)

The Base environment from which the base archive set is created

Development
Environment
(Required Value)

The environment where development takes place

Last Update
(Read Only)

The date and time that this record was last updated

Update By
(Read Only)

The user who last updated this record

Stage Database

The default PeopleSoft staging database.

Migration Path Diagram

After you have specified the migration code and description, click Apply to save your work. Then select the migration path and click Template.... This opens the Migration Path Definition window. The left section of the window displays a list of each environment that can be added to the new migration path. The right section of the window is where you arrange the icons to create a graphical diagram representing the sequence of the migration.

* 
NOTE: It is recommended that you have the basic design of your migration path diagram in place before you build it in the Migration Path Definition window. This avoids the time-consuming process of rebuilding a diagram if mistakes or oversights occur.
To create a migration path:
1
In the left section of the window, click and hold on the first environment of the migration path. Then drag into the right section of the window to where you want to place the graphic and release the mouse button.
2
Following the sequence of the migration path, place the other environments in the migration path in the diagram.
Environments are labeled according to the order in which they are placed in the diagram. The first environment you place in the diagram is labeled “1”, the second “2” and so on.
3
Right-click on the graphic representing the base environment in the migration path. Then in the pop-up menu, select Set base environment.
4
Right-click on the graphic representing the development environment in the migration path. Then in the pop-menu, select Set dev environment.
5
(Optional) If you want to designate a distribution database, right-click on the graphic representing the distribution environment in the migration path. Then in the pop-up menu, select Enable distribution environment.
For more information, see Defining Distribution Environments .
6
(Optional) If you want to modify the migration path, right-click the graphic representing the environment you want to change and do any of the following:
•
To designate the environment as the new base environment in the migration path, select Set base environment.
•
To designate the environment as the new development environment in the migration path, select Set dev environment.
•
To switch the environment’s place in the migration path with another environment, select Swap environment number. Then in the prompt select the number of the environment you want to switch and click OK.
•
To remove the environment from the diagram, select Delete environment.
* 
NOTE: After deleting an environment, you may need to adjust the order numbers of the remaining environments in the diagram to make them consecutive. Stat does this for you automatically when you save.

Defining Distribution Environments

Distribution environments allow users to migrate objects to multiple environments distributed over a network at one time. When a user migrates an archive set to a distribution environment, Stat automatically migrates the archive set to a list of connected environments.

You define distribution environments at the migration path level. The first step is to designate certain environments in a migration path as distribution environments. Then you determine which environments you want to connect to them. For example, let’s say you have ten production environments. All of your development work is done centrally, and when ready, changes are migrated out to all the production environments at the same time. Most likely you would define the local or ‘in-house’ production environment as the distribution environment on the migration path and connect it to the nine other production environments.

Although connected to the distribution environment, the other environments are not represented graphically and are not technically part of the migration path. This means that objects cannot be locked in the environments connected to a distribution environment. Likewise, objects can only be migrated to them; you cannot archive objects from these environments.

In order for Stat to migrate PeopleSoft proprietary objects automatically to a distribution environment and its associated environments, the CLI Auto-Migration option must be activated for the distribution environment, as well as each connected environment to which you want to migrate PeopleSoft proprietary objects. If the CLI Auto-Migration option is activated for just some of the environments in the distribution list, Stat migrates PeopleSoft proprietary objects to the activated environments and ignores the rest. For more information on activating the CLI Auto-Migration option, see PeopleSoft Environment Connection Maintenance .

For more information on distribution environments, see the book, Change Management for PeopleSoft, Chapter 3, “Object Migrations.”

* 
CAUTION: Because objects are not locked when migrated to the environments connected to a distribution environment, it is recommended that you do not include these environments in any other migration path. This eliminates the possibility of two developers accidently overwriting each other’s work.
To define a distribution environment:
1
Open the migration path diagram containing the environment you want to designate as a distribution environment.
2
Right-click on the graphic representing the distribution environment in the migration path. Then in the pop-up menu, select Enable distribution environment.
An icon is displayed next to the environment graphic signifying its status as a distribution environment.
3
Double-click the distribution icon.
Stat opens the Distributed database window.
4
In the left section of the Migration Path Definition window, select the environment you want to add to the list of distributed environments.
5
Click Add.
6
Repeat steps 4 and 5 for each environment you want to add.
7
If you want to deactivate an environment, deselect Active.
When a user migrates an archive set to a distribution environment, Stat migrates the objects only to the active environments in the distribution list and ignores the rest. However, this setting can be changed on the CSR at the time of migration, in which case deactivated environments are reactivated only for that CSR.
8
Click OK.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级