The standard execution environment of ELOxc.exe is that of a Windows service. This means that ELOxc should be registered as a service so that the program runs on system start just like other services. For this reason, the default execution mode of an instance is set to interval control. In addition to this standard execution mode, it is also possible to call individual ELOxc functions directly using a command prompt or via a browser using the integrated REST interface.

As a Windows service, ELOxc can be executed in the Local System context. The necessary authentication for the system environment and for ELO is provided in the configuration. It is recommended to run cmd.exe with administrative permissions when using a command prompt. When using the REST API, besides having to specify an ELO ticket, which the interface requires for most functions, HTTPS protocol can also be used to secure the product functions.

The results of each function call are written to the corresponding "_Replies" child folders of the log directory. See the Troubleshooting chapter for details on the structure of the log directory.

Enter the following URL in your browser to display the full range of functions:

http://host.domain.net:port/usage

You will see a short descriptions of the functions:

Enter the following URL to view the functions of the REST API:

http://host.domain.net:port/swagger

Click the WebRequest link to see a list of the available functions.

If you click on one of the buttons, the program code for the respective function appears in a separate window. You can click the Try it out! button to test the function.

It makes sense to use the ELOxc REST interface if communication between ELOxc and the ELOxc Console is not working properly, if there isn't a console available or if you haven't installed one yet. We recommend that you proceed with the configuration in the ELOxc Console. However, you should register ELOxc and carry out subsequent product updates with ELOxc Tools.