Top Description Methods
org.eclipse.persistence.platform.server

public Interface JMXEnabledPlatform

Known Direct Implementers
org.eclipse.persistence.platform.server.glassfish.GlassfishPlatform, org.eclipse.persistence.platform.server.was.WebSphere_7_Platform, org.eclipse.persistence.platform.server.wls.WebLogic_10_Platform, org.eclipse.persistence.platform.server.jboss.JBossPlatform, org.eclipse.persistence.platform.server.wildfly.WildFlyPlatform

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
org.eclipse.persistence.platform.server.JMXServerPlatformBase

Method Summary

Modifier and TypeMethod and Description
public String

Returns:

String applicationName
getApplicationName
()

INTERNAL: getApplicationName(): Answer the name of the module (EAR name) that this session is associated with.

public 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

getApplicationNameback to summary
public 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

String applicationName

prepareServerSpecificServicesMBeanback to summary
public 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()