I wonder if someone can give me a bit more information about Templates and 
Binding of those Templates to different classes in the hierarchy.

The explanation of this is quite brief in the admin guide so I wonder if anyone 
can explain it with more clarity.

The first thing in the guide that I need clarification on is the relevance to 
the name of the template and the name of the the class that the template is to 
bind to... Does the template name have to the be the same as the class it is 
bound to?

Secondly, I created a class called 'IIS' at /Server/Windows/IIS and bound the 
IIS template to this level in the hierarchy and everything  worked as expected, 
any devices I dropped into this /Server/Windows/IIS inherited the template and 
the IIS graphs were generated.  

However, I have one server which has SQL Server and IIS on it and naturally I 
want the MSSQLServer and IIS template to be bound to the class the I created 
for it 'IIS and MSSQLServer'.  I managed to bind the IIS class correctly, but 
the MSSQLServer template wasn't available in the list, so I had to copy the 
template upto /Server/Windows from /Server/Windows/MSSQLServer... Is this the 
correct way to go about it?  Why was the MSSQLServer only available at 
/Server/Windows/MSSQLServer?  Surely it would be better to have all templates 
at the top level so they are available to all classes?

Finally, once I managed to bind both the IIS and MSSQLServer template to the 
'IIS and MSSQLServer' class, and dropped in the server, not all of the graphs 
are displaying correctly.

I know that wasn't particularly concise a description, but I hope people can 
help me out with the whole template binding thing!

Thanks in advance.




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=32299#32299

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to