User guide

UDMD_STATUS=STOPPED

UDMD_REASON=’daemon no longer running’

DS_DIR=${DS_DIR-/opt/IBM/InformationServer/Server/DSEngine}

SAM_JMSURL1=${SAM_JMSURL1-10.0.0.56}

SAM_JMSURL2=${SAM_JMSURL2-10.0.0.79}

DS_WORKSPACE=${DS_WORKSPACE-//opt/IBM/InformationServer/Server/Projects/UDM}

SAM_UNIQUE_ID=${SAM_UNIQUE_ID-devds_J01main5620sam}

SAM_USERNAME=${SAM_USERNAME-sam-o}

SAM_PASSWORD=${SAM_PASSWORD-5620Sam!}

Look at the sam-jms-daemon.log file from the /opt/IBM/InformationServer/

Server/Projects/UDM/udm/logs directory. You can troubleshoot and start the

daemon manually. For more information about starting the daemon, see

“Starting the daemon manually”

Starting the daemon manually

At the time of job start, it checks whether the daemon process is running or not. If

the daemon is not running, the job starts the daemon. You can run the daemon

manually.

About this task

To run the daemon manually, follow these steps:

Procedure

1. Go to /opt/IBM/InformationServer/Server/Projects/UDM/udm/bin directory.

2. Start the daemon process by using the following command:

./daemon.sh start

STATUS:SUCCESS

3. To check the status of the daemon, use the following command:

./daemon.sh status

The following output is displayed:

UDMD_STATUS=RUNNING

UDMD_REASON=’daemon is running’

UDMD_PID=6505