AppLoader
How It Works |
|
|
The end to end monitoring by AppLoader is achieved by robots that simulate multiple users from PC's at multiple test locations. You can set up a scenario in minutes, and then apply consistent, measurable, and repeatable loads, and use the data to pinpoint scalability concerns before they impact end users. Read more... |
|
|
|
AppLoader is a tool that can help you simulate user actions on any kind of application for any number of users. It allows you to load stress applications or to test the quality of the applications you deployed.
You can build any scenario with the AppLoader Station without scripting, (including mouse events, keyboard inputs, if conditions, etc), and replay these actions as an automat. AppLoader allows you to indicate WAIT times so the scenario will not proceed until these same objects appear at playback time. That way, the script never gets desynchronized even if the tested application becomes less responsive. For Windows objects that don't have a "handle", AppLoader provides a way to capture Bitmaps around the mouse cursor so playback will not continue until these same Bitmaps appear at playback time.
AppLoader generates performance reports, charts and triggers alarms if playback exceeds recording time by a certain percentage. In short, AppLoader is not only a tool to load stress applications on IT platforms, but is also a perfect tool for tracking user satisfaction.
AppLoader also works with Terminal Services from Microsoft and MetaFrame from Citrix. Let's say you need to simulate 100 users on a specific application, you can then set a Terminal Server or a MetaFrame Server to host these 100 virtual users instead of setting 100 physical PCs. Install AppLoader Agent on Terminal Server, Build your Script, Deploy the Script to other Terminal Server sessions and you're done. Additionally, AppLoader Agent can drive both RDP and ICA sessions from inside or outside the session.
AppLoader Modules
AppLoader is comprised of 4 parts: the AppLoader Station, the Management Console, the Session Initiator, and the AppLoader Reporter. Read more ...
|
