comprehensive-sap-basis-training-day-1.ppt

The document title is Arial, 32-point bold. IBM standard is blue, but black can be usedModule 2: SAP Project Lifecycle
3 Module 3: Fundamentals of SAP WAS
Module 4: Starting and Stopping SAP Systems
Day 1: Module map
*
*
After completion of this module, you should be able to:
Define an ERP
Understand SAP Netweaver Concept.
Understand the various kinds of Client-Server Architecture from SAP perspective.
Know SAP’s Release and Maintenance Strategy
SAP Basis FastTrak WAS 700
*
IBM Business Consulting Services
© Copyright IBM Corporation 2006
Module 1: Agenda
Topic 3: SAP evolution
Topic 5: Features of Sap Netweaver
Topic 6: SAP client-server architecture
Topic 7: SAP release and maintenance strategy
*
Large corporations developed their software in-house.
These software aimed at automating functional processes.
Advantages:
Disadvantages:
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 70’s
*
Make vs. Buy vs. Mix ‘n Merge
*
1970’s
1980’s
1990’s
Enterprise Resource Planning (ERP)
ERP is the planning of how business resources (materials, employees,
*
*
The roles of contract owner, annuitant, payee, and beneficiary can be understood with respect to a real life example in the next slide.
IBM Global Business Services
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.
*
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).
*
SAP- A brief History
In 1972, five former IBM employees– Dietmar Hopp, Hans- Werner Hector, Hasso Plattner, Klaus Tschira, and Claus Wellenreuther launched a company called SAP System Analysis and Program Development in Manheim, Germany. Their vision: to develop standard application s/w for real- time business processing. One year later, the first financial accounting software was completed, forming the basis for the continuous development of other s/w components in what later came to known as the “R/1 system”.
"R" stands for real-time data processing.
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.
*
SAP followed the trend from mainframe computing to client-server architectures. (R/2 to R/3 systems)
The development of SAP’s internet strategy with mySAP.com redesigned the concept of business processes (integration via Internet).
ERP packages
mySAP from SAP
PeopleSoft from Oracle
*
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.
*
Notes:
The SAP R/2 system attained the high level of stability of the previous generation of programs. Keeping in mind its multinational customers, SAP designed SAP R/2 to handle different languages and currencies. With this other innovations in SAP R/2, SAP sees rapid growth.
What was unique about R/2 was that it was a packaged software application that processed real-time on a mainframe computer taking advantage of Time Sharing Option and integrated all of an enterprise's functions, such as accounting, manufacturing processes, supply chain logistics and human resources.
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).
*
*
SAP R/3 is designed to handle all of the business management tasks of a company. Some particular examples that you'll see are: the payment of invoices, the management of production resources and the control of financial accounts.
When we install Microsoft Excel on our PC, each component of Excel (printing components, graphing components, word processing components, and etc.) is stored, managed, and processed via the hardware of our PC. When a company installs SAP’s software each component (or "layer” in R/3’s case) is stored, managed, and processed via the hardware of separate and specialized computer systems.
Each of the various layers is capable of calling upon the specialty of any of the other installed layers in order to complete a given task.
Source: SAP
*
SAP’s go-to-market approach is shown in figure. SAP’s S/W Product is constantly extended, optimized and tailored to the needs of market and of customers. therefore SAP has developed many industry specific solutions over the years. SAP products integrate different business systems (different vendors and across company boundaries). Products for small to midsize business have also been added to SAP’s Family Solutions.
*
*
The figure’s three levels portray a business-oriented view of solutions that address your specific business issues (top level) and a product oriented
view of the SAP applications and of the technical infrastructure that are the foundation for those solutions (middle and bottom levels).
The business solutions in the first level are flexible combinations of application software, services, and support that help you
solve business problems and achieve your business objectives. The business applications in the middle level are both cross industry
and industry-specific software offerings from SAP. They include the mySAP Business Suite family of business applications, SAP xApps packaged composite applications, and SAP applications that perform specialized functions in particular industries. These business applications are assembled as needed to create your business solutions, as portrayed in the top layer.
The integration and application infrastructure on the lowermost level is the SAP NetWeaver technology platform. All SAP software offerings and a large ecosystem of SAP partner software offerings are built on the open SAP NetWeaver technology platform. Applications built on the SAP NetWeaver technology platform are easy to combine into highly industry-specific business solutions and easy to integrate with non-SAP applications for added value.
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.
*
www.sap.com/netweaver
www.sap.com/solutions
www.sap.com/smb
www.sap.com/xapps
www.sap.com/industry
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.
*
SAP business suite
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.
SAP business suite (continued)
One of the major product is SAP NetWeaver.
*
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.
Source: SAP
Complete package of cross-industry solutions that link people, information & processes.
All components of the mySAP Business Suite are based on SAP NetWeaver:
customer relationship management (CRM) - helps companies acquire and retain customers, gain deep marketing and customer insight, and align organization on customer-focused strategies.
product lifecycle management (PLM) - helps manufacturers with a single source of all product-related information necessary for collaborating with business partners and supporting product lines.
supply chain management (SCM) - helps companies enhance operational flexibility across global enterprises and provide real-time visibility for customers and suppliers.
supplier relationship management (SRM) - customers can collaborate closely with suppliers and integrate sourcing processes with applications throughout the enterprise to enhance transparency and lower costs.
Possible Business Scenarios with SAP Business Suite
Source: SAP
mySAP Business Suite offers many options for integrating your company-internal business processes and, likewise, integrating business partners. systems. You can implement the integration of cross-enterprise processes using different technologies, such as with Application Link Enabling, using Electronic Data Interchange (EDI), through XML data exchange, or also using Collaborative Cross-Applications (xApps) and Web Services.
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
*
R/3 / ECC Releases
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
NetWeaver: A snapshot
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
*
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
*
Components of SAP NetWeaver
Source: SAP
Notes:
The SAP system was historically designed so that the presentation layer, application logic, and data management were logically separate as well as potentially physically separate from one another. In this way, a flexible system can be architected, one where additional headroom can be easily added when required.
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.
*
Notes:
That is, many database versions and releases are supported in which to house all the data and configuration information that help create a solution rather than a bunch of data and a pile of equipment.
Client / server environment
Source: SAP
Client / server is still very popular concept.
SAP R/3 was built around the concept of client/server; ECC, on the other hand, is built around SAP NetWeaver and the concept of Enterprise Services Architecture.
A client / server environment is one in which the client machine (an individual PC, workstation, mobile computing device, or even another computer system) requests information (via a connection) from the supplying machine, known as the server. The communication and interchange of data between the requesting and supplying machine is known as the client / server relationship.
Three-tiered architecture
Source: SAP
Notes:
SAP AG’s approach was client server architecture which was brilliant. The SAP engineers solved many issue using this approach, issue like scalability (or lack of it, actually), the need to easily upgrade business application logic, and the desire for technical flexibility.
To this last point, the engineers at SAP wanted to abstract the database layer so that many different databases could be supported without having to go back and recode existing programs.
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)
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)
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
Notes:
The SAP Web Application Server has, in addition to the traditional runtime environment for ABAP programs, a runtime environment for J2EE-based Java programs, the SAP Web AS Java. The SAP Web AS is . together with the database. the Application Platform of SAP NetWeaver.
SAP Web Application Server (SAP Web AS)
Source: SAP
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.
*
SAP’s release and maintenance strategy defines how SAP delivers and maintains SAP applications and SAP NetWeaver.
SAP’s release strategy assures the following:
Aligned availability
Possibilities for you to participate in different phases of shipment
Well-defined upgrade paths
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
SAP’s release and maintenance strategy
*
Notes:
This strategy determines the availability of new SAP releases, the length and conditions of their maintenance, and the dependencies among individual releases.
Thus SAP’s release and maintenance strategy provides planning reliability for your implementation and upgrade projects as well
as for optimal use of SAP applications and SAP NetWeaver. This reduces your TCO.
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
Notes:
The release strategy defines rules for delivering releases of SAP applications and SAP NetWeaver.
Releases of SAP applications or SAP NetWeaver are introduced to the market in several phases.
mySAP Business Suite always contains the application releases that have already reached the final phase (unrestricted shipment).
All releases are available to all customers and can be used in production operation. They have a predefined scope in terms of country, language, and platform versions.
SAP applications and SAP NetWeaver have a defined upgrade path: SAP provides upgrade procedures to the latest release. A new SAP application release can be seamlessly integrated with all releases of other applications that are still in mainstream maintenance or extended maintenance.
After an upgrade of an application, all previously used scenarios are still available. However, if you want to take full advantage of the latest version of a scenario or of a new scenario, you might need to upgrade more than one SAP application within your landscape.
The example in figure 3 shows that you only need to upgrade the applications your new scenarios rely on. For each scenario, SAP publishes the list of possible application releases within Master Guides documents on SAP Service Marketplace.
The Ramp-Up
Ramp-Up process is SAP’s 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”).
*
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.
Type of Subaccount Characteristics
Bond Fund Holds only bonds. Some bond funds hold only specific kinds of bonds such as municipal bonds.
Stock Fund Holds only stocks.
Balanced Fund Holds both stocks and bonds.
Value Fund Holds stocks for which the market price is significantly lower than the company's financial and economic situation warrants. Such stocks are said to be undervalued.
International Fund Holds securities issued by companies or governments outside the United States.
Money Market Fund Holds securities that mature within one year of purchase. These funds invest heavily in Treasury Bills.
Maintenance strategy (continued)
5-1-2 maintenance strategy:
• One year of extended maintenance at an additional 2% fee
• Two years of extended maintenance at an additional 4% fee
Mainstream and extended maintenance include all industry specific
applications which are delivered as add-ons. However, if there are several releases of an industry-specific application
for the same underlying release, only the latest release of the industry-specific application will be supported until the end of
mainstream maintenance and during extended maintenance of the underlying release.
The SAP software maintenance strategy for SAP R/3 and mySAP ERP
Source: SAP
One way in which equity-indexed annuities are similar to traditional fixed annuities is that premiums for both types of annuities are deposited in the insurer's general account. This characteristic clearly differentiates equity-indexed annuities from variable annuities, whose premiums are deposited in the insurer's separate account.
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
*
IBM_USER (I) - Should you consider offering answers to the questions? If not, delete...
Having completed this module, you should now be able to:
Define an ERP
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 SAP’s release as well as maintenance strategy
*
On completion of this module, you should be able to:
Describe the different phases of SAP Project Lifecycle
*
*
SAP project lifecycle
Sustain
Sustain
Evaluation
Realization
Testing
Final
Preparation
Sustain
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
*
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.
*
Module takeaways
A SAP project lifecycle consists of various stages starting from evaluation to the projects subsequent support.
*
*
Identify the different phases of SAP Project Lifecycle
*
Interpret the architecture of SAP Web Application Server (WAS)
Describe ABAP and JAVA Processes
Identify the different types of SAP WAS
*
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.
*
*
*
WebAS or Basis system is the middleware or software that functions as a conversion or translation layer between the technology and business/application layers of a computing solution and allows the various SAP applications to run on different hardware and system platforms.
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
*
*
Message Server (Service):
The Message Server handles the communication between the distributed dispatchers within the ABAP stack, and enables scalability of several parallel AS’s. 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.
The ABAP dispatcher
Background work processes (BGD)
*
Background work processes (BGD)
*
The ABAP dispatcher distributes the user requests to ABAP work processes.
Dialog work processes (DIA) fulfill all requests for the execution of dialog steps
triggered by an active user. Every dispatcher requires at least two dialog
work processes.
Spool work processes (SPO) pass sequential data flows on to printers. Every SAP
system requires at least one spool work process, you can also have more than
one spool work process per dispatcher.
Update work processes (UPD and UPD2) execute update requests. Similarly to spool work processes, you need at least one update work process per SAP system, and you can have more than one per dispatcher.
Background work processes (BGD) execute programs that run without interacting
with the user. You need at least two background work processes for each
SAP system. You can configure more than one background work process
for each dispatcher.
The enqueue work process (ENQ) administers the lock table in the shared memory.
The lock table contains the logical database locks of the ABAP stack of the
SAP system. Only one enqueue work process is needed for each system.
The Java dispatcher
*
*
The Java dispatcher distributes new incoming Java requests to the Java
server processes.
The Java server process executes the Java applications. The server processes
are implemented in the form of a Multi Threaded Server and can (in contrast
to the ABAP work processes) process several queries in parallel.
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 SAP Java Connector (Jco,) is responsible for the communication between the ABAP stack and the Java stack; it enables calls of the ABAP stack from the Java stack as well as vice versa.
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.
*
*
The message server (MS) enables the scalability of several parallel application servers. The message server is configured only once per SAP system.
The services provided by an instance are started or stopped together. You use a common instance profile to set parameters for all components of an instance. Each instance has its own buffer areas.
An application server can then take on several roles,for example, as a dialog server and simultaneously as a background server, if it provides several dialog work processes and at least one background work process.
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.
*
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.
*
Java applets are intended for execution within the Java Runtime Environment of a browser. They are transferred (as is also the case, for example, with embedded images) with the HTML page using the HTTP protocol, and then executed on the client computer.
*
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.
*
The message service represents the infrastructure of data exchange (for small quantities of data) between the nodes involved. In the case of load balancing between a large number of Java instances, it also provides the load balancing information for the SAP Web Dispatcher.
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.
*
*
*
Central Instance
** The terms (SAP) instance and (SAP web) application server are often used as synonyms.
Dispatcher
Dispatcher
*
*
The Internet Communication Manager (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. In doing so, it recognizes whether the request is a call of a business server page or a Java application and forwards this request to the ABAP runtime environment or the Java runtime environment. It can also direct HTTP requests from an
SAP system to a Web server and send the response back to the SAP system.
You can configure a maximum of one ICM process per application server.
*
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).
*
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.
*
Interpret the architecture of SAP Web Application Server (WAS)
Describe ABAP and JAVA Processes
Identify the different types of SAP WAS
*
Module 4
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
*
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
*
*
*
The starting of an SAP system is the basic prerequisite for being able to work with the system. Restarts of SAP systems are also required after maintenance work on the hardware in use and changes to the SAP system's profile.
Starting an SAP System is the task of the
operating system user <sid>adm.
Starting database:
. The SAP system lies over the database, it is essential that database should be started first.
Starting Central Instance:
. The operating system collector SAPOSCOL is started, if it is not already active. This stand alone program runs in the operating system background, independently of SAP instances. This program collects data about operating system resources and makes this data available through the shared memory of all SAP instances.
The central instance with the message server and the dispatcher and its work
processes is then started. If the start up parameters are set correspondingly,
the dispatcher also starts the Internet Communication manager (ICM) and the
SAP Web AS Java (if it is installed). You should only start other (optional)
instances once the message and enqueue servers are active.
If the dialog instance is not running on the same host as the central instance,
the SAPOSCOL operating system collector is first started on this host (if
it is not yet running).
The dispatcher is then started with its work processes.
Starting the SAP system
*
Central instance
Other instance
*
Under Microsoft Windows 2000/2003, you can start and stop the SAP system with the Microsoft Management Console (MMC).
the administrator logs on to the operating system as user <sid>adm,
and opens the Microsoft Management Console.
Choose the node for the central instance in the tree. Call up the context menu with the right mouse button and choose the Start function. The system first checks whether the database is active. If not, it is automatically started. If the database is active, the central instance (message server and dispatcher) is started by SAP Service SAP<SID>_<Instance no.>. The communication between the Microsoft
Management Console and the SAP Service takes place through a named pipe. Other instances can then be started.
The status of the SAP system, individual instances, and the message server and dispatcher are displayed in the Microsoft Management Console in accordance with the following color legend:
. Gray not running
. Yellow is starting
*
*
The specifications of the instances; that is, the type and number of processes, main memory sizes, and other options are controlled at the start of the instances using profiles. These are files at operating system level that are stored in the directory
\\<SAPGLOBALHOST>\sapmnt\<SID>\sys\profile.
When the instances are started, SAP Service reads which processes (message server, dispatcher) are to be started from the instance-specific start profile. The start profile can be displayed in the Microsoft Management Console by right-clicking the entry for the instance and selecting the function All tasks →View Start Profile.
The specification of the configuration of the instances is stored in the default profile and in the instance profile. These profiles are read by the dispatcher, which starts the work processes and creates the instance-specific configuration.
After the instance has been successfully started, all work processes connect to the database.
2
*
Microsoft Windows
*
Start process being very important is logged by the OS, SAP System and the Database. All the problems pertaining to which the SAP System could not start up is logged on them.
All messages that are created by services or the Microsoft Management Console are recorded at operating system level by an event logging service, the Event Manager. This Event Viewer writes an event log that contains the following three components:
. System Log:
. Application Log:
List of errors, warnings, and information that is generated by application software
. Security Log:
Events such as log ons and log offs and user access to files
*
*
Logs about the start process of the SAP system are stored in the file system. If there are problems during the start, these logs can provide useful information such as error messages or problem descriptions. These files are stored in the home directory (DIR_HOME) of the relevant instance.
The log files STDERR<n> are created by the SAP service during the start process. The starting processes write to the individual files, depending on the sequence in which they are listed in the start profile.
. STDERR1: Information about the start process of the database system
. STDERR2: Information about the start process of the message server
. STDERR3: Information about the start process of the dispatcher.
Granularity of the logged information to four levels using the
profile parameter rdisp/TRACE.
0: Errors only
. 2: Error messages and a short trace
. 3: Error messages and a complete trace
The higher the trace level, the larger the amount of logged information, and therefore, the larger the size of the files. You should only increase the default value for short periods for problem analysis.
*
*
A variety of causes can cause the SAP system not to start correctly. To analyze the problem, proceed as follows:
. Check the error messages and warnings in the Event Viewer. Check that the service SAP<SID>_<Instance Number> (such as SAPDEV_00) was started. To do this, go to the Services window (Start → Programs → Administrative Tools → Services).
. Check the status of the respective database system using the error log files.
For more information about this, see the lesson: Appendix - Database Logs.
. Check the start log in the MMC. To do this, select the affected instance and choose All Tasks → View Developer Traces in the context menu.
. Check the error files stderr<n> that were created by SAP Service.
. Check the trace files of the individual SAP work processes:
. dev_ms : Developer trace for the message server
. dev_rd : Developer trace for the gateway
. dev_disp : Developer trace for the dispatcher
. dev_w<m> (m is the work process number): Developer trace for the work process
*
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:
*
. Active Users:
Check which users are logged on using the User List (SM04).
. Background Processing :
Check which jobs are active using the Job Overview (SM37). If jobs are
terminated by the system stop, these jobs must be rescheduled. Jobs that are scheduled for the time when the system is stopped run automatically once the system restarts.
. Batch Input:
The transaction Batch Input: Session Overview (SM35) displays running batch input jobs.
. Update:
Use the Update Overview (SM13) to check whether update processes are terminated by the system stop. These update records are rolled back during the stop, and these are set to the status .init.. These records are then updated again during the restart.
Stopping the SAP system
*
*
The stopping of the SAP system is performed in the opposite order of starting.
. In the SAP system itself, in the Computing Center Management System
(CCMS) (transaction RZ03), by choosing Control → Stop SAP instance.
. In the Microsoft Management Console, right-click to show the context menu and choose the Stop function. Depending on whether you have selected an individual instance or the SAP system, the following are stopped:
. A single instance
. Central instance and all dialog instances
The SAP service waits for a stop message from the MMC or from the CCMS and then stops the SAP system. The service itself does not stop.
The services can be stopped and restarted with the Microsoft Windows Service Control Manager.
The database is stopped using the relevant database system tools.
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 has developed the SAP Systems Manager snap-in which allows you to monitor, start or stop the SAP system centrally from the SAP MMC.
This only exists for Windows, Unix environment has another technology .
Services concept in Windows
*
*
As long as users are logged on, services in MS Windows runs, but when user logs off all the services end. The SAP System therefore uses the concept of services to start. These programs are automatically started and administered by the operating system. Services provide support to other programs and run even if there are no users logged on to the host.
SAP Services:
. SAPOSCOL: Collects performance data for one or more SAP instances
and runs once for each host.
. SAP<sid>_<instance no.>: Controls the SAP instances and runs once for each instance.
Database Services:
. Control DB actions
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.
*
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.
*
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
*
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 has developed the SAP Systems Manager snap-in which allows you to monitor, start or stop the SAP system centrally from the SAP MMC.
This only exists for Windows, Unix environment has another technology .
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)
*
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.)
*
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.
*
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.
*
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.
*
*
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)
*
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
*
Preparation &

comprehensive-sap-basis-training-day-1.ppt

Documents

Transcript of comprehensive-sap-basis-training-day-1.ppt