<div class="callout callout-important">

In a IPv4/IPv6 mixed system, if you want to force systemd to use IPv4, set ListenStream=0.0.0.0:4343.

        2.  **dss\@.service** should contain the following:

            ```plaintext
            [Unit]
            Description=DSS service

            [Service]
            Environment="DSS_HOME=/home/datasourcesolutions/dss_home"
            Environment="DSS_CONFIG=/home/datasourcesolutions/dss_config"
            Environment="DSS_TMP=/home/datasourcesolutions/dss_tmp"
            User=datasourcesolutions
            ExecStart=/home/datasourcesolutions/dss_home/bin/dssagent
            StandardInput=socket
            KillMode=process
            TimeoutStartSec=infinity

            [Install]
            WantedBy=multi-user.target
            ```

            <div class="callout callout-important">

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

    2.  To enable and start the service, execute the following commands:

        ```plaintext
        systemctl enable dss.socket
        ```

        ```plaintext
        systemctl start dss.socket
        ```

        1.  To verify whether the service is active, execute the following command:

            ```plaintext
            systemctl status dss.socket
            ```

            Sample output:

            ```plaintext
            dss.socket - DSS service socket
             Loaded: loaded (/etc/systemd/system/dss.socket; enabled; vendor preset: enabled)
             Active: active (listening) since Mon 2020-09-07 17:54:44 CEST; 5s ago
             Listen: [::]:4343 (Stream)
             Accepted: 0; Connected: 0
            ```

    </details>

-   Linux **xinetd**  
    Used on other Linux distributions. Requires **root** privilege.

    <details><summary>Xinetd configuration steps</summary>

    The following steps should be performed as user **root** to configure **xinetd**:

    1.  Create an **xinetd** service file **dss** in **/etc/xinetd.d/** directory. This service file should contain the following:

        ```plaintext
        service dss

        {
          socket_type = stream
          wait = no
          user = datasourcesolutions
          server = /home/datasourcesolutions/dss_home/bin/dssagent
          env += DSS_HOME=/home/datasourcesolutions/dss_home
          env += DSS_CONFIG=/home/datasourcesolutions/dss_config
          env += DSS_TMP=/home/datasourcesolutions/dss_tmp
          disable = no
          cps = 10000 30
          per_source = 100
          instances = 500
        }
        ```

        <div class="callout callout-important">

user must be set to the user under which DSS Agent is installed/running.

    2.  Added the following to **/etc/services** - the name of the **xinetd** service for DSS Agent (created in the previous step) and the TCP/IP port number for DSS Agent Listener.

        ```plaintext
        dss 4343/tcp    #Port for DSS Agent
        ```

    3.  Reload or restart the **xinetd** service to apply the changes. For information about restarting the **xinetd** service, refer to the operating system documentation.

    </details>

-   DSS Agent Listener  
    Our own daemon [**dssagentlistener**](/docs/dss6-command-line-interface-command-reference-dssagentlistener). Does not require **root** privilege.

    <details><summary>Start DSS Agent Listener as daemon process</summary>

    The command [**dssagentlistener**](/docs/dss6-command-line-interface-command-reference-dssagentlistener) should be executed with option `<b>-d</b>` to start the DSS Agent Listener service as a daemon process on the required port:

    ```plaintext
    dssagentlistener -d 4343
    ```

    </details>

To test the connection to the DSS Agent, execute the command [**dssagenttest**](/docs/dss6-command-line-interface-command-reference-dssagenttest) on the machine from which you are connecting to the agent. You can also check whether [**dssagentlistener**](/docs/dss6-command-line-interface-command-reference-dssagentlistener) is running by executing the command [**dssagenttest**](/docs/dss6-command-line-interface-command-reference-dssagenttest) directly on the DSS Agent machine.

<details><summary>Examples for testing the connection to a DSS Agent</summary>

##### Example 1: Check connection to a DSS Agent

You can check the connection to the DSS Agent installed/running on a remote machine with username and password authentication enabled. Execute the following command on the hub machine or on the machine from which you are connecting to the DSS Agent:

```plaintext
dssagenttest -L myuser/mypassword mynode 4343
```

Sample output in Linux with successful authentication and also indicating that the DSS Agent Listener is running:

```plaintext
dssagenttest: Data Source Solutions 6.1.0/21 (linux_glibc2.17-x64-64bit)
dssagenttest: Agent version 6.1.0/21.
dssagenttest: Authentication with username and password enabled.
dssagenttest: Authentication successful.
dssagenttest: Finished. (elapsed=0.34s)
```

##### Example 2: Check whether dssagentlistener is running

After installing and starting the DSS Agent Listener service, you can verify whether the [**dssagentlistener**](/docs/dss6-command-line-interface-command-reference-dssagentlistener) is running on the agent machine. Execute the following command on the agent machine:

```plaintext
dssagenttest mynode 4343
```

Sample output in Linux with successful authentication indicating that the DSS Agent Listener is running:

```plaintext
dssagenttest: Data Source Solutions 6.1.0/21 
dssagenttest: Agent version 6.1.0/21.
dssagenttest: Authentication with username and password enabled.
dssagenttest: Authentication successful.
dssagenttest: Finished. (elapsed=0.18s)
```

</details>

6. Configure the DSS Agent, which requires setting its network security and authentication properties. This can be done from a web browser (UI) while creating a location (provided the agent is in 'setup mode') or from the command-line (CLI).

   • For configuring the DSS Agent from browser, see Configuring DSS Agent from Browser.
   • For configuring the DSS Agent from CLI, see Configuring DSS Agent from CLI.

By default, after starting the DSS Agent for the first time, it will be available in 'setup mode' for the next 60 minutes. In 'setup mode', you can configure the DSS Agent remotely from the hub machine using browser or CLI. When the 'setup mode' expires after 60 minutes, the agent can not be configured remotely. If you want to re-initiate the DSS Agent 'setup mode' later, use the command dssagentconfig directly on the agent machine. For example, to enable 'setup mode' for the next 1 hour, execute:

```plaintext
dssagentconfig Setup_Mode_Timed_Until=now+1h
```