Skip to Content

Scheduled publications run for a long time

Dec 28, 2016 at 06:09 PM


avatar image

We are having severe scheduler problems. Every morning we have thousands of webi reports scheduled and a few hundred publications. The publications may contain 1 - 10 webi reports and the vast majority don't do anything special like bursting. They are mostly being used to have to schedule 'less' things by bundling the webi reports. One example i have is a publication contains 2 webi reports. Individually the reports run in minutes but as a publication it will take hours. These long running publications are causing our webi reports to be stuck in pending or take a longer time to be submitted.

Interestingly enough when i terminate and pause all publications in the morning, the webi reports flow through the scheduler. I can then resume the paused publications in the afternoon when activity is light and they fly through the scheduler.

Why is running them intertwined causing so many issues? We are on BI 4.1 SP5 if that helps.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Sivakumar Chandrasekaran Jan 02, 2017 at 06:39 AM

Hi There,

Actually, I don't have answer for your question but help you narrow down the issue and get answer or workaround!!

you can create a server group(APS, Webi processing server, etc) and schedule the publisher to run on the server group so that it will not touch any other services on the system. it will help to narrow down the issue. Hope this helps!

10 |10000 characters needed characters left characters exceeded
Dell Stinnett-Christy Jan 03, 2017 at 04:04 PM

When you're running Webi reports, either individually or through a publication, the actual processing for the reports happens in the Webi Processing Server. When you're running them through a publication, I believe that the publication job server "holds" the connection to the Webi Processing Server for all of its reports until the last one has finished processing. Depending on how many publications are simultaneously processing, this could be causing your issue. Depending on the time of the morning when this is occurring, I also suspect there may be some competition for resources with users who get to work and immediately log in to your BO system to either view completed schedules or run whatever reports they need for that morning. This also uses the Webi Processing Server.

Depending on the physical configuration of your server(s) (RAM, # of CPUs, etc) you may be able to create additional Webi Processing Servers to handle some of this load. If you create a "Publication" server group like Sivakumar suggests, it will need to include a special Adaptive Job Server that contains just the Publication Job Server, an Adaptive Processing Server that contains the two Publication servers, at least one Webi Processing Server, and one or more Adaptive Processing Servers that all together contain the following: Adaptive Connectivity Service, Custom Data Access Service, DSL Bridge Service, Data Federation Service, Document Recovery Service, Excel Data Access Service, Rebean Service, Security Token Service (if you're doing SSO to an SAP system), TraceLog Service, Visualization Service, Web Intelligence Monitoring Service. Ideally, these will be a completely separate set of services and not be also used for your regular Webi processing. You would then configure all of the publications to use this server group by default and reschedule them to use this server group.


10 |10000 characters needed characters left characters exceeded