Showing posts with label middleware layer. Show all posts
Showing posts with label middleware layer. Show all posts
ABAP Development Workbench

ABAP Development Workbench

11:37 AM 0
ABAP/4 was SAP’s own fourth-generation programming language, and that was the name up to release 3.1. When release 4.0 was introduced, the name lost the 4 suffix and the language started to be known simply as ABAP. It is exactly the same language with several new technical improvements, mainly in the field of adding all the features that make a programming language object oriented. The name is taken from Advanced Business Application Programming Language and is the programming language used by SAP for the development of all standard business applications included within the R/3 suite.

On top of ABAP, SAP has designed a full-purpose development environment, known as the ABAP development workbench, which is integrated within the R/3 system and is available for customers to develop their own solutions and enhance or extend the capabilities of the existing applications.

The ABAP development workbench includes all tools necessary develop and design programs, screens, menus, and so forth. It also contains performance and debugging facilities. Central to the workbench is the ABAP object repository and the data dictionary.

The object repository stores all the development objects of the workbench: programs, dictionary data, dynpros (dynamic programs), and documentation. The repository is the key to managing and testing ongoing development.

The data dictionary contains the descriptions of the data structures used within programs. This is the metadata repository that includes table definitions, allowed values, and relationships between tables. Administartors should be very familiar with this SAP component since it is widely and extensively used. The ABAP data dictionary is covered in detail in next post.

As of version 3.0, the development workbench included the workbench organizer, the evolution of the correction system of previous releases. The organizer handles the transition of new developments and customizations into productive systems. Some of the available features are version management, programs modification control, and team project developments. The transport system handles the movement of development work from one system to another. For instance, migrations to new SAP releases are, in reality, massive objects transported from the systems at SAP to customers’ systems. This is a very important tool in the SAP System and is explained in next post.

Application Integration

The data from the different SAP functional applications are shared and integrated, building what is often known as an internal information highway. This integration can be seen as an implicit applications work flow.

One of the main benefits of the set of SAP applications is their capacity for creating a perfect integration between the different business processes of companies. It is that integration between applications is available to all areas of a company.

An accompanying feature that makes application integration stand out is the capacity of doing it in real time. This means that information is constantly updated, so when a manager request a report about the status of the financial statements. This avoids the difficulty of running end-of-period reports and programs from a traditional legacy system, which has to search and incorporate needed data from other applications before the run.


From the point of view of the business processes, the integration of the SAP R/3 application modules is represented using the tools available within the SAP R/3 Business Engineer. At the level of data models, tis integration can be accessed using the available functions included in the Data modeler.

Related Post :

SAP System Multi Tier Client/server Solutions

11:21 AM 0
In general, client/server is a style of computing that distributes the workload of a computer application across several cooperating computer programs. This type of computing separates user-oriented,application, and data management tasks. Client/server is mainly a software concept that includes a set of service providers and service requesters. In client/server computing, individual software components act as service providers, service requesters, or both. These software services communicate witheach other via predefined interfaces.

Major advantages of the client/server approach are as follows:

·         Flexible configuration. With the deployment of standard communication interfaces, there are many possibilities for distributing and planning a client/server installation: from a centralized configuration to a highly distributed system.
·         Workload distribution. Since application servers work in parallel and communicate with the database, user can be evenly distributed based on their jobs tasks. Also, there is the possibility of deploying dedicated application servers to specific business areas.
·         High scalability. Client/server permits users to adapt the capacity of their hardware according to the performance needs of their businesses, such as adding additional application servers when there is an increase in number of users, when additional modules start production, and when the database becomes larger. This enables companies to protect software and hardware investments.

One of the widely used client/server configuratins with the R/3 system is the three-tiered architecture (see the picture below), which separates a system’s computers into three function groups: presentation, application, and database. Since client/server is a software concept, it must be clear that an service requester of the database services.

SAP-R3-three-tiered-client-server-architecture
SAP R3 three tiered client-server architecture



With the three-tiered architecture, each group is set up to support the demands of its functions. The central server contains the database, widely known as the database server. Application servers include the processing logic of the system, including services such as spooling, dispatching user requests, and formatting data. The tasks related to presentation of the data are handled by the presentation servers, which typically are personal computers or workstations, enabling easy access to the system.

Communication among the three tiers or server types is accomplished with the use of standard protocol services, such as the ones provided by TCP/IP or CPIC.

CPIC stands for Common Programming Interface Communication and includes standard functions and services for program-to-program communication with the ABAP programming language.

The section entitled “R/3 Basis Software” in the next post i will shows in greater detail the services, processes, and components of the client/server architecture of SAP R/3.


Definition of SAP System

12:07 PM 0
From previous sections, it became clear what the use of this software system is and who decides to implement it : SAP R/3 controls business processes and manages esential company information. Enterprises needing those services implement this standard software.

To manage the complex business needs of companies, the R3 product family offers leading technology solution:

·         Multitier client/server architecture.
·         Based on middleware for supporting open systems technology.
·         Business Framework architecture, open to total integration with other components and applications, including the internet world. This is achived by the use of standard Business Application program interfaces (BAPIs).
·         Homogeneous user interface among applications.
·         Comprehensive development environment.
·         Total application integration.
·         Solution Sets for configuring the system.
·         Wide range of services including hotline support, training, consulting, quality checks, and so on.
·         Complete support for solving all the problems arising from the millenium change (Y2K) and the appearance of the new European currency, the euro.
sap-system-component
SAP System Component

The picture above shows the R3 components from a functional point of view. The overall SAP R3 system is represented by everything included inside the ellipse.

The lower layer is made of the operating system, physical database (whose software is included in the SAP kit), and the network. The middleware layer, which is above it, interfaces with the lower one and integrates the SAP R/3 applications on top of it. This middle layer is known as the basis system, as the basis system, and includes components such as the ABAP development workbench, the system administration tools, batch job handling, authorization and security management, and all cross-application modules.

ABAP/4 is a fourth-generation programing language that was used to develop all R/3 application modules. When releases 4.0 and 4.5 were introduced, and SAP’s strategy began to focus on object orientation, it was decided to rename the programming language to simply ABAP, abandoning the 4 in reference to fourth generation.

Middleware are the layered software components that facilitate the development of client/server applications that can be deployed in heterogeneous vendor platforms. The basis system, also known as the kernel, is the SAP R/3 middleware.

The upper layer, the functional layer, contains the different business applications: financial, human resources, sales and distribution, materials management, and so on. The integration of all applications relies on the basis system.


SAP defines client/server also from a business solution point of view: a technology concept that leverages computing power to link core business processes with software, trying together various functions, such as financials, human resources, sales and distribution, logistics, and manufacturing.

Related Post:

TopMenu

Powered by Blogger.

Awesome Video