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

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

Adding Custom Reports

All Stat reports are defined by corresponding .jrxml files. Custom reports are created by formatting a .jrxml file using the 3rd party reporting tool Jaspersoft Studio. You can create a report file from scratch, or you use a copy of an existing file as a starting point. For more information on creating report files, see Appendix: Custom Report Files .

After you have defined the .jrxml file that is the basis for your custom report, you can add it to the Stat Report Library.

To add a custom report:
1
Click New.
This opens the Define New Custom Report window.
2
Click Load and select the custom report .jrxml file you want use as the basis for the report.
The file name is displayed in the Report field without the extension. This file name must be unique. This is the name that the agent searched for to compile the report.
3
Enter a short description of up to 40 characters.
This description is displayed in the Stat Report Library.
4
Enter a long description of up to 250 characters.
This description appears in the Presentation Preview and can give the user an idea of what data will appear on the report or when to use this report.
5
Select a report category or enter a new category.
You can add a custom report to a predefined category, or you can add it to a new category that you create.
6
Select a report format type.
The format is a graphical representation of what the report will look like displayed in the Presentation Previews.
7
Set the security level for the report (1-99 with 1 being the least secure).
8
Click OK.
Stat adds the report file information to the Stat Repository and loads the report to <stat_home>report\custom\format on the Stat Central Agent file structure.

Turning off the Emailing of Blank Reports

Stat reports are configured to bring up a blank page with a report title if there is no data. This is intended to demonstrate to the user that the report actually ran. Some sites however may not want Stat to email blank reports.

Stat report files (.jrxml files) are stored on the Stat Central agent under Stat_home/report/%category%/format. The subfolder they are stored under is named the same as the Report Category drop down listing on the Stat Report Wizard. Under each category subfolder the .jrxml files are located in the /format folder.

Each report has a file name that starts with dw_ and has a .jrxml extension. The linkage between the file name and the report name is in the STAT_REPORT_DEFN table.

Select DESCR, DW_NAME, CATEGORY from STAT_REPORT_DEFN where DESCR like '%Report name from Stat Report Wizard%' will give you the file name that needs to be modified.

As with customized reports, if you modify the .jrxml file in situ it may be overridden the next time you upgrade Stat. If this is a concern, then follow the procedure for creating a custom report which places a copy of the .jrxml file in the stat_home/report/custom directory/format folder and add the custom report to the Stat repository.

To turn off the emailing of blank reports:
1
Open the .jrxml file with Jaspersoft Studio.
2
Right click on the report name under Outline view and choose Show Properties.
3
In Report Properties View, open the Advanced tab, scroll down to the option When No Data and change the value from All Sections, No Detail to No Pages.
4
Close the Properties Window and save the report.
5
If there is a corresponding file name with a .jasper extension in the folder you save the file in, delete the .jasper file.
This is a compiled report file. The Central agent will recreated the .jasper file with the new properties the next time the report is run.
6
Run the scheduled report in Stat.
If there is no data on the report the Central agent will log a message:
“Job ID:xxx generated empty report. Email has been skipped.”

Version Control Management Connection Maintenance

You can integrate Stat with your 3rd party version control management (VCM) system. This allows you to save your file objects from a VCM repository directly into Stat to control the process and the migration of the objects. Currently Stat supports the following VCM platforms: SVN, PVCS, Perforce, and CVS.

VCM Maintenance security is controlled by the following user class rights:

•
3rd Party VCM Connection - Add
•
3rd Party VCM Connection - Change
* 
IMPORTANT: Before connecting to a VCM system, be aware of the following:
•
All Stat VCM functionality is performed by the Stat Central Agent. Except for P4 and TFS, this means that for the connection to be established the machine hosting the Stat Central Agent must have a client copy of the VCM software installed and that the Stat Central Agent must be running.
•
For Stat to archive file objects from a VCM repository, the subdirectories where the object types reside in the repository must match the subdirectories in the source environments. For example, if *sql files reside in a .../admin/sql subdirectory in the source environment, the sql files in the VCM repository must also reside in a .../admin/sql directory.

The 3rd Party Version Control Connection maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | General | VCM Connect.

To connect to a VCM repository:
1
In the 3rd Party Version Control Connection maintenance table, click New.
2
Specify unique code which identifies the VCM repository.
3
Enter a description of the VCM repository.
4
Select the type of VCM platform you are connecting to.
Options include CVS, PVCS, SVN, P4, GIT, and TFS.
After defining the VCM repository, you must define the required connection parameter values that allows Stat to connect to the VCM repository.
Click Apply to save your work.
5
Click Setup.
This displays the VCM Connection Setup window where you specify the connection parameter values. The list of parameters varies depending on the type of VCM platform you are connecting to.
6
Enter the parameter values required to establish a connection to the VCM repository.
See the following tables for a description of each parameter. Which parameter values are required will depend on the configuration details of your VCM repository.
CVS Parameters
Parameter
Description

CVS_CONNECTION_TYPE

CVS connection type

CVS_HOST

CVS host machine

CVS_MODULE

CVS module

CVS_PASSWORD

CVS password

CVS_PORT

CVS host port

