RTView® EM
User Guide

Configure Solution Package
 This section describes how to configure a Solution Package for RTView EM. When you have finished this part of the RTView EM configuration, your Solution Package-specific displays will contain monitoring data from the Solution Package Data Collection Server. This Step is required.

The following figure illustrates the RTView EM component that is the subject of this section: the Solution Package.  

To configure a Solution Package you connect the EM Central Servers to the Data Collection Server.

At this point you have:

To configure the Solution Package:
1. Connect the Data Server for the Solution Package. In an initialized command window, change directory (cd) to your project directory/servers directory.

2. Execute the following script to stop the Solution Package Data Server:

    Windows
    stop_rtv <packagename>
    where packagename is the Solution Package data key. For example:
    stop_rtv wlm stops a WebLogic Data Server.
   
    UNIX
    stop_rtv.sh <packagename>
    where packagename is the Solution Package data key. For example:
    stop_rtv.sh wlm stops a WebLogic Data Server.

In the Architecture / System Overview display the Solution Package Data Server turns red after a few seconds.

3. Change directory (cd) to your Solution Package project directory/servers/<Solution Package> directory.

4. Create a file named mycustom.properties in a text editor and refer to the README.txt file in your Solution Package directory for information about configuring properties for your Solution Package.

5. Navigate to the project directory/servers directory and open the rtvservers.dat file in a text editor. Locate the section for your Solution Package Data Server. For example, the WebLogic Data Server entry, by default, is the following:

      ### WLM
#
wlm ./wlm dataserver rundata
#wlm ./wlm historian runhist -ds

6. Make the following entry to point EM to the mycustom.properties file you just created:

        -properties:mycustom

    For example, for the WebLogic Data Server we enter:

      ### WLM
#
wlm ./wlm dataserver rundata -properties:mycustom
#wlm ./wlm historian runhist -ds
     
    Save the file.

7. In the command line window (from the project directory/servers directory), start the Solution Package Data Server by typing:

    Windows
    start_rtv <packagename>
    where packagename is the Solution Package data key. For example:
    start_rtv wlm starts a WebLogic Data Server.
   
    UNIX
    start_rtv.sh <packagename>
    where packagename is the Solution Package data key. For example:
    start_rtv.sh wlm starts a WebLogic Data Server.
       
  In the Architecture / System Overview display the Solution Package Data Server turns green after a few seconds and subsequently receives monitoring data, as indicated by the positive value in the CI Metrics field (this can take up to a minute).

8. Open the Administration / Alert Administration display and locate alerts for the Solution Package Data Server. The alert prefix corresponds to the Solution Package name. For example, the WebLogic alert prefix is Wls.

    Identify an alert for your Solution Package that is likely to activate and set the alert Warning Level to zero (0) and the Alarm Level to ten (10). This ensures the alert thresholds are exceeded and you can verify your Solution Package configuration. For example, for WebLogic we set the WlsThreadsTotalHigh alert Warning Level to zero (0) and the Alarm Level to ten (10). Keep in mind that eventually your alert thresholds should be changed to more meaningful values within your system.
    Select Enabled to enable the alert.
    Click Save Settings and OK.

    Open the Alert Views/ Alerts Table display and verify you see warning alerts for the alert you just modified and enabled. For example, when the WebLogic thread count goes above zero (0) and above zero (10) the WlsThreadsTotalHigh warning and alarm alerts, respectively, are activated and visible in the Alerts Table display.
    Open the All Servers Heatmap display for your Solution Package. For example, for WebLogic we open the WebLogic All Servers Heatmap display. The heatmap contains monitored data for your Solution Package, including the status for the alert you just lowered the threshold on and enabled.

9. Repeat the previous steps for each installed Solution Package.

This completes your Solution Package configuration. Solution Package-specific displays contain monitoring data from your environment. For example, if you just configured the WebLogic Solution Package, displays such as the Oracle WebLogic Servers All Servers Heatmap are populated with data from your WebLogic servers. You do not yet see the data in displays such as the Area Heatmap as the Service Data Model (CMDB) is not yet configured.

Proceed to Configure Service Data Model.

 

 

 

 
 
 
SL, SL-GMS, GMS, RTView, SL Corporation, and the SL logo are trademarks or registered trademarks of Sherrill-Lubinski Corporation in the United States and other countries. Copyright © 1998-2013 Sherrill-Lubinski Corporation. All Rights Reserved.
 
 
 

JMS, JMX and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. They are mentioned in this document for identification purposes only.

 
 
 

Third Party Notice Requirements