Question:
How can I set up an antivirus to work with E3?
Solution:
While working, Elipse E3 both generates and uses some specific files that must be set up as exceptions in the antivirus. These files all have one of the following extensions:
- *.e3i and *.e3o: for files used as data buffers. They are generated in the folder containing the object Database whenever the connection between E3 and the Database fails.
- *.etl: for log files generated by E. These files are at C:\eeLogs.
- *.dll: for the application’s I/O Driver’s files.
In addition, there are a few processes generated by Elipse E3 that must also be set up as exceptions in the antivirus:
- IOServer: this process corresponds to the I/O Driver’s execution.
- E3Server: this process executes the application’s server, where most processes in E3 run, including the control of communication with devices and the sending of data and screens to clients.
- E3Run: this process is responsible for executing the application’s server objects, such as tags, alarms, databases, historics, etc.
- E3Admin: this process is responsible for interfacing E3Server and other E3 modules with the user.
- Viewer: this process allows operating the applications residing in the server.
- E3Studio: this process is responsible for setting up the application.
Finally, please notice that Elipse E3 uses Windows’ 6515 port as default for connecting the Viewer to the application’s server. Therefore, this port must be unobstructed for this application to work properly. However, it could alternatively be changed via E3Tweak, if you want to.
