Perform the following procedures to configure TrueSight Operations Management Report Engine:
Perform the following configurations for proper operation of the performance reports.
An External Report attribute set enables the following:
To create an External Report attribute set:
After you create attribute sets, external attribute set displays monitor types that do not contain any instances. To display the monitor types which have instances only, perform the following steps:
Select the Roles/Users tab, and select the newly add role from the Available Roles list to assign to the user group.
Changing the report engine properties is not required. If you must change the report engine properties, the properties are located in the perfsladatatransfer.properties file, located in the appropriate directory for your operating system:
To change the Report Engine properties:
Open the perfsladatatransfer.properties file using a text editor. The following properties are included in the file:
Property type | Parameter | Description |
---|---|---|
Data transfer schedule
| reportengine.datatransfer. | Schedule interval in seconds of the performance data transfer job. Valid values are positive whole numbers. |
reportengine.configjob | Schedule interval in seconds for configuration job which transfers configuration data. Valid values are positive whole numbers. | |
reportengine.deleteconfigjob | Schedule interval for Delete job. | |
reportengine.datagapfillerjob | Schedule interval for Delete job. | |
reportengine.datatransfer. | Defines the number of threads to read data from the TrueSight Infrastructure Management database. Default value (recommended): 10 | |
Maximum history
| reportengine.datatransfer. | Maximum stats history data in days to be transferred from TrueSight Infrastructure Management server to report engine. |
reportengine.datatransfer | Maximum rate history data in days to be transferred from TrueSight Infrastructure Management server to report engine. | |
Chunk size | reportengine.datatransfer | Stats and rate data in hours that is transferred in one data transfer job cycle. To collect history, the chunk size must be greater than the job schedule interval. Valid values are positive whole numbers. |
CSV file generation | reportengine.csvfilegeneration | Generates .csv files in case of a data gap. If you do not want the Report Engine to generate .csv files during a data gap, set this parameter to false. |
Collection of rate data | reportengine.ratedatatransfer | Collects the rate data. If you want the Report Engine to collect rate data, set this parameter to true. Default value: false |
Boolean |
| Indicates the value for default logging for performance data transfer in reportengine.log file. Default is ERROR. Recommended value is ERROR. If this is upgraded setup, change the value to ERROR |
Note
To change the Retention Age property, use the ConfigureRetention CLI command.
This section describes the configuration for transferring performance data from TrueSight Infrastructure Management database to reporting engine database. Reporting Engine can be configured to transfer history data present in TrueSight Infrastructure Management Server before it has been registered with reporting engine.
You can configure the maximum history of performance data to be retrieved from TrueSight Infrastructure Management server over multiple cycles by modifying the following parameters. See Configuring BMC TrueSight Operations Management Report Engine for performance reports for more information.
reportengine.datatransfer.maxhistoryretention.statdata.days=0 reportengine.datatransfer.maxhistoryretention.ratedata.days=90
Maximum history is relative to current time. Default is set to 30 days.
Note
After the Report Engine installation is finished, complete the following procedure to update the Oracle Real Application Cluster (RAC) JDBC URL:
In a text editor, create an URL based on the number of host names and instances.
The syntax is:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=fullyQua lifiedHostName1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST= fullyQualifiedHostName2)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST= fullyQualifiedHostName3)(PORT=1521))(LOAD_BALANCE=OFF)(FAILOVER=ON)( CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=serviceName)(FAILOVER_M ODE=(TYPE=SELECT)(METHOD=BASIC)(RETRIES=10)(DELAY=10))))
where,
fullyQualifiedHostName1 is the full name of node1 in the Oracle RAC.
fullyQualifiedHostName2 is the full name of node2 in the Oracle RAC.
fullyQualifiedHostName3 is the full name of node3 in the Oracle RAC.
serviceName is the connector to one or more instances.
Note
The URL must be a single string and should not contain any new line characters in between the URL. The number of node entries can be modified based on the number of nodes in the RAC.
You can also provide virtual IP in the RAC URL.
Example:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rac112-scan1.bmc.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORA95NEW)))
where, rac112-scan1.bmc.com
is the virtual IP.
smsConsoleServer-ds.xml file located at ReportEngineInstallDir\ReportEngine\tools\jboss\server\all\modules
Note
If you create the backup files in the same directory, ensure the backup files do not have the .xml extension. Create the back up outside the BMC_PROACTIVENET_REPORTENGINE_HOME directory.
Update the following value with the URL that you created in step 3.
jdbc:oracle:thin:@hostName:1521:instanceName
Using a text editor, open websdk-ds.xml and smsConsoleServer-ds.xml files, and search for the <xa-datasource-property name="URL"> tag.
Update the following value with the URL that you created in step 3.
jdbc:oracle:thin:@hostName:1521:instanceName
2 Comments
Bharath kumar Chitrala
Mukta Kirloskar