Appeon 6.6 Prev Page Prev Page
Appeon Performance Tuning Guide
Appeon Performance
Expected performance level
Automatic performance boosting
Impact of the Internet and slow networks
Impact of “heavy” client-side logic
Impact of large data transmission
Performance-Related Settings
Appeon Developer performance settings
Appeon Enterprise Manager performance settings
Timeout settings
DataWindow data caching
Multi-thread download settings
Custom Libraries download settings
Log file settings
Internet Explorer performance settings
Web and application server performance settings
SAP Sybase EAServer
JVM startup option
Configuring data sources
HTTP properties
Microsoft IIS server
Recommendations for avoiding common errors on IIS
Advanced thread settings
Database performance settings
Recommended database driver
Recommended database setting
Identifying Performance Bottlenecks
Heavy window report
Appeon Performance Analyzer
Getting Started
Enabling Appeon Performance Analyzer
Starting Appeon Performance Analyzer
Getting to know Appeon Performance Analyzer
Removing Appeon Performance Analyzer
Working with Appeon Performance Analyzer
System Configuration
Calls Analysis
Download Analysis
View Detail
Additional Functions
Testing Appeon Web applications with LoadRunner
General Limitations on Performance Testing
Testing Environment
Testing Steps
Configuring AEM
Data Preparation (for update only)
Preparing Test Cases
Recording Scripts
Modifying Scripts
Additional steps for Update operation
Parameterization of SQL statements
Playing back Script to test the correctness of scripts
Setting Scenarios
Additional steps for Update operation
Running Scenarios
Modifying the scripts of NVO
Modifying the scripts of EJB/JavaBean
Errors appear when playing back scripts with LoadRunner 8.0
The value of sessionID is null
Error message appears in script playback
Error message in Appeon Log
Failed to parameterize scripts
Out of memory error and application server shut down
Field values do not change after parameterization and playback
Runtime errors causing scenario failure
Transactions failed
Unable to connect to remote servers
Analyzing log files
Analyzing Windows application log files
Analyzing Appeon Server log files
Analyzing active transaction log
Identifying Performance Bottlenecks of Web Server and Application Server
Identifying Performance Bottlenecks of DB Server
Deadlock analysis
Identifying Performance Bottlenecks of PB application
Analyzing performance bottlenecks of PB application
Tuning: DB Server
Tuning: Excessive Server Calls
Technique #1: partitioning transactions via stored procedures
Technique #2: partitioning non-visual logic via NVOs
Technique #3: eliminating recursive Embedded SQL
Technique #4: grouping multiple server calls with Appeon Labels
Tuning: Heavy Client
Technique #1: thin-out “heavy” Windows
Technique #2: thin-out “heavy” UI logic
Manipulating the UI in loops
Triggering events repeatedly
Performing single repetitive tasks
Initializing “heavy” tabs
Using ShareData or RowsCopy/RowsMove for data synchronization
Using computed fields
Using DataWindow expressions
Using complex filters
Using RowsFocusChanging/RowsFocusChanged events
Technique #3: offload “heavy” non-visual logic
Tuning: Large Data Transmissions
Technique #1: retrieving data incrementally
For Oracle database server
For all other database servers
Technique #2: minimizing excessive number of columns

Starting Appeon Performance Analyzer

Performance Analyzer is a Web tool that can only be launched side by side with the Web application you want to analyze.


  1. Appeon Performance Analyzer can only run on a 32-bit operating system.

  2. For the first time to run it, users should log into Windows as an administrator and turn off UAC (if using Windows Vista, Windows 7 etc.). To turn off UAC, go to Windows Control Panel | User Accounts, click Turn User Account Control on or off, then uncheck the check box of Use User Account Control (UAC) to help protect your computer.

You can start Appeon Performance Analyzer by the following steps:

Step 1 -- Run the Web application you want to analyze. The URL of the Web application should look like this: http://hostname:port/applicationname/x32_index.htm.

Note: Hostname indicates the IP address or machine name of the Web Server, and port indicates the HTTP port number of the Web Server. Port is optional and specifies the port number that your Web Server accepts for HTTP connections. If it is not specified, the default port is 80. If several Web Servers are running on the same machine, make sure that the port specified is a port of the Appeon Web Server.

Step 2 -- When the application has started up, append "?performance=1" to the application URL in the address bar and press Enter to refresh the application.

So the complete URL should look like http://hostname:port/applicationname/x32_index.htm?performance=1 orhttp://localhost/pet_world/x32_application.htm?performance=1.

Then the main window of the Performance Analyzer pops up.

Note: A prompt window pops up if the Performance Analyzer is run for the first time.

Performance analyze prompt

Click Yes to close the browser running the Web application; then re-do Step 1 and 2; Appeon Performance Analyzer will start up side by side with the Web application. Or click No, to let the Web application continue to run as it is.

The main window of Appeon Performance Analyzer looks like this.

Performance analyzer main window

Appeon Performance Analyzer will automatically open when the Web application runs by URL http://hostname:port/applicationname/x32_index.htm?performance=1, unless you deselect the Show window when started option in the Appeon Performance Analyzer Configuration dialog (from menu System | Config) See System Configuration for details.