SAP Architecture

SAP Web Application Server

SAP products are built on a platform called Web Application Server (WebAS). WebAS is a very powerful and highly standardized platform. WebAS could be installed on a variety of hardware and could work with various databases. This gives IT department great flexibility in terms of SAP`s installation. WebAS supports popular programming language and protocols including Web Services, XML, HTML, ABAP, and Java.ABAP is SAP's traditional programming language. Hence WebAS is very flexible in terms of its development capabilities as well.

Three-Tiered Architecture

SAP software uses a three-tiered architecture. In a three-tiered architecture there are three nodes:

Presentation Layer or Client Business Logic or Application Server Database Server

Presentation Layer

Various devices could be used to access SAP business software. For example: desktop, mobile devices, laptops, and so run. This device would be called a presentation layer. You might have to install a piece of software on these devices so that they could talk to the application server (computer running the actual SAP software). You could also use your web browser to access SAP application. Whatever the case may be, the front end device would communicate with the application server. The device would simply display you a presentation layer while the application is actually running on the application server. The device is also called a "client".

Application Server

The actual SAP software runs on an application server. Client node simply displays the image of the screen that is actually being produced on the application server. It is important to note the application server only runs SAP software. Data is not stored in application server

Database Server

Data is stored on a separate machine called database server. Presentation layer communicates with application server to retrieve the screen image to be displayed to the user. Application server in turn communicates with the database server to write data to the database and to retrieve data from the database. The database server would be hosting a database management system like Oracle. Oracle is the most popular choice of database to be used with SAP software. Other databases could be used as well e.g. SQL Server (from Microsoft) and DB2 (form IBM).

Network

Network is an important part of a three tiered architecture. The client computer would connect to the application server through internet, or company specific intranet, local area, network, dial up line etc. Similar media is used by application server to communicate with database server. This way user can run business application virtually from anywhere.

Scalability, Flexibility, and Ease of Maintenance

Three-tiered architecture provides scalability and flexibility. If overtime, load is increased on the application server, then another application server could be added. Or simply more memory or CPU could be added to the same application server without disturbing other nodes. Similarly database server could be upgraded without touching the other nodes. Also when it is time to upgrade the business logic to a newer version, only application server absorbs the new business logic patches.

Service-Oriented Architecture

SAP is SOA enabled. SOA (pronounced as so-uh) stands for Service-Oriented Architecture. SOA architecture is based on NetWeaver technology. Being SOA enabled means that SAP software support service calls. Any program (even external to SAP) can make a service call to SAP to retrieve some useful information or to register new information. For example lets say you have developed an external website that needs to retrieve current pricing information from SAP software. Instead of retrieving information from the database (by writing SQL) your website will make a service all to SAP requesting prices on selected items. Also your website may make a service call to SAP to register a new customer. The information might arrive to your program responsible for generating website in an XML (Extensible Mark-up Language) format.XML is a popular choice of protocol for data exchange. You can then parse this data and display it to the website in any layout you like using HTML (Hypertext

Mark-up Language). Websites are built using HTML language. This is the language that your browser can decode. SOA architecture brings flexibility to the table. It makes it easy for external applications to communicate with SAP.

SAP Processes
SAP runs eight different types of processes on Application Server. How many actual processes would be run for each type is dictated by SAP instance profiles (which we will talk about next).

These SAP processed are sometimes references as DVEBMSG, where

D - dial work process V - update work processes V1 - high priority update V2 - low priority update E - enqueue B - background/batch jobs M - message service S - spooling (print) G - gateway

System Administrator can monitor these processes through SAP's front end interface.

DVEBMSG Descriptions

Process Name: Dialog Letter: D Description: Process real-time information in the foreground

Process Name: Background Letter: D Description: Background processing for long-running processes, reports, and batch jobs.

Process Name: Synchronous Update Letter: V1 Description: Processes immediate updates to the database Letter: V2 Description: Processes updates to the database on a lower priority than V1; on time-permits basis.

Process Name: Enqueue Letter: E Description: Manages database locks.

Process Name: Message Letter: M Description: Manages communication between application servers.

Process Name: Spool Letter: S Description: Manages print jobs (the print spool).

Process Name: Gateway Letter: G Description: Communicates with other SAP and non-SAP systems.

SAP Profiles

SAP Profiles are text files containing configuration information. There are three SAP Profiles:

Default Profile Start Profile Instance Profile

An SAP System may consists of more than one SAP instance for the purpose of load balancing. Default Profile contains information common to all SAP instances within an SAP system. Start profile contains the executable commands for starting SAP processes. Instance profile contains information specific to an instance. There would be one Instance profile for each SAP instance.

It would contain configuration information like:

Memory configuration Buffer sizes Number of Work Processes

SAP Hardware
Hard is an essential component of a SAP system. Hardware consists of:

Servers (middle tier and database tier computers) Disk Storage System Network Gear (routers, switches etc) Take Backup Units

All of these components work together to create a healthy system. Failure of even one component could halt the whole system, costing the company millions of dollars. All kind of systems are available in SAP hardware marketplace, from small and medium user platforms to large and highly resilient platforms.

Some large platforms are also capable of scale on the fly to meet the changing needs. When making a hardware purchase decision, solutions from different vendors should be compared. Most solutions cannot be compared as apples to apples. E.g. one solution could support the same workload as the other system but the level of scalability, availability, and reliability offered by the two systems could differ considerably. Spending little more money upfront could save the company tons of dollars on monthly maintenance and downtime costs.

Server Hardware

Server hardware comes in three main categories:

Small Medium High

A server can cost from a few thousand dollars to several million. Servers vary in performance as well. Main factors influencing server performance include:

CPUs Speed of CPUs Amount of RAM Internal server architecture Support for high-speed disk operations

Servers also vary in terms of configuration flexibility and adaptability.

SAP Hardware Solution

An SAP solution may utilize severs from any of the three categories. Typically high performance servers are used at database tier, while a middle tier could utilize inexpensive servers. Some businesses choose to utilize high performance machines at all tiers. Machines could be carved up into partitions or virtual machines. While other businesses might decide to go with low end hardware across the board relying on SAP's horizontal scalability.

Propriety Platforms

Most large hardware vendors use proprietary CPU (Central Processing Units) chips in their machines. Also most large vendors support only proprietary OS (Operating System) Examples are:

IBMs POwerPC chip running AIX operating system. HPs end-of-plife PA-RISC running HP-UX operating system. HPs Itanium2-based IA64 running HP-UX operating system.

You should also explore the ability of the machine to run other operating system as well. If you seek to retire SAP then you can simply use the same box internally after deploying less expensive operating system like Linux. For example HP's Itanium2-based IA64 also supports Linux and Windows operating systems

X64 Platforms

Late trend is investing in x64 platforms. An x64 platform is a low cost server based on Intel or AMD CPU rather than proprietary CPU. Windows based desktops and laptops that you buy from retail stores are also x64 machines. Recently x64 machines have become very powerful and now are rivalling proprietary systems in terms of high availability and visualization options. HP and Dell are big players in this market. Sun also offers bit of a choice. One time low up front cost should be a decision making criteria. Total cost through the life time of the system should be considered while making a decision.

High Availability

High availability feature is very important for an SAP system. Even if you are incurring additional charges you should consider high availability feature for SAP. High availability is an implementation of features that ensures a certain absolute degree of operational continuity. High availability features include:

Redundant power supplies Disk array controllers (RAID) (array of disks keeps system running even if one disk fails) Support for multiple network cards

Networks should be configured in a redundant fashion as well. Using dual network switches is a good example in this regards.

Disk Subsystem Hardware

Disk subsystems are enclosures for multiple disks. Disk subsystems could be used at database tier or at middle tier. Storage Area Networks (SANs) are example of most robust and high performance disk systems. Network-attached storage (NAS) is example of lesser extent disk systems. SANs and NAS devices are marketed under three categories: low-tier, mid-tier, and high-end.

Storage for SAP

Storage used with SAP system should support redundant connectivity between the storage device and the servers connected to it. This will avoid the single point of failure

RAID

RAID (Redundant Array of Inexpensive Disks) should be configured as well. RAID is a technology that allowed computer users to achieve high levels of storage reliability from low-cost and less reliable PC-class disk-drive components. This is achieved by arranging the devices into arrays for redundancy. RAID comes in following levels:

Level 0 Level 1 Level 5 Level 10

Different levels provide various combinations of availability, cost, and performance. RAID 0 is the cheapest and RAID 10 is the most expensive option.

SAP Operating Systems

Operating system is a software that lets applications and other software to communicate with computer hardware. Consider operating system as a layer on top of hardware. All other software runs on top of the operating system. Operating system provides basic services to applications. ,br> Example includes file sharing, support for network connections etc. Examples of operating systems on which SAP software could run include:

Microsoft Windows Server, Red Hat Linux, Suse Linux, HP-UX Unix, AIX, Solaris, OS400, z/OS. Solaris is a UNIX version for Sun machines.HP-UX UNIX is a UNIX for HP machines OS400 is an operating system that runs on IBMs AS/400 machines. Z/OS is an operating system that runs on mainframe machines. Microsoft Windows Server, Red Hat Linux, and Suse Linux could be installed on x64 (Intel/AMD CPU) machines.

Operating System for SAP

Following factors should be considered when deciding which Operating System to use with SAP.

Current skill set of IT staff, cost of retraining, and cost of hiring new staff Support from operating system vendors Confidence on the Operating System and the vendor Verifiable client references Relationship of operating system vendor with SAP

64-bit OS

Starting 2007, SAP software is only supported on 64-bit operating systems. 64-bit hardware is more prevalent. The demand for 32-bit hardware and therefore 32-bit operating system is reducing with time. For SAP systems, only 64-bit hardware should be considered unless you have good reasons to support older versions of SAP or some other related software that only runs on 32-bit environment.

Selecting OS

When making a decision on which Operating System to use with your SAP system, you should keep in mind following features:

Memory Management Crash Recovery Patch Management Security

Clustering Capabilities Support for third party management utilities Presence of built-in management utilities

It may or may not be compatible with your IT department's vision to invest in new toolsets. In that case you also have to make sure that your existing monitoring applications, virus scanning software and backup solutions would work with this operating system.

SAP OS Directory Structure

On UNIX and Linux OS, SAP is installed on the directory: /usr/sap On Windows SAP resides in: x:\usr\sap Where x is a drive letter.

On windows the folder x:\usr\sap is shared as SAPMNT. You can access this folder from other machine as \\machinename\sapmnt where machine name is the name or IP address of the machine hosting SAP. If you have multiple SAP instances on Windows machine then all instances must be installed under the same directory SAPMNT. On all OS, UNIX, Linux, and Windows the next directory level is SID. SID stands for SAP system identifier.

SAP Instance
SAP instance resides on an Application Server under the directory: Windows: x:\usr\sap\sapsid Unix/Linux: /usr/sap/sapsid The SAP instance on an Application Server communicates with a database associated with this instance. SAP instance on an Application Server together with its associated database is called an "SAP System". The term "SAP System" is also known as "SAP Installation". When you talk about an SAP System or an SAP Installation, you are talking about an SAPSID folder on an Application Server and the database associated with this folder.

Multiple SAP Instances

One Application Server (or host) could contain multiple SAP instances. In other words there would be multiple SAPSID folders under the directory /usr/sap (x:\user\sap on Window). Where SAPSID is the actual name of the SAP identifier; for example: PROD, TEST etc. Each SAPSID folder would point to its own database. SAP System refers to the pair of SAP instance and its database. The folder /usr/sap could contain more than one SAP instance. It is important to know the difference between SAP System (pairing) and SAP instance (folder).

Load Balancing

When number of users increases, load balancing is implemented. The SAPSID folder is simply cloned to more than one Application Servers. Load is shared by making users connect to different Application Servers. Load balancing software controls which user would connect to would Application Server. SAPSID folders on all Application Servers would be talking to the same database. All sibling SAPSID folders together with their database would be called one SAP System. When load balancing is implemented, SAP System would consist of multiple SAPSID folders on difference Application Server machines and a database. An Application Server may host more than one SAP instance under the directory /usr/sap

SAP Database
SAP supports most databases. However you may be restricted to only a few based on the platform (hardware/OS) you have selected. When selecting a platform you should keep in mind the choice of databases you would be restricted to. Not all platforms supports all databases. SAP supports most databases including:

Microsoft SQL Server IBM DB2 Oracle MaxDB

MAX DB

MaxDB is SAP's own database. It is growing in popularity. It is more common on Linux platform. It is a low-cost alternative to other popular databases.

Log Shipping

Most databases support log shipping feature including Oracle and Microsoft SQL Server. Log shipping is a concept where changes to the database are transferred in regular intervals to another standby database. When production system goes down for any reason, the standby system is ready to be activated as production. This would result in almost zero downtime.

Database Overview

You can imagine database as a filing system that contains useful information. Information is stored in tables within a database. A database could contain many tables

Tables

Table has rows and columns. You can imagine table as a spreadsheet with rows and columns. At the intersection of rows and columns, there are cells. Cells contain values. A table stores information about entities e.g. Employee, Department etc. Something of importance is referred to as entities. The columns of the table represent attributes of the entity. For example Name, Salary, Department Number etc are attributes of an Employee. Each record (or row) of the table represents an instance on the entity. For example Scott and Larry. No two rows could be the same. That is why there are ID columns in tables. ID columns contain incremental values like 1, 2, 3 etc. This creates uniqueness for each row. Each value represent distinct instance of the entity.

Tables Relationships

Tables are tied together through relationships Entities could have one to one, one to many, or many to many relationships with each other. This relationship is represented in tables. Lets take a case of EMPLOYEE and DEPARTMENT tables. In a DEPARTMENT table we would store department IDs and Names.

TABLE: DEPARTMENT

ID NAME 10 Sales 20 Finance

In a EMPLOYEE table we would store employee IDs, Names, and the Department ID in which they work.

TABLE: EMPLOYEE

ID NAME DEPTID 10 Scott 10 20 Larry 10 30 Peter 20

The DEPTID column of EMPLOYEE table is tied to the ID column of the DEPARTMENT table creating one to many relationship (through a foreign key) Each department could be assigned to various employees. After establishing this relationship the database would not let you insert a value in DEPTID column of EMPLOYEE table that does not exist in ID column of DEPARTMENT table. E.g. you cannot insert 30 in DEPTID because it does not exist in DEPARTMENT table. The tables are tied to each other through relationships. This is where the name "relational database" comes from.

SAP Components and Databases

SAP software has various components (or products). For example: SAP ERP, SAP CRM etc Each component generally has its own database. If a company is using both components SAP ERP and SAP CRM, then SAP ERP would have its own database and SAP CRM would have its own database as well.

Programs and Data

You can think of SAP as a combination of two things:

Programs

Data

Programs contain application logic. Programs read data from the database and also write data to the database. The database is there to make the data retrieval and data modification easy for the programs. Programs are separate from the database. Programs contain application logic e.g. how to create checks, how validate invoices. Database contain actual data (in tables) that would be retrieved and modified by the programs

SAP Tables

SAP database contains thousands of tables. For example SAP ERP database contains more than 30,000 tables. Some lighter products like SAP NetWeaver Process Integration (PI) contains less than 10,000 tables. In SAP about 10% of the tables contain 90% of the data.

That means few tables grow in size while other remains relatively constant. The tables that grow in size are most transactional tables. Transactional tables contain transactions like Invoices, Journal etc.

The table that remain unchanged are mostly master tables. Master tables contain master data like list of currencies, list of states within USA etc. Master data does not change as often as transactional data.

Indexes

Tables store data.

Indexes are used to speed up retrieval of data. Imagine a table containing 1 million records. Lets say a program has requested the database to fetch records for all employees whose name is SCOTT. The database would have to start reading the table from row 1 to the last row until it finds all the records where name is SCOTT. This is called a full table scan. Full table scan slows down the performance as it is time consuming. Indexes are created to avoid the full table scan. In this example you would create an index on column NAME of EMPLOYEE table.

Imagine index as a table that only contains one or two columns. The actual EMP table could have more than 10 columns. The index on NAME column could be imagined as a table with one column NAME.

Now if you ask the database to retrieve all rows where NAME is SCOTT, first the database would visit this index. Index could be scans in a matter of seconds since it is a small object as oppose to the table.

Index has pointers pointing to the actual rows of the table.

First the database finds all desired values within the index.

Pointers could be used to retrieve other attributes of the entity residing in the actual table e.g. SALARY etc.

SAP Indexes SAP relies heavily on indexes to improve the performance. 50% of the SAP database size comprise of indexes.

SAP Sizing
Before SAP software is installed SAP environment must be planned.

The process of planning the environment is called "sizing".

Following decisions must be made:

How many installations would be there in the landscape (see next article). How many application servers (middle tier) will be deployed to share the load. What SAP components will be deployed. How the components will be they deployed. What would be the size of the database and hence the disk capacity of the database server. How scalable the system needs to be (How fast the company will grow). What would be the disaster recovery plan. What should be the availability of the system. (Time when system is not down). What kind of performance is acceptable especially when workload is high (month-end processes).

The above questions are answered by IT department working closely with SAP's implementation consultants (integrator) and the hardware partners.

The design process should start early.

Business should be engaged as quickly as possible to gather requirements.

Then SAP integrator and hardware partners should translate these requirements into sizing recommendations.

SAP Instances

An SAP environment consists of multiple SAP instances or installations.

Most common approach is to have three installations (also refer to as three-system landscape):

Development System - Used by developers to develop or modify the software. Quality assurance or Test System - Used by testers to test the new development. Production System - Used by users to run the business.

When developers modify the applications or functional consultant modifies any setup, changes are first promoted to the Test System where testers test the changes. Once approved changes are moved over to the Production System.

Some companies keep a separate installation as "sandbox".

Sandbox could be used for technical training. New things could be tried safely in this environment.

Some companies also keep dedicates systems for testing new releases. Such systems are called "Stage" systems. Other companies would simply test the new releases on their Test Systems.

From a technical roadmap perspective it is important to decide how many SAP installations would be there in your landscape. This has to be figured out before starting the actual installation. This decision is part of the "sizing". Each installation would have its own application tier and a database tier. Hence each installation would be using at least two machines.

Technology Stack: ABAP and Java

SAP components are either built on ABAP technology stack or on Java technology stack.

ABAP stands for Advanced Business Application Programming. It is a high level programming language created by SAP. Before sizing the SAP installation it is import to determine which technical stack would be deployed. The SAP NetWeaver platform supports both technology stacks: ABAP and Java. Either one is support as well as both are supported in conjunction. SAP components that are being implemented dictates which technology stack company will end up using.

For example Employee Self-Service component requires Java whereas ERP 6.0 component requires ABAP.

The SAP Master Guides help you find out which underlying technology stack (ABAP or Java) is behind which module

SAP Opportunities
SAP Roles

Both technical and functional jobs are created when a company plans to SAP implementation or when a company maintains already implemented system. Following roles come into play in a new SAP implementation and in an environment where SAP is already implemented:

Super Users Functional and Technical Analysts System Administrator Programmers Project Managers

Super Users

In any SAP environment, a gap has to be bridged between business requirements and business processes. When a company undergo SAP implementation, it needs personnel who can champion business solution for their team. These are called super users. Super users have little bit of IT knowledge as well. They have the ability to bring along those as well who are challenged by new technology. Super users are the first one to get training on SAP software. They work closely with SAP functional consultants. This makes easy for super users to gain SAP knowledge.

Functional and Technical Analysts

Analysts could be divided into two types: functional and technical. Analysts are also referred to as consultants. Functional analysts are also called configuration leads, business analysts; business process owners. Technical analysts are also called functional developers or configuration experts. Both functional and technical analysts role are aligned with a particular SAP module or group of modules. Analysts work with client's business-side counterparts or super users, to implement SAP. More modules a company will implement, more analysts will be required. Job of a functional analyst is to gain business requirements, by working closely with super users. The functional analyst would then work with technical analyst of that module, to have SAP configured according to the business requirements captured. Analysts roles are vital for an SAP implementation. These roles require a person to have excellent coordination expertise.

System Administrator

System Administrator is an expert on Basis module of SAP. This person often takes team lead role or architect role. The person is expected to design overall technical strategy.SAP security also comes under Basis. Person responsible for implementing security works closely with functional team to make sure security is implemented as per business requirements.

Programmers

SAP programmers are specialized in programming language called ABAP. ABAP stands for: Advanced Business Application Programming. Most of the SAP software is written in ABAP language. ABAP is a C like language. Programmers are also called developers and ABAPers (pronounced as ah-bop-ers). Besides ABAP, programmers are also expected to know Java, .NET, SAP Business Intelligence, SAP Process Integration, and SAP Enterprise Portal etc. Programmers mainly come into the picture when customization is needed. Customization simply means modifying the code such that the functionality of the application fits the business requirement. Software code is only modified if team is unable to achieve the desired results using functional configuration. Programmers are also required when interfaces need to be written. Interfaces connect SAP with external software. For example if a company is using SAP Financials and Oracle Manufacturing then programmers will write interface so that both business software could communicate with each other.

Project Management

Project Manager is responsible for managing SAP implementation project or an upgrade project. There is a high demand for project managers specialized in SAP. Demand for project managers is increasing as number of SAP implementations and upgrades are increasing. Upgrades are something that will keep on happening, as new product releases will keep on occurring. Companies have to keep pace with the new releases in order to keep their SAP support valid. SAP AG would not support software if it is too old. Many consulting companies have established Project Management Offices (PMOs) in order to coordinate groups of project managers. You can consider breaking into SAP arena as a project manager. PMP (Project Management Professional) certification from PMI (Project Management Institute) would come handy if you wish to go this route.

1) What is the difference between 32-bit and 64-bit versions of Windows?

The terms 32-bit and 64-bit refer to the way a computer's processor (also called a CPU), handles information. The 64-bit version of Windows handles large amounts of random access memory (RAM) more effectively than a 32-bit system. To use a 64-bit version of Windows, you must have a computer that has a 64-bit processor. Also, you must have 64-bit device drivers for the devices that are in the computer You may want to determine whether the platform of Windows is installed. To verify that you have the platform of Windows, follow these steps:

1.Click Start, right-click Computer, and then click Properties. 2.The operating system appears as follows: oFor a 64-bit version operating system, "64-bit Operating System" appears for the system type under System. oFor a 32-bit version operating system, "32-bit Operating System" appears for the system type under System.

Note: Microsoft Win32 uses the x86 processor in 32-bit flat mode. Therefore, a x86-based version means a 32-bit version operating system. The main differences between the 32-bit versions of Windows and the 64-bit versions of Windows relate to memory accessibility, memory management, and enhanced security features. The security features that are available in the 64-bit versions of Windows include the following:

Kernel Patch Protection Support for hardware-backed Data Execution Protection (DEP) Mandatory driver signing

Removal of support for 32-bit drivers

Removal of the 16-bit subsystem

One of the greatest advantages of using a 64-bit version of Windows is the ability to access physical memory (RAM) that is above the 4-gigabyte (GB) range. This physical memory is not addressable by 32-bit versions of Windows.

2) What is Virtualization?

Virtualization is a proven software technology that is rapidly transforming the IT landscape and fundamentally changing the way that people compute. Todays powerful x86 computer hardware was designed to run a single operating system and a single application. This leaves most machines vastly underutilized. Virtualization lets you run multiple virtual machines on a single physical machine, sharing the resources of that single computer across multiple environments. Different virtual machines can run different operating systems and multiple applications on the same physical computer. While others are leaping aboard the virtualization bandwagon now, VMware is the market leader in virtualization

Hardware virtualization technology or VT is built-in natively by CPU processors. In Intel chip, the VT is called Intel VT, while AMD calls it AMD-V. The VT capability in the processor on the computer is built onto the tiny piece of chip, and cannot be added or removed using any manual process. And even if the CPU features VT, it must be enabled in BIOS.

Most newer CPU includes VT operation by default. However, some older or even current processors available for purchase for DIY or operating on OEM computer may not support VT. When there is no VT support, Windows Virtual PC may fail to install or cannot be powered up and started virtual machine

3) How do I know if I can run a 64-bit Virtual Machine on my Computer?

Most users who buy computer are just paying notice to the speed (how fast) and size of RAM memory (how big) of the PC. In fact, most modern CPU microprocessors have great lots of features and capabilities other than constantly higher clock rate. With the evolving of software development, some of these features are now required. With SecurAble, user can easily check and determine if the system is x86 or x64 architecture, support hardware DEP and/or hardware virtualization. SecurAble probes the systems processor, determine the presence, absence and operational status and displays the status of the three most significant security-related processor features:

64-bit instruction extensions Hardware support for detecting and preventing the execution of code in program data areas Hardware support for system resource virtualization

SAP Installation:

1)We do not sell any SAP IDES software's and people who are selling this in the market are doing illegally which is against the law and in breach of copyrights of SAP AG Germany. We respect the law and protect the rights of the original vendor, we also endeavour to stop people being deceived by unscrupulous websites. 2) The SAP Community Network provides an SAP Software Download Catalog for all downloads, including SAP NetWeaver trial software, tools based on SAP products, widgets, samples and many more. All downloads are available for free. http://www.sdn.sap.com/irj/scn/downloads Note: Integra Services do not own any responsibility of your use or otherwise of the information provided in the above web link, it is only provided for easy browsing of the desired information. 3) The remit of our services is strictly limited to the possibility of providing technical assistance for people who want to learn SAP and also professionals who may need help in troubleshooting during SAP Installation.