BI Platform: Restarting the unresponsive

Adaptive Job Service using a script

Posted by Mohanraj Periyasamy May 23, 2016
We recently came across an issue where our scheduled jobs on BI 4.1 platform wouldn't run as expected; they
would just not start. We have a clustered server setup and the job servers are running on couple of nodes.
When this happens, the job server status on CMC would appear to be fine. We have raised this issue with SAP
support and working on finding a resolution. In the meantime, we used the below Power Shell script as a work
around to restart the job service when the schedules don't run as expected.
Solution
We scheduled a simple web intelligence report that runs every 5 mins; Using PS, we checked for the status
of this report through Auditing database. When there are no entries made in the auditing database for a set
threshold time, we use CCM.exe to restart the JobServer.

#Auditing database credentials $dataSource = "Auditing Database Server" $user = "Auditing database user" $pwd = 'Auditing
238 Views Tags: biplatform41

Mohanraj Periyasamy in response to JinChong Tsai on page 1

May 24, 2016 9:15 AM
We have been asked by SAP to add these additional parameters to Job Server this week. I shall wait for few
weeks before confirming whether it helps in our case or not. Usually our job server goes to the unresponsive
state once a month.
Sivakumar Chandrasekaran
May 24, 2016 9:07 AM
we are using this parameter but no luck. outproc parameter is good, each job is running on the separate child
process.
JinChong Tsai in response to Mohanraj Periyasamy on page 2
May 23, 2016 9:22 PM
Have you test the following to the end of the AdaptiveJobServers' command line,
-RequestTimeoutMinutes 60 -type outproc
so that AJS will timeout after 60 mites of idle time and terminate children when job is completed.
Regards,
Jin-Chong
Mohanraj Periyasamy in response to Sivakumar Chandrasekaran on page 2
May 23, 2016 8:59 AM

Generated by Jive on 2016-05-24+02:00

1

BI Platform: Restarting the unresponsive Adaptive Job Service using a script

4.1 is much stabler and our job servers do not fail often, I hope 4.2 makes it even more better.
Sivakumar Chandrasekaran in response to Mohanraj Periyasamy on page 2
May 23, 2016 8:43 AM
if 5 jobs are running then 5 job server child process will be there so :-)
Our BO environment got 4 job server and each can run 5 jobs at a time so we were struggling with this issue
for some time :-)
Mohanraj Periyasamy in response to Sivakumar Chandrasekaran on page 2
May 23, 2016 8:26 AM
With the job server, it is one of the JobServerChild process that seems to be hanging.
Sivakumar Chandrasekaran
May 23, 2016 8:15 AM
yes Mohanraj, it's bit tricky to find hung service. we can find easily if the service is failed but it's not easy to find
the service working properly or not.
we also used another mechanism to find the service is responding or not. we were using a perl script :-). I was
thinking another option like checking the process is moving or not.. never got change to try this..

Generated by Jive on 2016-05-24+02:00

2