For Exampla : Report A : –> Need exported file copy in 2 different Locations :
1. C:/Reports
2. D:/Reports

Thanks in Advance.
karnan

I think this topic deserves its own article. I have consulted with my SAP-BO engineers and the following is the product of those discussions. It is surprising how little info there is on this topic:

Shutdown your servers in this order (use the clean/disabled method if possible for each):
1) Stop your web servers first. This will cut your users off and stop them from getting strange errors.
2) Stop Event Servers
3) Stop Job Servers
4) Stop Report Servers
5) Stop all other non-CMS servers
6) Stop CMS servers

If you do things in this order you will find that the CMS will stop more quickly and cleanly.

Start up should pretty much be the reverse. As I said before, I will dedicate an article to this and put more details there.

Thanks for asking for this! Julian

Can any one of you please let me know the correct way of stopping and starting the BO Servers?

Thanks,
Raju

Thanks for your clarifying the points. Now we both are in same page:)

You are absolutely right, if we have an additional Webi Report Server to handle the new loads we can do it as suggested by you.

In our project what we do is our all data loads starts in the evening. So before the main loads starts, all the BOXI services will go down. As soon as it completes, it will start. This happens early morning. This activity is done with the help of a script. We are using “Net Stop” as well “Net Start” commands. This schedule is known to all users, so no issues

Regards

Aravind

But My question is as soon as you disable say many users try to access or process reports. What will happen to those requests?

Your question makes me think that I may not have stated that this technique was best used in a “rolling” restart of WebI Report Servers. Those request coming in from users that have either lost their session or closed their previous reports will go to other WebI Report Servers. So you need to be sure that you reserve enough capacity of handle these, of course. However, if the user continues to edit the same report then most likely all requests will go to the same WebI Report Server. Refreshing is different, in that as fas as I know each request to refresh is assigned a new WebI Report Server at the click of the “refresh” button.

Querying during data loading

This is an excellent point that I have never touched on. It is a very difficult matter when you have a global user base (usually the best down time is late afternoon in Pacific time, in such cases). It would be nice if you could easily suspend activity based on a time schedule. This would be a great enhancement from SAP Business Objects.