State of affairs You’ve gotten an SAP BW system with a number of (utility) servers. You want to distribute the workload of the info hundreds and different knowledge warehouse administration actions in a manner that matches your wants greatest. This might imply that you just want to have all processes distributed throughout all obtainable servers or that you just want to have one devoted server for these processes. 2 Introduction SAP makes use of the phrases occasion and utility server synonymously. With a view to keep away from misunderstandings we use the time period occasion for an SAP occasion (utility server) on this doc.
For a bodily machine we use the time period server. Among the settings described on this doc are performed on an occasion stage, some on a server stage. Should you don’t have a number of situations (of the identical SAP system) on one server you don’t have to attract this distinction between occasion and server when studying this doc. There are a bunch of features and settings within the space of load balancing supplied by the premise system (Internet Utility Server). Nevertheless, these have been designed primarily for SAP’s ERP system.
Customizing these options for optimum use with SAP BW requires additional issues. The challenges offered with knowledge load processing originate from the truth that many pretty lengthy operating processes could be began virtually simultanesouly. The usual SAP load balancing method takes the standard of the situations into consideration when distributing the load. This high quality is evaluated in common intervals (5 minutes by default). Inside one interval quite a lot of parallel processes could also be began on the most effective occasion, utilizing quite a lot of work processes whereas the opposite situations are idle.
An optimum distribution of BW OLAP workload or knowledge load useful resource consumption can not readily be achieved with this commonplace methodology. With out ample planning, and beneath heavy workload (peak) situations, the dangers can enhance that turns into a bottleneck; a restricted variety of servers can grow to be saturated with processes consuming sources, and efficiency (and stability) can doubtlessly endure considerably. A profitable load balancing method optimally makes use of the sources which were allotted to the BW system.
Word that this dialogue assumes that an ample sizing has been carried out to correctly measurement the SAP BW system (see SAP Service Market alias “quicksizer” for extra info). This doc describes load balancing approaches for typical SAP BW actions. Generally these actions course of giant quantities of information. Data (inside one course of) is cut up into packages and may thus be processed in parallel on one or throughout a number of servers or situations. Alternatively, a number of processes can run in parallel on one or on a number of servers or situations.
Because of this we will have parallel processing (and consequently obtain load balancing) each inside one course of and throughout processes. In our examples we’ll use a system known as XXX as SAP BW system and a system known as YYY as an SAP supply system of XXX. Throughout knowledge load processing, knowledge is extracted from the supply system and despatched to the goal SAP BW system. Different load processes contain the SAP BW system as supply system, in addition to the goal system (for instance, DataMarts, activation of information in ODS objects). The situations and servers on XXX are as follows, the server ab1234 being the database server:
