Chatta subito con l'assistenza
Chat con il supporto

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

Synchronizing Your Development Workspace

It is good practice to synchronize your development workspace with your base archive set. This ensures that you are making changes to the correct version of the objects. This is true of all your environments. As you make changes, you should create interim archive sets that document those changes and then migrate them to the appropriate environments. The migration process is virtually the same, regardless of the type of archive set.

The development workspace is where you make the changes. For data objects, this is the Development environment. For file objects, it can be either the Development environment’s source file locations or the assigned developers’ working directories. It is recommended that each developer make changes to file objects in their own working directories so that the changes can be documented and controlled. System administrators can enforce that developers modify objects only in either their working directories or in the source file locations.

Migrating File Objects

When an archive set contains file objects, the file archives are stored in the Stat Repository. When you migrate the archive set to an Oracle Applications environment, Stat copies the file archives from the Stat Repository to the source file locations defined for the target environment. If the file objects already reside in any of these source file locations, Stat replaces each existing instance with the archive copy. If the files exist in none of the source file locations, Stat either copies the files to all the source locations defined for the target environment or copies the files to the designated default location. These options are set up by system administrators when configuring the target environment.

To migrate file objects in an archive set to the developers’ working directories, you migrate the archive set to the Development environment. Stat gives you the option of migrating the file objects to the Development environment’s source file locations, the developers’ working directories, or to both. To migrate an archive set taken from the Development environment to the developer’s working directories, or vice versa, the migration must be initiated from the Object Management tab, not the Migration Path tab.

If two or more environments on a migration path share the same source file locations for a particular file type, whenever you migrate an archive set that contains file objects of that type to one of the environments, by default the file objects are also migrated to any other environment that shares the same source file locations. For example, if the Development environment and Quality Assurance environment share the same source file locations for COBOL file objects, and you migrate an archive set containing a COBOL file object to Development, Stat documents that the same file object was also migrated to Quality Assurance. This eliminates the time consuming process of having to perform multiple migrations in order to document the migration of the same file objects to each environment on the migration path.

* 
NOTE: Unix and Windows-based file servers have different formats for ASCII type file objects. Accordingly, when you migrate a ASCII type file object via SFTP, the Stat Central Agent checks its destination file server. If the server is Unix, the agent converts the file to the Unix ASCII format, which means singly occurring carriage returns followed by linefeed characters are converted to linefeed characters. If the destination server is Windows, the agent converts the file to the Windows ASCII format, which means singly occurring linefeed characters are converted to carriage returns followed by linefeed characters. In either case, the size of the migrated file may be smaller or larger than it was before it was migrated.

Migrating Data Objects

As with file objects, data object definitions are archived in the Stat Repository. When you migrate an archive set that contains data objects, Stat copies the data object definitions from the Stat Repository to the target environment. If the data object already exists in the target environment, Stat replaces that object definition with the archived copy using the delete and insert method.

Migrating to Distributed Environments

When you migrate objects to a distribution environment, by default Stat migrates those objects to all the environments on its distribution list. However, you can opt to exclude certain environments from the migration.

When defining a migration path, system administrators designate distribution environments and add other environments to their distribution lists. For example, let’s say you have ten production environments and each one physically resides in a different location. 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 your system administrator would define the local or ‘in-house’ production environment as the distribution environment 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 on a distribution list. Also, objects can only be migrated to them, not from them.

* 
TIP: Because objects are not locked when migrated to the environments connected to a distribution environment, it is recommended that your system administrator not include these environments in any other migration path. This eliminates the possibility of two developers accidently overwriting each other’s work.

Graphically, distribution environments are designated by a small icon displayed to the left of the environment graphic, as shown below:

To view a listing of the environments connected to the distribution environment, double-click on the distribution icon. Stat opens the Distributed Environments window, which shows a list of all the environments connected to the distribution environment.

In this window, you can deactivate any environment you do not want to include in a migration. This way, when you migrate an archive set to a distribution environment, Stat migrates the objects only to the active environments in the distribution list. To deactivate all the environments, click Set All Inactive. If you want to reactivate an environment, you can do so at any time by selecting the Active check box, or if you want to reactivate all the environments, click Set All Active.

Also, Stat does displays an error message if it successfully completes a migration to a distribution environment but not to one or more of its associated environments (which would be the case if, for example, the password to one of the environments was incorrect). Instead, this information is displayed in the Migration Details window. For more information, see Documenting Migrations and Process Requests (Oracle Applications) .

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione