The Citrix ICA Client Integration with Mercury Interactive is an extension of the ICA Client Object that first shipped with the MetaFrame XP 1.0 Client CD and was included with the ICA Win32 Client, version 6.01. The initial release of the ICA Client Object provided an application programming interface (API) to the Citrix Win32 ICA Client.
Using this API, the ICA Client Object can be embedded into applications and scripts to launch ICA sessions while shielding the mechanics of accessing a MetaFrame XP Server Farm. This integration extends this functionality by exposing functions that allow programmatic control of actions within an ICA session such as mouse movements and keystrokes. Additionally, modifications have been made to ICA client code to allow the launching of a session with minimal resource requirements; thus allowing numerous connections to be made and controlled from a single client machine.
Client Based Scalability Testing advantages (Pre-deployment):
- Simulate hundreds of users with just a few workstations.
- Load testing tools can be used which can effectively emulates real environments.
- Define, test, and measure performance of definable business transactions.
- Pinpoint potential bottlenecks and resolve before going production.
- Reduce risk by load testing just before going live.
Application Performance Management (Post-deployment):
- End to End monitoring of infrastructure, including MetaFrame XP systems (synthetic transactions).
- Segmented metrics provide information for increasing performance and capacity planning of infrastructure.
LoadRunner for Citrix Functionality: The LoadRunner for Citrix integration provides the ability to launch multiple ICA sessions from a single client machine as well as programmatically control the actions of a session from the client machine. The following list briefly outlines the core functionality exposed through the Citrix Client integration. These items are explained in detail in the “readme” and API function list included with the integration.
- Scalability: Exposes 4 modes of operations: Normal, Headless, Windowless, and Renderless.
- Windows Information: (1)Exposes some window events such as re-size / move / create / destroy, etc. (2). Allow querying of window information such as caption / style / position, etc.
- Input Events: Expose events such as Mouse Move / Mouse Click / Key Down, etc.
- Input Simulation: Allow simulation of mouse and keyboard events.
- Other APIs: ScreenShot API to get screen hash or actual bitmap and Ping API to get network latency.
Rahnuma is a technical content writer at software testing stuff. A software engineer by degree and a dynamic content creator by passion, she brings to table over 3 years of writing experience in tech niche. Combining her enthusiasm for writing and technology, she loves to share her thoughts on the latest tech trends.