Page tree

Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

  1. On the BMC ProactiveNet Server, open the TMARTAdaptor.conf file, located in the installDirectory\pw\monitors\shared\TMARTAdaptor directory.
  2. Set or add the configuration properties listed in the following table.Place each property on a separate line and prefix it with the following string: com.proactivenet.monitors.TMARTAdaptor.

    Property line



    Activation of an HTTP timeout.
    Values are no (default) and yes.
    Recommended value: yes


    The length of the HTTP timeout, in milliseconds.
    Recommended value and default: 180000 ms (3 minutes)


    Activation of a polling timeout.
    Values are no (default) and yes.
    Recommendations: For a large number of measures from BMC TM ART, set to yes. Otherwise, set to no.


    The length of the polling timeout, in milliseconds.
    Recommended value and default: 300000 ms (5 minutes)


    The maximum length of time, in minutes, for which to obtain historical data points (that is, how far back to poll).
    Values are:
    0 – Do not query historical data points
    -1 – Query all available data points since the last timestamp with no additional backward time limit.
    Any other integer -- Query historical data points as far back as the specified number of minutes.
    Recommendation: Unless a complete history is critical, BMC does not recommend exceeding the prior 2 hours (120 minutes), to avoid slowing down the polling of BMC TM ART Central data.


    The maximum age, in minutes, of data in the cache that can be used for detailed diagnostics.
    The default value is 1 minute.
    Recommendations: When using a rule to automatically trigger Detailed Diagnostics (RunNow + TrueLog or Page Timers) in response to an event, to ensure that fresh data is received in each poll, set a value that does not exceed the shortest polling interval.
    Otherwise, choose larger values to reduce the Detailed Diagnostics overhead but that still match how frequently you want new diagnostic values.


  3. Save and close the file.
  4. Restart the BMC ProactiveNet Agent.
  5. Reconnect the BMC ProactiveNet Agent with the BMC ProactiveNet Server using the following pw command:
    pw rem rec <Agent Name> 

Whenever you restart the BMC ProactiveNet Agent, all the last time stamps in the cache are cleared and revert to the first cycle. Therefore, activation of the Historical Data Points feature enables backfilling historical data points only with data that was collected after the time of activation.

  • No labels