Random, Happy Dev Thoughts

(Alternate) Chicken and Egg Problem == solved: How to extract BeanSpy or PowerShell scripts if there is no discovery?

Christopher Crammond — Fri, 03 May 2013 20:24:15 GMT

I recently found another solution to the chicken v. egg problem that I mentioned in the previous blog post. This script from TechNet should be run on the Management Server and will copy BeanSpy and the JEE PowerShell scripts to a well-defined location. See which works for you.

Chicken and Egg Problem == solved: How to extract BeanSpy or PowerShell scripts if there is no discovery?

Christopher Crammond — Thu, 25 Apr 2013 21:30:33 GMT

One issue that you might experience with BeanSpy (or the universal discovery PowerShell script) is how to get a hold of these binaries. The expect flow is that the Management Packs (MPs) and Management Pack Bundles (MPBs) get imported, some discoveries occur, and then from the application server instance a task can be run to copy the binaries to disk. All of this is provided from the comfort of the Operations Manager Console. :)

Of course, the problem is simply:

The difference between theory and practice is that in theory they are the same, but in practice they are different.

Luckily some of my cohorts have detailed two potential workarounds:

Command-Line - Use PowerShell to extract the binaries (System Center Central blog post)
GUI approach - Use MPViewer to extract the binaries (Boris's OpsMgr Tools blog post)

MSSQL Report Builder: Connecting to a Report Server

Christopher Crammond — Tue, 05 Feb 2013 00:11:58 GMT

By far the most useful page that I have view today is this one about Connecting to a Report Server for MSSQL.

Howto: Monitor EJBs with BeanSpy in SCOM 2012 on WebSphere 6.1 (version 2)

Christopher Crammond — Thu, 31 Jan 2013 21:43:00 GMT

It would appear that yesterday's post may not work for everyone, and here is a second version that will bypass this problem.

The problem relates to the fact that I elected to have the newly created EJB class extend the base Microsoft.JEE.Application class from the Microsoft.JEE.Library management pack. It so happens that the library class has a key property of the ObjectName with a length of 512 (characters). It turns out that sometimes an object name can be more than that. In this case, the discovery data is gathered on the Agent and sent to the Management Server which fails. If you check your event viewer, you'll see something like:

The fix is pretty simple: instead of extending the existing class, just create a class that extends System.Component and create an appropriate relationship

 <ClassTypes>

 <ClassType ID="Microsoft.JEE.WebSphere.6.1.EJB.Application" Abstract="false" Accessibility="Public" Hosted="true" Base="System!System.ApplicationComponent">
 <Property ID="ApplicationName" Type="string" CaseSensitive="true" MaxLength="256" MinLength="0" />
 <Property ID="j2eeType" Type="string" CaseSensitive="true" MaxLength="32" MinLength="0" />
 <Property ID="ObjectName" Type="string" Key="true" CaseSensitive="true" MaxLength="1024" MinLength="0" />
 </ClassType>

 </ClassTypes>

 <RelationshipTypes>
 
 <RelationshipType ID="Microsoft.JEE.WebSphere.6.1.EJB.MonitoredApplicationServerHostsEjbRelationship"
 Accessibility="Public" Abstract="false" Base="System!System.Hosting">
 <Source ID="Source" MinCardinality="0" MaxCardinality="2147483647" Type="WebSphere61!Microsoft.JEE.WebSphere.6.1.Monitored.Profile" />
 <Target ID="Target" MinCardinality="0" MaxCardinality="2147483647" Type="Microsoft.JEE.WebSphere.6.1.EJB.Application"/>
 </RelationshipType>
 
 </RelationshipTypes>

Now, you need to update the discovery class mappings (b/c the class properties should now be part of the class above).

 <Discovery ID="Microsoft.JEE.WebSphere.6.1.EJB.Application.Discovery" 
 Target="WebSphere61!Microsoft.JEE.WebSphere.6.1.Monitored.Profile" Remotable="true" Enabled="true">
 <Category>Discovery</Category>
 <DiscoveryTypes>
 <DiscoveryClass TypeID="Microsoft.JEE.WebSphere.6.1.EJB.Application" />
 <DiscoveryRelationship TypeID="Microsoft.JEE.WebSphere.6.1.EJB.MonitoredApplicationServerHostsEjbRelationship" />
 </DiscoveryTypes>
 <DataSource ID="DS" TypeID="JEE!Microsoft.JEE.Discovery.MBeans.DataSource">
 <ApplicationServerGuid>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</ApplicationServerGuid>
 <ComputerName>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</ComputerName>
 <Protocol>$Target/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Monitored.Instance"]/Protocol$</Protocol>
 <Port>$Target/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Monitored.Instance"]/Port$</Port>
 <BaseURL />
 <JMXQuery>WebSphere:j2eeType=EJBModule,*</JMXQuery>
 <AdditionalArguments>&amp;MaxDepth=0</AdditionalArguments>
 <ReturnMultiplePropertyBags>true</ReturnMultiplePropertyBags>
 <UseAttributesInKeysOfReturnedPropertyBags>false</UseAttributesInKeysOfReturnedPropertyBags>
 <!-- Interval currently set to four hours -->
 <IntervalSeconds>14400</IntervalSeconds>
 <TimeoutSeconds>900</TimeoutSeconds>
 <ClassId>$MPElement[Name="Microsoft.JEE.WebSphere.6.1.EJB.Application"]$</ClassId>
 <InstanceSettings>
 <Settings>
 <!-- The following properties are defined for the Application's parent classes -->
 <Setting>
 <Name>$MPElement[Name="System!System.Entity"]/DisplayName$</Name>
 <Value>$Data/Property[@Name='/MBeans/javax.management.modelmbean.RequiredModelMBean/objectNameElements/name']$</Value>
 </Setting>
 <!-- These properties are for the WebSphere Configuration-->
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</Name>
 <Value>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</Name>
 <Value>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</Value>
 </Setting>
 <!-- The following properties are defined for the Application-->
 <Setting>
 <Name>$MPElement[Name="Microsoft.JEE.WebSphere.6.1.EJB.Application"]/ApplicationName$</Name>
 <Value>$Data/Property[@Name='/MBeans/javax.management.modelmbean.RequiredModelMBean/objectNameElements/name']$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="Microsoft.JEE.WebSphere.6.1.EJB.Application"]/j2eeType$</Name>
 <Value>$Data/Property[@Name='/MBeans/javax.management.modelmbean.RequiredModelMBean/objectNameElements/j2eeType']$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="Microsoft.JEE.WebSphere.6.1.EJB.Application"]/ObjectName$</Name>
 <Value>$Data/Property[@Name='/MBeans/javax.management.modelmbean.RequiredModelMBean/objectName']$</Value>
 </Setting>
 </Settings>
 </InstanceSettings>
 </DataSource>
 </Discovery>

