Configuring services for IBM InfoSphere DataStage and QualityStage Operations Console to automatically start after reboot
Configuring
services for IBM InfoSphere DataStage and QualityStage Operations
Console to automatically start after reboot
On
Windows, by default the "DataStage AppWatcher Service" is
configured to automatically start when the system is started. The
configuration can be altered by modifying the service settings in the
control panel.
On
Unix and Linux, configure the system to automatically call the
DSAppWatcher.sh script upon startup. This can be achieved in a
variety of different ways, the simplest of which is to modify the
DataStage Engine startup script.
As
the root user, edit the
file InformationServerRoot/Server/DSEngine/sample/ds.rc
and insert the following lines (you might have to make the file
read/write before it can be changed):
1)
After the block commented "#start PX JobMonApp" add the
call to start the DSAppWatcher script:
#start px JobMonApp:
if [ "${PXHOME}" != "" ]
then
...
fi
echo "Starting DSAppWatcher"
su dsadm -c "${DSHOME}/../DSODB/bin/DSAppWatcher.sh -start"
In some cases it may be necessary to delay the call to start the DSAppWatcher script until other dependent processes have been started. For example, if the database being used by the monitoring services (specified in InformationServerRoot/Server/DSODB/DSODBConnect.cfg) is located on the same system as the engine, the database will need to be up and running before the DSAppWatcher script is started. Similarly on some systems it is necessary to add a delay in order to ensure system services like networking are up and running. A delay can be added by using the following:
echo "Starting DSAppWatcher"
su dsadm -c "sleep 120; ${DSHOME}/../DSODB/bin/DSAppWatcher.sh -start" > /dev/null 2>&1 &
#start px JobMonApp:
if [ "${PXHOME}" != "" ]
then
...
fi
echo "Starting DSAppWatcher"
su dsadm -c "${DSHOME}/../DSODB/bin/DSAppWatcher.sh -start"
In some cases it may be necessary to delay the call to start the DSAppWatcher script until other dependent processes have been started. For example, if the database being used by the monitoring services (specified in InformationServerRoot/Server/DSODB/DSODBConnect.cfg) is located on the same system as the engine, the database will need to be up and running before the DSAppWatcher script is started. Similarly on some systems it is necessary to add a delay in order to ensure system services like networking are up and running. A delay can be added by using the following:
echo "Starting DSAppWatcher"
su dsadm -c "sleep 120; ${DSHOME}/../DSODB/bin/DSAppWatcher.sh -start" > /dev/null 2>&1 &
2)
Optionally, after the block commented "#stop PX JobMonApp"
add the call to stop the DSAppWatcher script:
#stop PX JobMonApp
if [ -n "${PXHOME}" ]
then
...
fi
echo "Stopping DSAppWatcher"
su dsadm -c "${DSHOME}/../DSODB/bin/DSAppWatcher.sh -stop"
#stop PX JobMonApp
if [ -n "${PXHOME}" ]
then
...
fi
echo "Stopping DSAppWatcher"
su dsadm -c "${DSHOME}/../DSODB/bin/DSAppWatcher.sh -stop"
Note
these changes start the DSAppWatcher services as the DataStage
administrator user (dsadm by default). If your system has been
configured with a user other than dsadm, change the user specified
above accordingly.
With
these changes, the DSAppWatcher services are now be included when
starting (or stopping) the DSEngine services, either through a reboot
or a manual restart using uv -admin commands.