Isah Web Services

Installation

Start Isah.Sevice.Setup.msi to install the Isah Web Services. This will create the Isah Website in IIS and install the following web services:

• Authentication Service
• Document Service
• Hour Registration Service
• Production Service
• Report Service.

During the installation you will be asked to enter the database connection details:

• Server: SQL server name + instance name
• Database: Database name
• User name: 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'.
• Password.

In addition, the installation will ask for a separate username and password for the report service. This user needs to have the IsahUserRole. The database user that has been configured for access to the Isah database in the Isah License Server has this role and can be used here.

Note:

• 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>;

  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 still need to install the SQL Server Native Client.

Configuration

To be able to print reports, you will need to configure Report Service.

1. Assign permissions on DCOM ReportPrintService Object

   For the ReportService to work properly, it is necessary to set the right authorization on the COM object responsible for creating reports. This is done via the MMC snap-in Component Services, which must be run in 32-bit mode:

   1. Execute the command ‘mmc comexp.msc -32’ from an elevated command prompt.
   2. Go to Component Services – Computers – My Computer – DCOM config.
   3. Search for ‘ReportPrintService Object’ and open the properties.
   4. Go to the Security tab.
   5. Set the Launch and Activation Permissions to 'Customize'.
   6. Click the Edit button.
   7. Add the user ‘IIS AppPool\Isah AppPool’.
   8. Assign all permissions to this user.
2. Assign user permissions to folder

   If the Isah Web Services have been installed in the standard IIS folder 'inetpub\wwwroot', all rights have already been configured correctly. If the Isah Web Services have been installed elsewhere, follow these steps:

   • Check if the standard Windows user group IIS_IUSRS is present. If it is not, add it.
   • The user group IIS_IUSRS must be authorized to use the folder that holds the Isah Web Services. Check if this is the case. The user group needs the following permissions:

     - Read & Execute

     - List Folder Contents

     - Read.

3. Configure port and firewall

   When you install the Isah Web Services, they are configured to use HTTP Port 80. If you want to use another port, you can change it in the IIS management application. After changing the port, you will need to restart the Isah Website.

   Make sure the servers' firewall allows the incoming HTTP traffic on the configured port.