WinGate Engine

The WinGate Engine is installed as a Windows service to manage and coordinate all of the modules which provide functionality to WinGate. In previous versions the WinGate Engine provided most of the features and functionality, but from WinGate onwards its purpose is to provide the architecture and framework to house and manage all of the available modules that are currently loaded.

WinGate provides the WinGate Schema, where modules can register objects and capabilities and make them available to other components via the WinGate engine. This includes the registering of objects which allow access to data that the module can provide, and the registering of extension items to other modules (e.g. events to the Events system, policy items to the Policy system etc). These extension items usually provide enhanced capabilities and features to other WinGate components, while their module is loaded.

The WinGate Engine monitor which runs in the systray, provides a real time indication of the WinGate Engine's current status. You can also use it to stop and start the WinGate Engine, and provide access to the WinGate Management console. When the WinGate Engine is stopped, all WinGate functionality (such as client Internet access, logging into the WinGate Management console etc.) will be disabled.

You can also configure the stop and start settings of the WinGate Engine service from the services section of Computer Management mmc, in the Windows operating system. Since it runs as a service, it will start when the computer is started (unless configured not to). It is listed as the Qbik WinGate Engine service.

The WinGate Engine itself is not configurable, but you can use the WinGate Management console to load, unload, and configure component functionality when required.

Read more about the WinGate Management console