Howto: Monitor EJBs with BeanSpy in SCOM 2012 on WebSphere 6.1

Christopher Crammond — Wed, 30 Jan 2013 22:43:00 GMT

By simply taking yesterday's post and applying the match of judicious copy-n-paste methodology: may I present a MP for managing EJBs for WebSphere 6.1.

All of the caveats regarding support (or rather lack thereof) and this is for information use apply. :)

Finally, the MP presented uses the debug product key and targets SCOM 2012 SP1; however, by a simple change to the reference section for the right key and adjust the appropriate MP versions this will work with SCOM 2012.

Update February 1st 2013: this implementation can be problematic as it limits the ObjectName to 512 characters. Refer to this posting for another implementation that declares a longer ObjectName (key) property.

Howto: Monitor EJBs with BeanSpy in SCOM 2012 on WebSphere 7.0

Christopher Crammond — Tue, 29 Jan 2013 00:02:00 GMT

Similar to my previous posting, here is a sample management pack for monitoring EJBs on WebSphere 7.0. For an explanation of what is happening, refer to the previous posting (and all of the legal warnings denying responsibility therein). :)

Basically, the differences are:

Changed references and class targets to point at WebSphere
Updated the discovery's JMX Query
Updated the discovery's "xpath-like" syntax used for string matching to find EJB class information

