JMXEnabledPlatform (EclipseLink Core 3.0.3-RC2 API)

All Known Implementing Classes:

GlassfishPlatform, JBossPlatform, WebLogic_10_Platform, WebLogic_12_Platform, WebSphere_7_Platform, WebSphere_EJBEmbeddable_Platform, WebSphere_Liberty_Platform
```
public interface JMXEnabledPlatform
```
PUBLIC: This interface must be implemented by server platform classes that have JMX/MBean functionality enabled in EclipseLink.
As of EclipseLink

Since:

EclipseLink 2.1.1

See Also:

JMXServerPlatformBase

Method Summary

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`String`	`getApplicationName()`	INTERNAL: getApplicationName(): Answer the name of the module (EAR name) that this session is associated with.
`void`	`prepareServerSpecificServicesMBean()`	INTERNAL: prepareServerSpecificServicesMBean(): Server specific implementation of the creation and deployment of the JMX MBean to provide runtime services for the databaseSession.

- Method Detail
  - prepareServerSpecificServicesMBean
```
void prepareServerSpecificServicesMBean()
```
    INTERNAL: prepareServerSpecificServicesMBean(): Server specific implementation of the creation and deployment of the JMX MBean to provide runtime services for the databaseSession. JMX Implementing platform classes must override this function and supply the server specific MBean instance for later registration by calling it in the constructor.
    
    Since:
    
    EclipseLink 2.1.1
    
    See Also:
    
    ServerPlatform.isRuntimeServicesEnabledDefault(), ServerPlatform.isRuntimeServicesEnabled(), ServerPlatform.disableRuntimeServices(), ServerPlatform.registerMBean()
  - getApplicationName
```
String getApplicationName()
```
    INTERNAL: getApplicationName(): Answer the name of the module (EAR name) that this session is associated with. Answer "unknown" if there is no application name available. Default behavior is to return "unknown" There are 4 levels of implementation. 1) use the property override weblogic|jboss|glassfish|websphere.applicationName, or 2) perform a reflective weblogic.work.executeThreadRuntime.getApplicationName() call on WebLogic for example 3) extract the moduleName:persistence_unit from the weblogic classloader string representation, or 3) defer to superclass - usually return "unknown"
    
    Returns:
    
    String applicationName