Creating and Starting New Sessions
Use
You organize VMC profiling in sessions. With the session you can determine which data you want to collect and analyze.
Prerequisites
You are in the profiling overview of the VMC system administration (transaction SM53)
Procedure
...
1. Choose Create New Session.
2. In the Name field enter a name for the session that you will easily recognize again in the session overview. Together with the creation time stamp, profiling ID, client, and user name of the profiling user, the session is now uniquely specified. The session name is mandatory; you can use the fields in the general filter to restrict the data to be collected.
○ Client: System client in which the application program was started.
○ User name: System user name under which the application program was started. Client and user name of the current user are predefined.
○ Session: Number of the external session in which the program was started. On an SAP application server a GUI window of a user corresponds to an external session.
○ Function module: Name of the ABAP function module on whose associated Java implementation you want to restrict the data collection.
○ Reserve VM: When this is activated, all subsequent Java calls belonging to this profiling session will be processed by the same VM. This VM is reserved exclusively for this session.
The VM is reserved as soon as the session is started. Subsequently, only those requests that have parameters set for Client, User Name, Session and Function Module, are sent to this VM. This prevents the data collection from being potentially distributed to several VMs, making it easier to evaluate the data. On the other hand, by doing this you are creating a possible "artificial" system environment in which normal application behavior cannot be measured at all.
3. (Optional) Specify the analysis parameters for traces that affect aspects of memory usage. Due to limited space, the input elements are distributed on two tab pages: Memory 1 and Memory More information: Setting Analysis Parameters for Memory Usage
4. (Optional) Activate the method sampling by activating the trace on the Runtime tab page. The input field Stack Frames is used as described under Setting Analysis Parameters for Memory Usage.
5. (Optional) Activate the analyses for Java exceptions and the method trace by activating the trace on the tab page Application. The input field Class Filters is used as described under Setting Analysis Parameters for Memory Usage.
6. (Optional) Activate the analyses for the monitor trace and shared lock trace by activating the trace on the tab page Synchronization. The input fields Stack Trace and Class Filters are used as described under Setting Analysis Parameters for Memory Usage. With the shared lock trace, traces can be activated for the individual lock types. By default all traces are activated.
More
information:
Shared
Locks
7.
(Optional) Check
that your entries are consistent by choosing 
Check Parameters in the header bar.
8.
(Optional) Check that your entries are
consistent by choosing 
Check Parameters in the header bar.
9.
To start your
session, choose 
Start Session in the header bar.
The set analysis parameters are saved, the data collection starts, and the program returns to the overview screen. A note popup appears if no session name has been entered or no analysis activated.
If analysis
parameters have already been saved once on this application server, these
settings are copied into the input fields. You can delete the saved settings
by first choosing 
Delete Parameter in the header bar, and then Save Parameter.
More Information
Setting Analysis Parameters for Memory Usage