Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Physical File Locking Option

Physical file locking works in conjunction with Stat logical locking. When set up appropriately, physical file locking prevents developers from modifying file objects that have not been locked in a CSR and assigned to them. Stat does this by allowing developers to modify only file objects that are in their working directory. Once a file is locked and assigned to a developer, the developer can only use Stat to migrate the file to their working directory as well as all source directories. This enforces that all changes to the file objects are documented and orchestrated through Stat.

Your system administrator defines the scope of the physical file locking. Source file locations for file types, specific users, as well as for entire environments can be excluded from physical locking.

Associating Objects with CSRs (Oracle Applications)

If a change request requires modifications to objects, you access and work with these objects in a CSR. The CSR becomes the logical grouping of all the affected objects.

Remember that objects are associated with CSRs as opposed to users. In order to lock, archive, or migrate an object, you must first associate it with a CSR. The modifications that you make to objects are still made in the Oracle Applications environment. Quest® Stat® simply provides tools that manage and track those changes.

You can manually associate objects with a CSR, or you can use the CSR Read Wizard, which associates file objects associated with another CSR

To associate objects with a CSR, first select the Oracle Applications Tab.

Oracle Applications Tab

The Oracle Applications tab feature tools that connect directly to your environments and file servers. Because the functionality behind these tabs is specific to a development environment, they are also service domain-specific. When defining a service domain, your system administrator determines which change management tab, if any, is displayed on its CSRs. Access to these tabs should be restricted to developers and migrators. For more information on security settings, see the Stat System Administration Guide, Chapter 3, “Stat Security.”

In order to associate objects with a CSR, you must specify the environment you want to copy them from. This is done first by opening the CSR window and selecting the Migration Path tab.

Selecting Migration Paths

In Quest® Stat®, migration paths are logical groupings of environments that serve as road maps for object migrations. They are set up by your system administrator.

Your system administrator creates migration paths based on your Business needs. For different situations you have different paths.

To select a migration path:
1
Open the CSR window and select the Migration Path tab.
2
In the Migration Path drop-down, select the appropriate migration path. The displayed paths vary, depending on the service domain. You should select the path most suited to your current needs.
* 
IMPORTANT: If a CSR is assigned to a workflow that specifies a migration path, that path is the default path displayed and cannot be changed. For more information on workflows, see Change/Service Requests . For more information on migration paths, see Documenting Migrations and Process Requests (Oracle Applications) .
3
Click the Select Default Developer field and select the developer assigned to most of the objects in the CSR. You can assign different developers to different objects, but this is the person that the objects are assigned to by default.
4
(Optional) If you want to associate the CSR with a version control management system (VCM) record, select the record you want in the VCM Repository field
This field is enabled only if your system administrator has defined at least one VCM record in the VCM Connection Maintenance table. It lists all the currently defined VCM records. After you add objects to the CSR, this field is disabled and you cannot select a different VCM record.
5
Click Generate Path.
Stat displays a graphical representation of the migration path. Also, additional tabs appear on the window, including Patches, Process Request, Objects, and Object Management.

Each drum represents an Oracle Applications environment. This includes the file directories that the environment uses for each of the defined file types. Your system administrator determines which environments are designated as Base and Development. The original, “pre-change” archive of the objects in the CSR is taken from the Base environment and its designated source file locations. The Development environment is where you change the objects.

For more information, see About Archive Sets .

After selecting a migration path, select the Objects tab.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation