Topic
  • 3 replies
  • Latest Post - ‏2013-10-01T14:09:49Z by randybrown
wxyzabc
wxyzabc
29 Posts

Pinned topic Autopopulation using ESDA

‏2013-09-30T13:04:38Z |

Hi ,

Will ESDA policy will execute after every restart(mannual) of the server?

Regards

wxyzabc

  • randybrown
    randybrown
    60 Posts

    Re: Autopopulation using ESDA

    ‏2013-09-30T15:18:33Z  

    Hi,

    ESDA rules are run when a service becomes invalidated, which happens at regular intervals based on properties set in the template for the service. Restarting the server will also invalidate an ESDA service. A service must be marked "invalid" before the ESDA rules will run.

    However, the ESDA child and parent rules are not run until the user expands a node in the service tree. Thus you must expand the plus signs down your tree to cause the rules to run and add child services.

    There is a rad_radshell method called discoverHierarchy("serviceinstancename"); that can be used to drive the ESDA rules (policy) all the way down the hierarchy that is rooted at "serviceinstancename".

    I hope that helps...

     

    Randy Brown

  • wxyzabc
    wxyzabc
    29 Posts

    Re: Autopopulation using ESDA

    ‏2013-10-01T12:25:24Z  

    Hi Randy,

    Thanks for your reply...

    Its really helpful .

    Can you please clear diffrence between ESDA rule and ESDA child or Parent Rule in your statement.

    Regards

    wxyzabc

     

    Updated on 2013-10-01T12:28:20Z at 2013-10-01T12:28:20Z by wxyzabc
  • randybrown
    randybrown
    60 Posts

    Re: Autopopulation using ESDA

    ‏2013-10-01T14:09:49Z  
    • wxyzabc
    • ‏2013-10-01T12:25:24Z

    Hi Randy,

    Thanks for your reply...

    Its really helpful .

    Can you please clear diffrence between ESDA rule and ESDA child or Parent Rule in your statement.

    Regards

    wxyzabc

     

    Hi,

    An ESDA rule is defined for one or more templates that are in a template hierarchy. This template hierarchy evolves as you add aggregation rules where one template depends on another.

    When you use the ESDA rule editor, you will see template names listed in the left border and right border. These are "tabs" that allow you to specify the ESDA query to be used for each template. The tabs on the left allow you to define child rules and the tabs on the right are for parent rules.

    So you may have one query that will create children for a service and another that would create parents. Generally you would only use one or the other.

    A typical usage is to start at a root service and execute child rules to build a hierarchy. No parent rules would be used. Another common usage is to autopopulate a leaf service from an event and define parent rules to build its parent hierarchy.

    I hope this helps make it clearer...

     

    Randy Brown