USER MANUALS

Configure Windows Services

The installer of the Solution for Windows creates a Windows service for each of its components: Solution Manager, License Manager, etc.

Note

Go to the next post-installation task if you installed on Linux.

When, during the installation process, you selected the option to create the Windows services, the installer creates them with these settings:

  • The services start manually.

  • Run under the predefined “local system user account”.

If you are doing an initial evaluation of Denodo, use the Denodo Platform Control Center to start each component because it is easier than using the Windows services. In that case, you can skip this post-installation task. However, for a “real-world” installation, usually it is better to launch the Denodo components as Windows services. If you do, follow these steps now:

  1. Change the account under which the Denodo services run, to be the same account used to launch the Denodo Control Center.

  2. 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:

  1. Press the keys Windows logo+R to open the “Run” dialog.

  2. Enter services.msc to open the Window services configuration tool.

  3. Search for a Denodo service, right-click on it (all of them start with word “Denodo”) and click Properties.

  4. In the tab General, in the box Startup type, select Automatic.

  5. Click the Log on tab.

  6. Select This account, enter the user name of the user that will be used to run the Denodo Control Center and enter its password.

  7. Repeat steps 3 to 6 to configure the other Windows services of Denodo.

Privileges Required by This User Account

This user account requires:

  1. 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.

  2. 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.

Add feedback