Running ARDI Services Under Domain Accounts

ARDI includes three major types of service.

Backend Services - These services include the driver management service, the live-data consolidators and MySQL. These are designed to reside on the server and should never require special rights.

Apache - This is the web-hosting software that allows the ARDI web interface and API to run. If addons require access to resources that require domain accounts, you will need to change the rights of this service.

Drivers - Drivers access live and historical data from your information stores. If these need domain authentication in order to operate, you will need to start your drivers using domain accounts.

Changing the Apache user is done the same way as any service user - through the Services application.

Open the Apache service, choose the user you want to launch the service as, and enter the password. Note that this user must be an administrator on the local machine - the ARDI service needs to be able to create and destroy driver services.

Because ARDI manages your driver services and regularly destroys and re-creates the service entries, the same method isn't effective unless you are doing short-term testing.

To launch Windows services, ARDI uses the NSSM tool. You can add parameters - such as user credentials - for ARDI to give to NSSM when creating services.

To do this, edit the nssm.conf file in your Site Folder.

The nssm.conf file controls all drivers - a change to this file will be applied to every Windows service that is launched.

You can also override individual drivers by adding the driver port number to the end of the file name, before the extension.

For example, in the above example the MySQL driver has a port number of 12097. If you wanted this specific driver to run as a user, you could create a file named nssm12097.conf - the settings in this file will only be applied to the MySQL driver.

For more details, see the nssm.conf file documentation