Using Siebel Tools > Using Siebel Script Editors > Using the Script Profiler >

Running the Script Profiler


This topic describes how to run the Script Profiler. For more information, see Overview of the Script Profiler.

To run the Script Profiler

  1. Log in to Siebel Tools.
  2. Make sure the Script Profiler is enabled.

    For more information, see Enabling the Script Profiler and Line Profiler.

  3. Open the Siebel Script Editor for a scriptable object, and then compile the script to a new repository.

    Make sure you compile the scripted objects or the projects that these objects reference to the repository that the Siebel client uses. If you do not compile these objects, then the Script Profiler does not display them. For more information, see Object Types You Can Script and Compiling Your Modifications.

  4. Open the configuration file that your Siebel application uses and replace the default siebel.srf file with the file that you compiled in Step 3.

    The Script Profiler is now enabled for runtime sessions and you can open the Siebel application from Siebel Tools in debug mode.

    For more information, see Specifying the Data Source That Siebel Tools Uses.

  5. In Siebel Tools, click the Debug menu, and then click Start.

    This step opens the Siebel application in debug mode. If Siebel CRM prompts you for a login, then enter the user name and password, and then click Run. For example, to run a script for the Business Service Simulator, you query for the Service Name and Method Name, and then click Run.

  6. In Siebel Tools, click the View menu, Profiler, and then click Call Tree.

    Siebel Tools displays the functions that Siebel CRM calls when it runs a script as a hierarchy in the Script Performance Profiler window. It displays the functions that it calls from other functions as child objects. For an example, see Example of the Script Performance Profiler Window.

  7. In the Script Performance Profiler window, you can do the following:
  8. (Optional) To set or reset line profile rules for a function, do one of the following:
    • Right-click a function node, and then click Enable Line Profiling or Disable Line Profiling. If you modify a line profile rule, then this modification applies to future calls to the function that this rule references. For more information, see Enabling the Script Profiler and Line Profiler.
    • Use the Debug tab in the Development Tools Options dialog box. For more information, see Setting Debug Options.
  9. Continue monitoring your script.

    For example, assume you must test custom script on a business service. In the Siebel client, you can navigate to the Business Service Simulator to run a business service, and then navigate back to the Profiler window to examine the profile data that Siebel CRM logs while the script runs.

Navigating in the Script Performance Profiler Window

You can right-click in the Script Performance Profiler window, and then click one of the following menu items. The menu items that Siebel Tools enables depends on the script. Some of these items might not be available for all scripts:

  • Expand Node. Expands the function node.
  • Expand All. Expands the entire tree of a function node.
  • Export. Exports profile data to a text file that you specify.

    You can use Expand All and Export in the Profiler toolbar. For more information about the Profiler toolbar, see Example of the Script Performance Profiler Window.

  • View Source. Navigates to the current function in the script. If a Script Editor window is not open for this function, then Siebel Tools opens a new editor window and places the cursor at the beginning of this function.
  • Enable Line Profiler. Enables a function for line profiling. If a function is not in the list of functions chosen for line profiling, then you can click Enable Line Profiler to enable it.
  • Disable Line Profiler. Disables a function for line profiling.
Using Siebel Tools Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.