Installing the Micetro Web Application on Windows

Note

On Windows, the Micetro Web Application requires Microsoft Internet Information Services (IIS) to be installed. The installer will verify the presence of all required components.

To install the Micetro Web Application, double-click on the Microsoft installer file and follow the instructions on the screen.

Warning

If the Micetro Web Application is installed on a different server than Micetro Central, you’ll need to configure the Web app server host to the hostname of the webserver. This setting can be adjusted in the System Settings on the Admin page. Check System Settings ‣ Advanced to make sure that the auto-update feature for the Web Application works correctly.

Setting up SSL for the Web Application

To set up a secure sockets layer (SSL) for the Web Application, follow these instructions.

Note

Make sure that certificates include a Subject Alternative Name (SAN) so that web browsers mark the site as secure.

Configuring SSL certificate

Open the IIS Manager.
Select the Web Server node in the left sidebar, under Start Page, and double-click Server Certificates in the middle pane.
In the Actions pane, select an action to import an existing .pfx SSL certificate or to create a self-signed certificate. If your certificate is in a format other than .pfx, refer to the documentation or tools provided by your certificate authority to convert certificates to .pfx format.
Select your website under Sites in the left sidebar (usually Default Web Site), and then click Bindings… in the Actions pane on the right.
In the Site Bindings dialog box, click Add, select https from the Type dropdown, and then select the certificate you added in Step 3 from the SSL certificate list. Click OK.
- The Host name and Require Server Name Indication fields can be left empty if this the first certificate installed on the server.

Redirecting HTTP traffic to HTTPS

Navigate to URL Rewrite rules and locate the grayed out HTTP –> HTTPS redirect rule.
Make sure it’s postitioned at the top of the list, select it, and click Enable under Actions on the right side.
Restart the web server. This automatically redirects all HTTP queries to HTTPS.

Using the IIS Manager

With Default Web Site selected in the left sidebar, double-click URL Rewrite in the middle pane.

If there’s already an HTTP to HTTPS redirect rule at the top of the list, no further action is needed.

To add a new rule:

Select Add Rules in the Actions pane on the right, then click OK to create an empty inbound rule.
In the Name field, enter HTTP to HTTPS redirect.
In the Pattern field, enter (.*).
Under Conditions, select Add and enter the required condition:
In the Actions pane at the bottom, select Redirect from the Action type dropdown, set the redirect URL to https://{HTTP_HOST}/{R:1} and the redirect type to Permanent (301).
Select Apply in the Actions pane on the left, and then click Back to rules.
Move the new HTTP to HTTPS redirect rule to the top of the list using the Move Up button in the Actions pane on the right.

Allowing the Web Application to log into other Micetro Central servers

By default, the Micetro UI and API only allow connecting to a single Micetro Central server, determined during the first login to Micetro after installation.

To allow users to specify a custom Micetro Central server to connect to:

Edit the preferences.cfg file for the Micetro Web Services located at c:\\ProgramData\\Men and Mice\\Web Services\\preferences.cfg by adding the following line to define the default Micetro Central server name:
```
<DefaultCentralServer value="your Micetro Central DNS name or IP" />
```
Note

If DefaultCentralServer is not specified, the web service will use the first-specified Micetro Central server, typically localhost.
Add the following XML-tag to lock the web service to use the default Micetro Central server:
```
<LockToDefaultServer value="0" />
```

Restart the Micetro Web Services Windows service.

A Server field will appear on the Micetro login page and the serverName field in the API Login command will be honored.

Increase timeout for webserver proxy

To ensure that the Web Application operates efficiently with larger change request queues that take longer for Central to process, modify the /etc/httpd/conf file and increase the mmws proxy timeout value:

ProxyTimeOut 60