The basic steps to use Application Performance Explorer are:
With Application Performance Explorer you can define a variety of parameters to determine their overall impact on your application's performance. Each of the profiles uses the same set of component object types, with user settings to control various aspects of their functionality.
APE profiles are divided into two categories: asynchronous and synchronous. Each profile contains preconfigured settings for each of the component characteristics, quantities, connection options, workers, services, and clients. All of these settings collectively form the profile of the application design scenario to be modeled. You can also create your own profile by selecting an existing profile, individually configuring the component services, and then saving the profile with a custom name.
You configure each type of object by clicking any of the five large buttons on the APE Manager user interface.
The buttons display dialog boxes that specify the number of objects to be created, data passing options, timing requirements, callback options, logging options, and other variations in the construction and use of the objects. Configuring the component objects provides great flexibility for modeling your enterprise application. You can even specify your own component service objects.
Once the test configuration is complete, you click Start to run the APE test. As the test runs, certain test events such as creating the clients and service objects appear in the results window. When the test is complete, you can view the overall test performance in the results window. As you become familiar with how Application Performance Explorer works and what it can do, you might want to store the detailed test information by configuring the log file to save selected test events.
In the procedure below, you will select a typical APE profile, make a few simple modifications, run a performance test, and examine the output.
To run a simple APE test
The main Application Performance Explorer window appears.
The Client Options dialog box appears.
This shortens the duration of the test to the time it takes to make 50 client calls (instead of the default 100 calls).
This causes the test to allocate four concurrent client processes on the single APE Manager machine. More than one client process is realistic, since a user might be expected to simultaneously run at least four applications (such as your enterprise application, word processing, scheduling, and e-mail).
The results window shows that all requested clients were successfully created for a test run total of 200 calls (50 calls for each of four client processes). The Elapsed Time, Client Calls Per Second, and Overall Calls Per Second are also indicated.