Installing Clustered EngageIP Windows Services
Summary
This document describes how to install EngageIP services in a clustered environment.
Monitoring Clustered Services
EngageIP does not currently monitor clustered services. If you refer to the Configuration page, these services will not be shown as running as the local machine is being checked and not the cluster. The cluster administrator will be the interface you will need to rely on for accurate information as to the state of the services in this case.
Installing Clustered Services
Copy Billing Service and Event Service folders to an EngageIP directory (in the same location on a drive on each clustered server)
Â
Install the services
For the billing service, open a command window, surf to the billing service directory and paste: C:\WINDOWS\Microsoft.NET\Frameworkv2.0.50727\installutil.exe -i bossbillservice.exe (where -i installs the service, -u would uninstall the service For the Event Service, open a command window, surf to the event service directory and paste:C:\WINDOWS\Microsoft.NET\Frameworkv2.0.50727\installutil.exe -i bosseventservice.exeÂ
Update the web.config files, enter the correct connection strings so that the services can talk to the SQL servers they are on without the registry. (Please contact LogiSense Customer Care for assistance with the encrypted connection strings)
Open Cluster Administrator, click file, click NEW, click ResourceSelect resource type and Group as required
Â
Select the Possible Owners
Â
Assign dependencies (i.e. SQL needs to be running if the service is to operate correctly so SQL would be selected here. Other items as needed such as drive access should be considered)
Â
Click Save once complete, then you will see the service in the resource list in the cluster administrator. You can now start or stop the service as required
Â
Note: Ensure that these services are not running on the webserver. If they are installed on the webserver (as opposed to the clustered SQL servers), make sure to disable the services so they will not start up. The cluster administrator will then control the starting and stopping of services in the clustered environment