《SAP标准培训教材bc040 PRINT1.doc》由会员分享，可在线阅读，更多相关《SAP标准培训教材bc040 PRINT1.doc（54页珍藏版）》请在三一办公上搜索。
1、 BC040: ObjectivesIf I were to introduce the R/3 System to my company, as an IT manager I would ask the following questions:What makes SAP R/3 stand out from the applications that we are currently using?andWhat are the decisive factors for a successful implementation of an SAP R/3 System based on th
2、e experience of several thousand installations?Dr. Uwe HommelDirector of TCC Center SAP AG Course BC040 Covers:Topics central to the technical implementation of R/3The functionality for administering, configuring, and monitoring the R/3 SystemParticular aspects of R/3 Client/Server architecture from
3、 the point of view of computing center operation Policies, procedures, roles, and responsibilities Training and educationThis course gives you comprehensive preparation for your technical R/3 implementation project The technical R/3 Implemenation, OverviewThe typical tasks of an IT operation from th
4、e SAP R/3 point of viewBackground information with respect to the SAP architecture conceringService AreasOverview of Software LogisticsBackground information with respect to the SAP architecture conceringSoftware LogisticDesktop Management, Installation Scenarions (I)Desktop Management, Installation
5、 Scenarions (II)Background information with respect to the SAP architecture conceringDesktop ManagementAbout BC040 - Contents Descriptiono As client/server technology has increased in importance, the task of handling and maintaining the end devices and servers has also become more important. o When
6、you plan a desktop management scenario, you should develop strategies and procedures for using the SAP frontend software.o These strategies and procedures can also be applied to other standard software.o To achieve a uniform desktop configuration, your company must have standards that define a minim
7、um configuration for end devices. Compare your companys existing standards with the SAP requirements for desktops. o Users can be assigned to groups for specific tasks or areas. To do this, you define user profiles, which authorize users to use specific functions. For example, users working in bookk
8、eeping use different functions than users working in human resources management, and therefore need different user profiles. o Hardware planning forms the basis for your desktop configuration. With each new installation, a PC is set up to conform to your companys standards. Take into account the sys
9、tem requirements for SAP Frontend Software.o Each frontend is connected to R/3 through the network, so you must consider which network product is appropriate. See the information brochure “SAP-supported Network Products”.o Your installation strategy influences both the initial installation and the u
10、pgrade strategy, and is an important factor in desktop planning. o SAP Frontend Software can be installed from a local CD-ROM drive, from a server, or to a server (server installation). Each installation strategy has particular advantages and disadvantages, and depends on the network infrastructure
11、and the size of the R/3 System.o 1. Local installation of the SAP Frontend Software from a CD-ROM drive. The software is installed manually on each PC. If the software has to be installed on a large number of desktops, this method is very inefficient.o 2. Installation of the SAP Frontend Software fr
12、om a file server.This method is more efficient. The CD-ROM is made available in the CD-ROM drive of the server or copied to the servers hard disk. The SAP Frontend Software for each desktop is installed from the server. You must ensure that there is sufficient space on the desktop. For more details,
13、 see the SAP Frontend Software installation guide.o With this installation strategy, a high load is only placed on the network during the installation. As the SAPGUI is still available locally, no additional load is placed on the network during productive operation. In addition, the desktops do not
14、depend on the availability of the server.o 3. The SAP Frontend Software is installed directly on the server. A server setup is performed on each desktop in order to install icons pointing directly to the SAPGUI installed on the server. o The space required on each desktop is less (a few KB for the i
15、cons), but the server must have sufficient hard disk space to install the SAP Frontend Software. o The network load is increased because every time SAPGUI is called, the SAPGUI is loaded into desktop memory. This affects the server capacity and network topology, so you should consider this in your n
16、etwork planning.o R/3 documentation is delivered on CD-ROM, and can be used online. You should plan how best to make the documentation available to end users.o You can either make the documentation CD available in a CD-ROM drive, connected to the server, or copy all the documentation to the server.
17、For performance reasons, it is better to copy the documentation to the server. Make sure that there is sufficient space on the server. See the installation guide for more details.o Planning printing infrastructure o It makes little sense to provide each user with his or her own printer connected dir
18、ectly to the desktop. One printer can normally be used by all the people in one office or department. In order to increase the efficiency of printers, make then accessible through the network, and place them in a central location.o You must also consider how your companys standards affect the use of
19、 different different printer types in different departments. Departments must decide whether they require several different printers.o The expected print volume is an important factor in planning. The printers used and the print server must be able to cope.o The network infrastructure must be able t
20、o cope with the workload caused by individual applications, for example Communications requirements in R/3Communication between the servers (server LAN)Communication between frontends and R/3Communication with external systems Communications requirements from further applications (CAD, Office.) Load
21、 generated by the network serverFile sharingPrintingAccess to central data (documentation CD.)o Each application may have different requirements (band width, availability, security.)Your planning should address these factors.o Check the appropriate brochure for the SAP requirements.o In addition to
22、the normal data paths, you must also plan the network server infrastructure to be part of the basic supply line.o The availability of network servers is crucial for software distribution access to online documentation and other information services office communicationo You must plan the server sizi
23、ng, and assignments to clients and subnetworks to cope with increased demand on the network servers (increased number of clients and data volume per client). The dependence of clients on the servers is increased. Without access to a network server, the function of the clients is limited. This makes
24、server availability and access times even more important. Servers are not only needed to store uncritical files, supporting the use of mission-critical applications.o Administration, setting up a domain concept for central administration, is also crucial.o In larger networks, servers are used for so
25、ftware distribution. To minimize the need for manual intervention, and to ensure that the status of the end devices can be controlled centrally, special tools for PC administration and software distribution should be used. For example, Microsofts Systems Management Server (SMS) can be used to distri
26、bute the SAP Frontend Software. Other tools with similar functionality are also available.o To gain benefits such as central administration and automated software distribution from these special administration tools, employees must have the appropriate training. An infrastructure must be planned in
27、detail in accordance with the general network plan and the server infrastructure.o You should reserve a separate segment for communication between the application servers and the database server. This segment must have the appropriate band width and special mechanisms to ensure availability, securit
28、y, and to prevent failure.o Connections between the R/3 System and external systems affect the performance, availability and security of the entire R/3 System. There are several ways of implementing these connections. You should always adhere to the SAP requirements. See “Integration of R/3 Servers
29、in TCP/IP Networks”.o If you are planning to establish a connection to subsidiaries using WAN networks, you should first analyze the basic requirements: band width, how critical is the availability of the network connection for each subsidiary, network security, data integrity.Compare these requirem
30、ents with the cost of the different variants.o When you are planning the network connections, consider all the applications, and network and server administration, including software distribution.o Trained personnel, mostly in central locations, is required to administer the network servers. Sometim
31、es, the PC support personnel do not know enough to be able to solve problems with the end devices. o Remote-access tools help to administer more efficiently servers, and also end devices, in subsidiaries or in other company buildings. Trained specialists can administer the servers and other importan
32、t computers centrally.o When you select appropriate tools, consider whether the tools support the platforms you are using, and their compatibility with your companys network and security plans (which protocols are used, can the user concept of the network servers be used, can firewalls be used, are
33、proxies supported.).o The flow chart shows how a problem is processed by the HelpDesk.o If a problem is occurs, it is reported:-on a questionnaire, which the user fills out and sends to the HelpDesk. -by telephone to a Call Center. The problem is entered into the system online. These reporting metho
34、ds co-exist. This means, for example, that a problem can still be reported online if there is a network failure.o The HelpDesk is divided into 3 levels: First Level records the problems. If a problem is not serious, it is solved at this level.Otherwise, it is classified and passed to the appropriate
35、 department that provides Second Level support. Second LevelMost problems can be solved at this level. If the problem is particularlycomplex, it is passed on to Third Level Support. Third Level is manned by specialists in very specific areas. This level is often outsourced.o Personnel for the HelpDe
36、sk must be planned. The number of people manning the First Level depends on the size of your company and the number of problems that are reported. Second Level support is provided by departments in addition to their normal work.o In order to simplify problem processing and solving, plan the use of a
37、ppropriate tools.o After the planning phase is completed, you can begin implementation.o Implementation consists of the following steps: Configure the frontend components in accordance with your plan. Install the SAP Frontend Software in accordance with your chosen strategy. Make the documentation f
38、or the system landscape available. this documentation is essential for optimizing the network and the desktop environment. End users attend training in the new software. The HelpDesk starts work solving problems.o During productive operation, there are further tasks connected with planning and imple
39、mentation. These tasks include: Planning and implementing a software upgrade in accordance with your strategy. Tuning the R/3 upgrade, taking into consideration R/3 Systems with different Releases. Tune the R/3 components in accordance with your plan. Adapting new upgrades to the office components.o
40、 To prevent problems occurring and escalating, your system should be monitored and maintained continuously: LAN monitoring helps to locate and remedy bottlenecks and network errors early. LAN server statistics provides system administration with an overview of the load on the LAN resources. If load
41、limits are exceeded, measures can be taken. Print servers are also monitored continuously.o When you evaluate the monitoring measures, you may decide that you need to change the system configuration or the concept. o Change management comes into action when offices are moved within a company, new de
42、sktops are installed, or new network cables are laid. The system landscape is subject to continuous adaptation to changing environmental parameters.o It is important to adapt company standards to changing requirements. This applies to all components in a companys IT infrastructure.o Running the Help
43、Desk is also a major part of productive system operation.n Regardless of how sensitive your data may or may not be, every administrator should take appropriate steps to secure their system from unwanted or malicious access.n The SAP system provides a high level of security within the application usi
44、ng the R/3 Authorization scheme. This however is only the first step. Every system is as secure as its weakest link. SAP provides some security features and recommendations for each external component of an R/3 system. These external components, the host OS, the network, the presentation server and
45、the database each have their own security solutions and procedures. These tools and procedures should be analyzed and implemented.n The presentation servers provide users with access to the R/3 data. Machines left logged into the system can be used by intruders to gain access to your data. SAP recom
46、mends using screen blankers with password control. These passwords should follow similar procedures for expiration, length and other restrictions as designed for your R/3 system.n Security features of the pcs OS should be analyzed to include securing locally stored data and remote access control.n A
47、s with all aspects of your system, passwords are only useful when controlled. Enforce regular password changes. R/3 uses very few OS and DB users. Where possible, no other users should be created and or used in a productive R/3 system host. This will simplify your password control procedures.n The file system and file attributes configured by the R/3 installation pr
