Report Post-Processing Examples

Example 1: Monthly Extraction of Raw Data

Use Case: FlexNet Manager for Engineering Applications should provide the Raw data format for the managed licensing system on a monthly basis. A nightly raw report is run on the first day of the next month to extract the data. The post processing includes replacing of the user IDs with full User names and department information.

Report Configuration: Define a raw report configuration with the following settings.

1. Set the Date/Time Range to “Prior Month,” scheduled at the first of each month. Because the raw report contains data for the entire system, all of the server hosts, vendor daemons and features are included.
2. The Event Types (on the Filter Properties page) can be restricted to Used, Queued and Denied, because exceptions are not relevant to the further processing.
3. On the Raw Report Output Properties page, select the RIF format. Note that for this format, there is no parameter because the you can deduce the report output format based on the file endings of output files.
4. Select “Time as Seconds” and specify the appropriate location in the Report Output Directory field. Also, select the “Overwrite the content” option (in case the output after post processing does not need to be preserved) and specify the post-processing command (in this example, Perl on Unix is used):

/usr/bin/perl /opt/cblecken/perl/rawProcess.pl $outputDir $outputFiles $errorStatus $errorLine $reportType $user $startDate $endDate $eventFilter $delimiter $elimFalseDenials $sortOrder $featureUniq $timeInSeconds

These are all of the parameters that apply to a Raw report. As noted previously, because none of the servers host, vendor daemons or features are selected, the associated parameters $servers, $vendorDaemons, and $features are not included in the post-processing command expression. They should be included only in case a non-zero selection has been made.

5. Next, the Raw Report Fields page lists the fields you can select to include in the Raw report. The list of Raw report fields is not included in the list of parameters, because the Raw RIF format will describe the number of columns and the name of the columns in the report itself and it is more consistent to take the column numbers and column names from the report.

Report Generation: Given the sample perl script from the previous code sample (which writes the parameters to stdout), generating a report from this configuration leads to the following invocation on the command line as described in the following table.

Example 1 command-line arguments

Argument

Description

/opt/username/extout

Output directory

Raw_Sample.txt,Raw_Sample.fns

Output files; the .fns file contains the debug log

0

Report generation successful

""

No error message

FLEXnet.Usage.Raw

Indicates Raw report

Admin

The user running the report

3/1/06 12:00 AM

Report start date

3/26/06 12:00 AM

Report end date

used,queued,denied

The event type filters; all selected except Exceptions

 

The delimiter; not visible because it is a space

true

False denials enabled

f

Sort by feature

name

Distinguish features by name

true

Dates are recorded in UNIX seconds

Example 2: Month-to-Date High Water Mark

Use Case: Every day the aggregated High Water Mark report is calculated for the entire month up to today. This report should include only a subset of vendor daemons (for this example, the two vendor daemons “examlmd” and “exanlmd”). This report is run every night.

Report Configuration: Define a High Water Mark report configuration with the following settings.

1. Set the Date/Time Range to “Month to Date,” scheduled to run every night. Also select the vendor daemons “examlmd” and “exanlmd” from the Vendor Daemons selection box. Do not select anything for the license server hosts or the features (on the Feature Selection page).
2. On the Summary Options page, select the “Show Zero Usage” option.
3. On the Output Options page, select the RIF and the Image output format. In the Additional Options section, select the “Show Available Licenses” and “Auto-Reduce Large Datasets” options.
4. Specify the appropriate location in the Report Output Directory field. Also, select the “Overwrite the content” option (in case the output after post processing does not need to be preserved) and specify the post-processing command (in this example, Perl on Unix is used):

/usr/bin/perl /opt/cblecken/perl/hwmProcess.pl $outputDir $outputFiles $errorStatus $errorLine $reportType $user $vendorDaemons $startDate $endDate $showZero $showAvail $sortOrder $featureUniq

5. On the Report Scheduling page (available by clicking the Schedule button for the report from the Report Configurations page), schedule the report to run on the first of each month.

Report Generation: Given the sample perl script from the previous code sample (which writes the parameters to stdout), generating a report from this configuration leads to the following invocation on the command line as described in the following table.

Example 2 command-line arguments

Post-Processor Command-Line Arguments

Description

/opt/username/extout

Output directory

High_Water_Mark_Sample2.png,

High_Water_Mark_Sample0.png,

High_Water_Mark_Sample1.png,

High_Water_Mark_Sample3.png,

High_Water_Mark_Sample4.png,

High_Water_Mark_Sample5.png,

High_Water_Mark_Sample6.png,

High_Water_Mark_Sample0.htm,

High_Water_Mark_Sample1.htm,

High_Water_Mark_Sample2.htm,

High_Water_Mark_Sample3.htm,

High_Water_Mark_Sample4.htm,

High_Water_Mark_Sample5.htm,

High_Water_Mark_Sample6.htm,

High_Water_Mark_Sample_toc.htm,

High_Water_Mark_Sample.fns

Output files; the .fns file contains the debug log

0

Report generation successful

""

No error message

FLEXnet.Usage.HighWatermark

Indicates High Water Mark report

Admin

The user running the report

examlmd,exanlmd

Vendor daemon list

2/1/96 12:00 AM

Report start date

10/20/06 12:00 AM

Report end date

false

Do not show zero regions

true

Show the available licenses

f

Sort by feature

name

Distinguish features by name

See Also