サポートと今すぐチャット
サポートとのチャット

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

The Options Tab

The Options Tab

The Options tab displays information contained in the Options and Shared Profile sections of the Stat INI file. The database parameters displayed on this tab must be set at startup and are workstation specific.

In the Options tab, you can share database profile records if you want to use a file that resides on the network. This field displays the full path and name of the file you want to use in either a “drive:\directory\file” format or a UNC format (\\servername\share\directory\file).

The Local failover options indicate what action the Stat INI Editor takes if the shared profile (.ini file) is not found. Options include:

•
Yes – The application displays an alert message and then uses the local default INI file instead
•
No – The application halts and displays an alert message

Encryption Key Update

As a general security precaution, you may want to periodically change the encryption key for all the active passwords contained in the Stat database, including Stat user ID passwords, environment and file server passwords, and email server passwords. When the encryption update utility encounters a password for an inactive record that cannot be decrypted, it substitutes a randomly-generated string for the password and issues a warning. When it encounters a password for an active record that cannot be decrypted, it issues an error message and does not complete the update procedure.

* 
CAUTION: Before updating the encryption key, shut down any Stat Central Agents that are running and have all users log out of Stat.
To change the encryption key:
1
Log in to Stat as the SYSTEM user.
2
Select Tools | Update Encryption Key.

Data Replicator

You can use the Data Replicator tool to copy data from one service domain to another, either within the same Stat database or between two Stat databases. This tool allows you to quickly populate new service domains with pre-existing data and to maintain consistency throughout your Stat environment. For example, if you create a new service domain in your Stat production database, you can use the Data Replicator to populate that service domain with data from an existing service domain in your Stat development database.

Access to the Data Replicator should be restricted to system administrators and is controlled by the following user class rights:

•
Data Replication - Inbound
•
Data Replication - Outbound

Note the following before using Data Replicator to copy either business rules or workflows:

•
Both business rules and workflows are keyed on an internal identifier that is unique across the whole Stat environment. It is not service domain unique.
•
When either is copied from a Dev Stat environment to a Prod Stat environment for the first time, there should be no issue given that the Prod environment is empty. From that point forward the internal identifier list may never match again. Therefore, both business rules and workflows require that the Description field be unique.
•
The Data Replicator can be used to copy business rules between environments, or between service domains in the same environment
* 
NOTE: To copy business rules to service domains within the same Stat environment, you can also use the copy function in the Business Rule Maintenance table. For more information, see Copying Rules
•
When business rules are copied, it is your responsibility to double-check the Criteria window after the copy and validate that the rules make sense in the new environment or new service domain. The Data Replicator does not validate that all of the criteria fields are exactly the same between environments or service domains.
•
The Data Replicator can be used to copy workflows between Stat environments, but do not use the Data Replicator to copy workflows between service domains within the same environment. Instead use the copy function in the Workflow Maintenance table. For more information, see Copying Workflows .
•
For workflows, the Workflow Name, Service Domain, CSR Type, and Migration Path Code must be unique
•
When workflows are copied between Stat environments, the assumption is that the CSR fields in the like service domain are exactly the same. The Data Replicator does not do this validation. The user should validate the workflow on the maintenance window after the copy.
To use the Data Replicator:
1
Select Tools | Data Replicator.
Stat opens the Data Replicator tool, which displays a list of all the maintenance tables and CSR information defined in the Stat database. These collections of data are called entities and are grouped into five categories:
•
General Tables – General tables usually affect an application across all service domains. For example, Customers and Departments.
•
Service Domain Specific – These tables are specific to individual service domains. For example, CSR Status.
•
Stat Central Agent – These tables allow you to configure and maintain the Stat Central Agent as well as email
•
Security Settings – These tables are used to manage security settings such as creating new user accounts and user classes
•
CSRs – These tables contain CSR information, excluding associated objects and archive sets
2
In the Destination field, click Connect.
This opens the Connect to Destination Database window, which looks and behaves exactly like the Stat Login window.
3
In the Connect to Destination Database window, log in to the database to which you want to copy data.
If you want to copy data between service domains within the same Stat database you are currently logged into, select that database in the Connect to Destination Database window.
4
In the Source field and select the service domain whose maintenance tables you want to copy.
If you want to copy maintenance tables regardless of service domain, select Any Service Domain.
5
(Optional) If you are want to replicate the data to a service domain that is named differently than the source service domain, select the Copy to Alternative Service Domain option and select the service domain you want.
You do not need to select this option if you are replicating data between databases and the target service domain has the same name as the source service domain.
6
(Optional) Select the Include Dependencies option if you want to copy the dependency data of each entity you select.
Certain entities include information defined in other entities, and you may want replicate all these tables together as a single unit. For example, the Customers maintenance table includes information defined in the Countries and Departments maintenance tables. The Include Dependencies option configures Stat to select these tables automatically when you select the Customers maintenance table. You can de-select any dependency table that you do not want to replicate.
* 
NOTE: Stat does not replicate a record in a maintenance table if that record references dependency data that is not selected for replication and is missing in the target service domain.
7
(Optional) Select the Copy only active records option if you only want to replicate only records that are currently active in each entity you select.
8
Select each entity you want to copy.
To select all the entities, click Select All. To deselect all, click Select None.
9
Click Copy Data.
Entities that were successfully copied are designated in the Status column by a green check mark. Entities that weren’t copied successfully are designated by a red ‘X.’ If you want to clear the copy status of the maintenance tables and make another attempt at copying data, click Clear Status....
To view log entries that were generated during processing, select the Copy Log tab. Data Replicator saves the log file. You can change the location of the log file on the Copy Log tab.
You can filter the log entries so that only information, warning, or error messages are displayed.

Table Dump Utility

The Table Dump Utility is a troubleshooting tool that allows you to dump the contents of a table so that it can be emailed to the Quest Support staff. Support then evaluates the contents of the file in order to find the cause of the problem.

You should use this utility only as instructed by the Quest Support staff. If called for, a Support representative may give you a SQL statement to execute or send you a .sql file that you can upload into the utility. You then execute the statement or file and forward the resulting data (as a .psr file) to Support.

Access to this tool should be restricted to system administrators. It is important to note that the tool bypasses service domain security. This means you could dump data from any service domain, regardless of your security restrictions.

To use the Table Dump Utility:
1
Select Tools | Table Dump Utility.
2
Do one of the following:
•
Enter the SQL statement manually as instructed.
•
Click Open SQL. Then browse for and select the .sql file you want to load.
3
(Optionally) If you entered a SQL statement manually and want to save the statement as a .sql file for re-use later, click Save SQL. Then specify a location and name for the file and click Save.
4
Click Execute.
The data appears in the lower box and a counter shows the system’s progress.
5
Click Export. By default, Stat names the file “tabledmp.psr.”
6
Rename the file and save.
7
Attach the file to an email and send it as instructed by the Support staff.
8
Click Clear.
The SQL statement remains in the upper window.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択