Howto: Monitor EJBs with BeanSpy in SCOM 2012 on JBoss 5

Christopher Crammond — Fri, 25 Jan 2013 23:46:00 GMT

Out-of-the-box, EJB discovery and monitoring are not supported by the SCOM 2012 JEE MPs (http://blogs.technet.com/b/random_happy_dev_thoughts/archive/2012/04/18/system-center-operations-manager-scom-2012-released.aspx). That said, there is nothing to preclude a customer to write their own management pack for doing so. In this blog post I will detail how one could do this for JBoss 5.

Introduction

Please note that this is provided as an instructional demonstration of the software capabilities and this management pack is not supported by Microsoft. And any other legal disclaimers I may have forgotten. :)

Most anything deployed to an application server (be it Tomcat, JBoss, WebSphere, or WebLogic) is represented as a MBean. The good news is that if it is a MBean, then BeanSpy can find and monitor it! That is the good news.

The other news (I would not call it bad), is that you need to facilitate this.

BeanSpy Output

Before you start writing a MP, first let's find the input were going after directly from BeanSpy. On Jboss 5, a query directly BeanSpy to list deployed EJB modules is:

http://localhost:8180/BeanSpy/MBeans?JMXQuery=jboss.management.local:j2eeType=EJBModule,*

I know this because I know this. :) If you don't already know what you're looking for, try a more general query and use find (i.e. Control + F on most browsers) to search for EJB to find what you're looking for - such as a specific application name. If all else fails, save the XML and open it in a fancy text editor that does syntax highlighting and code folding. Point being, figure out what exactly you're looking for first and the best JMX query to return that information

This will give XML that looks like below (note the MBean class returned will vary by Application Server and version of said Application Server):