CVS_REPOSITORY_PATH

CVS root directory

CVS_RSH

CVS protocol used when connection type is ext

CVS_TAG_BRANCH

CVS tag or branch

CVS_TAG_BRANCH_FILE

CVS entity filename (full path) to use for retrieving list of tag/branch labels

CVS_USERNAME

CVS username

PVCS Parameters
Parameter
Description

PVCS_LABEL

PVCS revision label

PVCS_LABEL_FILE

PVCS entity filename (full path) to use for retrieving list of revision labels

PVCS_PASSWORD

PVCS password

PVCS_PROJECT_DATABASE

PVCS project database

PVCS_PROJECT_PATH

PVCS current project

PVCS_PROMO_GROUP

PVCS use label for promotional group

PVCS_REPOSITORY_PATH

PVCS entity folder

PVCS_USERNAME

PVCS username

P4 Parameters
Parameter
Description

P4_CLIENT

Perforce client/workstation

P4_DEPOT

Perforce depot path (ex. //depot)

P4_PASSWORD

Perforce password

P4_PORT

Perforce host port

P4_PROJECT_PATH

Perforce project path relative to depot (ex. //depot/project1)

P4_REVISION

Perforce revision (if left blank, latest revision is used)

P4_REVISION_USING

Perforce revision can be retrieved using revision, label, or changelist

P4_SERVER

Perforce server hostname

P4_TICKET_PATH

Perforce ticket path (ex. c:\\p4tickets.txt)

P4_USERNAME

Perforce username

 
SVN Parameters
Parameter
Description

SVN_ALT_CONFIG_DIR

SVN configuration directory

SVN_CONNECTION_TYPE

SVN connection type

SVN_HOST

SVN host machine

SVN_PASSWORD

SVN password

SVN_PORT

SVN host port

SVN_REPOSITORY_PATH

SVN repository directory

SVN_REVISION

SVN revision

SVN_USERNAME

SVN username

Git Parameters
Parameter
Description

GIT_CONNECTION_TYPE

GIT repository connection type (ssh://, http://, https://)

GIT_HOST

Hostname of the repository

GIT_PORT

Port number (Optional)

GIT_REPOSITORY_PATH

Path to the remote repository

IT_PROJECT_PATH

An optional path to a directory under the main repository (Optional)

GGIT_TAG_BRANCH

Specific branch or tag. If left blank, objects are pulled from master branch. (Optional)

GIT_USERNAME

Username to connect to the repository

GIT_PASSWORD

Password

TFS Parameters
Parameter
Description

TFS_CONNECTION_TYPE

TFS connection types (http or https)

TFS_HOST

Hostname of the machine housing the repository

TFS_PORT

Port number

TFS_COLLECTION

The TFS project collection including the virtual directory, like /tfs/DefaultCollection

TFS_SERVER_PATH

The mapping server folder including $/ and project, like $/Project/folder.

TFS_USERNAME

Usually the network username that has access to the repository

TFS_PASSWORD

Network user password

TFS_HTTP_PROXY_URL

The url to the proxy server including the port, like http://server:9191

TFS_HTTP_PROXY_USERNAME

The proxy server username

TFS_HTTP_PROXY_PASSWORD

The proxy server password

TFS_VERSION_USING

Has 3 values: Label, Changeset, or LatestVersion.

•
By default files are retrieved from the repository by LatestVersion (T).
•
If Label is used, files are retrieved from a specific Label in the repository.
•
If Changeset is used, files are retrieved from a specific Change Set (C11 for example)

TFS_VERSION

Used to retrieve from a specific Label or Changeset.

•
If TFS_VERSION_USING is set to Label, set TFS_VERSION to a specific Label from which files are retrieved.
•
If TFS_VERSION_USING is set to Changeset, set TFS_VERSION to a specific Change set from which files are retrieved.
* 
IMPORTANT: When users add file objects from a VCM repository to an archive set, a VCM-specific field is displayed in the Archive Set window (Revision for SVN and P4, Tag/Branch for CVS and Git, Label for PVCS, and Version for TFS). In this field users can override the default value specified by system administrators by specifying the particular version of the objects they want to add from the VCM repository. If left blank, Stat adds the most recent version of the objects in the repository.
7
Click Apply.
8
Click Test Connect to make sure that you have entered all the information correctly.
This makes Stat establish a connection to the VCM repository. If successful, Stat immediately disconnects from the repository and displays a “Connection Successful” message. If Stat is unable to connect, it displays an error message.
9
Click OK.

Service Domain-Specific Maintenance

•
Working With Service Domains
•
Activity Code Maintenance
•
Application Maintenance
•
Application Environment Maintenance
•
Auto Task Maintenance
•
Business Rule Maintenance
•
CSR Log Topics Maintenance
•
CSR Priority Maintenance
•
CSR Type and Status Maintenance
•
Customer Priority Maintenance
•
Generic Application Migration Path Maintenance
•
PeopleSoft Migration Path Maintenance
•
Oracle Application Migration Path Maintenance
•
Pre and Post Migration Steps
•
Release Management Maintenance
•
Template Maintenance
•
Queue Maintenance
•
Workflow Maintenance
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択