Skip to main content
ComponentsGermainUX JS Profiler anddepending on the monitoring scopeRUM ExtensionRUM JSand Engine Feature availability: GermainUX 2018.4 or laterEngineJS ProfilerMobile AppRPA Bot RecorderRUM JS
Availability2014.1 or later

What the JS Profiler captures

Browser and eScript evidence collected

Configure eScript diagnostics

Enable eScript and Object Manager data

Recommended investigation workflow

Steps from symptom to cause

Troubleshooting

Fix debugger data gaps
Configure eScript and Browser Real-Time Diagnostics for Oracle Siebel CRM GermainUX provides continuous and targeted diagnostics for technology issues affecting Oracle Siebel CRM users, including:
  • Browser errors
  • Slow or unresponsive interactions
  • Browser freezes
  • Expensive JavaScript execution
  • Repeated function calls
  • Slow network requests
  • Integration delays
  • Siebel server-side errors
  • eScript-related failures recorded by Siebel
  • Object Manager and database activity
The GermainUX JS Profiler provides browser-side diagnostics similar to the evidence available through browser developer tools, but collects it remotely from selected Siebel user sessions without requiring the user to reproduce the issue while a support engineer is present.

​
Siebel eScript

These technologies run in different execution contexts and require different monitoring methods. The browser extension cannot directly inspect server-side eScript execution. It can capture the browser action, request, response, error, and timing associated with that execution. Combine this evidence with Engine and log telemetry to diagnose the corresponding server-side eScript problem. References to Salesforce Apex in older versions of this page do not apply to Oracle Siebel CRM.

​
Continuous monitoring versus targeted diagnostics

Use standard RUM continuously. Enable detailed JS profiling only for the users, pages, scripts, and time periods required for a specific investigation.

​
When to use the JS Profiler

Deploy the JS Profiler when RUM identifies a symptom but does not provide enough evidence to isolate its cause. Typical cases include:
  • A Siebel click is consistently slow.
  • A screen, view, or applet freezes the browser.
  • The browser consumes excessive CPU.
  • A custom client-side script is suspected.
  • A function runs repeatedly or recursively.
  • A JavaScript exception affects a workflow.
  • A network request blocks the interface.
  • Only certain users or browsers experience the problem.
  • The issue cannot be reproduced by support personnel.
  • Session Replay shows the impact but not the responsible code.

​
What the JS Profiler captures

Depending on the supported browser, profiler version, and configuration, the collected evidence can include:
  • JavaScript function names
  • Call relationships
  • Function execution counts
  • Exclusive execution time
  • Cumulative execution time
  • Browser activity
  • Network requests
  • Errors and stack traces
  • Siebel screen, view, and applet context
  • User and session context
  • Related RUM clicks and transactions

​
Exclusive and cumulative time

A function with high exclusive time is itself expensive. A function with high cumulative but low exclusive time is delayed primarily by functions or operations beneath it.

​
Prerequisites

Before enabling targeted diagnostics:
  • Configure the Siebel application in GermainUX.
  • Deploy continuous user monitoring.
  • Deploy the supported GermainUX RUM Extension if required by the environment.
  • Install the GermainUX JS Profiler extension on selected computers.
  • Verify that browser-extension policies permit the extension.
  • Confirm that the selected users can reproduce the issue.
  • Confirm that browsers can reach GermainUX.
  • Configure the Engine and Siebel log monitoring for server-side correlation.
  • Review privacy and data-retention requirements.
  • Identify a controlled profiling scope.
See JS Profiler Deployment for Oracle Siebel CRM.

​
Deploy the browser extension

Install the supported GermainUX JS Profiler extension on the computers of the users or testers included in the investigation. For enterprise deployments, distribute it through:
  • Google Chrome Enterprise
  • Microsoft Edge management policies
  • Managed browser-extension policies
  • An approved internal extension store
  • The organization’s endpoint-management platform
After installation:
1

Confirm that the extension is enabled

2

Verify that it recognizes the intended Siebel URL

3

Confirm that it has retrieved its configuration

4

Open a new browser session

5

Sign in to Siebel

6

Reproduce a controlled interaction

7

Verify that profiler data appears in GermainUX

​
Configure the profiling scope

Limit profiling using the most precise available criteria. Possible criteria include:
  • Application
  • Environment
  • Siebel URL
  • User or user group
  • Computer
  • Browser
  • Screen or view
  • Applet
  • Script
  • Time window
  • Troubleshooting case
A recommended scope is:
Expand the scope only if the initial capture does not provide sufficient evidence.

​
Configure Siebel context

Associate profiler data with the relevant Siebel dimensions:
  • User
  • Session
  • Application
  • Environment
  • Screen
  • View
  • Applet
  • Command
  • Browser
  • Computer
This makes it possible to trace a slow user click to its functions and requests, then compare it with other users or sessions performing the same workflow.

​
Configure eScript diagnostics

