4. If the private-key is encrypted, optionally, you can set password for the private-key.
        ```shell
        dsshubserverconfig HTTPS_Private_Key_Password=@prompt
        ```

        Supply a password when prompted.

-   If HTTPS private-key and public-certificate files are not available, configure HTTP instead:

    -   Set the HTTP port by using the command [**dsshubserverconfig**](/docs/dss6-command-line-interface-command-reference-dsshubserverconfig).
        ```shell
        dsshubserverconfig HTTP_Port=4340
        ```

        <div class="callout callout-note">

• Port 4340 is recommended for DSS's use of HTTP protocol. - Browser may give warnings that HTTP is insecure. These warnings must be ignored (until HTTPS is configured).

6. Set up the DSS Hub System, which requires connecting it to its repository database and initializing that database's repository tables. This can be done from a web browser (UI) or from the command-line (CLI).

   • Setting up system from browser.

     1. Start the DSS Hub Server by using the command dsshubserver:

        dsshubserver
        

        It should show output similar to this:

        2020-09-10T12:24:21+02:00: dsshubserver: Data Source Solutions 6.1.0/0 (linux_glibc2.17-x64-64bit)
        2020-09-10T12:24:21+02:00: dsshubserver: Listening on http://mynode:4340/
        2020-09-10T12:24:21+02:00: dsshubserver: No Repository_Class property configured. 
        2020-09-10T12:24:21+02:00: dsshubserver: Setup mode enabled. To set up, browse to the URL mentioned above.
        

     2. In the web browser, connect to the URL shown (e.g. http://mynode:4340/) in the command dsshubserver output above. The DSS Hub System will be running in a 'setup mode'. Once the system setup steps are completed, the DSS Hub System will automatically exit the 'setup mode'. For more information about setting up the DSS Hub System from browser, see Setting up DSS Hub from Browser.

   • Setting up system from command-line (advanced usage). For more information about setting up the DSS Hub System from CLI, see Setting up DSS Hub from CLI.

7. Configure alerts. DSS can send alert notifications if a problem affects replication. Alerts can also be configured to be sent if the replication latency (the delay between capturing a change and delivering that change to the target) exceeds an SLA (Service Level Agreement).

   Alerts are sent by a separate process called dssalertmanager, which should be scheduled to run at a fixed frequency (e.g. every 10 minutes)

   1. To check alerts every 10 minutes, add the following line to the crontab for user root (these should be single line without wrapping):

      0,10,20,30,40,50 * * * * su dss -c /home/datasourcesolutions/dss_home/bin/dss -EDSS_HOME=/home/datasourcesolutions/dss_home -EDSS_CONFIG=/home/datasourcesolutions/dss_config dssalertmanager
      

      Alternatively, the crontab can be run directly as the DSS user. Typically, the DSS user does not have this permission, unless it is named in file /etc/cron.allow, or file /etc/cron.deny exists. In that case the following line should be added to crontab for DSS user (e.g. datasourcesolutions):

      0,10,20,30,40,50 * * * * /home/datasourcesolutions/dss_home/bin/dss -EDSS_HOME=/home/datasourcesolutions/dss_home -EDSS_CONFIG=/home/datasourcesolutions/dss_config dssalertmanager
      

Output/error redirection to cronout.log is optional.

2.  To verify that [**dssalertmanager**](/docs/dss6-command-line-interface-command-reference-dssalertmanager) is running correctly, check 10 minutes later that lines are being written to file **alertmanager.out** available in **DSS_CONFIG/logs** directory.

Configuring Restarting of Hub Server after System Reboot

After setting up the DSS Hub System, it is normally necessary to ensure that the DSS Hub Server service is restarted after the hub machine gets rebooted. Note that a reboot is not necessary now; rather setting this up should be done because eventually a reboot is inevitable.

The necessary steps depend on the service management system used by the operating system:

• Some Linux distributions use systemd
• Other Linux systems use the older 'Unix init daemon' system

Linux systemd

The following steps should be performed as user root:

1. Create a systemd unit file dsshubserver.service in /etc/systemd/system directory. This unit file should contain the following:

   [Unit]
   Description=DSS Hub Server
   
   [Service]
   # The process start-up type 'forking' allows this service to spawn new processes
   Type=forking
   Environment="DSS_HOME=/home/datasourcesolutions/dss_home"
   Environment="DSS_CONFIG=/home/datasourcesolutions/dss_config"
   Environment="DSS_TMP=/home/datasourcesolutions/dss_tmp"
   
   # This should be user that owns DSS_HOME, DSS_CONFIG etc..
   User=datasourcesolutions
   ExecStart=/home/datasourcesolutions/dss_home/bin/dsshubserver
   
   # Restart this service after a crash
   Restart=always
   
   # The number of seconds to wait before attempting a restart 
   RestartSec=5s
   
   [Install]
   WantedBy=multi-user.target
   

User must be set to the user under which DSS Hub System is installed/running.

2. Enable and start the service:

   systemctl enable dsshubserver
   

   systemctl start dsshubserver
   

3. Verify whether the service is active:

   systemctl status dsshubserver
   

   It should show output similar to this:

   dsshubserver.service - Data Source Solutions HubServer
   Loaded: loaded (/etc/systemd/system/dsshubserver.service; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-09-12 10:03:18 EST; 14min ago
   Process: 7587 ExecStart=/home/datasourcesolutions/dss_home/bin/dsshubserver
   Main PID: 7588 (dsshubserver)