| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Administering: Configuring Master Index Command Line Reports (Repository) |
|
Administering the Sun Business Process Manager Database
Using the Sun Business Process Manager Worklist Manager for User Activities
Maintaining Sun Master Indexes (Repository)
Defining Master Index Security (Repository)
To Create a Master Index User Account
Master Index User Roles (Repository)
Learning About Master Index Reports (Repository)
Master Index Command Line Reports (Repository)
Master Index Report Configuration (Repository)
Creating Custom Master Index Reports (Repository)
Masked Data in Master Index Reports (Repository)
Master Index Production Reports (Repository)
Master Index Activity Reports (Repository)
Master Index Database Indexes (Repository)
Working With Master Index Command Line Reports (Repository)
Configuring the Master Index Report Environment (Repository)
Master Index Command Line Report Properties (Repository)
Running Master Index Command Line Reports (Repository)
Maintaining the Master Index Database (Repository)
Backing up the Master Index Database
Restoring the Master Index Database
Implementing Changes to the Master Index Project (Repository)
Modifying Master Index Configuration Files (Repository)
Modifying Standard Master Index Project Components (Repository)
Modifying the Master Index Database (Repository)
Modifying Master Index Security (Repository)
Modifying the Local ID Format (Repository)
Working With the EDM for Sun Master Patient Index
Working With the EDM for Sun Master Index
Working With the Master Index Data Manager
Maintaining Sun Master Indexes
Before running any reports from the command line, you must customize the XML
configuration file. You can use either of the files located in the reports
directory in the eView or eIndex subdirectory. A default XML file named eIndexPersonReport.xml
is defined for a person object and a default XML file named eView CompanyReport.xml
is defined for a company object. You can use either of these
as a basis for your production configuration file. Report configuration includes two steps: defining
the overall report configuration and configuring the individual reports.
The first section of the report configuration file is indicated by the DOCTYPE and the report elements and tells the report client how to connect to the application server, which application to run the reports against, and where to output the report files.
Note - The DOCTYPE element indicates the type of document being generated. Do not change this value.
By default, this file is named report.dtd, and is located in the config
directory. You should not need to modify this attribute unless you move report.dtd
This must be in the format corbaname:iiop:host:port, where host is the name of the
server and port is the ORB port number.
If an output directory is specified in the command line, that directory overrides the one specified here. If the output directory already exists, the report client issues a warning that any existing report files will be overwritten and gives you the option of cancelling the reports.
A configuration section is defined for each of the six report templates. Use these sections to configure each report to display information as you want to view it. You can also specify which reports to run.
For each report, make the following modifications before running the reports. Each element or attribute mentioned in the following instructions is defined in . There are six stanzas for you to modify, one for each report.
A sample report configuration appears below.
<report name="Potential Duplicate Today"
template="Potential Duplicate">
<enable>true</enable>
<output-file>pot_dup_t.txt</output-file>
<max-result-size>0</max-result-size>
<page-size>100</page-size>
<criteria>
<dates type="today" from-date="" to-date=""/>
<status></status>
</criteria>
<fields>
<field path="Person.FirstName" label="First Name" width="10"/>
<field path="Person.LastName" label="Last Name" width="10"/>
<field path="Person.SSN" label="SSN" width="9"/>
<field path="Person.DOB" label="DOB" width="10"/>
<field path="Person.Address.AddressLine1"
label="AddressLine1" width="30"/>
<field path="Person.Address.AddressLine2"
label="AddressLine2" width="30"/>
</fields>
</report>