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

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

Status Rules

Status rules let you apply restrictions to a CSR while it is in a particular status, such as the queue(s) that it can belong to, whether objects can be added or locked on a CSR and what environments objects associated with the CSR can be migrated to. For Oracle Applications, you can also limit the environments that can have patches applied to them.

If you select {None}, no migrations can take place while the CSR is in the particular status. If you do not select an environment, the objects can be migrated to any of the environments in the list.
If you select {None}, no archive sets can be created while the CSR is in the particular status. If you do not select an environment, archive sets can be created in any of the environments in the list.
If you select {None}, no patches can be applied while the CSR is in the particular status. If you do not select an environment, a patch can be applied to any of the environments in the list. The patch application option is not used for workflows in the PeopleSoft and generic applications modules.
8
Click OK or Apply to save your work.

Copying Workflows

If you want to copy a workflow to another service domain, associate a workflow to more than one CSR type, or if you want to create a new workflow that closely resembles an existing workflow, you can make a copy of that workflow and then modify it as needed.

You can associate a copied workflow with a different CSR type. However, you must associate it with a CSR type that is associated with same CSR statuses as the original CSR type. To copy a workflow to another service domain, the target service domain must include a CSR type that is associated with the same set of CSR statuses as the CSR type in the original workflow.

When copying a workflow, you can also select a different module and migration path. However, if you select a different migration path, this may conflict with any workflow rules you copy that require migrations to specific environments. When this is the case, you can either remove the migration requirements from the copied workflow rules, or you can update the copied workflow rules by referencing the new environments.

The CSR Type field lists all the CSR types in the selected service domain that are associated with the same set of CSR statuses as the CSR type in the original workflow. If there are no matching CSR types, the CSR Type field is blank and you cannot copy the workflow to the selected service domain.
3
In the CSR Type field, select the CSR type you want to base the copied workflow on.
5
(Optional) In the Migration Path field, select the migration path you want to assign to the workflow.
6
7
Deselect the Copy Status Rules or Copy Transfer Rules options if you do not want to copy either the status rules or transfer rules.
8
Deselect the Exclude Migr. Env option if you want to copy status and transfer rules that require migrations to specific environments.
10
Click OK when done.
The copied workflow is displayed in the Workflow Maintenance table. If you copied the workflow to a different service domain, select that service domain in the Domain field to see the copied workflow. At this point, you can open the workflow in the Workflow Template window and modify the template diagram and workflow rules as needed.

Configuring the Stat Central Agent

Starting and Stopping the Stat Central Agent

The Stat Central Agent is responsible for automating necessary but time-consuming work, such as generating and printing reports, sending email messages, archiving objects, and maintaining specific database parameters.

The Stat Central Agent is designed to run behind-the-scenes with minimal supervision on the part of system administrators. However, you can manually start and stop the Stat Central Agent when circumstances demand it.

You can run the Stat Central Agent on either a Windows or a Unix platform. If configured properly, the Stat Central Agent can also be run as a Windows Service. For information, see Stat Install Notes.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation