EclipseLink/DesignDocs/316513

Design Specification: Extend WebLogic 10.3 JMX MBean support to JBoss 5.1.0 and WebSphere 7 as generic API

Work in Queue

• 316513: JMX: Refactor MBean support to include JBoss and WebSphere
  • 316510: JMX: Add JMX MBean support to WebSphere 7
  • 316511: JMX: Add JMX MBean support to JBoss 5.1.0 EAP
  • 316512: JMX: Add JMX MBean support to Glassfish 3 - nofix
  • 316509: JMX: Move JMX MBean support for WebLogic 10.3 to a generic ServerPlatformBase
  • 265540: JMX: Add runtime services MBean monitoring to Java SE clients

Completed Work

• Design document for generic JMX MBeans for WebLogic
• Bug# 248748 - WebLogic extensions to generic JMX MBeans
• JMX MBean Tutorial for Oracle WebLogic Server

JPA EAR, EJB, WAR and SE (DDL Generation) WebLogic 10.3 J2EE application Eclipse projects in SVN - use to perform JMX MBean registration

Document History

Date	Author	Version Description & Notes
2010-06-10	Michael O'Brien	0.1 Starting Draft for Generic JMX MBean support to extend WebLogic 10.3 support to JBoss 5.1.0 EAP and WebSphere 7 for ER 316513
2010-06-22	Michael O'Brien	0.2 Develop/Document JBoss 5.1.0 EAP JMX registration code ER 316511

Project overview

• This document is an extension of the work done in enhancement 248748 that added JMX MBean support for EclipseLink to WebLogic 10.x.

Analysis

Enabling JMX MBeans

• The following properties will continue to enable registration for any capable application server.
  • http://wiki.eclipse.org/EclipseLink/DesignDocs/248748#Disabling_EclipseLink_Managed_Lazy_Registration

JBoss JMX Integration

• 20100622: This section details the JMX registration code for EclipseLink MBeans on JBoss 5.1.0 EAP
• See jar signing and JMX prepending issues solved in bug# 305331 specific to the JBoss EAP edition that need to be covered off.

Testing

JBoss Specific EAR Configuration

• The following scenario specifies @Remote on the remote interface and @Stateless on the stateless session bean.
  • This results in the following JNDI name emitted by the server on EAR deploy

@Stateless(name="ApplicationService", mappedName="ApplicationService")
@Remote(ApplicationServiceRemote.class)
public class ApplicationService implements ApplicationServiceRemote  {
	@PersistenceContext(unitName="example", type=PersistenceContextType.TRANSACTION)	
	private EntityManager entityManager;
...
}
 
public class FrontController extends HttpServlet implements Servlet {
    public static final String APPLICATION_SERVICE_JNDI_NAME 
      = "org.eclipse.persistence.example.jpa.server.jboss.EnterpriseEAR/ApplicationService/remote-org.eclipse.persistence.example.jpa.server.business.ApplicationServiceRemote";    
 
    /**
     * Get the SSB ApplicationService bean - using a JNDI context lookup (no EJB injection was used on this servlet)
     * @param viaJNDILookup
     * @return
     */
    public ApplicationServiceRemote getApplicationService(boolean viaJNDILookup) {
        if(null == applicationService && viaJNDILookup) {
            try {
                Hashtable<String, String> env = new Hashtable<String, String>();      
                env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");     
                env.put(Context.PROVIDER_URL, "localhost");      
                env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces" );     
                InitialContext ctx = new InitialContext(env);
                System.out.println("FrontController.getApplicationService() JNDI lookup of " + APPLICATION_SERVICE_JNDI_NAME);
                return (ApplicationServiceRemote) ctx.lookup(APPLICATION_SERVICE_JNDI_NAME);            
            } catch (Exception e) {
                e.printStackTrace();
                throw new RuntimeException("couldn't lookup Dao", e);
            }
        } else {
            return applicationService;
        }
    }
...
}