Install DataLayer Server

In this section you will learn: How to set up the DataLayer web application.

The DataLayer Server files are contained in a folder called <date>_DataLayer_<VersionNumber>.<build>, for example 20190614_DataLayer_2019.3_12345.67_2019.3. This folder is referred to as <DataLayerFolder> in the remainder of this manual.

1. Copy the <DataLayerFolder> folder into a suitable location, for example \Web\SpiralSuite\DataLayer.

2. Extract the zip package in the NetCore folder of your installation files. These instructions assume you extract the package in the same folder.

3. Open Internet Information Services (IIS) Manager and browse to <ServerName>\Application Pools.

4. Create a new DataLayer AppPool, the same way you did for CrudeSync:

   • Choose No Managed Code as .NET CLR version.

   • Choose Integrated as Managed pipeline mode.

5. Close the Add Application Pool dialog box and right-click on the DataLayer application pool you just created. Choose Advanced Settings. The Advanced Settings dialog box opens.

6. Click the Identity entry under Process Model. Click the ellipsis button () that appears at the end of the row. The Application Pool Identity dialog box opens.

7. From the Built-in account list, select NetworkService. Click OK.

8. Right click on the Default Web Site and select Add Application from the context menu.

   1. Enter DataLayer as the Alias.

   2. Select the DataLayer Application Pool.

   3. Set the physical path to the DataLayer installation folder:

      \Web\SpiralSuite\DataLayer\<DataLayerFolder>\NETCore

9. Select the DataLayer website and open Authentication Settings.

10. Set Windows Authentication to Enabled and all other authentication types to Disabled.

11. Right-click on DataLayer under Default Web Site and choose Edit Permissions. The DataLayer Properties dialog box opens. Set the NTFS permissions of the folder as follows:

    4. Select the Security tab, click the Edit button and click Add.

    5. Click Locations, select the host server name then click OK.

    6. Enter IIS Apppool\Datalayer and click Check Names.

    7. Click OK.

    8. Grant the Application Pool Identity (in this case NetworkService) modify permission on the folder.

12. Upgrade the SuiteServer database as follows:

    9. In the \Web\SpiralSuite\DataLayer\<DataLayerFolder>\Release folder, run the following command with elevated privileges:

       .\DataLayerServerUpgrade.exe UI

    10. Configure the options as detailed below, replacing <values> accordingly:

        • Server Instance: <ServerName>\<InstanceName>

        • Database Name: SuiteServer

        

        Note: If your user account is not mapped as dbo on the SuiteServer database, clear the Use Integrated Security check box and enter the appropriate SQL Login credentials.

    11. In the Database Schema section, select Server.

    12. Ensure the Backup existing database and Recreate Database are not selected.

    13. Once all settings have been entered and confirmed, click Upgrade to begin.

    14. Close the SpiralSuite Server Database Manager.

13. Add an administration account by running this command from the \Web\SpiralSuite\DataLayer\<DataLayerFolder>\Release folder:

    .\DataLayerServerUpgrade.exe AssignRole /Role=Admin /Users=domain\username /Server=<ServerName> /Database=SuiteServer

    Change the /Users and /Server parameters to match your situation. The /Users parameter accepts a list of comma-separated users or domain groups.

    Beware of line breaks in the printed version of this document: the above is one command on a single line.

    Once you have at least one user with Admin role, you can assign more roles via the Roles page of the DataLayer administration website. Alternatively, you can run the DataLayerServerUpgrade.exe command multiple times.

    • Adding a user with Admin role grants access to modify user and shares permissions.

    • You can run the command with /Role=Import to grant the necessary rights to the user the CrudeSync Import service will run as. See Set up the CrudeSync import service for more information about CrudeSync Import.

14. Create an appSettings.Production.json file in the same folder as appsettings.json, with the following contents:

    {
    "ServerDbSettings": {
    "ConnectionString": "Data Source=<ServerName>;Initial Catalog=SuiteServer;Connection Timeout=30;Integrated Security=SSPI;"
    },
    "CrudeSyncSettings": {
    "CrudeSyncConnectionString": "Data Source=<ServerName>;Initial Catalog=CrudeSync;Connection Timeout=30;Integrated Security=SSPI;",
    "ManageCrudeSync": "True"
    }
    }
    

    If you have chosen not to enable SQL Server TLS, add Encrypt=False; to the ConnectionString and CrudeSyncConnectionString string.

    Note that <ServerName> should include the instance, if appropriate. Make sure to escape any backslashes: for example, write Data Source=.\\SQL2017 instead of Data Source=.\SQL2017. Also, beware of line breaks in the printed version of this document: the strings between double quotes must not have any line breaks. Note that Initial Catalog is two words separated by a space.

    Note: Additionally you can perform the same action here to restrict the list of authorized users in the same way you did for Crudesync.

15. Open the Authorization Rules feature in IIS.

16. Right click and remove All Users.

17. Right click and Add Allow Rule.

18. Select Specified Users and enter NT AUTHORITY\NETWORK SERVICE.

19. Click OK.

20. Add another Rule.

21. Select Specified roles or user groups.

22. Enter the name of an Active folder group containing the required users accounts.

23. Click OK.

    Tip: To check that the DataLayer server has been installed correctly, type the following in a command prompt or PowerShell window in the NETCore folder:
    dotnet Spiral.DataLayer.Server.dll
    If successful, the command will start a temporary server. Browse to the address shown in the command output: if you see the DataLayer website home page, the installation was successful. If not, check any console output or log files written to the logs folder inside NETCore, and contact AVEVA support (spiral.support@aveva.com) for assistance.