Using Standard Application Models
Standard application models include preconfigured models of the following commonly-used network applications:
Table 2: Standard Application Models
| Available Application | Description |
|---|---|
| FTP in Application Modeling | File transfer |
| Email in Application Modeling | Sending and receiving email |
| Peer-to-Peer File Sharing in Application Modeling | P2P file sharing |
| Remote Login in Application Modeling | Rlogin (telnet) |
| Database in Application Modeling | Database queries and updates |
| HTTP in Application Modeling | Web browsing |
| Mobile User Applications in Application Modeling | User applications for smartphones and other mobile devices |
| Print in Application Modeling | Print job submission |
| Voice in Application Modeling | On-Off voice model |
| Video Conferencing in Application Modeling | Video conferencing involving image exchanges |
These models are shipped as part of the standard model suite. Each of these models has attributes that relate to a specific standard application and generate an appropriate traffic pattern.
Note: Standard application models have default values that represent typical application behavior. To customize the behavior to represent your own network, you must modify the values, as described in Standard Applications Supported by Application Models.
For example, the FTP model has attributes for file size, upload/download ratio, and so on, while the Voice model has attributes for encoder scheme, talk/silence duration, and other voice-related attributes. Similarly, from a behavior perspective, the FTP model uploads/downloads files directly over the user-configurable transport protocol (TCP/UDP, for example), while Voice runs on RTP streams and can use SIP signalling.
Advantages
Standard application models enable you to create representative models for commonly-used network applications quickly. The attributes and statistics for these models are targeted for the specific application they represent and are simple to understand and configure.
Limitations
Standard application models represent common network applications in a generic way and do not represent any specific vendor's implementation of the application. In actual networks, each application type has specific vendor implementations that create different traffic patterns.
Standard application models represent only two-tier (client-server or peer-to-peer) applications and cannot model multi-tier applications such as WebService or enterprise resource planning (ERP). Standard application models are not integrated with the Advanced Server Models.
Use Cases
Standard application models are useful for studying traffic generated by a typical user or to model an office environment in which most traffic is due to the usage of standard network applications such as FTP, Email, HTTP, and so on. These models provide the necessary traffic generation patterns for performing capacity planning and response time studies.
Using the Custom Application Model
The custom application model is more of an application modeling framework than a true model. It lets you define your own, custom traffic pattern for your study instead of using a more generic model. The custom application model breaks down the application into smaller components known as tasks and phases and lets you configure each detail of how and when the application sends requests and responses, how it sets up and reuses connections, and how much time is spent in server processing, for example.
Advantages
The custom application model has no predefined behavior and follows only the specifications you configure. It is a flexible model that lets you configure it to behave in a variety of ways.
The model supports multi-tier applications, so there is no limit to the number of tiers over which you can configure an application to run. Custom application model is integrated with the Advanced Server Models.
Limitations
The custom application model provides a high level of configurability, which means that you must specifically configure each attribute to represent the behavior you want to model. Though it is possible to capture some basic application decision-making logic in a custom application model with attribute configuration, full support for programmable logic is not supported.
Use Cases
The custom application model is useful for modeling multi-tier, complex applications in which the architecture, in terms of its transactions, is known and in which there is limited logic that can alter the application traffic pattern. The model is also useful for modeling application-layer signaling protocols, which usually have well-defined behavior.