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

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:


  1. Changed references and class targets to point at WebSphere
  2. Updated the discovery’s JMX Query
  3. Updated the discovery’s “xpath-like” syntax used for string matching to find EJB class information



Comments (2)

  1. Anonymous says:

    This attached XML file is for the DEBUG version of OpsMgr!  If you want to use it with a signed version of the product (which all of you should have – shame if you do not 🙂 )

    See here getting the right string:…/locating-the-public-key-token-for-a-management-pack

  2. Anonymous says:

    Also, although the XML provided is targeting SCOM 2012 SP1, this will work with SCOM 2012 – just change the versions as appropriate and you're good-to-go.