For eScript and Object Manager analysis, configure the GermainUX RUM JS, JS Profiler and Engine to collect:
  • eScript end-to-end execution (front and backend)
  • Object Manager logs
  • Server Manager output
  • Siebel errors and exceptions
  • Workflow and integration events
  • FDR files
  • Core dumps
  • Related database activity
Verify that error codes, component aliases, process IDs, task IDs, users, and timestamps are extracted. These values help correlate the browser action with the corresponding server-side execution. See:
1

Use RUM to identify a slow click, error, freeze, or workflow

2

Review the affected session and Session Replay

3

Identify a user or test account that can reproduce the issue

4

Enable JS Profiler for that controlled scope

5

Reproduce the workflow

6

Review the browser execution timeline

7

Compare exclusive and cumulative function times

8

Identify repeated or expensive functions

9

Review related network requests

10

Correlate the browser evidence with Object Manager logs and server telemetry

11

Identify the responsible script, eScript, integration, configuration, or database operation

12

Implement the correction

13

Repeat the same scenario

14

Compare performance before and after the change

15

Disable detailed profiling when the investigation is complete

​
Example: diagnosing a slow Siebel click

A complete investigation can follow this path:
Review the complete timeline rather than assuming the longest browser function is always the root cause. It may simply be waiting for a server or integration response.

​
Privacy and security

Detailed profiling can expose script names, URLs, parameters, errors, and diagnostic values. Before enabling it in production:
  • Use an approved extension package.
  • Distribute it through managed enterprise channels.
  • Restrict profiling to authorized users.
  • Use encrypted communication.
  • Exclude passwords and authentication tokens.
  • Mask customer and employee information.
  • Avoid capturing sensitive URL parameters or response content.
  • Restrict access through GermainUX roles.
  • Define a suitable retention period.
  • Disable profiling after the investigation.
Do not use detailed profiling as an unrestricted, permanent capture mechanism for every production user.

​
Performance safeguards

The JS Profiler collects more detailed data than standard RUM and can introduce additional browser and processing overhead. To control its impact:
  • Begin with one or a small number of users.
  • Limit profiling to the affected Siebel domain.
  • Exclude unrelated and third-party scripts.
  • Profile only the required workflow.
  • Use a limited time window.
  • Monitor browser CPU and memory.
  • Review collected data volume.
  • Disable profiling after sufficient evidence is captured.
If browser performance degrades, reduce the scope or level of detail before continuing.

​
Validate the configuration

Confirm that:
  • The JS Profiler extension is installed and enabled.
  • The intended Siebel URL is recognized.
  • Only selected users or computers are profiled.
  • JavaScript function data appears in GermainUX.
  • Exclusive and cumulative times are available.
  • Network requests are captured.
  • Errors retain their stack traces.
  • Profiler data is associated with the correct user session.
  • Screen, view, and applet context are correct.
  • Server-side errors and logs can be correlated by time and context.
  • Sensitive data is excluded.
  • Browser overhead remains acceptable.

​
KPIs

Use the Siebel Click KPIs and related browser or network KPIs to begin the investigation. See KPIs for Oracle Siebel CRM. Relevant KPI categories can include:
  • Siebel user clicks
  • Browser transactions
  • JavaScript execution
  • JavaScript console errors
  • Outbound HTTP requests
  • Object Manager transactions
  • Siebel errors
  • Integration requests
  • Database operations

​
Dashboards

Go to: Workspace > Left Menu > Dashboards > All Search for Siebel dashboards such as:
  • Siebel Performance
  • Siebel Availability
  • Siebel User Experience
  • Insights for DX
Use the AnalysisDashboard and instance-level drill-through to correlate:
  • Slow clicks
  • Browser functions
  • Network requests
  • Errors
  • Server transactions
  • Affected users and sessions

​
Troubleshooting

​
No profiler data appears

Verify:
  • The extension is installed and enabled.
  • The browser version is supported.
  • The Siebel URL matches the configuration.
  • Profiling is enabled for the current user or computer.
  • The browser was restarted after deployment.
  • Enterprise policy has not blocked the extension.
  • Proxy and TLS settings permit communication.
  • The extension has refreshed its configuration.

​
JavaScript details are incomplete

Check:
  • Profiling began before the interaction.
  • The intended scripts are included.
  • The page was refreshed after profiling was enabled.
  • The extension version is supported.
  • The code executes in the browser rather than on the Siebel server.

​
No eScript details appear

Remember that Siebel eScript normally executes on the browser and on the application server. Verify:
  • RUM deployment
  • JS Profiler deployment
  • Engine deployment
  • Availability of supported server-side tracing
Browser profiling alone cannot expose internal server-side eScript execution.

​
Browser performance degrades

Reduce:
  • RUM monitoring frequency and depth
  • JS Profiler

Dashboard & Reports

Dashboard & Reports

AI

Insights & Recommendations

Analytics

More Analytics Features

Automation

More Automation Features

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.