Automatically starting and stopping the AppWatcher process

-
Automatically starting and stopping the AppWatcher process
Configure the AppWatcher process to automatically start after restarting the engine system.
About this task

On Windows, the AppWatcher process is implemented by a service called DataStage AppWatcher Service. By default, this service is not configured to automatically start when the system is started. You can configure this service by modifying the settings for the service in the control panel.
On UNIX and Linux, you can update the DataStage Engine startup script to automatically start and stop the AppWatcher process.

Procedure
  1. As the root user, edit the file InformationServerRoot/Server/DSEngine/sample/ds.rc.
  2. Update the DataStage Engine startup script to start the AppWatcher process automatically.
    1. Locate the block of the script that is commented #start PX JobMonApp.
The block looks like this example:
#start px JobMonApp:
if [ "${PXHOME}" != "" ]
then
...
fi
    1. Add these two lines after that block:
    2. echo "Starting DSAppWatcher"
su dsadm "${DSHOME}/../DSODB/bin/DSAppWatcher.sh -start"
In some cases, it might be necessary to delay starting the DSAppWatcher script until other dependent processes are running. For example, if the operations database that is used by the monitoring services is on the same system as the engine, the database must be running before the DSAppWatcher script is started. Similarly, on some systems it might be necessary to add a delay so that system services like networking are available. A delay can be added by using the following command:
echo "Starting DSAppWatcher"
su dsadm -c "sleep 120; ${DSHOME}/../DSODB/bin/DSAppWatcher.sh -start" >
/dev/null 2>&1 &
If your system is configured with an administrator user name other than dsadm, change the user specified accordingly.
  1. Optional: Update the DataStage Engine startup script to automatically stop the AppWatcher process.
    1. Locate the block of the script that is commented #stop PX JobMonApp.
The block looks like this example:
#stop px JobMonApp:
if [ -n "${PXHOME}" ]
then
...
fi
    1. Add these two lines after that block:
    2. echo "Stopping DSAppWatcher"
su dsadm "${DSHOME}/../DSODB/bin/DSAppWatcher.sh -stop"
If your system is configured with an administrator user name other than dsadm, change the user specified accordingly.



Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more