test

Oracle Waveset 8.1.1 System Administrator's Guide

Tuning the Waveset Profiler

Each Waveset server captures profiling data by default. You can use this data with the Waveset IDE to diagnose a large range of performance problems. However, capturing and storing this profiling data adds a measurable load to the server, which consumes both memory and CPU. In a stable production environment, disable the profiler in production servers. Enable the profiler only when you are investigating a performance problem.

Note –

For information about using the Waveset IDE, see Identity Manager IDE Frequently Asked Questions (FAQ) in Oracle Waveset 8.1.1 Release Notes.

Example 4–1 Modifying the SystemConfiguration Configuration Object

    The following example shows how to disable the Profiler from capturing data.

  1. Import the following XML to disable the profiler.

    Note –

    Setting the attribute value to true disables the profiler, and setting it to false enables the profiler.

  2. Use the lh import command to import the following XML

    <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE Waveset PUBLIC 'waveset.dtd' 'waveset.dtd'>

  <Waveset>
     <ImportCommand class='com.waveset.session.SystemConfigurationUpdater' >
       <Object>
         <Attribute name='server.default.disableProfiling'>
           <Boolean>true</Boolean>
         </Attribute>
       </Object>
     </ImportCommand>
   </Waveset>

  3. Restart all Waveset servers.