For information about basic administration and monitoring tasks, see the documentation for Application Server for ABAP and the Application Server for Java:
Administration of the Application Server Java
When performing the following tasks however, you are advised to read the SAP NetWeaver BW-specific information.
To start and stop the system, we recommend using soft shutdown. More information: Soft Shutdown in SAP Application Server.
Process chain jobs continue to run during the wait time set for the soft shutdown. You can configure the wait time so that you can end process chain jobs before a shutdown. The background scheduler does not start new process chain jobs during the soft shutdown. It only does this when the system is restarted. If you cannot use soft shutdown, we recommend using Report BTCTRNS1 (shutdown) or BTCTRNS2 (restart). BTCTRNS1 ensures that no new jobs are started during the shutdown. BTCTRNS2 schedules the jobs again after the restart and starts jobs that the start conditions were met for during shutdown.
If you use soft shutdown, background jobs for real time data acquisition daemons (RDS) are terminated early but without stopping the daemons or closing the open requests. Successor jobs for daemons are scheduled using immediate start (as in the normal background job change for daemons). The background job scheduler does not start the jobs during the soft shutdown however. It only does this when the system is restarted. The open requests are then processed as usual. If you want the shutdown to stop the daemons and close requests, use BW-specific report RS_SYSTEM_SHUTDOWN instead of the soft shutdown. We recommend using the report especially for making a system copy (see below).
For more information about making a system copy of a BW system, see SAP Note 886102. This Note provides additional information (specific to SAP NetWeaver BW) to the Best Practices document SAP System Landscape Copy for SAP NetWeaver and mySAP Solutions. You can find this document on the SAP Service Marketplace at http://service.sap.com/solutionmanagerbp. See also SAP Note 885343. This provides the latest news, updates and corrections to the Best Practices document.
To stop and starting the system to make a system copy, we recommend executing BW-specific report RS_SYSTEM_SHUTDOWN (transaction SE38). You can use the report to stop the process chains and real time data acquisition load processes (RDA load processes) of the system and to restart them again once the system is started. The report resets the planning for the scheduled process chains. The report stops the RDA load processes and closes the open requests. The assignments of DataSources to daemons remain unchanged. The report terminates after the specified maximum wait time, even if there are still processes running. After restarting the system, you can use the report to start the RDA load processes again. If you do this, all daemons are started again, including ones that were not running (anymore) before the shutdown but that are assigned to DataSources. You should therefore make sure that DataSources are only assigned to a daemon if you want to start the daemon.
During data saving and recovery, note the following when you extract data in the delta process from a source system into an SAP NetWeaver BW system:
Installing a backup on a BW system or on a source system connected to it can cause irreparable damage to cross-system data consistency. This mainly affects active delta processes between the BW system and the source system. We therefore recommend only performing synchronous backups in systems that are networked with each other and (to be safe) always running a synchronous recovery. If this is not possible, read SAP Note 731682. This contains information about the risks involved in making backups and recommendations for backups with regard to active delta processes.