Session Management Services

Runtime Services

The RuntimeServices API enables you to monitor a running in-production system. It offers statistical functions and reporting, as well as logging functions. Typical uses for RuntimeServices include turning logging on or off and generating real time reports on the number and type of objects in a given cache or subcache.

For more information, see the RuntimeServices class in the Oracle Application Server TopLink API Reference.

Development Services

The DevelopmentServices API enables you to make changes to a running nonproduction application that can destabilize or even crash the application. For example, use the DevelopmentServices API to change the states of selected objects and modify and reinitialize identity maps. This feature is useful for stress and performance testing of preproduction applications and also enables you to build prototypes quickly and easily.

For more information, see the RuntimeServices class in the Oracle Application Server TopLink API Reference.

Using Session Management Services

To instantiate a session management service, you pass a session to the constructor. After instantiating the service, you can attach a graphical interface or other applications to the object to provide statistical feedback and runtime option settings.

import oracle.toplink.services.RuntimeServices;
import oracle.toplink.publicinterface.Session;
...
...
RuntimeServices service = newRuntimeServices ((session) session);
java.util.List classNames = service.getClassesInSession();

Session Management Services and BEA WebLogic Server

OracleAS TopLink support for BEA WebLogic Server automatically deploys the session management services to the JMX server. You can retrieve the JMX Mbeans with the following object names:

WebLogicObjectName("TopLink_Domain:Name=Development <Session><Name> Type=Configuration");
WebLogicObjectName("TopLink_Domain:Name=Runtime <Session><Name> Type=Reporting");

Session Name represents the session type and name under which you store the required session configuration in the toplink-ejb-jar.xml file.

For more information about the WebLogicObjectName API, see

http://e-docs.bea.com/wls/docs70/javadocs/weblogic/management/WebLogicObjectName.html