Installing MainBoss Service |
< Previous section | Table of Contents | Index | Next section >
In order to install MainBoss Service, you must be logged in to Windows under a login name that has both Windows Administration privileges and SQL Server Administration privileges.
Note: You should only install MainBoss Service after you have used Manually run the MainBoss Service to test your configuration and are satisfied that the configuration works the way you want.
Start MainBoss and go to Administration | MainBoss Service. Click the button Configure the Windows Service for MainBoss. This actually installs the service as a Windows service, using the configuration information specified in Administration | MainBoss Service | Configuration. The service will be installed to run under the Network Service login name on the computer where you are currently running MainBoss.
Note that you can install MainBoss Service on any computer in your network, provided that the computer has access to the instance of SQL Server that manages your MainBoss database.
The installation process accesses SQL Server in order to give MainBoss Service appropriate SQL Server permissions for accessing the MainBoss database. (This is why you must have SQL Server Administrator permissions to install MainBoss Service.) See SQL Server and MainBoss Service for information about how MainBoss Service identifies itself to SQL Server.
MainBoss Service can also be installed from a command line, rather than using MainBoss itself. For more information, see Invoking MainBoss Service from a Command Line.
Access to the MainBoss Database: MainBoss Service must access the MainBoss database in order to do some of its work. This means it must go through the instance of SQL Server that manages the MainBoss database, and it must have appropriate permissions to do so.
MainBoss Service inherits its SQL Server permissions from the person who installs the service.
We recommend using Windows Authentication with Network Service unless there's some good reason to do otherwise. In particular, we've seen cases where MainBoss Service stopped working because it was set up to access the database using the SQL name-and-password associated with a particular IT person. When that person left the organization, the name and password were deleted and suddenly MainBoss Service couldn't access SQL Server anymore.
< Previous section | Table of Contents | Index | Next section >