Before you can configure application services as one

Prerequisites

  • Each Java class or service must instantiate Model MBeans that meet the requirements described in Model MBean Naming and Descriptor Data.

  • The vRealize Hyperic agent managing the server instance where your application runs should discover model MBeans in the MBean server that meet the requirements specified in Model MBean Naming and Descriptor Data.The server instance that hosts the application appears in the Auto-Discovery portlet on the dashboard of the vRealize Hyperic user interface. After you import the new or changed server instance to inventory, you can browse to the application services, which appear as children of the host server.

Procedure

  1. Set up the resources to export model MBeans

    If your applications run with Spring-instrumented JARs, they should automatically export model MBeans with the required name format and descriptors. If your applications expose MBeans using the Spring 3.0 JMX annotations (@ManagedResource, @ManagedMetric, @ManagedAttribute, @ManagedOperation), they should automatically be exported with the required descriptors.

  2. Redeploy your application after enabling export of Model MBeans

    To verify that your application services have instantiated model MBeans, use a JMX client to browse the MBean server.

  3. Verify the model MBean export to the MBean server.
  4. Verify the service application auto-discovery.

    The server instance that hosts the application appears in the Auto-Discovery portlet on the dashboard of the vRealize Hyperic user interface. After you import the new or changed server instance to inventory, you can browse to the application services, which appear as children of the host server.

  5. (Optional) : Solve problems with service auto-discovery.

    If your application services were not discovered, perform some verifications.

    1. Verify that the hosting application server is enabled for remote JMX remote access.
    2. Verify that the JMX URL, username, and password properties for the server were auto-discovered by the vRealize Hyperic agent, or were entered manually.
      • If the agent auto-discovered the JMX properties, they appear on the Configuration Properties page for the server instance.

      • If the agent did not discover the JMX properties, an authorized vRealize Hyperic user must specify them on the server instance's Configuration Properties page.