Knowledge Base > Automation Engine and Target Systems > UNIX > Solaris: Seperate Jobs from Agent process

Solaris: Separating Jobs from Agent Processes

When you start the agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host under Solaris by using SMF, all the processes (jobs) that this agent starts will run in the same contract. The effect is that when this agent crashes, ends or is restarted, all its processes will also end. To solve this problems, you can separate the jobs from the agent contract so that they can run without being affected by the agent processes.

The following steps are required for this purpose:

Step 1: Create the two shell scriptA particular Automation Engine object type. files chk-AE-start.ksh and chk-uc4.ksh with the following contents:

chk-AE-start.ksh:

nohup /usr/local/bin/sudo -u mgws /var/tmp/chk-uc4.ksh&

 

chk-uc4.ksh :

while true
do
echo "$(date) $0" >> /var/tmp/chk-uc4.log
sleep 10
done

 

Step 2: In the jobAn Automation Engine object type for a process that runs on a target system. script, call the shell script chk-AE-start.ksh with the utility "ctrun" and at the beginning of the job script, insert the following line:

ctrun -l childA subordinate task (such as a task that runs in a workflow). /var/tmp/chk-AE-start.ksh

 

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH