Symantec Developer Group

 View Only
  • 1.  Resource target membership in-memory evaluating

    Posted Jun 01, 2010 05:29 AM

    Hello!
    I am implementing a custom resource target, which should resolve its resources on the information available only in memory, not in the NS database. What should I do in order NS would call its Evaluate() method during membership update process (both Complete and Delta)?

    thanks in advance
     



  • 2.  RE: Resource target membership in-memory evaluating

    Posted Jun 01, 2010 11:02 AM
    Can you give more detail about what it is you want the resource target to do, what its purpose is, and why it needs to behave this way? What I believe you are asking for is not something I can see a need for, so I'd like to check that you are not trying to do something in a more difficult way than is necessary.


  • 3.  RE: Resource target membership in-memory evaluating

    Posted Jun 02, 2010 04:05 AM
    Custom resource target should find upon evaluation request intersection of site server resources assigned to (served by) particular site server with the resources of agentless monitor policies. Resources (IP addresses), which are served by given site server could be found also from database, but it is extremely inconvenient to manipulate/calculate IP addresses and masks at SQL level. Besides, there is quite elaborated API for finding them from site servers management cache.



  • 4.  RE: Resource target membership in-memory evaluating
    Best Answer

    Posted Jun 04, 2010 05:10 PM
    I think you'll find that calculating this at the SQL level is your best option. You can easily get the IP addresses of resources from the Inv_AeX_AC_TCPIP table. This comes with basic inventory on a computer. If your solution isn't adding resource information to this table, I'd suggest you either start adding the data or create a new data class that is smaller to hold this information for your resources.

    Either way, once you have this information in a table it's just a matter of joining against another table or two to get your list. That's really something SQL is made for. Plus, using a standard filter and resource target on this will mean you get security automatically.