Configure Windows Services¶
The installer of the Denodo Platform for Windows creates a Windows service for each of its components: Virtual DataPort, Scheduler, Data Catalog, etc.
By default, these Windows services are configured to:
Run under the predefined “local system user account”.
If you are going to launch any Denodo component as a Windows service, you have to change the following options on these Windows services:
Change the account under which the Denodo services run, to be the same account used to launch the Denodo Control Center.
Set the Startup type to Automatic. That way, if the computer is restarted, Windows will start all Denodo services automatically. This is not mandatory but recommended.
To configure a Windows service this way, follow these steps:
Press the keys Windows logo+R to open the “Run” dialog.
services.mscto open the Window services configuration tool.
Search for a Denodo service, right-click on it (all of them start with word “Denodo”) and click Properties.
In the tab General, in the box Startup type, select Automatic.
Click the Log on tab.
Select This account, enter the user name of the user that will be used to run the Denodo Control Center and enter its password.
Repeat steps 3 to 6 to configure the other Windows services of Denodo.
Privileges Required by This User Account
This user account requires:
Full privileges over the folder and subfolders where the Denodo Platform is installed. The reason is that if first, you launch a Denodo server using the Control Center and later, you launch it as a Windows service, the Denodo server may not be able to modify the files created by the Denodo server when it was launched from the Control Center. E.g. Virtual DataPort will not be able to modify the existing metadata.
Be the only owner of the file
<DENODO_HOME>/resources/apache-tomcat/conf/jmxssl.properties. If you enabled SSL on the web container embedded in Denodo and this account is not the only owner of this file, the web container will not start.
If Denodo is installed on Windows 11, Windows 10, Windows Server 2016 or newer, do not configure the ITPilot Browser Pool component as a Windows service. That is because in these versions, Internet Explorer does not use the configuration of the user starting the Windows service so it will start with an incorrect configuration.
To automate the launch of the Browser Pool, read the article Automating status check and startup of Denodo processes of the Knowledge Base. It contains a script to automate this task.