Programming Contexts
Riverbed APIs fill different needs and are designed for use in different contexts. You can use Riverbed APIs in programs that execute in the following contexts:
- DES—APIs that support the DES context can be used in code that executes within a discrete event simulation, such as callback functions and process models. The primary APIs for this context are Kernel Procedures (KPs).
- GUI—APIs that support the GUI context can be used in code that executes within a Riverbed graphical program environment. The primary API for this context is the Ets package.
- EMA—APIs that support the EMA context can be used in code that executes independently of Riverbed programs. EMA programs typically are used to create, modify, and extract data from Riverbed models.
- ACE—APIs that support the ACE context can be used in code that executes within SteelCentral Transaction Analyzer.
Table 1: API Contexts
| Package | Prefix | DES | GUI | EMA | ACE |
|---|---|---|---|---|---|
| ACE | ace | 4 | |||
| Application Task Configuration | atc | ✔ | ✔ | ||
| External Model Access | Ema | ✔ | |||
| External Simulation Access | Esa | ✔ | |||
| External Tool Support | Ets | ✔ | |||
| Hardware Configuration | hcon | ✔ | |||
| HTML | Html | ✔ | |||
| HTTP | Http | ✔ | |||
| Import/Export | Imex | ✔ | |||
| Network Resources and Consumers | nrac | ✔ | |||
| OPNET Design and Analysis | Odan | ✔ | |||
| Output Model Access | Oma | ✔ | ✔ | ||
| OPNET Model Support | oms | ✔ | ✔ | ||
| Kernel Procedures | op | ✔ | |||
| Optimization | Optim | ✔ | |||
| OPNET System Environment | Osys | ✔ | ✔ | ||
| OPNET Visualization | Ovis | ✔ | ✔ | ||
| Programming | prg, Prg | ✔ | ✔ | ✔ | |
| Rule | Rule | ✔ | |||
| Terrain Modeling Module | tmm | ✔ | ✔ |