At some point you might find yourself stuck with the task of creating an additional Scense server. After taking a look at the Scense Setup you have learned that there’s no option to do this automatically without setting up a new database as well. So here’s your guide to creating an additional Scense server manually…
First make sure your new server meets all prerequisites as described in the Scense Installation Guide. Without setting up the prerequisites it will never work. You might want to collect some information you will need about the user account name (and password) to be used for the application pool. This account will probably be: <domain>\Scense_SVC_1, unless you chose to use another account during the original setup. Also make sure you’re logged onto the new Scense server with an administrator account. The next thing we’re going to do is set the files in place for the Scense Engine web service. You should copy the entire content of the ScenseEngine folder of the first (existing) Scense Server to this new one. The path to this folder probably is: C:\Program Files\Scense\ScenseEngine.
The next important thing is to copy the UDL-file from the first Scense server to this one. The file ‘Scense.udl’ can be found in: C:\Program Files\Scense and should be copied in the exact same location on the new server.
Create the application pool
Ok, now let’s get started by opening the IIS Manager, navigate to the Application Pools container and create a new application pool by clicking ‘Add Application Pool’. Name it ‘ScenseAppPool’, set the .NET Framework version to v2.0 and set the pipeline mode to Classic. Do not let the application pool start immediately because it needs some more configuration.
After you created the application pool, select it and click ‘Advanced settings…’ In the advanced settings property page we need to change the application pool identity in the ‘Process Model’ category. Select ‘Custom Account’ and click the ‘Set…’ button.
Fill out the ‘Set Credentials’ dialog with the correct input and click OK a couple of times so all windows are closed. You can check your settings with the screenshot below for reference and subsequently start the application pool.
Create the web service
The next thing we’re going to do is create the actual Scense Engine web service. So navigate to “Default Web Site”, add a new application and configure it to match the screenshot below.
It is recommended to use the standard name ‘ScenseEngineService’ so your new Scense server will comply with any documentation you may have for your first Scense server. Be sure to select the ‘ScenseAppPool’ you just created as the application pool for this new web service. The Physical path should point to the location where you copied the Scense Engine Service’s files.
Time to test
Now it’s time to do a first test to see if the new Scense Engine web service actually works. (Did you remember to start the application pool?) Testing is done easily by opening this URL in a web browser: http://localhost/ScenseEngineService/ScenseEngineService.svc. If the web service is properly configured you will get a result page very similar to the screenshot below, where the magic words will be: You have created a service.
In some cases you might get an error page in your web browser indicating that some more configuration is necessary.Assuming all prerequisites were properly installed and configured there are some additional step we could take to get the web service to work. In a command window (make sure to run it ‘As Administrator’) the following two commands should be started:
- aspnet_regiis -ir
- aspnet_regiis -s W3SVC/1/ROOT/ScenseEngineService
After issuing these commands (aspnet_regiis.exe can be found in C:\Windows\Microsoft.NET\Framework\v2.0.50727\) you should retry the service URL in the web browser to see if the web service is responding.Should the web browser still show an error page, then it’s very likely the prerequisites were not configured completely or correctly.If you chose a different location to put the Scense Engine service files than C:\Program Files\Scense\ScenseEngine; you should probably edit the Web.config file and correct the path to the UDL-file.You should now have a fully functional additional Scense Engine web service and you can start using it in different scenarios like e.g. a Network Load Balancing cluster.