GetResults™

—Creating Speed and Agility

TotalWeb℠–Citrix

Monitoring of the End–User Experience

Customer Experience Management is the best way to determine how well IT services are meeting business demands. Knowing your end-users' experiences and pro-actively addressing issues before they call your help desk is the greatest level of customer awareness.

The Inforonics Difference:

knowing your Customer's Experiences helps you improve them

Inforonics' TotalWeb℠–Citrix monitoring provides a unique approach to measure and report on the performance and availability of Citrix applications. While many companies have struggled with the challenges of monitoring their Citrix applications, Inforonics has addressed this challenge extending our TotalWebView monitoring service to Citrix applications.

Inforonics TotalWebTotalWeb℠–Citrix is a browser-driven system to check, analyze, and measure the availability, functionality and performance of Web—and Citrix—hosted applications as experienced by an end-user with emphasis on application validity.

Unlike traditional ICA monitoring, TotalWebView–Citrix checks the application end-to-end. Your application may launch fine, but then fails because of an pplication-level issue such as an authentication problem or a backend database issue. TotalWebView–Citrix lets you know when your Citrix–published applications are not working for your users.

Application Validity:

Run your application using the Citrix web plug-in in either Firefox or Internet Explorer
Run the launched application and interact with it via keyboard and mouse actions
Save snippets of target elements as screenshots
Validity is measured by comparing known conditions to actual conditions

The Difference:

Is not a Citrix ICA monitoring solution, but rather one that interacts with your application
Shows you when Citrix gateways and other infrastructure fail by identifying their tell-tale dialog boxes
Allows business logic to be inserted into transactions to accomplish complex analysis of an application
Provides screenshots of errors.

Answer These Typical Questions:

What are users actually seeing when there is a failure with the application?
How often does the application fail?
How long does it take to perform a typical application transaction?
(Example for a CRM: log in, open a case, comment on the case, resolve the case)
How is performance of the application trending over time?
In what ways does the application fail the most?
Does clicking on a button or other control in my application consistently yield the correct result?

Benefits: