> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superoffice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manual steps to install Service

> Manual steps to install Service

From SuperOffice 8.1 both SuperOffice Web and Service must run on the same root domain. It will be easier to create Application Routing Routing rules (ARR) if you do the manual installation and place Service in a sub-application.

Installing SuperOffice Web client and Service on the same domain under different applications requires some manual steps for Service.

<Danger>
  From SuperOffice 10.2.5, SuperOffice Web and Service must run on HTTPS. The in-app editor does not support HTTP.
</Danger>

## Install Service

If the IIS website is not created, first run the installer for Service (SuperOffice.CustomerService.exe) which is the only installer from SuperOffice that will also create the IIS websites.

If the website is created, then you may create the application first, and just point the path to the default location for Customer Service: *C:\SuperOffice*.

![x -screenshot][img1]

Run **SuperOffice.CustomerService.exe** to install the software on the server, the default location is *C:\SuperOffice*.

<Note>
  SuperOffice Service v11 has a new dependency: Microsoft WebView2. It is not included in the Service installer. You must [download][1] it from the Microsoft website and install it before installing or upgrading SuperOffice Service.
</Note>

[1]: https://developer.microsoft.com/en-us/microsoft-edge/webview2/?form=MA13LH

![x -screenshot][img2]

If you upgrade an existing site, do not tick the Create IIS website since it will cause the installer to fail. We will create/update the application manually.

![x -screenshot][img3]

Either set up a new application under `socrm.myorganization.com` for Service or edit the one you created earlier. Point the physical path to the *Customer service\www\doc* folder, in this example, it would be *C:\SuperOffice\Customer Service\www\doc* folder.

![x -screenshot][img4]

Below service, you also need to add 2 applications, one for scripts, which points to the *Customer Service\www\scripts* folder. Make sure it uses the same application pool as the Service application.

![x -screenshot][img5]

And one application for csplugins pointing to *\customer service\www\csplugins*.

![x -screenshot][img6]

## Make sure NetServer is available first

You need remote web services / NetServer installed on the same domain, in this example, we have used `socrm.myorganization.com/netserver`. This is installed by using the [web installer][1] to the Sales web client, and in the product configurator, tick the **Expose NetServer web services** on the Security chapter.

Browse to `http://socrm.myorganization.com/Sales/Remote/Services84/Contact.svc` to verify before the ejTermSetup.exe is run to prime the database for Service.

![x -screenshot][img8]

## Continue with priming the database for Service

ejTermSetup.exe is only run for NEW installations.

Now run ejTermSetup found in the Bin folder, when asked for Hostname give the path including the application, `socrm.myorganization.com/service` which will correctly set the value for database table registry where `reg_id = 109` to /service/.

![x -screenshot][img9]

When ejtermsetup later asks for **The full HTTP Path to your server (for URLs)**, then just use the hostname without sub-application, like `http://socrm.myorganization.com`. It will in most cases default to the correct URL.

When asked for the **NetServer URL** you give the URL for NetServer created on the same domain.

<Note>
  Service does not support HTTPS connection to NetServer, so only HTTP is allowed.
</Note>

From SuperOffice 8.1, all authentication for all clients will be done by the web client, and after successfully authenticating a session key is stored in a browser cookie. This is why Sales and Service must be installed on the same domain.

![x -screenshot][img10]

After completing the ejTermSetup you may start `https://socrm.myorganization.com/service/scripts/rms.fcgi` (or.exe) - note that if your screen is completely missing pictures, then it's the `reg_id=109` that has a wrong value.

![x -screenshot][img11]

## Verify the database registry and config table values

If Service is installed in a sub-folder of the domain named *service*, then

`select * from crm7.registry where reg_id = 109`

should have value */service/*

![x -screenshot][img12]

`select cgi_bin, cgi_url, cgi_url_internal from crm7.config`

![x -screenshot][img13]

[1]: ../netserver/index

[img1]: /media/loc/en/onsite/add-application-1.png

[img2]: /media/loc/en/onsite/run-installer.png

[img3]: /media/loc/en/onsite/uncheck-create-iis-web-site.png

[img4]: /media/loc/en/onsite/change-app-paths.png

[img5]: /media/loc/en/onsite/add-app-scripts.png

[img6]: /media/loc/en/onsite/add-app-csplugins.png

[img8]: /media/loc/en/onsite/verifyremotewebservices.png

[img9]: /media/loc/en/onsite/hostpath-and-odbc.png

[img10]: /media/loc/en/onsite/netserver-url-and-admin.png

[img11]: /media/loc/en/onsite/loginservice.png

[img12]: /media/loc/en/onsite/regid109wrong.png

[img13]: /media/loc/en/onsite/cgibinurlsconfig.png


## Related topics

- [Manual install of Travel gateway service](/en/onsite/travel/travel-gateway/install.md)
- [Set up the Database Mirroring client](/en/online/mirroring/setup-guide.md)
- [Install Service](/en/onsite/install/service/index.md)
- [Prepare for Service](/en/onsite/install/service/prepare.md)
- [Install WebTools](/integrations/webtools/install.md)
- [Install Mail Link](/integrations/mail-link/install.md)