Configuring the Reporting Service

Minimum number of minutes that a license server must be down (not running) for a gap in service to be recorded.

The maximum number of report logs that can be imported concurrently. Specify any number greater than 0.

Report log imports can be initiated simultaneously in a variety of ways:

Every time an import process runs, it uses system resources like memory. Because of this, it is important to limit the number of imports that run at the same time. Although there is no simple formula to determine how much memory a single report log import consumes, large log files will typically use more memory, as will report logs with many long-running check-outs.

This setting ensures that no more than the configured number of report logs are imported concurrently. If more than the specified number of report log import processes are triggered, the overflow jobs are queued and are run after a currently running job completes (successfully or otherwise).

Note:If you change the value for this setting, you must restart the server for the new value to take effect.

The number of report jobs that can be running in parallel at a given time. If a report job cannot be run because too many other reports are running simultaneously, the report is rescheduled to run again within 90 seconds.

It is recommended that the value in this field be set to the number of CPUs on the FlexNet Manager for Engineering Applications machine.

The number of times that the system will keep retrying.

The reporting engine retries to run a report job if the reporting engine postpones execution because it is running the maximum number of concurrent reports. The reporting engine retries running a report job approximately one minute after a postponement and every two minutes for subsequent retries.

When the number of retries is exceeded, the report will appear in the Reports Inbox page with its status set to Canceled. In the Reports Inbox page, you can click the View Log button to see the report log, which provides information about why the report was canceled.

As log files are imported to the database, records are committed in batches to improve performance. The optimal batch size may vary, depending on your database configuration.

Report log files can include a variety of unsupported events, due to licenses expiring or other reasons. Most reports do not rely on these events being present. Storing these events will consume extra space in your database, but will provide a more complete picture of the contents of each log file.

Report log files can include many regular denial events. Most reports do not rely on these events being present. Storing all of the regular denial events will consume additional space in your database, but will provide a more complete picture of the contents of each log file.

Note:Regular denial events for vendor daemons version 9.2 or earlier will always be imported, regardless of this setting. This is because these report logs do not contain ultimate denial events.

Reports may have different results, depending on whether user names are case sensitive.

Time interval (in seconds) in which the aggregation process should consider identical denials to be part of the same denial event.

The number of days of usage data the aggregation process can consider at one time. A larger number will increase the load on the database.

Specify the date (using the format YYYY-MM-DD) to reduce the size of the data warehouse and the time the aggregation process takes. When a date is provided for this setting, the aggregation will be limited to consider only usage data that occurs after the specified date.

Time periods specified in the Incremental Aggregation page override this setting.

Note:This field is for use primarily by Platform Computing customers.

If your Project Name field contains data in addition to the project name, you can use this field to specify which part of the Project Name string you want FlexNet Manager for Engineering Applications to consider when usage data is aggregated.

Specify a regular expression in this field to indicate that aggregation should select substrings from the project name strings. FlexNet Manager for Engineering Applications will use the regular expression to parse the project name string as described, which results in fewer projects being shown for the aggregated usage data.

If this field is blank, FlexNet Manager for Engineering Applications does not parse the Project Name string.

Select this check box to enable product aggregation. This option must be selected to enable product-based reporting. In addition, you must add products to FlexNet Manager for Engineering Applications and map features to products.

Note:If your organization uses Investment Planning functionality (available under the Planner tab in the user interface), you must select this option to enable reporting on the products you have defined.

Select this check box to enable product-based reporting for IBM feature usage. See the topic, Reporting on IBM Rational Products: Mapping Features to Products, for information on how FlexNet Manager for Engineering Applications maps feature usage to product usage for IBM Rational products.

Note:This setting is relevant only for organizations that use features served by the vendor daemon ibmratl.

Select this check box to enable tier-based reporting functionality and display the Tiers tab on the FlexNet Manager for Engineering Applications user interface.

In addition, the user signed in to FlexNet Manager for Engineering Applications must have a role containing the View and Manage Investment Planner permission and/or the Import Products and Contracts from Command Line permission.

Select this check box to enable token-based reporting functionality.

Fully qualified name of the host on which Cognos server (Flexera Analytics) is running.

This can be http or https. If you do not specify a protocol, this setting defaults to http://. For example, if you provide a Cognos server host value hostname, the setting defaults to http://hostname.

Port number of the Cognos server

The port number of Cognos web services

"Cognos Token Lifetime", which determines how long the token that FNMEA creates for Cognos to authenticate will live for.

The setting has a minimum value of 60, a Default value of 60, and a maximum value of 315,360,000.

Routine usage data cleanup for the deleted report logs on the Reporting database. Clear the check box if the data cleanup is not required.

The default currency used in FlexNet Manager for Engineering Applications.

Select option to archive report log files before cleanup