Altair EEvision™

Integration into Customer Environment

Altair EEvision is integrated into the Customer's Environment on two levels, (a) creating an EDB file from Customer's connectivity data and (b) linking into Customer's Web GUI. For (b) EEvision is intended to run on the same Web Server, and must be installed as CGI extension. In this scenario, the EEvision GUI should be linked with the customer's web GUI using the GUI API, and started with an URL as described in the GUI Startup document.

Creating an EDB from Customer's Connectivity Data

[EDB Integration]

The EDB is created with the EDB Creator API, available for the languages C, Tcl and Java. For understanding the Customer data and the EDB structure, the default EEvision GUI is useful. It uses the same Terminology as the Creator API. For this purpose, standalone executable may also be useful.

There is also a Semantic Validator for the EDB. It it a simple EEvision plugin that checks an EDB file for inconsistencies that can lead to erroneous or at least unexpected behavior of EEvision.

Other useful tools are the "debug.cgi" program to display the current OS environment settings, and the "cleanup.cgi" program to cleanup the temp directory (this might be called periodically to avoid polluting the temp directory).

Linking EEvision GUI into Customer's Web GUI

[GUI Integration]

The EEvision GUI may run in "slave mode", that means inside an HTML iframe object, and fully controlled by Customer's GUI using the GUI API and the GUI Startup document. In this "slave mode" the EEvision GUI is normally reduced to a simple Canvas with control buttons by the Customer application. There is an example for is iframe GUI integration.