Tracking Scalability Data for RDC

RDC provides the capability to track the change in certain data related to the scalability of the system. When you enable this feature, RDC tracks the following metrics:

• Number of RDC users
• Number of Business Components for Java (BC4J) application modules
• Number of data entry sessions
• Number of DCAPI instances

For more information, see:

• Enabling Tracking of Scalability
  
• Viewing the Scalability Metrics
  

Enabling Tracking of Scalability

To enable tracking of scalability:

1. Login to admin server console for OPADomain and locate olsardc. See Locating the olsardc.ear File for details.
2. Open olsardc.ear using any utility to unzip. See Manually Extracting and Repacking the olsardc.ear File for details.
3. Navigate to the following path: OPA_HOME\rdc\olsardc.ear\RdcSurroundAdfWebUIWebApp.war\WEB-INF\
4. Open the web.xml file with a text editor.
5. Insert the following lines into the file:

   <context-param>     <param-name>enablesensor</param-name>     <param-value>1</param-value> </context-param>

   Note:

   Make sure the XML syntax is preserved when you insert these lines.
6. Save your changes.
7. Re-deploy olsardc. See Redeploying RDC with Customizations for details.
8. Restart the OPA server. See Restarting the OPA Server for details.

Viewing the Scalability Metrics

Once you enable tracking of scalability data, RDC will generate sensor reports at specific intervals. The sensor reports are CSV files. RDC saves the files in the application_path\log folder defined in rdcConfig.properties file.

For each instance running, RDC creates a new folder in the application_path\log folder:

      opasensorreport_n

      where n is the instance number.

The opasensorreport_n folder has four files that correspond to the metrics collected:

• NumberOfRdcUsers.csv — number of RDC users
• RdcAM.csv — number of BC4J application modules
• NumberOfDEWindows.csv — number of data entry sessions
• NumberOfDcapi.csv — number of DCAPI instances

Each file records a new entry whenever an event that triggers a change in value occurs, for example, when a user logs in or logs out. Note that RDC updates the files only at specific intervals (every 10 minutes). Therefore, the files may not always reflect the latest data.

In each file, the first column is the number of milliseconds since the WebLogic Server was started. The second column represents the number (metric) that is being tracked.