<?xml version="1.0" encoding="UTF-8"?>
 <MBeans version="7.3.2106.0">
 <MBean Name="org.jboss.management.j2ee.EJBModule" objectName="jboss.management.local:J2EEApplication=null,J2EEServer=Local,j2eeType=EJBModule,name=profileservice-secured.jar">
 <Properties>
 <Property Name="jawsDeploymentDescriptor" type="java.lang.String"/>
 <Property Name="eventProvider" type="java.lang.Boolean">true</Property>
 <Property Name="javaVMs" type="[Ljava.lang.String;">
 <Property Name="javaVMs" index="0">jboss.management.local:J2EEServer=Local,j2eeType=JVM,name=Oracle Corporation 1.7.0</Property>
 </Property>
 <Property Name="statisticsProvider" type="java.lang.Boolean">false</Property>
 <objectName type="java.lang.String">jboss.management.local:J2EEApplication=null,J2EEServer=Local,j2eeType=EJBModule,name=profileservice-secured.jar</objectName>
 <objectNameElements type="objectName">
 <Domain>jboss.management.local</Domain>
 <J2EEApplication>null</J2EEApplication>
 <J2EEServer>Local</J2EEServer>
 <j2eeType>EJBModule</j2eeType>
 <name>profileservice-secured.jar</name>
 </objectNameElements>
 <Property Name="parent" type="java.lang.String">jboss.management.local:j2eeType=J2EEServer,name=Local</Property>
 <Property Name="cmpDeploymentDescriptor" type="java.lang.String"/>
 <Property Name="deploymentDescriptor" type="java.lang.String">
 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
 &lt;ejb-jar
 xmlns="http://java.sun.com/xml/ns/javaee"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
 http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
 version="3.0"&gt;
 &lt;display-name&gt;Secured ManagementView&lt;/display-name&gt;
 &lt;enterprise-beans&gt;
 &lt;session&gt;
 &lt;ejb-name&gt;SecureProfileService&lt;/ejb-name&gt;
 &lt;ejb-class&gt;org.jboss.profileservice.ejb.SecureProfileServiceBean&lt;/ejb-class&gt;
 &lt;session-type&gt;Stateless&lt;/session-type&gt;
 &lt;resource-ref&gt;
 &lt;res-ref-name&gt;profileService&lt;/res-ref-name&gt;
 &lt;res-type&gt;org.jboss.profileservice.spi.ProfileService&lt;/res-type&gt;
 &lt;mapped-name&gt;ProfileService&lt;/mapped-name&gt;
 &lt;injection-target&gt;
 &lt;injection-target-class&gt;org.jboss.profileservice.ejb.SecureProfileServiceBean&lt;/injection-target-class&gt;
 &lt;injection-target-name&gt;delegate&lt;/injection-target-name&gt;
 &lt;/injection-target&gt;
 &lt;/resource-ref&gt;
 &lt;/session&gt;
 &lt;session&gt;
 &lt;ejb-name&gt;SecureManagementView&lt;/ejb-name&gt;
 &lt;ejb-class&gt;org.jboss.profileservice.ejb.SecureManagementView&lt;/ejb-class&gt;
 &lt;session-type&gt;Stateless&lt;/session-type&gt;
 &lt;resource-ref&gt;
 &lt;res-ref-name&gt;profileService&lt;/res-ref-name&gt;
 &lt;res-type&gt;org.jboss.profileservice.spi.ProfileService&lt;/res-type&gt;
 &lt;mapped-name&gt;ProfileService&lt;/mapped-name&gt;
 &lt;injection-target&gt;
 &lt;injection-target-class&gt;org.jboss.profileservice.ejb.SecureManagementView&lt;/injection-target-class&gt;
 &lt;injection-target-name&gt;profileService&lt;/injection-target-name&gt;
 &lt;/injection-target&gt;
 &lt;/resource-ref&gt;
 &lt;/session&gt;
 &lt;session&gt;
 &lt;ejb-name&gt;SecureDeploymentManager&lt;/ejb-name&gt;
 &lt;ejb-class&gt;org.jboss.profileservice.ejb.SecureDeploymentManager&lt;/ejb-class&gt;
 &lt;session-type&gt;Stateless&lt;/session-type&gt;
 &lt;resource-ref&gt;
 &lt;res-ref-name&gt;profileService&lt;/res-ref-name&gt;
 &lt;res-type&gt;org.jboss.profileservice.spi.ProfileService&lt;/res-type&gt;
 &lt;mapped-name&gt;ProfileService&lt;/mapped-name&gt;
 &lt;injection-target&gt;
 &lt;injection-target-class&gt;org.jboss.profileservice.ejb.SecureDeploymentManager&lt;/injection-target-class&gt;
 &lt;injection-target-name&gt;profileService&lt;/injection-target-name&gt;
 &lt;/injection-target&gt;
 &lt;/resource-ref&gt;
 &lt;/session&gt;
 &lt;/enterprise-beans&gt;
 &lt;/ejb-jar&gt;
 </Property>
 <Property Name="jbossDeploymentDescriptor" type="java.lang.String"/>
 <Property Name="stateManageable" type="java.lang.Boolean">false</Property>
 <Property Name="ejbs" type="[Ljava.lang.String;"/>
 <Property Name="server" type="java.lang.String">unknown server name</Property>
 <Property Name="EventTypes" type="[Ljava.lang.String;">
 <Property Name="EventTypes" index="0">j2ee.object.created</Property>
 <Property Name="EventTypes" index="1">j2ee.object.deleted</Property>
 </Property>
 </Properties>
 </MBean>
 </MBeans>

