<div class="callout callout-note">

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

Solaris Service Management Facility (SMF)

In Solaris 10 and higher, the /etc/inetd.conf file has been replaced by SMF manifests. All inetd services are now configured/controlled under the SMF. The following steps should be performed as user root to configure the SMF service:

1. In the /etc/services file, add the following line specifying the name (e.g. mydss) and the TCP/IP port number of the DSS Agent:

   mydss 4343/tcp    #Port for DSS Agent
   

2. Create a temporary file (e.g. /tmp/inet.dss) containing the following inetd.conf-style entry for the DSS Agent:

   mydss stream tcp nowait datasourcesolutions /home/datasourcesolutions/dss_home/bin/dssagent dssagent -EDSS_HOME=/home/datasourcesolutions/dss_home -EDSS_CONFIG=/home/datasourcesolutions/dss_config -EDSS_TMP=/home/datasourcesolutions/dss_tmp
   

• The user must be set to the user (e.g. datasourcesolutions) under which the DSS Agent is installed/running.
  • The service name (e.g. mydss) specified in this temporary file must match with the name specified (step #1) in the /etc/services file.
  • The above configuration should be defined in a single line (without manual line break).

<div class="callout callout-note">

Option <b>-E</b> defines the environment variables.

3. Import the temporary file (e.g. /tmp/inet.dss) into System Management Facility (SMF) using the command inetconv.
   For example:

   inetconv -i /tmp/inet.dss
   

4. Enable the service using the command inetadm.
   For example:

   inetadm -e svc:/network/dss/tcp:default
   

5. Refresh the service using the command svcadm:

   svcadm refresh inetd
   

DSS Agent Listener

The command dssagentlistener should be executed with option <b>-d</b> to start the DSS Agent Listener service as a daemon process on the required port:

dssagentlistener -d 4343

Testing Connection to a DSS Agent

To test the connection to an DSS Agent, execute the command dssagenttest on the machine from which you are connecting to the DSS Agent. You can also check whether dssagentlistener is running by executing the command dssagenttest directly on the DSS Agent machine.

Following are few examples for testing the connection to an DSS Agent.

Example 1: Check connection to a DSS Agent

You can check the connection to an 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:

dssagenttest -L myuser/mypassword mynode 4343

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

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 is running on the agent machine. Execute the following command on the agent machine:

dssagenttest mynode 4343

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

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

See Also

• Configuring DSS Agent from Browser
• Configuring DSS Agent from CLI