org.eclipse.persistence.platform.server.JMXServerPlatformBase
| Modifier and Type | Method and Description |
|---|---|
| public String | Returns: String applicationNameINTERNAL: 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. |
| getApplicationName | back 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"
| |
| prepareServerSpecificServicesMBean | back 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. | |