Management Pack

Now that we know what we want to find, we need to write a management pack to find the EJBs. First, we'll declare a class Microsoft.JEE.JBoss.5.EJB.Application.EAR that extends the existing JBoss 5 EAR class:

 <ClassTypes>
 <ClassType ID="Microsoft.JEE.JBoss.5.EJB.Application.EAR" 
 Abstract="false" Accessibility="Public" Hosted="true"
 Base="JBoss5!Microsoft.JEE.JBoss.5.Application.EAR" />
 </ClassTypes>

Next, we need a discovery. EJBs live in an application server, so we should target the monitored instance of the JEE applications servers. Depending on the application server, you may be able to target the generic classes. For this article, I will target a specific JBoss 5 class because I do not want this discovery to run against other versions of JBoss.

The discovery needs to use the query mentioned above:

jboss.management.local:j2eeType=EJBModule,*

As listed above, the XML returned from the BeanSpy query needs to be parsed. Depending on what you need to pull out, you could have some fun with XPaths. Luckily, we are promised by underlying datasource that each MBean will be separated into its own XML chunk (so you probably don't need to worry about an instance & more than likely you'll just be parsing one MBean.

Here is the full discovery:

 <Discovery ID="Microsoft.JEE.JBoss.5.EJB.Application.EAR.Discovery" 
 Target="JBoss5!Microsoft.JEE.JBoss.5.Monitored.Configuration" 
 Remotable="true" Enabled="true">
 <Category>Discovery</Category>
 <DiscoveryTypes>
 <DiscoveryClass TypeID="Microsoft.JEE.JBoss.5.EJB.Application.EAR" />
 <DiscoveryRelationship TypeID="JEE!Microsoft.JEE.MonitoredApplicationServerHostsApplicationRelationship" />
 </DiscoveryTypes>
 <DataSource ID="DS" TypeID="JEE!Microsoft.JEE.Discovery.MBeans.DataSource">
 <ApplicationServerGuid>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</ApplicationServerGuid>
 <ComputerName>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</ComputerName>
 <Protocol>$Target/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Monitored.Instance"]/Protocol$</Protocol>
 <Port>$Target/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Monitored.Instance"]/Port$</Port>
 <BaseURL />
 <JMXQuery>jboss.management.local:j2eeType=EJBModule,*</JMXQuery>
 <AdditionalArguments>&amp;MaxDepth=0</AdditionalArguments>
 <ReturnMultiplePropertyBags>true</ReturnMultiplePropertyBags>
 <UseAttributesInKeysOfReturnedPropertyBags>false</UseAttributesInKeysOfReturnedPropertyBags>
 <!-- Interval currently set to four hours -->
 <IntervalSeconds>14400</IntervalSeconds>
 <TimeoutSeconds>900</TimeoutSeconds>
 <ClassId>$MPElement[Name="Microsoft.JEE.JBoss.5.EJB.Application.EAR"]$</ClassId>
 <InstanceSettings>
 <Settings>
 <!-- The following properties are defined for the Application's parent classes -->
 <Setting>
 <Name>$MPElement[Name="System!System.Entity"]/DisplayName$</Name>
 <Value>$Data/Property[@Name='/MBeans/org.jboss.management.j2ee.EJBModule/objectNameElements/name']$</Value>
 </Setting>
 <!-- These properties are for the JBoss Configuration-->
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</Name>
 <Value>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</Name>
 <Value>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</Value>
 </Setting>
 <!-- The following properties are defined for the Application-->
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/ApplicationName$</Name>
 <Value>$Data/Property[@Name='/MBeans/org.jboss.management.j2ee.EJBModule/objectNameElements/name']$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/j2eeType$</Name>
 <Value>$Data/Property[@Name='/MBeans/org.jboss.management.j2ee.EJBModule/objectNameElements/j2eeType']$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/ObjectName$</Name>
 <Value>$Data/Property[@Name='/MBeans/org.jboss.management.j2ee.EJBModule/objectName']$</Value>
 </Setting>
 </Settings>
 </InstanceSettings>
 </DataSource>
 </Discovery>

The only interesting piece in the discovery is mapping the object. A relic of how some of the work was done, the "XPath" is slightly different from the actual XML that is sent over. It turns out for several reasons it was necessary to slightly manage the XML returned by the discovery source. Rather than use the short name (MBean), the name attribute of the actual class is used by the logic that creates the individual discovery data items.

 <ClassId>$MPElement[Name="Microsoft.JEE.JBoss.5.EJB.Application.EAR"]$</ClassId>
 <InstanceSettings>
 <Settings>
 <!-- The following properties are defined for the Application's parent classes -->
 <Setting>
 <Name>$MPElement[Name="System!System.Entity"]/DisplayName$</Name>
 <Value>$Data/Property[@Name='/MBeans/org.jboss.management.j2ee.EJBModule/objectNameElements/name']$</Value>
 </Setting>
 <!-- These properties are for the JBoss Configuration-->
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</Name>
 <Value>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</Name>
 <Value>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</Value>
 </Setting>
 <!-- The following properties are defined for the Application-->
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/ApplicationName$</Name>
 <Value>$Data/Property[@Name='/MBeans/org.jboss.management.j2ee.EJBModule/objectNameElements/name']$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/j2eeType$</Name>
 <Value>$Data/Property[@Name='/MBeans/org.jboss.management.j2ee.EJBModule/objectNameElements/j2eeType']$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/ObjectName$</Name>
 <Value>$Data/Property[@Name='/MBeans/org.jboss.management.j2ee.EJBModule/objectName']$</Value>
 </Setting>
 </Settings>
 </InstanceSettings>

The trick is to make sure that the XPath matches (see above highlights).

The rest of the management pack is some rote state views and display strings - not too interesting. Since the EJB extends the existing JBoss Application class, EJBs will appear in that state view in addition to the new EJB state view that I created in this management pack.

As for monitoring, you are welcome to write your own monitors, but one blog post at a time. :)

