Installation process

1. Start Isah.ShopFloorControl.Service.Setup.msi to install the Isah Web Services for Shop Floor Control.
2. If you already have an installation of the Isah Web Services, it is possible to add another instance (or more), for example for test purposes. In the first window, specify if you want to install a new instance or upgrade an existing instance.

   Note: You can only use letters, numbers, spaces and underscores when you specify an instance name.

3. Follow instructions and press Next when necessary.
4. In the IIS Application Pool window, specify the Windows user that will access and run the web services. There are several built-in user accounts with varying permissions. The standard account is ApplicationPoolIdentity.

   If you want to use a custom account, you will need to verify its credentials before you can continue the installation process.

   Information on Windows users

   • ApplicationPoolIdentity: This is a dedicated user account for the working process of the application pool.
   • LocalService: This account has the same user rights as the Network Service account, but it is limited to the local computer.
   • LocalSystem: This account has all user permissions. It is part of the Administrators group on the web server.
   • NetworkService: This account is a member of the Users group and has permission to run applications.
5. The installation will ask you to enter the database connection details:

   SQL instance

   Enter your SQL server name and instance name.

   Trusted (Windows Authentication) / Specify username and password

   Trusted (Windows Authentication)

   If you want to use the Windows Authentication, click Trusted. The installer will use the account you entered for the Application Pool; this user needs to have the IsahWebServicesRole on the database you will use. Assign it to your application pool user if necessary. Please note:

   • If your trusted user is the ApplicationPoolIdentity and the Web Services are being installed on the database server (which is not recommended), you need to assign permissions to user IIS Appool\Isah AppPool x, in which x is the Isah Web Services number in the name of the installation.
   • If your trusted user is the ApplicationPoolIdentity and the Web Services are being installed on another server, user {DOMAINNAME\COMPUTERNAME$} - for instance {ISAH\C0258$} - needs permissions for the database.

   You will not need to enter a login and password and can proceed with Next.

   Specify username and password

   If you want to specify another user name, click Specify username and password:

   • Login: This must be a user with IsahWebServicesRole in the Isah database. Use SQL Server Management Studio to assign this role to the SQL Server user in the Isah database. Isah recommends a user name with IsahWebServiceRole permissions only. These are the only permissions required to run the Web Services.

     Isah does not recommend the use of SQL user 'sa'.

   • Verify connection: ensure the connection works properly by pressing this button. After the connection has been verified, the Next button becomes active.
6. Test environment: activate this field to create a test environment. If this setting is active when you install the web services, you will see that you are working in a test environment in both SFC and the SFC configuration tool.
7. In the Database window, enter the database name and verify the connection if necessary (you will not need to verify the connection if you have chosen Windows authentication in the previous window). If the user you entered in the previous window does not have sufficient permission, a message to that effect will appear. In that case, to avoid installation problems, it is better to go back and enter a user name with IsahWebServicesRole in the Isah database.
8. The Document Service retrieves the documents that can be viewed in SFC. It needs a user account to verify the access rights to the documents and their location. Make sure the directories that the documents are stored in are shared with the user you enter here.
9. Enter the web site name and the port number.
10. Enter the Isah license server host and port.
11. Enter the path for the installation.
12. Press Install.

Notes

If you receive a ‘Failed to map the path’ or '404 (Not Found)' error when connecting to the service for the first time, you may need to reset IIS and your ASP.NET registration. For this, open an elevated command prompt. Then:

1. in the command prompt, go to the folder that holds your most recent .NET Framework installation
2. run the command aspnet_regiis -iru. When this has finished succesfully:
3. run the command iisreset to restart IIS.

If you receive a '500.19' notification, you need to uninstall the web services and install them a second time.

If you want to change the connection after installation, you will need IIS Management Console:

1. Start the IIS Management Console.
2. Select the Isah website.
3. Open the configuration editor.
4. Select the value ConnectionStrings to modify the web services data connection.
5. In the following line, replace the data between brackets with the login credentials for the Microsoft SQL Server and the Isah database you are using:

   data source=<server name>;initial catalog=<database name>;user=<user name>;pwd=<password>;

   If you installed the Web Services using Windows authentication, the strings should be as follows:

   data source=<server name>;initial catalog=<database name>;Integrated Security=SSPI;

6. Select the value AppSettings to modify the database connection for the report service and license server.

If the server holding IIS and the Isah Web Services is not your Microsoft SQL Server, you will need to install the SQL Server Native Client.