Page History

...

• About customizing your reports
• About defining properties for a customized report
• Filling in gaps in a customized report
• About importing and exporting customized reports
• About copying customized reports

...

Do not rerun the report by clicking Edit.

Anchor
Fillingingapsinacustomizedreport Fillingingapsinacustomizedreport

Filling in gaps in a customized report

Retrieving information collected over time from the Performance Management Database may result in missing information. These are specific timestamps for which no data is available. For example, an Oracle program may not include data for a specific timestamp, if the program was not invoked during the interval that started with this timestamp. In this case, you may want, for example, to fill in the number of executions counter with a zero value.

...

For example, <object id="4000" name="Instance" fill="const" const="666"/>
id    Specifies the object identifier.
Set to one of the objects ID defined in the selection tag at the beginning of the report’s .xml file.
name    Specifies the data field name.
This attribute is optional. You may set this attribute to add clarity to the report.
fill    Specifies the method of data completion.
Possible values include:
•    const
The data is completed with a constant value. In this case, you must also set the const attribute.
•    prev
The data is completed with the value of the previous timestamp.
•    next
The data is completed with the value of the next timestamp.

const    Specifies the constant value that completes the missing data.
Set the const attribute if you set the fill attribute to const.
By default, Report Manager fills in counters with zeros, and strings with nulls. You can set the const attribute, together with the prev or next fill types, to specify a different value other than the default value (zero or null), so that Report Manager also completes the margins, where there is no previous or next value.
5.    Add the timeframe tag under the fill_holes tag level and set its attributes.
The timeframe tag defines the time frame for which the data completion applies. You can set the time frame using one of the following methods:
•    Absolute date range.
Set the start and end attributes. For example, <timeframe start="2004-05-20 00:15:23.11" end="2004-06-10 22:35:23.11" />.
•    Relative date time.
Set the lastNType, lastNStart and lastNLen attributes.
start    Specifies the start date and time.
The format is: yyyy-mm-dd hh24:mi:ss.ms
You must apply the entire format, except the ms (milliseconds), which is optional. For example:
<timeframe start="2004-05-15 18:30:15.00" end="2004-05-20 23:59:59.59"/>
end    Specifies the end date and time. See the format of the start attribute.
lastNType    Specifies the time units for the lastNStart and lastNLen attributes.
Possible values include:
•    H - Hours
•    D - Days
•    W - Weeks
•    M - Months
Set a value that is not lower than the report summary level resolution (that is, the report summary level must be at least as the lastNType value).
For example: lastNType="D" can be used with a report summary level of H (hours).
lastNStart    Specifies the start of the time frame counting back from the current time (current time is always 0).
For example, if lastNType="D", then a lastNStart="0" signifies that the start time of the time frame is today.
If lastNStart="10" and lastNLen = "5", this signifies that the start time of the time frame was 15 days ago.
lastNLen    Specifies the length of the time frame counting back from the lastNStart time.
The following example defines a start time of 15 days ago and end time of 10 days ago.
<timeframe lastNType="D" lastNStart="10" lastNLen="5"/>
6.    Save the .xml file.
7.    Rerun the report by doing one of the following:
•    Click Scheduling.
•    Click View and then Rerun.
Don't click Edit to rerun the report

Anchor
Aboutimportingandexportingcustomizedreports Aboutimportingandexportingcustomizedreports

About importing and exporting customized reports

The following section describes how to export a customized report from one Precise system and import it to another Precise system.NOTE    Before

To export/import a customized report1.    In

1. In the source Precise system, create the ForesightExportRequest.xml file in the Precise root folder. For example:
   <root name="Export">
   <report-name>In Sybase Breakdown</report-name>
   <apptier>1201</apptier>
   </root>

   Info

...

1. The report-name value is case-sensitive.

...

1. Run the following command:
   infra\bin\psin_http_requestor -dp -x fs-export-import FS < ForesightExportRequest.xml > out.xml

...

1. Check the out.xml file in the <precise_root >, to view the status.

...

1. Copy the exported report’s .zip file from the source Precise root folder to the destination Precise installation in:
   <precise_root>\distribution

   Info

...

1. The .zip file name consists of <technology code>_<report name> (SY_In Sybase Breakdown.zip). For cross-Tiers the Tech code is ALL (ALL_CA_Rep.zip).

...

...

1. In the destination Precise system, create the ForesightImportRequest.xml file in the Precise root folder. For example:
   <root name="Import">
        <report-name>SY_In Sybase Breakdown.zip</report-name>
        <apptier>1174</apptier>
   </root>

...

1. Run the following command:
   infra\bin\psin_http_requestor -dp -x fs-export-import FS <

...

1. ForesightImportRequest.xml > out.xml

...

1. Check the out.xml file in the Precise root folder, to view the status.

About copying customized reports

The following section describes how to copy customized reports from one Tier to another with the CLI utility. To copy a customized report1.    Run

1. Run the following commands from the Precise root folder:
   
   • UNIX
   1. • infra/bin/psin_cli.sh -i3-user <user> {-i3-clear-password <i3_clear_password> |
        -i3-encrypted-password <i3_encrypted_password>}
        -action fs-copy-foresight-custom-report
        -parametersfile <parameters-file.xml>
   • Windows
   1. • infra\bin\psin_cli.bat -i3-user <user> {-i3-clear-password <i3_clear_password> |
        -i3-encrypted-password <i3_encrypted_password>}
        -action fs-copy-foresight-custom-report
        -parametersfile <parameters-file.xml>
        Example:
        infra\bin\psin_cli.bat -i3-user admin -i3-clear-password admin -action fs-copy-foresight-custom-report -parametersfile my_parameters_file.xml

...

1. Create the parameters-file.xml file in the Precise root folder and verify that it contains the following:
   <parameters>
        <parameter name="source-environment" value="Default"/>
        <parameter name="source-apptier" value="SQL Server"/>
        <parameter name="source-report" value="My_report"/>
        <parameter name="destination-environment" value="Default"/>
        <parameter name="destination-apptier" value="SQL Server"/>
   </parameters>
   and verify that the information in the following notes is applied.

...

...

...

...

Precise. Performance intelligence from click to storage. Learn more > >