0 оценок0% нашли этот документ полезным (0 голосов)
237 просмотров102 страницы
SAP Basis FastTrak WAS 700 is an Introduction to Enterprise Resource Planning (ERP) it is the planning of how business resources (materials, employees, customers etc.) are acquired and moved from one state to another.
SAP Basis FastTrak WAS 700 is an Introduction to Enterprise Resource Planning (ERP) it is the planning of how business resources (materials, employees, customers etc.) are acquired and moved from one state to another.
SAP Basis FastTrak WAS 700 is an Introduction to Enterprise Resource Planning (ERP) it is the planning of how business resources (materials, employees, customers etc.) are acquired and moved from one state to another.
Module 1: Introduction to Enterprise Resource Planning (ERP) Module 2: SAP Project Lifecycle 3 Module 3: Fundamentals of SAP WAS Module 4: Starting and Stopping SAP Systems
Day 1: Module map SAP Basis FastTrak WAS 700 1 Copyright IBM Corporation 2009
IBM Global Business Services Course Title Introduction to ERP Module 1 IBM Global Business Services Copyright IBM Corporation 2009 Module 1: Objectives After completion of this module, you should be able to: Define an ERP Relate SAP to an ERP Understand the evolution of SAP Identify the components of SAP. Understand SAP Netweaver Concept. Understand the various kinds of Client-Server Architecture from SAP perspective. Know SAPs Release and Maintenance Strategy
SAP Basis FastTrak WAS 700 3 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Module 1: Agenda Topic 1: ERP: Definition Topic 2: Relation between SAP and ERP Topic 3: SAP evolution Topic 4: Components of SAP Topic 5: Features of Sap Netweaver Topic 6: SAP client-server architecture Topic 7: SAP release and maintenance strategy 4 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Large corporations developed their software in-house. These software aimed at automating functional processes. Advantages: Application tailored to Organizations requirement. Disadvantages: Systems could not be changed on demand. Excessive change made the applications difficult to manage. Required large number of skilled in-house personnel to maintain the systems. Very high cost of maintenance.
Enterprise computing in the 70s 5 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700
Make vs. Buy vs. Mix n Merge Make Buy Mix n Merge In-house developed applications
3 rd Party developed applications Packaged Corporate Applications, such as SAP & Oracle Financials 1970s 1980s 1990s 6 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700
Enterprise Resource Planning (ERP) ERP is the planning of how business resources (materials, employees, customers etc.) are acquired and moved from one state to another.
7 IBM Global Business Services Copyright IBM Corporation 2009 Overview of SAP The SAP system is software which is composed of different software and a server as a whole and has the ability to perform standard business functions for corporations. SAP (pronounced ess-aye-pea ) is based in Walldorf, Germany . It stands for Systems, Applications and Products in Data Processing. Its an ERP Package. SAP's foundation is built upon the concepts of specialization and integration. It is world premier provider of client/server business solutions. SAP products can be broken down further into modules portions of functionality.
SAP Basis FastTrak WAS 700 8 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Evolution of SAP AG SAP was founded in the year 1972 as Systemanalyse und Programmentwicklung ("System Analysis and Program Development") The acronym was later changed to stand for Systeme, Anwendungen und Produkte in der Datenverarbeitung ("Systems, Applications and Products in Data Processing"). In 1976 "SAP GmbH" is founded and the following year it moved headquarters to Walldorf . SAP AG became the company's official name in 2005 (AG is short for Aktiengesellschaft). In August 1988, SAP GmbH transferred into SAP AG (a corporation by German law). In 1995, SAP was included in the German stock index DAX and On August 3, 1998, the letters S-A-P appear for the first time on the Big board at the New York Stock Exchange (NYSW). Henning Kagermann became the sole CEO of SAP in 2003 till date. 9 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Technical solutions In 1972 the SAP R/1 solution was launched -the first financial accounting software. Seven years later, in 1979, SAP launched SAP R/2. In 1981, SAP brought a completely re-designed solution to market. With the change from R/2 to R/3 in 1992. 10 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700
ERP packages SAP ERP 6.0 from SAP mySAP from SAP SAP Business One from SAP PeopleSoft from Oracle JD Edwards EnterpriseOne & JD Edwards World from Oracle
11 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 R/2 system SAP R/2 is a real-time enterprise resource planning (ERP) software. R/2 is SAP AG mainframe software that runs on IBM, Siemens, Amdahl, and compatible equipment. R/2 can be linked to R/3 systems and share online data. R/2 system is mainly targeted at enterprises with data intensive and centralized industries. R/2 is the predecessor of the client/server R/3 system. R/2 system offers comprehensive, fully functional business applications to satisfy the demands of mainframe users. 12 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 R/3 system and further on SAP R/3 is a client/server based application and it is designed to run simultaneously across several separate computer systems. The R/3 architecture allows distribution of the workload to multiple PC's connecting in a network. The SAP runtime system is designed in such a way that it distributes the presentation, application logic and the data management to different computers. SAP R/3 is arranged into distinct functional modules. The most widely used modules are Financials and Controlling (FICO), Human Resources (HR), Materials Management (MM), Sales & Distribution (SD), and Production Planning (PP). By 1996, the company had earned 1,089 new SAP R/3 customers. At the end of the year, SAP R/3 has been installed in more than 9,000 systems worldwide. 13 IBM Global Business Services Copyright IBM Corporation 2009 SAPs go-to-market-approach SAP Basis FastTrak WAS 700 Source: SAP 14 IBM Global Business Services Copyright IBM Corporation 2009 SAP product portfolio Industry Solutions IS- Aerospace & Defense IS- Automotive IS- Oil SAP xAPPS SAP xAPP Resource & Management SAP xAPP Product Definition
SAP Smart Business Solutions mySAP All-in-One SAP Business One mySAP Business Suite mySAP ERP mySAP SCM mySAP CRM mySAP PLM mySAP SRM
SAP NetWeaver SAP Enterprise Portal SAP Master Data Management SAP Business Information Warehouse SAP Exchange Infrastructure SAP Mobile Infrastructure SAP Web Application Server SAP Basis FastTrak WAS 700 15 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Basic elements of SAP solution SAP NetWeaver: Technological infrastructure for all SAP solutions. SAP Business Suite: Compromise of cross-industry, SAP Netweaver based solutions. SAP Smart Business Solutions: SAP solution for small and midsize businesses. The mySAP All-in-One solution is an SAP R/3- based system that has been extended with business functions from other SAP solutions. This means that each combination of functions result in a different mySAP All-in-one package. SAP Packaged Solutions offer a similar approach. These solution are packages of functions from different solutions of mySAP Business Suite combined individually for each customer.
16 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Basic elements of SAP solution SAP xAPPS (Collaborative Cross Applications): Allow for integration of existing applications with each other by accessing existing datasets and functions using open interfaces. This means that new applications can be implemented based on an existing infrastructure. Industry Solutions provide business functions for selected industries. These functions are implemented in an SAP R/3(Enterprise) System and are available as Add-Ons.
17 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP business suite Previously known as mySAP.com. Its a complete spectrum of business solutions. A technological infrastructure that combines openness and flexibility with maturity and stability. Interfaces for integrating non-SAP products. Components that can be adapted to meet multiple business requirements. Numerous industry-specific functions. 18 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP business suite (continued) Comprises of the following solutions: SAP ERP (Enterprise Resource Planning) SAP CRM (Customer Relationship Management) SAP SRM (Supplier Relationship Management) SAP SCM (Supply Chain Management) SAP PLM ( Product Life-Cycle Management) One of the major product is SAP NetWeaver.
19 IBM Global Business Services Copyright IBM Corporation 2009 Solutions and components Many solutions for business challenges are provided in context of mySAP Business Suite. Different solutions therefore contain, in part, similar components. Components refer to, e.g. an SAP ECC system, an SAP SCM system or also an SAP Business Information Warehouse system.
SAP Basis FastTrak WAS 700 Source: SAP 20 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Possibilities with SAP business suite Possible Business Scenarios with SAP Business Suite Source: SAP 21 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 NetWeaver is a technology stack provided by SAP to support SAP Business Suite and its SAP solutions and other SAP products. SAP Netweaver allows the integration of non-SAP products. Customers can make use of the SAP NetWeaver functions for a specific solution. SAP for Industry solutions, not only provide add-ons to SAP components but also preconfigurations and best practices. mySAP ERP (now SAP ERP 6.0) is available since March 2003. SAP offered a bundle of components supporting ERP business processes. SAP R/3 Enterprise was one of those components. SAP ERP Central Component (ECC) is next step in this evolution. Some key features of SAP NetWeavers 22 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 R/3 / ECC Releases Source: SAP 23 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP NetWeaver SAP NetWeaver is the technical basis of the solutions from mySAP Business Suite and the Composite Applications the SAP xAPPS. It is also the core of the Enterprise Services Architecture, SAP basic concept for Web Service solution. It is the functionally successor of the SAP application platform mySAP Technology and serves the basis for the Enterprise Services Architecture, in order to meet requests for flexibility and integration between systems, interfaces, users and processes. It connects information, business processes and people across system and organizational boundaries. It the central tool for reducing TCO of complex system infrastructure.
Source: SAP 24 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 NetWeaver: A snapshot Integration Layer Who would use it? What is it? Which Component? People Integration Information Integration Process Integration Application Platform All users Managers, Power users, Administrators & Developers Administrators & Developers Administrators & Developers Linking various systems in a unified UI Preparation & consolidation of data & data views Modeling processes, disturbing & grouping data Core technology on which all NetWeaver components are built Enterprise Portal, SAP Mobile Infrastructure Master Data Management, Business Warehousing XI Web Application Server 25 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP NetWeaver provides core functions for the technical infrastructure of your business solutions in four integration levels. People Integration: This ensures the employees to have the information and functions that is required to perform their work as quickly and efficiently as possible. Information Integration: The Information Integration level provides access to all structured and unstructured information in the company. Process Integration: Process Integration ensures that business processes run across system boundaries in a heterogeneous system landscape. Application Platform: With SAP Web Application Server, the Application Platform has J2EE and ABAP runtime environments. Thus it supports Web applications and Web services in an open development environment.
Integration Levels of SAP NetWeaver 26 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP NetWeaver also supports cross-application software, so-called composite applications or xAPPs. (xAPPs connect heterogeneous systems in continuous cross-function processes so that the underlying applications can be more or less ignored). Different software interfaces ensures full interoperability of applications that are running on Microsoft .NET and IBM WebSphere.
Integration Levels of SAP NetWeaver 27 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Components of SAP NetWeaver Source: SAP 28 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP system architecture and WebAS Source: SAP 29 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP system architecture and WebAS (continued) The SAP classic system architecture requires a database server, one or more application servers, and one or more (typically hundreds or thousands of) front-end presentation servers. Many of SAP products (including ECC) are build upon powerful platform called Web Application Server, or WebAS. WebAS offers an "open" front-end. Uses the most popular computer communication languages HTML, XML, Web Services, and traditional "SAP." It is very helpful for the programmers for customizing. WebAS provide an "open" back-end. A company deploying it, can navigate a number of different roads.
30 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Client / server environment A standard client/server environment connects workstations, printers, and other client devices to a server.
Source: SAP 31 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Three-tiered architecture Source: SAP 32 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 The three layers are: Presentation layer: The PC-based GUI interface that is used by the end-user community. Application layer: The SAP application servers that service requests for data and manage the interface to the presentation layer. Database layer: The actual DBMS that communicates with the application servers to fulfill their requests for data.
Three-Tiered architecture (continued) 33 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Advantages of Three-tier Architectures: 1. Scalability: Add machines in middle tier to support more users 2. Portability: It is possible to use different platforms at all levels. 3. Interoperability and openness: Middleware serves as platform to integrate and interact with third-party products. 4. Nice GUIs: Presentation servers can interact with Microsoft Word, Excel, etc.
Three-Tiered architecture (continued) 34 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 The SAP Web as a fixed component of SAP systems Every SAP system is based on the SAP Web as a runtime environment Source: SAP 35 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP Web Application Server (SAP Web AS) Source: SAP 36 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP Web Application Server (SAP Web AS) (continued) SAP Web AS is the logical result of further development of the SAP. Application Server Technology (formerly also known as SAP Basis), with particular attention being paid to Web-based applications. SAP Web Application Server offers: A reliable and thoroughly tested runtime environment, evolved over more than ten years. A framework for executing complex business processes that meets the highest security standards. A reliable and user-friendly development environment. Support for open technical standards, such as: HTTP, HTTPS, SMTP, WebDAV, SOAP, SSL, SSO, X.509, Unicode, HTML, XML, and WML. High scalability, inherited from SAP Basis. Support for various operating systems and database systems.
37 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAPs release and maintenance strategy defines how SAP delivers and maintains SAP applications and SAP NetWeaver. SAPs release strategy assures the following: Aligned availability Availability of country, language, and platform versions Possibilities for you to participate in different phases of shipment Well-defined upgrade paths SAPs maintenance strategy provides the following: Aligned maintenance between SAP applications and SAP NetWeaver A three-phase maintenance model to satisfy different customer needs Well-defined timelines for different maintenance phases
SAPs release and maintenance strategy 38 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 The release strategy is based on the following principles: You can obtain the entire mySAP Business Suite, individual SAP applications or SAP NetWeaver. SAP applications and SAP NetWeaver have their individual release cycles. Usually, SAP delivers a new release of SAP NetWeaver first, and shortly afterwards, new releases for SAP applications of mySAP Business Suite follow synchronously. SAP always gives you access to the current release of an SAP application and to procedures to upgrade to the current release. A new release of an SAP application can always be integrated with any release of any other SAP application that is still in mainstream and extended maintenance. This approach offers you maximal flexibility for continuous improvement. Release strategy 39 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 The Ramp-Up Ramp-Up process is SAPs process of introducing new application releases to the market. Ramp-Up program provides a risk-free way for you to implement new SAP software as soon as it becomes available. At the beginning of the Ramp-Up process, SAP identifies target industries as well as customers who then implement and use the new release in closely monitored and documented projects. During the Ramp Up, the software is only available for limited circle of customers, customers apply at SAP to participate in Ramp-Up. The Ramp-Up servers to take customer wishes into consideration before the respective SAP software is generally available (unrestricted shipment). Participants in Ramp-Up are given direct contact to the SAP development and are provided with wide support in implementing the SAP software. 40 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Maintenance strategy The maintenance strategy for cross-industry applications is based on the following principles: SAP offers three successive maintenance phases: mainstream maintenance, extended maintenance, and customer-specific maintenance. SAP provides support packages during mainstream maintenance and extended maintenance. The delivery frequency of support packages is dependent on the maintenance phase. SAP also provides legal changes to adapt the SAP application to new or changed legal requirements during mainstream and extended maintenance. As part of its release strategy, SAP announces the planned period and scope of mainstream maintenance for a release as soon as the release is announced 5-1-2 maintenance strategy.
41 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 Maintenance strategy (continued) Source: SAP 42 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 The SAP software maintenance strategy for SAP R/3 and mySAP ERP Source: SAP 43 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 The SAP system is software which is composed of different software and a server as a whole and has the ability to perform standard business functions for corporations. Its stands for Systems, Applications and Products in Data Processing. SAP has evolved from a R/2 to R/3 type architecture. SAP Web Application server opens up a variety of new opportunities. SAP follows a release and maintenance strategy.
Module takeaways 44 IBM Global Business Services Copyright IBM Corporation 2009 Questions and Answers SAP Basis FastTrak WAS 700 45 IBM Global Business Services Copyright IBM Corporation 2009 Module 1: Summary Having completed this module, you should now be able to: Define an ERP Relate SAP to an ERP Recognize the evolution of SAP Identify the various components of SAP Put in your own words the underlying features of SAP Netweaver Categorize various kinds of client-server architecture from a SAP perspective Analyze SAPs release as well as maintenance strategy SAP Basis FastTrak WAS 700 46 Copyright IBM Corporation 2009
IBM Global Business Services Course Title SAP Project Lifecycle Module 2 IBM Global Business Services Copyright IBM Corporation 2009 Module 2: Objectives On completion of this module, you should be able to: Describe the different phases of SAP Project Lifecycle
SAP Basis FastTrak WAS 700 48 IBM Global Business Services Copyright IBM Corporation 2009 Module 2: Agenda Topic 1: SAP Project Lifecycle SAP Basis FastTrak WAS 700 49 IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 SAP project lifecycle 50 Evaluations Project Preparation Business Blueprint Realization Testing Final Preparations Go live Sustain/ Support A typical new SAP implementation lifecycle Sustain Sustain Evaluation Realization Testing Final Preparation Go live Sustain A Typical Multiphase SAP Implementation IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 The stages are described briefly below: Evaluation: This may be a decision to choose between different software vendors or selection of products from a single vendor. Project Preparation: Since a SAP implementation intends to map the organization processes to the ones defined by SAP, the implementation needs to be have on-board people with complete knowledge of the organization business processes. The project preparation phase, amongst other things, aims to identify this team. Business Blueprint: What modules of the SAP product would be used and the mapping of the existing business processes to the processes provided by SAP. Realization: The actual work of adapting the SAP software to be aligned with the organizations business processes is done is this phases. This would include customizing the software and also development of new objects based on requirement.
The stages of SAP project lifecycle 51 IBM Global Business Services Copyright IBM Corporation 2009 The stages of SAP project lifecycle (continued) Testing: The changes made in realization phase need to be tested in isolation as well as in a consolidated manner using real life like data. This is done in the testing phase Final preparation: The production system is prepared using the changes from the realization & testing phases. Certain activities need to be done directly in the production system as well- these are done during the Final preparation phase. Go-live: Releasing the productive system to the end-users. The go-live may be done in a Big Bang (all modules at one go) or in a phase-by-phase manner. Sustain / support: The project now moves into the sustain & maintain phase, where end-users issues would be resolved & ongoing maintenance of the system would be taken care of.
SAP Basis FastTrak WAS 700 52 IBM Global Business Services Copyright IBM Corporation 2009 Module takeaways A SAP project lifecycle consists of various stages starting from evaluation to the projects subsequent support.
SAP Basis FastTrak WAS 700 53 IBM Global Business Services Copyright IBM Corporation 2009 Questions and Answers SAP Basis FastTrak WAS 700 54 IBM Global Business Services Copyright IBM Corporation 2009 Module 2: Summary Having completed this module, you should now be able to: Identify the different phases of SAP Project Lifecycle
SAP Basis FastTrak WAS 700 55 Copyright IBM Corporation 2009
IBM Global Business Services Course Title Fundamentals of SAP WAS Module 3 IBM Global Business Services Copyright IBM Corporation 2009 Module 3: Objectives On completion of this module, you should be able to: Interpret the architecture of SAP Web Application Server (WAS) Describe ABAP and JAVA Processes Identify the different types of SAP WAS SAP Basis FastTrak WAS 700 57 IBM Global Business Services Copyright IBM Corporation 2009
SAP NetWeaver NetWeaver is essentially an umbrella term, encompassing a number of SAP products and technologies that combine to create a platform for building, extending, and integrating enterprise applications. It has built in interoperability which hooks into SAP-, Microsoft-, and Java- based technologies. Development cost is decreased. Integration is enabled, speeding up time to deploy as well as shrinking the time necessary to perform system upgrades and so on. Total cost of ownership is reduced significantly because maintenance and support costs are dramatically reduced. Thus, innovation is enabled; IT can spend more time meeting the needs of the business, and less time maintaining existing solutions.
SAP Basis FastTrak WAS 700 58 IBM Global Business Services Copyright IBM Corporation 2009 SAP Web AS / Basis available platform SAP Basis FastTrak WAS 700 59 Source: SAP IBM Global Business Services Copyright IBM Corporation 2009 SAP Web AS / Basis available platform (continued) The WebAS / Basis layer manages all your application modules within your SAP system and ensures that these modules are integrated. It enables platform independence as well. Some important functions of the WebAS / Basis System include: Constitutes the run time environment for SAP Represents the heart of the administrative core of SAP Enables management and distribution of your SAP technical components and resources Permits optimal integration of the various SAP applications into the overall computing environment Establishes a stable structural framework for system upgrades, enhancements, and so on Makes it possible to interface with third-party applications and products, thus extending SAP functionality beyond its own innate capabilities
SAP Basis FastTrak WAS 700 60 IBM Global Business Services Copyright IBM Corporation 2009 Components of SAP WEB AS SAP Basis FastTrak WAS 700 61 Message Server (Service): The Message Server handles the communication between the distributed dispatchers within the ABAP stack, and enables scalability of several parallel ASs. The message server is configured only once per SAP System. Dispatchers Gateway Server (Service): The gateway server (GW) enables communication between SAP systems or between SAP systems and external application systems. There is one Gateway per dispatcher.
Internet Communication Manager ICM (Service): ICM enables SAP systems to communicate directly with the Internet. The ICM receives requests from the Internet and forwards them to the SAP system for processing. It also does recognize whether the request is a call of business server page or a JAVA application and forwards the request to ABAP or JAVA stack accordingly. You can configure a Maximum of one ICM process per application server. Enqueue Work Process: The Enqueue work process administers the lock table in the shared memory. The lock table contains the logical database locks of the ABAP stack. Only one enqueue work process is needed for each SAP system. Dialog Work Process: THE Dialog work process fulfil all requests for the execution of dialog steps triggered by an active user. Every dispatcher requires at least two dialog work processes. Update Work Process: Update work processes execute update requests. You need at least one update work process per SAP system and you can have more than one per dispatcher. *** You can use transaction SM50 to display an overview of ABAP work process Spool Work Process: The Spool work process pass sequential data flows on to printers. Every SAP system requires at least one Spool work process. However, there can be more than one per dispatcher. Background Work Process: The background work processes execute programs that run without user interaction. At least two background work processes are required per SAP system. More than one background work processes can be configured per dispatcher. IBM Global Business Services Copyright IBM Corporation 2009 Important terms for SAP WEB AS The ABAP dispatcher Dialog work processes (DIA) Spool work processes (SPO) Update work processes (UPD and UPD2) Background work processes (BGD) The enqueue work process (ENQ)
SAP Basis FastTrak WAS 700 62 The ABAP dispatcher Dialog work processes (DIA) Spool work processes (SPO) Update work processes (UPD and UPD2) Background work processes (BGD) The enqueue work process (ENQ) IBM Global Business Services Copyright IBM Corporation 2009 Java processes The following processes exist in the Java environment: The Java dispatcher The Java server process The Java message service The Java enqueue service The SAP Java Connector (Jco)
SAP Basis FastTrak WAS 700 63 Java Environment The Java dispatcher The Java server process The Java message service The Java enqueue service The SAP Java Connector (Jco) IBM Global Business Services Copyright IBM Corporation 2009 ABAP services In addition, the (ABAP) runtime system provides additional services (these are not work processes) for internal and external communication: The message server (MS) handles the communication between the distributed dispatchers within the ABAP stack of an SAP system. The gateway server (GW) enables communication between SAP systems, or between SAP systems and external application systems. There is one per dispatcher. An instance is an administrative unit that combines SAP system components providing one or more services. The instance shows all the processes that are required for error-free operation of an SAP system, collected on one instance. This instance is distinguished from all other instances of the SAP system and is also called central instance. The services that an application server can provide are determined by the type of work processes it has.
SAP Basis FastTrak WAS 700 64 IBM Global Business Services Copyright IBM Corporation 2009 Java basics The Java programming language was first introduced by the company Sun Microsystems Inc.in 1995. Java is an object-oriented and platform-independent programming language that is widely used in many areas. The powerful concept of Java allows the development of a large number of different types of application - from the classic application using Applets implemented in Web pages to client/server applications. Java was designed to be platform-independent. This means that the same Java program can be executed on any system for which a Java Runtime Environment (JRE) is available. In particular, Java applications can run on different systems that are based on different hardware.
SAP Basis FastTrak WAS 700 65 IBM Global Business Services Copyright IBM Corporation 2009 Basic java programs You need to differentiate between two basic types of Java programs, applications and applets: Applications: Java applications are computer programs with the full functional range also provided by other programming languages. Applets: The term applet essentially means little application. It usually means a Java applet, a small computer program that runs in a Web browser and is written in the Java programming language. SAP Basis FastTrak WAS 700 66 IBM Global Business Services Copyright IBM Corporation 2009
Three tier java architecture SAP Basis FastTrak WAS 700 67 Source: SAP IBM Global Business Services Copyright IBM Corporation 2009 Java services All Java components of an SAP system are known as a Java cluster. A Java cluster consists of: A (central) Java instance with a dispatcher and at least one server process. The central services, which contain a message server and an enqueue server. A database for the central storage of data. Optionally, additional Java instances. The central services provide the basis for communication and synchronization for the java cluster: The message service administers a list of the dispatchers and the server processes of the Java cluster. The enqueue service administers logical locks that are set in a server process by the executed application program. It is also used for cluster-wide synchronization.
SAP Basis FastTrak WAS 700 68 IBM Global Business Services Copyright IBM Corporation 2009 Java processes The dispatcher distributes incoming requests to the server processes. The server process executes the Java applications. Every server process is multi-threaded and can thus process a large number of requests in parallel (in contrast to the ABAP work processes). For each dispatcher there is at least one server processes and there can be up to 16 server processes. The Java message service manages a list of Java dispatchers and server processes. It is responsible for the communication within the Java runtime environment. The Java enqueue service manages logical locks that are set by the executed Java application program in a server process. The Software Deployment Manager (SDM) is the standard tool used to install Java software components on the SAP Web AS Java. SAP Basis FastTrak WAS 700 69 IBM Global Business Services Copyright IBM Corporation 2009 Multiple NetWeaver instances with AS Java SAP Basis FastTrak WAS 700 70 Source: SAP IBM Global Business Services Copyright IBM Corporation 2009 Instance in ABAP environment SAP Basis FastTrak WAS 700 71 Dispatcher Message Server Instance Instance Central Instance ** The terms (SAP) instance and (SAP web) application server are often used as synonyms.
Dispatcher Dispatcher IBM Global Business Services Copyright IBM Corporation 2009 Instances in an ABAP + Java environment SAP Basis FastTrak WAS 700 72 Message Server Internet Communication Manager Central Services ABAP Schema JAVA Schema SAP GUI Web Browser / Web Server JCo WP WP WP ABAP JAVA SDM JAVA Server Processes ABAP Dispatcher JAVA Dispatcher IBM Global Business Services Copyright IBM Corporation 2009
Different types of the SAP Web AS SAP Basis FastTrak WAS 700 73 SAP Web AS JAVA System SAP Web AS ABAP + JAVA System (Add-In Installation) Web AS Installation Types SAP Web AS ABAP System SAP Web AS ABAP System: Complete Infrastructure in which is ABAP based applications can be developed and used. SAP Web AS JAVA System: Complete Infrastructure for developing and using J2EE base applications SAP Web AS ABAP + JAVA (Add-In) System: Complete Infrastructure in which ABAP based and J2EE based applications can be developed and used. This installation emphasizes the seamless Java ABAP integration 1 2 3 3 2 1
NOTE: One of the main characteristics of the SAP Web AS is that ABAP tables, programs and application data are stored in the ABAP schema of the database while JAVA data is stored in the JAVA schema. Here, the ABAP runtime environment can access the ABAP schema of the database, and the JAVA runtime environment can access the JAVA schema. The SAP Java Connector is used for integrating the ABAP environment and the JAVA environment (JCo). IBM Global Business Services Copyright IBM Corporation 2009 Module takeaways
SAP Basis FastTrak WAS 700 74 The SAP WAS consists of an ABAP engine and a JAVA engine. They are constituted by different processes in SAP WAS Architecture. The Message Service and Enqueue service comprise the central services.
IBM Global Business Services Copyright IBM Corporation 2009 Questions and Answers SAP Basis FastTrak WAS 700 75 IBM Global Business Services Copyright IBM Corporation 2009 Module 3: Summary Having completed this module, you should now be able to: Interpret the architecture of SAP Web Application Server (WAS) Describe ABAP and JAVA Processes Identify the different types of SAP WAS SAP Basis FastTrak WAS 700 76 IBM Global Business Services Copyright IBM Corporation 2009 Starting and Stopping of SAP Systems Module 4 IBM Global Business Services Copyright IBM Corporation 2009 Module 4: Objectives On completion of this module, you should be able to: Describe the start sequence of an ABAP+JAVA System Analyze how to start and stop an SAP system using SAP MMC, JAVA MC or command line argument Recall the JAVA instance from ABAP interface
SAP Basis FastTrak WAS 700 78 IBM Global Business Services Copyright IBM Corporation 2009 Module 4: Agenda Topic 1: Start sequence of an ABAP+JAVA System Topic 2: Start and stop an SAP system using SAP MMC, JAVA MC or command line argument Topic 3: Restart JAVA instance SAP Basis FastTrak WAS 700 79 IBM Global Business Services Copyright IBM Corporation 2009 Start process of SAP System (ABAP + Java) SAP Basis FastTrak WAS 700 80 Source: SAP IBM Global Business Services Copyright IBM Corporation 2009 Starting the SAP system SAP Basis FastTrak WAS 700 81 Operating system: Windows 2000/2003 Microsoft Management Console using SAP MMC Snap-In Central instance Other instance DB 3 4 1 2 <sid>adm If not started log-on Start IBM Global Business Services Copyright IBM Corporation 2009 SAP Basis FastTrak WAS 700 82 Source: SAP IBM Global Business Services Copyright IBM Corporation 2009 System start: Logs SAP Basis FastTrak WAS 700 83 MMC with SAP MMC Snap-In Microsoft Windows SAP<sid>_no. SAPOsCOL Database Services Security log System log Application log Services IBM Global Business Services Copyright IBM Corporation 2009 Start process logging in the system SAP Basis FastTrak WAS 700 84 Source: SAP IBM Global Business Services Copyright IBM Corporation 2009 Problem analysis SAP Basis FastTrak WAS 700 85 SAP MMC Snap-In DB SAP INSTANCE Event Viewer Database error log files SAP<sid>instance no. Database service SAP trace files SAP system log IBM Global Business Services Copyright IBM Corporation 2009 SM21: System logs SAP Basis FastTrak WAS 700 86 IBM Global Business Services Copyright IBM Corporation 2009 Stopping SAP systems Why ?: For maintenance purposes or after changing system parameters, before installing kernel patches, or allowing hardware upgrades to be carried out. Things to be kept in mind before stopping:
SAP Basis FastTrak WAS 700 87 Check the status of Send a system message SM02 IBM Global Business Services Copyright IBM Corporation 2009
Stopping the SAP system SAP Basis FastTrak WAS 700 88 CCMS SAP Instance SAP System Admin SAP MMC Snap-in <sid>adm Database Tools DATABASE SAPOsCOL sap<sid>_<inst.no.> Database Services Windows Service Control Manager IBM Global Business Services Copyright IBM Corporation 2009 SAP Microsoft Management Console: Windows SAP MMC provides a common framework for system management. It allows various tools that were previously implemented separately to be integrated in a common user-interface enabling centralised system management. It provides an environment for incorporating and accessing tools. Tools are integrated in the SAP MMC in the form of snap-ins that allow standardised access to functions. SAP Basis FastTrak WAS 700 89 IBM Global Business Services Copyright IBM Corporation 2009 Services concept in Windows SAP Basis FastTrak WAS 700 90 Database process SAP process NT service control manager Registry Operating system: Microsoft Windows DB services SAP services OS services IBM Global Business Services Copyright IBM Corporation 2009
Using SMICM to restart Java In the case of SAP NetWeaver AS ABAP + Java, it is possible to allow the ABAP stack to continue running, and only stop and then restart the Java stack. You do this using transaction SMICM. You can either start / stop the (local) instance onto which you are logged in the transaction SMICM or start/stop all the instances in the (global) Java cluster.
SAP Basis FastTrak WAS 700 91 IBM Global Business Services Copyright IBM Corporation 2009 Using SMICM to restart Java (continued) SAP NetWeaver AS Java is started and stopped in the same way as SAP NetWeaver AS ABAP + Java by means of the SAP Management Console / Java MC.
SAP Basis FastTrak WAS 700 92
IBM Global Business Services Copyright IBM Corporation 2009 JAVA MC SAP MC is a Java application which is supplied as a Java applet as standard. You simply use a Web browser to do this. To use the applet correctly, you require a JRE (Java Runtime Environment) of version 1.4 or higher. In addition, the corresponding Java plug-in for the browser must be activated correctly. To start SAP MC after installing the corresponding SAP NetWeaver AS, enter the below URL in your browser: http://<host name>:5<instance number>13
SAP Basis FastTrak WAS 700 93 IBM Global Business Services Copyright IBM Corporation 2009 Unix Log on in UNIX as a user with SAP administrator authorization (<sid>adm). To start the central instance, call the shell script startsap_<host>_<instance no> in the home directory of the <sid>adm user. The script startsap first starts the saposcol process which collects statistical data for the operating system that it provides to the SAP system. The next step is a check to see if the database is running. If not, the script startdb is called to start the database. The final step starts all of the processes for the instance (message server, dispatcher, work processes, and so on). After the central instance is started, you can optionally start other instances. The startsap script can be called with the following options: DB: starts the database system R3: starts the instances and associated processes for the instance ALL: starts the database system and the instance (default setting, can be omitted) SAP Basis FastTrak WAS 700 94 IBM Global Business Services Copyright IBM Corporation 2009 Unix (continued) When you stop the SAP system, you should first stop all dialog instances and then stop the central instance. You have two options for doing this: From the SAP system using the CCMS Control Panel. Log on under UNIX as the SAP administrator (<sid>adm) at operating system level and enter the command stopsap from your home directory. The stopsap script can be called with the following options: DB: stops the database system with the help of the stopdb script R3: stops the instances of the SAP system ALL: stops the database system and the instance (default setting, can be omitted) SAP Basis FastTrak WAS 700 95 IBM Global Business Services Copyright IBM Corporation 2009 OS/400 Logon on to the AS/400 system with the SAP user profile for administrators. The authorizations of the group profile <SID>OPRGRP are required for this user (such as user profile <SID>OFR or <SID>OPR ). Enter the AS/400 command STARTSAP and request parameters with F4. Under SAP System ID, enter the name of your system (such as DEV). Under R/3 Instance, enter the instance number (such as 00). To start all instances on one or more hosts, choose *ALL. Under R/3 Instance Host Name, enter the name of the host on which the instance is to be started. To start all instances on all hosts, choose *ALL. (You must also have selected *ALL under R/3 Instance.) SAP Basis FastTrak WAS 700 96 IBM Global Business Services Copyright IBM Corporation 2009 OS/400 (continued) Confirm your entries with ENTER. The subsystem R3_nn is then started for each started instance (<nn> is the instance number). All associated SAP services are started together with the subsystem (such as dispatcher, work processes, spool processes). Enter the AS/400 command WRKACTJOB SBS(R3_<nn>) to check whether the SAP system(s) were started correctly. The system displays a screen with the column Status at the right-hand side. If an SAP system was started correctly, the first line of this column should contain the value RUN (running), SELW (waiting), or DEQW (waiting for completion of unlocking). It can take a few minutes for the file system to reach this status. SAP Basis FastTrak WAS 700 97 IBM Global Business Services Copyright IBM Corporation 2009 OS/400 (continued) Logon on to the AS/400 system with the SAP user profile for administrators (<SID>OFR or <SID>OPR). Enter the AS/400 command STOPSAP and request parameters with F4. Under SAP System ID, enter the name of the SAP system that you want to stop. Under R/3 Instance, enter the number of the instance that you want to stop, such as 90. To stop all instances on one or more hosts, choose *ALL. SAP Basis FastTrak WAS 700 98 IBM Global Business Services Copyright IBM Corporation 2009 OS/400 (continued) Under R/3 Instance Host Name enter *LOCAL to stop one or more instances on the local host. To stop all instances on all hosts, choose *ALL. (You must also have chosen *ALL under R/3 Instance.) If you enter *YES under Wait for instance to end, the command STOPSAP waits until the SAP instance is shut down before stopping the SAP system. (The instance is regarded as shut down if the number of active instance user jobs in the instance subsystem, other than the SAPOSCOL job, is zero.) Under Maximum wait time (seconds), you can enter the maximum time that the command should wait for the instance to be shut down. The default value is 120 (two minutes). If it takes longer than two minutes for the instance to be shut down, an exception message is sent. Confirm your entries with ENTER.
SAP Basis FastTrak WAS 700 99 IBM Global Business Services Copyright IBM Corporation 2009 Module takeaways
SAP Basis FastTrak WAS 700 100 The SAP Processes follow a definite start sequence. The log files are located in specific folders in an SAP system. System can be stopped/started using SAP MMC in windows. Command line argument or JAVA management console exists for other systems. (AS JAVA usage type)
IBM Global Business Services Copyright IBM Corporation 2009 Questions and Answers SAP Basis FastTrak WAS 700 101 IBM Global Business Services Copyright IBM Corporation 2009 Module 4: Summary Having completed this module, you should now be able to: Describe the start sequence of an ABAP+JAVA System Analyze how to start and stop an SAP system using SAP MMC, JAVA MC or command line argument Recall the JAVA instance from ABAP interface