User guide

8. Select File > Exit to close the Director client.
What to do next
You see many warning messages at the time of a job startup. These warning
messages can be ignored. These warnings are thrown by DataStage checks. But pay
attention to the warnings that you might see while the job is running. These
warnings are displayed to alert the user.
The job starts a daemon. This daemon is connected to SAM JMS and directs all the
messages to ActiveMQ. The DataStage job reads from the ActiveMQ. To check the
daemon process, follow these steps:
1. Go to /opt/IBM/InformationServer/Server/Projects/UDM/udm/logs directory.
2. Open the sam-jms-daemon.log file to see the messages that are flowing in. By
default, the KeepAlive messages appear every 30 seconds. This time interval
can be configured on the SAM server.
Attention: It is recommended to restart the DataStage job once in every few days.
When the job is restarted without restarting the JMS client daemon, the full dump
is not started.
Viewing the JMS message flow from SAM server in Apache
ActiveMQ
You can view the results of your job execution by opening the Apache AciveMQ
from the Web browser. You can see the JMS message flow from SAM server in
Apache ActiveMQ.
Procedure
1. Open the Apache ActiveMQ console from the web browser:
http://<Server_IP_Address>:8161/admin/
<Server_IP_Address> is the server where Apache ActiveMQ is installed.
2. Click the Queues tab. You can see the Number Of Consumers, Messages
Enqueued and Messages Dequeued. You can also perform maintenance from
here.
Gracefully shutting down the job
The stages are shut down one after the other. Job continues to run until its process
is complete and then shuts down. To stop a job, you must wait until the job is
completed.
Procedure
1. Go to /opt/IBM/InformationServer/Server/Projects/UDM/udm/bin directory.
2. Run the sendDoneMessage.sh file by using the following command:
cd /opt/IBM/InformationServer/Server/Projects/UDM/udm/bin
./sendDoneMessage.sh
Ideally, when you stop the Job, the daemon process must be running. Check the
status of the daemon by using the following command:
./daemon.sh status
If for some reason the status gives the following output:
Chapter 5. Deploying Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 DataStage jobs 33