Endpoint Operations Management Agent Plug-in Development Kit In the case of service, auto-discovery is supported for custom MBean services, driven by the OBJECT__NAME property. To implement auto-discovery at the service level, invoke the autoinventory plug-in leaving out the class attribute, within a service tag <service name=" Java Service Name"> <plugin type="autoinventory"/ service> The JMX plug-in uses the MBean Server query Names method to discover a service for each MBean instance. In the case where the OBJECT_NAME contains configuration properties, the properties are auto unfigured By default, auto-discovered service names are composed using the hosting-server name, configuration properties, and service type name. For example myhost Sun JVM 1.5 localhost /jsp-examples WebApp String Cache You can override the naming using the AUTOINVENTORY_ NAME property <property name= AUTOINVENTORY_ NAME value="platform. name%%path% Tomcat WebApp String Cache"/> You can use the configuration properties from the platform, hosting server, and the service itself in the %replacement% strings, resulting in a name such myhost /jsp-examples Tomcat WebApp String Cache Discovering Custom Properties Discovery of Custom Properties is supported using the OBJECT_NAME and MBeanServer getAttribute You define a properties tag with any number of property tags where the name attribute value is that of an MBean attribute property n description="Maximum Cache Size"/ that maps to the following MBean interface method public interface WebAppCacheMBean public int getCacheMaxSize O;In the case of service, auto-discovery is supported for custom MBean services, driven by the OBJECT_NAME property. To implement auto-discovery at the service level, invoke the autoinventory plug-in, leaving out the class attribute, within a service tag: <service name="Java Service Name"> ... <plugin type="autoinventory"/> ... </service> The JMX plug-in uses the MBeanServer.queryNames method to discover a service for each MBean instance. In the case where the OBJECT_NAME contains configuration properties, the properties are auto￾configured. By default, auto-discovered service names are composed using the hosting-server name, configuration properties, and service type name. For example: "myhost Sun JVM 1.5 localhost /jsp-examples WebApp String Cache" You can override the naming using the AUTOINVENTORY_NAME property: <property name="AUTOINVENTORY_NAME" value="%platform.name% %path% Tomcat WebApp String Cache"/> You can use the configuration properties from the platform, hosting server, and the service itself in the %replacement% strings, resulting in a name such as: "myhost /jsp-examples Tomcat WebApp String Cache" Discovering Custom Properties Discovery of Custom Properties is supported using the OBJECT_NAME and MBeanServer.getAttribute. You define a properties tag with any number of property tags where the name attribute value is that of an MBean attribute: <properties> <property name="cacheMaxSize" description="Maximum Cache Size"/> </properties> that maps to the following MBean interface method: public interface WebAppCacheMBean { public int getCacheMaxSize(); } Endpoint Operations Management Agent Plug-in Development Kit VMware, Inc. 8