22.7. JBoss Operations Network for Library Mode

Procedure 22.4. Add JBoss Data Grid Instances in Library Mode

1. Import the Platform

   1. Navigate to the Inventory and select Discovery Queue from the Resources list on the left of the console.
   2. Select the platform on which the application is running and click Import at the bottom of the screen.
   

   View larger image

   

   Figure 22.4. Import the Platform from the Discovery Queue.

2. Access the Servers on the Platform

   1. The jdg Platform now appears in the Platforms list.
   2. Click on the Platform to access the servers that are running on it.
   

   View larger image

   

   Figure 22.5. Open the jdg Platform to view the list of servers.

3. Import the JMX Server

   1. From the Inventory tab, select Child Resources.
   2. Click the Import button at the bottom of the screen and select the JMX Server option from the list.
   

   View larger image

   

   Figure 22.6. Import the JMX Server

4. Enable JDK Connection Settings

   1. In the Resource Import Wizard window, specify JDK 5 from the list of Connection Settings Template options.
   

   View larger image

   

   Figure 22.7. Select the JDK 5 Template.

5. Modify the Connector Address

   1. In the Deployment Options menu, modify the supplied Connector Address with the hostname and JMX port of the process containing the Infinispan Library.
   2. Enter the JMX connector address of the new JBoss Data Grid instance you want to monitor. For example:
      Connector Address:

      service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:7997/jmxrmi

      Copy to Clipboard Toggle word wrap

      Note

      The connector address varies depending on the host and the JMX port assigned to the new instance. In this case, instances require the following system properties at start up:

      -Dcom.sun.management.jmxremote.port=7997 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
      

      Copy to Clipboard Toggle word wrap
   3. Specify the Principal and Credentials information if required.
   4. Click Finish.
   

   View larger image

   

   Figure 22.8. Modify the values in the Deployment Options screen.

6. View Cache Statistics and Operations

   1. Click Refresh to refresh the list of servers.
   2. The JMX Servers tree in the panel on the left side of the screen contains the Infinispan Cache Managers node, which contains the available cache managers. The available cache managers contain the available caches.
   3. Select a cache from the available caches to view metrics.
   4. Select the Monitoring tab.
   5. The Tables view shows statistics and metrics.
   6. The Operations tab provides access to the various operations that can be performed on the services.
   

   View larger image

   

   Figure 22.9. Metrics and operational data relayed through JMX is now available in the JBoss Operations Network console.

Procedure 22.5. Monitor an Application Deployed in Standalone Mode

1. Start the JBoss Enterprise Application Platform Instance

   Start the JBoss Enterprise Application Platform instance as follows:
   1. Enter the following command at the command line or change standalone configuration file (/bin/standalone.conf) respectively:

      JAVA_OPTS="$JAVA_OPTS -Dorg.rhq.resourceKey=MyEAP"

      Copy to Clipboard Toggle word wrap
   2. Start the JBoss Enterprise Application Platform instance in standalone mode as follows:

      $JBOSS_HOME/bin/standalone.sh

      Copy to Clipboard Toggle word wrap

2. Deploy the Red Hat JBoss Data Grid Application

   Deploy the WAR file that contains the JBoss Data Grid Library mode application with globalJmxStatistics and jmxStatistics enabled.

3. Run JBoss Operations Network (JON) Discovery

   Run the discovery --full command in the JBoss Operations Network (JON) agent.

4. Locate Application Server Process

   In the JBoss Operations Network (JON) web interface, the JBoss Enterprise Application Platform process is listed as a JMX server.

5. Import the Process Into Inventory

   Import the process into the JBoss Operations Network (JON) inventory.

6. Optional: Run Discovery Again

   If required, run the discovery --full command again to discover the new resources.

Procedure 22.6. Monitor an Application Deployed in Domain Mode

1. Edit the Host Configuration

   Edit the domain/configuration/host.xml file to replace the server element with the following configuration:

   <servers>
   	<server name="server-one" group="main-server-group">
   		<jvm name="default">
   			<jvm-options>
   				<option value="-Dorg.rhq.resourceKey=EAP1"/>
   			</jvm-options>
   		</jvm>
   	</server>
   	<server name="server-two" group="main-server-group" auto-start="true">
   		<socket-bindings port-offset="150"/>
   		<jvm name="default">
   			<jvm-options>
   				<option value="-Dorg.rhq.resourceKey=EAP2"/>
   			</jvm-options>
   		</jvm>
   	</server>
   </servers>

   Copy to Clipboard Toggle word wrap

2. Start JBoss Enterprise Application Platform 6

   Start JBoss Enterprise Application Platform 6 in domain mode:

   $JBOSS_HOME/bin/domain.sh

   Copy to Clipboard Toggle word wrap

3. Deploy the Red Hat JBoss Data Grid Application

   Deploy the WAR file that contains the JBoss Data Grid Library mode application with globalJmxStatistics and jmxStatistics enabled.

4. Run Discovery in JBoss Operations Network (JON)

   If required, run the discovery --full command for the JBoss Operations Network (JON) agent to discover the new resources.