Hardware and software
Spider requirements
| Hardware / VM | Value |
|---|---|
| Diskspace | 100MB+ |
| Operating System | Windows Server 2012 or higher |
| Memory | 1GB+ |
| Processor | Intel i3 / 1Vcore+ |
Software
| Software | Value |
|---|---|
| .NET Framework | Versie 4.5.2 / 4.7.2 of hoger |
| IIS Webserver | 8+ |
| Spider DNS adres | DNS name for the Spider url. The url needs to be binded to the IIS server. Example: http(s)://IWM.nidaros.lan |
| Webdeploy | Versie 3.6 Webdeploy 3.6 |
| Url Rewrite | Versie 2.1 Url Rewrite 2.1 |
| SQL database/Instance | Preferred: SeparateSQL database/instance. |
| SQL user | Permissions: db_owner on SQL database , SQL authentication or windows authentication possible |
| Firewall settings | SQL: 1433, HTTP: 80/443. If the spider is licensed via API (instead of provided license file) Whitelisting to https://customer.roboplatform.net is needed. |
Info
The connection of the spider with the SQL is also possible through an Active Directory user. This depends if the SQL server and IIS server are connected to an Active Directory or are running as standalone applications.
Userroles
To install the Spider, this can be done with a Local Administrator account or with a Service Account which requires the following permissions.
| User | Rights |
|---|---|
| Service account, (installation account) | Member of Group: IIS_IUSRS (ComputerManagement > Group: IIS_IUSRS), Db_owner Permissions on the Spider SQL database. Read and write permissions to the installation directory of the spider environment. Must have import application rights from IIS Management. These are needed to be able to deploy the spider to the IIS environment. |
SQL-instance
The Spider uses a SQL database. Nidaros recommends that the database not be run on the same server in production environments. A user with db_owner rights needs to be connected to the spider database. Authentication can be done via Windows Authentication or SQL authentication.
SSL-certificate
If the Spider environment needs to be equipped with an SSL certificate then this needs to be created by your organization. You can request this from your IT department.
SMTP-provider
For Spider to work, at least an SMTP service needs to be present. If the above conditions can be met you can install Spider within your organization.