Stop all schedule for a time, every day

[Former Member]

Hi there ,

I'm glad to post for the first time in this discussion forum.

Here is my dilemma:

My system is under SAP 4.0 fp 2.

Every night, the entire Oracle database is refreshing all his records and tables. This is a long process and it’s preferable that Webi doesn’t generate any report during this time.

I’ve been searching a solution by configuring the APS but there isn’t any option there not to generate any scheduled reports during a defined time.

Here is my question:

Does anyone know how to daily block all scheduled reports for a limited time like two hours a day?

Thank you for your support and best regards,

Alexandre

[denis_konovalov · Accepted solution]

This is not trivial.

You can suspend all recuring schedules in Instance Manager in CMC. But this is manual.

You can create start stop scripts  for SIA or just job/processing servers and run them on schedule that corresponds to your Oracle maintenance using either BI4 program objects schedule or your OS scheduling capabilities.

[Former Member · Accepted solution]

Thanks Denis for your quick answer.

The start and stop script seems the cleanest solution at the moment, with a command in a batch file that kill the server process (servername.exe?) and start it again when the maintenance is over.

If I schedule a Program from BOE that stop and start, I’m not sure that the start program will be executed, because the APS will be down.

[denis_konovalov · Accepted solution]

Well , its all in the details

I wouldn't let the script kill the processes, but use ccm.exe managedstart/managedstop functionality to stop servers ou need stopping.

Second option depends on the APS you have, if you have single one - then yes, not possible, if you have split them as per recomended practices, then you can do it and take advantage of Events functionality so your stop/start scripts start when right around Oracle activity...

[Former Member · Accepted solution]

Thanks again Denis for your precious advice.

You’re right. The ccm.exe managedstart/managedstop looks easier and cleaner as a simple kill process.

I have a unique APS, the second option is no longer possible.

Have a nice evening!

Alexandre

[former_member188911 · Accepted solution]

I agree with Denis however I would be sure that there is a "clean" window in which there are no scheduled jobs.

You need to dedicate a couple of hours for the maintenance and avoid scheduling during that frametime 

The reason why I am suggesting this is because if you brutally stop the servers the jobs that were running may need to be restarted. This could lead to congestion in the scheduling queue, something that I wouldn't like to happen.

If some jobs were still being processed within  the lockout window, that would be an exception that can be easily handled.

Cheers

Simone

[Former Member]

Hi there,

Thanks to your good advices I come back with good news .

I created a .bat with the following  commands :

"C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\ccm.exe" -managedstop CMS_NAME.CentralManagementServer -cms CMS_NAME:6400 -username administrator -password secret -authentication secEnterprise

See page 843 in Admin guide.

I can easily run this .bat from a Linux server (Database Server) with a .sh

@ Simone
It doesn’t really matter if reports have to go in queue or interrupt suddenly.  The most important is to have the very newest information in the reports.

I would like to thank you again for your precious support,

Alexandre

[Former Member]

I don't know if this feature is back in XI 4.x as it seems they got rid of the all the good stuff that was in the last 2 releases that customers were asking for, but if they still have server groups, these have this very feature.  You can set windows of time where they can't process.  However, the only bad thing is, you must assign the reports to server groups and you can't massively do this which would have very beneficial if you could do this.  You could write a VBS script or program object that disables the service during the timeframe and enables after that timeframe. I have to think that's easy enough.