Configuring BMC ProactiveNet Report Engine

Perform the following procedures to configure BMC ProactiveNet Report Engine:

• • Configuring BMC ProactiveNet Report Engine for Oracle Real Application Cluster
    
  • Configuring BMC ProactiveNet Report Engine for performance reports
  • Configuring the Report Engine properties
  • Configuring maximum history of performance data

Configuring BMC ProactiveNet Report Engine for Oracle Real Application Cluster

1. When you install BMC ProactiveNet Report Engine, in the Database Information page on the BMC ProactiveNet Report Engine installation wizard, provide the following information:
   • Fully qualified database host name of any one of nodes in the Oracle RAC
   • Corresponding database instance name of the node
   • Listener port for the database
   • Database user credentials
2. Complete BMC ProactiveNet Report Engine installation.

3. On a text editor, create a 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.

4. Stop the BMC ProactiveNet Report Engine service. For details, see Starting/Stopping of the BMC ProactiveNet Report Engine service.
5. Create a backup of the following files:
   • database_config.xml file located at BMCProactiveNetReportEngineInstallDir\ReportEngine\bin\reportsCLI
   • websdk-ds.xml file located at BMCProactiveNetReportEngineInstallDir\ReportEngine\tools\jboss\server\all\deploy

   • smsConsoleServer-ds.xml file located at BMCProactiveNetReportEngineInstallDir\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.

6. Using a text editor, open database_config.xml, and search for the <url> tag.

7. Update the following value with the URL that you created in step 3.
   
   

   jdbc:oracle:thin:@hostName:1521:instanceName
8. Save and close the file.
9. Using a text editor, open websdk-ds.xml and smsConsoleServer-ds.xml files, and search for the <xa-datasource-property name="URL"> tag.

10. Update the following value with the URL that you created in step 3.
    
    

    jdbc:oracle:thin:@hostName:1521:instanceName
11. Save and close the files.
12. Start the BMC ProactiveNet Report Engine service. For details, see Stopping and starting the Report Engine Service. 

Configuring BMC ProactiveNet Report Engine for performance reports

Perform the following configurations for proper operation of the performance reports.

Creating an External Report attribute set

An External Report attribute set enables the following:

• Filtering capabilities — performance data is transferred from BMC ProactiveNet Server to the report engine, and performance reports are generated only on those attributes you have selected.
• Normalization of attributes across platforms — you can group similar attributes across platforms in one attribute set. For example, the "% CPU Utilization In System Mode (%)" attribute is used for UNIX, while the "System CPU Utilization (%)" is used for Windows monitors. You can group both attributes under one "CPU" attribute and generate performance reports using the "CPU" attribute set.

To create an External Report attribute set:

1. On the BMC ProactiveNet operational console, go to Options > Administration > Attribute Sets > Edit.
2. Click the relevant option:
   • For a new Attribute Set, click Add in the AttributeSet Administration screen.
   • To edit an existing Attribute Set, click Edit. Click Add Attributes to add more attributes.
3. On the Add Attribute Set screen, select the Attribute Set type External Report.
4. Select the Monitor Type. Select all monitor types corresponding to the attributes to be grouped.
   Use the Shift and Ctrl keys to make multiple selections. To locate a specific monitor, use the Search For field.
5. Click Next.
6. Select the attributes to be grouped from under each of the monitor types in the Attributes section.
   Use the Shift and Ctrl keys to make multiple selections. To locate a specific attribute, use the Search For field.
7. Click Next.
8. Specify a name for the attribute set.
9. Select the attributes to be included by selecting the corresponding check boxes in the Select column.
10. Click Finish. The new External Report attribute set is available for use.

To create a non super admin user to create attribute set with monitors that have instances

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:

1. In the BMC ProactiveNet Administration Console, select the Administration > General Administration tab.
2. Expand the Advanced Options folder.
3. Select and right-click the Role folder and select Add Role.
4. In the Add Roles and Permissions dialog box, enter the Name of the new role.
5. Select Limited Access option to select from the permissions in the Permissions List.
6. From the Permissions List, select all permissions and click Finish.
7. Expand the Advanced Options folder, to create a new user group.
8. Select and right-click the User Group folder and select Add User Group.
9. In the User Group dialog box, enter the Name of the user group.
10. Select the Roles/Users tab, and select the newly add role from the Available Roles list to assign to the user group.
11. Select the following other permissions:
    1. Views
    2. Monitor Groups
    3. CIs
    4. SLOs
    5. Reports
    6. Folders
12. To display all devices and its monitors, in CIs tab, select All Components.
13. Create a new user, highlight and right-click User and select Add User. 
14. In the Add User dialog box, enter all required fields and select the newly created user group from Available User Groups. Click Add.
15. Log on to BMC ProactiveNet Operations Console by using the newly created user.
16. Create attribute set for External Report. For more information, see To create an External Report attribute set. 

Configuring the Report Engine properties

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:

• (Windows) reportEngineInstallationDirectory\ReportEngine\tools\jboss\server\all\conf\properties
  \perfsladatatransfer
• (Solaris/Linux) ReportEngine/tools/jboss/server/all/conf/properties/perfsladatatransfer

To change the Report Engine properties:

1. Open the perfsladatatransfer.properties file using a text editor. The following properties are included in the file:

   
   

   Note

   To change the Retention Age property, use the ConfigureRetention CLI command.

2. Save the perfsladatatransfer.properties file.
3. Restart the BMC ProactiveNet Report Engine service. See, Starting-and-Stopping-the-Report-Engine-service.

Configuring maximum history of performance data

This section describes the configuration for transferring performance data from BMC ProactiveNet database to reporting engine database. Reporting Engine can be configured to transfer history data present in BMC ProactiveNet server before it has been registered with reporting engine.

You can configure the maximum history of performance data to be retrieved from BMC ProactiveNet Performance Management server over multiple cycles by modifying the following parameters. See Configuring BMC ProactiveNet Report Engine for performance reports for more information.

Maximum history is relative to current time. Default is set to 30 days.