 |
|
|
|
|
|
|
|
 |
 |
|
|
 |
|
|
| | System Architecture
|
| |
The Veraterm Technology components form four layers as shown in the diagram, below.
The core of the Veraterm System, the "Veraterm Technology Engine" (VTE)
is the combination of the service with the development toolkit and API (Application programmers' Interface).
The VTE is included with all Veraterm products and solutions.
|
| | 
|
| |
Veraterm Service
|
|
 |
Implemented as a standalone process |
|
Handles multiple host applications and Veraterm toolkit/API objects |
|
Manages most of the functionality described in the previous section (MRAA diagram) |
|
Manages system resources such as Logins, Connections, Parsers, Term Recognizers,
Metadata Objects and Entity Containers |
|
Accessible only to the Veraterm Toolkit/API. No other external access is allowed. |
|
The service component will be used by DMA for product enhancement and for additional products
that utilize Veraterm Technology |
Veraterm Toolkit/API
|
|
|
Implemented as an apartment-threaded DLL. All public classes are documented in the
Developer Reference Manual. This is the "application programmers' interface" (API)
to the Veraterm System. At last count it contained over 100 public classes. |
|
Services all functional aspects of Veraterm and Smart Tag solutions with tools and processes. |
|
To Smart Tag developers, this layer is a Smart Tag Development Toolkit. |
|
Solutions Partners use this layer to develop products and Veraterm Add-Ins. |
Veraterm Products
|
|
|
Using the VTE as a common foundation, DMA has packaged the product with different combinations of
connectors and functionality to service the needs of different markets. |
|
Personal Edition: For single users integrating with a single database application. |
|
Professional Edition: Full-featured product with the ability to connect to multiple database
applications. Supports multi-user configuration. |
|
Enterprise Edition: For organizations needing enterprise-level features such as
application-server integration, custom term-recognizer creation and group licensing. |
|
Technology Partners provide support, configuration, training and custom programming services
on the Veraterm product platform. |
Configuration Layer
|
|
|
Most tools and processes in the system are configurable and extensible. |
|
The "System Manager" is a standalone application with configuration windows for all aspects of the Veraterm System |
|
Users have direct access to tools such as: Term Lists, Connection Parameters, Action Item Menus and Display Properties |
|
Users can install additional third-party Add-Ins, Connectors, Displays, Term Recognizers and Actions |
Extensibility
| The architecture of the Veraterm System is open, flexible and extensible.
Veraterm has an unlimited number of potential uses across many vertical markets.
Partners and developers require access to its core components.
Extensibility is supported in different ways: |
|
|
|
Public Interfaces. The interfaces and the API for all core objects are made public. |
|
XML. Internally, core objects are serialized and cached as XML strings.
In the object model, all core objects have custom properties which can be used to add user-defined XML nodes.
By this mechanism the Veraterm System preserves third-party information attached to all core objects. |
|
By Design. The System Manager allows for the addition of user-defined objects in just about every category.
|
|
| |
 Technology Perspectives
|
|