For now, I would refer you to using the template wizard to generate some custom monitors (http://blogs.technet.com/b/random_happy_dev_thoughts/archive/2012/05/30/scomfaq-ch-scom-2012-jee-application-availability-monitor-template.aspx).

Extending Discovery Of Java Applications in SCOM 2012

Christopher Crammond — Thu, 24 Jan 2013 19:56:00 GMT

The solution to monitoring JEE Application Servers and Applications in SCOM 2012 is a good starting point, but sometimes you may want to do more. The good news is that the structure of theses MPs are extendable and this blog post will detail how to do that.

For instance, let’s suppose that I am a customer with my own Contoso (see http://blogs.technet.com/b/random_happy_dev_thoughts/archive/2012/03/26/sample-jee-application-contoso-order-service.aspx) application that I want to uniquely identify. There is not a way to change the default JEE discovery exclude certain applications; however, what you can do is create a discovery to create your own extended version of the existing JEE objects.

For the example below I have written a custom discovery that targets the Microsoft.JEE.Application objects from the Microsoft.JEE.Library MP. The discovery uses a simple condition detection module to filter on the name of the discovered application. The new class can be as simple as this:

<ClassType 
 ID="Contoso.JEE.SampleApplication" 
 Abstract="false" 
 Accessibility="Public" Hosted="true"
 Base="JEE!Microsoft.JEE.Application" />

The filtering is done in this library module where the TargetApplicationName is the application name that I want to find and ApplicationName is the name as reported from the object found by the existing Microsoft.JEE management packs. There is a discovery that has the hardcode name of the application I want:

 <Discovery ID="Contoso.JEE.CustomOrderService.Discovery" Target="JEE!Microsoft.JEE.Application"
 Remotable="true" Enabled="true">
 <Category>Discovery</Category>
 <DiscoveryTypes>
 <DiscoveryClass TypeID="Contoso.JEE.SampleApplication" />
 </DiscoveryTypes>
 <DataSource ID="DS" TypeID="Contoso.JEE.SampleApplication.Discovery.DataSource">
 <ClassId>$MPElement[Name="Contoso.JEE.SampleApplication"]$</ClassId>
 <TargetApplicationName>CustomOrderService</TargetApplicationName>
 <ApplicationName>$Target/Property[Type="JEE!Microsoft.JEE.Application"]/ApplicationName$</ApplicationName>
 <DisplayName>$Target/Property[Type="JEE!Microsoft.JEE.Application"]/ApplicationName$</DisplayName>
 <ObjectName>$Target/Property[Type="JEE!Microsoft.JEE.Application"]/ObjectName$</ObjectName>
 <PrincipalName>$Target/Host/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</PrincipalName>
 <Id>$Target/Host/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</Id>
 <j2eeType>$Target/Property[Type="JEE!Microsoft.JEE.Application"]/j2eeType$</j2eeType>
 <IntervalSeconds>14400</IntervalSeconds>
 </DataSource>
 </Discovery>

And the discovery call this module that does the dirty work of filtering.

 <DataSourceModuleType ID="Contoso.JEE.SampleApplication.Discovery.DataSource" Accessibility="Public">
 <Configuration>
 <IncludeSchemaTypes>
 <SchemaType>System!System.ExpressionEvaluatorSchema</SchemaType>
 </IncludeSchemaTypes>
 <xsd:element name="ClassId" type="xsd:string" />
 <xsd:element name="TargetApplicationName" type="xsd:string" />
 <xsd:element name="ApplicationName" type="xsd:string" />
 <xsd:element name="DisplayName" type="xsd:string" />
 <xsd:element name="ObjectName" type="xsd:string" />
 <xsd:element name="PrincipalName" type="xsd:string" />
 <xsd:element name="Id" type="xsd:string" />
 <xsd:element name="j2eeType" type="xsd:string" />
 <xsd:element name="IntervalSeconds" type="xsd:integer" />
 </Configuration>
 <OverrideableParameters>
 <OverrideableParameter ID="IntervalSeconds" Selector="$Config/IntervalSeconds$" ParameterType="int" />
 </OverrideableParameters>
 <ModuleImplementation>
 <Composite>
 <MemberModules>
 <DataSource TypeID="Contoso.SpecializedClass.Discovery.DataSource" ID="Specializer">
 <ClassId>$Config/ClassId$</ClassId>
 <IntervalSeconds>$Config/IntervalSeconds$</IntervalSeconds>
 <Expression>
 <RegExExpression>
 <ValueExpression>
 <Value>$Config/ApplicationName$</Value>
 </ValueExpression>
 <Operator>MatchesRegularExpression</Operator>
 <Pattern>$Config/TargetApplicationName$</Pattern>
 </RegExExpression>
 </Expression>
 <InstanceSettings>
 <Settings>
 <!-- These properties are for the Application Server Instance -->
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.ApplicationServer.Instance"]/Id$</Name>
 <Value>$Config/Id$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.ApplicationServer.Instance"]/HostName$</Name>
 <Value>$Config/PrincipalName$</Value>
 </Setting>
 <!-- The following properties are defined for the Application-->
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/ApplicationName$</Name>
 <Value>$Config/ApplicationName$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/j2eeType$</Name>
 <Value>$Config/j2eeType$</Value>
 </Setting>
 <Setting>
 <Name>$MPElement[Name="JEE!Microsoft.JEE.Application"]/ObjectName$</Name>
 <Value>$Config/ObjectName$</Value>
 </Setting>
 </Settings>
 </InstanceSettings>
 </DataSource>
 </MemberModules>
 <Composition>
 <Node ID="Specializer" />
 </Composition>
 </Composite>
 </ModuleImplementation>
 <OutputType>System!System.Discovery.Data</OutputType>
 </DataSourceModuleType>

Now that there is a discovery for my specific application, I can write rules specific to my new class. Since this order service that I have already exposes some metrics that I want to a MBean, I’ll just write my own rule that will capture this performance data and store it in the Perf Store.

 <Rule ID="Contoso.JEE.SampleApplication.PerformanceData.AverageTransactionTime" Target="Contoso.JEE.SampleApplication"
 Enabled="true" Remotable="true">
 <Category>PerformanceCollection</Category>
 
 <DataSources>
 <DataSource ID="DS" TypeID="JEE!Microsoft.JEE.Monitoring.UrlProbe.MBeans.DataSource">
 <ComputerName>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Monitored.Instance"]/HostName$</ComputerName>
 <Protocol>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Monitored.Instance"]/Protocol$</Protocol>
 <Port>$Target/Host/Property[Type="JEE!Microsoft.JEE.ApplicationServer.Monitored.Instance"]/Port$</Port>
 <BaseURL />
 <JMXQuery>com.contoso:Name=CustomPerformance,*</JMXQuery>
 <AdditionalArguments>&amp;MaxDepth=1</AdditionalArguments>
 <IntervalSeconds>300</IntervalSeconds>
 <TimeoutSeconds>100</TimeoutSeconds>
 </DataSource>
 </DataSources>
 
 <ConditionDetection TypeID="Performance!System.Performance.DataGenericMapper" ID="PerfMapper">
 <ObjectName>AverageTransactionTime</ObjectName>
 <CounterName>AverageTransactionTime</CounterName>
 <InstanceName />
 <Value>$Data/MBeans/MBean[@Name='com.contoso.ws.CustomPerformance']/Properties/Property[@Name='AverageTransactionTime']$</Value>
 </ConditionDetection>
 
 <WriteActions>
 <WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData"/>
 <WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData"/>
 </WriteActions>
 </Rule>

Finally, this application will appear in the view with all of the rest of the (application server specific) applications (i.e. there is not a new view created for only the Contoso applications. Of course you could do this by simply defining a view that targets your new class.

BeanSpy: WebLogic Application Server JMXQuery to list deployed applications

Christopher Crammond — Tue, 22 Jan 2013 22:24:00 GMT

If you are running WebLogic, here are a few quick steps to validating the BeanSpy installation.

Once you have deployed BeanSpy to a web application server, the next step is to see that it works. While look at the /Stats or /Stats/Info is a nice cross-platform solution, sometimes you want to know what is running on your specific application server.

As of this writing, the supported versions of WebLogic 10gR3 and 11gR1.

http://contoso:7001/BeanSpy/MBeans?JMXQuery=com.bea:Type=AppDeployment,*

Note: adjust hostname and port respectively

Finally, another quick test is to hit the previously mentioned Stats or Stats/Info pages for JVM information.

Finally, repeat this process for each admin AND managed server where BeanSpy is deployed.

BeanSpy: JBoss Application Server JMXQuery to list deployed applications

Christopher Crammond — Tue, 22 Jan 2013 22:17:00 GMT

IF you are running JBoss, here are a few quick steps to validating the BeanSpy installation.

Once you havedeployed BeanSpy to a web application server, the next step is to see that it works. While look at the /Stats or /Stats/Info is a nice cross-platform solution, sometimes you want to know what is running on your specific application server.

As of this writing, the supported versions of JBoss Application Server are 4, 5, & 6. JBoss allows users to deploy applications in both EAR and WAR formats. The EAR files will appear as J2EEApplications, while the WAR files will appear as WebModules. The respective queries are below:

Note: adjust hostname and port respectively

Finally, another quick test is to hit the previously mentioned Stats or Stats/Info pages for JVM information.