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. Make sure the Script Profiler is enabled.

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

2. Open the Siebel Script Editor for a scriptable object, and then deliver the changes to the script to a repository.

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

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

3. 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.

4. Click the View menu, click Profiler, and then click Call Tree.

   The functions that Siebel CRM calls when it runs a script as a hierarchy are displayed 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.

5. In the Script Performance Profiler window, you can do the following:

   • Navigate between nodes to view the different parameters for a function.

   • Right-click a node, and then choose a menu item. For more information, see Navigating in the Script Performance Profiler Window.

6. (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 for Siebel Server Script Debugger.

7. Continue monitoring your script.

   For example, you want to 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.