Skip to main content

SAP History - Middleware News

SAP was founded in 1972 as Systemanalyse und Programmentwicklung ("System Analysis and Program Development") by five former IBM engineers in Mannheim, Baden-Württemberg (Dietmar Hopp, Hans-Werner Hector, Hasso Plattner, Klaus E. Tschira, and Claus Wellenreuther).[3]

As part of the Xerox exit strategy from the computer industry, Xerox retained IBM to migrate their business systems to IBM technology. As part of IBM's compensation for the migration, IBM acquired the SDS/SAPE software, reportedly for a contract credit of $80,000. The SAPE software was given by IBM to the founding ex-IBM employees in exchange for founding stock provided to IBM, reportedly 8%. Imperial Chemical Industries (ICI) was SAP's first ever customer in 1972.[4]

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" was founded and the following year, it moved its headquarters to Walldorf. SAP AG became the company's official name after the 2005 annual general meeting (AG is short for Aktiengesellschaft).

In August 1988, SAP GmbH transferred into SAP AG (a corporation by German law), and public trading started November 4. Shares are listed on the Frankfurt and Stuttgart stock exchanges.[3]

Four of the founding members -- Hopp, Plattner, Tschira and Hector -- form the executive board. In 1995, SAP was included in the German stock index DAX. On 22 September 2003, SAP was included in the Dow Jones STOXX 50.[5] In 1991, Prof. Dr. Henning Kagermann joined the board; Dr. Peter Zencke became a board member in 1993.[6] Claus Heinrich,[7] and Gerhard Oswald [8] have been members of the SAP Executive Board since 1996. Two years later, in 1998, the first change at the helm took place. Dietmar Hopp and Klaus Tschira moved to the supervisory board and Dietmar Hopp was appointed Chairman of the supervisory board. Henning Kagermann was appointed as Co-Chairman and CEO of SAP next to Hasso Plattner. Werner Brandt joined SAP in 2001 as a member of the SAP Executive Board and Chief Financial Officer.[9] Léo Apotheker has been a member of the SAP Executive Board and president of Global Customer Solutions & Operations since 2002, was appointed Deputy CEO in 2007, and then became co-CEO alongside Kagermann in 2008.

Henning Kagermann became the sole CEO of SAP in 2003.[10] In February 2007, his contract was extended until 2009. After continuous disputes over the responsibility of the development organization, Shai Agassi, a member of the executive board who had been named as a potential successor to Kagermann, left the organization.[11] In April 2008, along with the announcement of Leo Apotheker as co-CEO, the SAP supervisory board also appointed to the SAP Executive Board, three new members, effective 1 July 2008: Corporate Officers Erwin Gunst, Bill McDermott and Jim Hagemann Snabe.[12]. With the retirement of Henning in May 2009, Leo has taken over as the sole CEO.

Comments

adsrerrapop

Popular posts from this blog

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...