7/05/2020

What's the difference between SAP HANA, S/4HANA and HANA Cloud Platform

What's the difference between SAP HANA, S/4HANA and HANA Cloud Platform

When SAP announced its next generation enterprise resource planning (ERP) solution S/4HANA in 2015 it was hailed by CEO Bill McDermott as its "biggest launch in 23 years, if not in the entire history of the company".
Two years on the technology is starting to see the sort of adoption the German software maker expected to see, but customer confusion over what S/4HANA and its underlying in-memory HANA data store were meant the road to widespread adoption has been a winding one.


Simply put, HANA is a new type of database, S/4HANA is a suite of enterprise resource planning (ERP) software run on top of that in-memory database. Then, either or both of these solutions can be run on SAP's managed private cloud platform, in the public cloud with AWS, Azure or Google Cloud, or a customer's own on-premise data centre.
It is important to note that SAP's HANA data store -- which was first release in 2010 -- is a fundamentally different architecture to your classic relational database. It runs in-memory, meaning data is stored in columns instead of rows, allowing for faster, near to real-time analytics and compute capabilities.
SAP has had trouble in the past getting across what HANA is, and why customers should shift their precious enterprise data to this new data store.
Speaking to Computerworld UK back in 2015, during the SAP Insider tour in Nice, SAP's cross platform product marketing vice president Matthias Haendly admitted that "there is confusion over HANA, and we can always do more to explain what exactly each one can do for you."



Then at the UK and Ireland SAP User Group conference in 2016 the then chairman Philip Adams admitted that 12 percent of the user group had never heard of S/4HANA. “That confused me and I am sure that has created a certain amount of head scratching amongst SAP marketing teams," he said at the time.
Now, according to SAP's July 2017 Q2 results, adoption of S4/HANA was up 70 percent year-on-year for customer numbers, standing at more than 6,000 and including big names like Google and energy giant Centrica.

SAP Cloud Platform

SAP customers can deploy HANA and S/4HANA in their own data centre, but SAP has been clear about the fact that they would rather customers run it on the SAP Cloud Platform.
Co-founder and chairman of the SAP advisory board Dr Hasso Plattner has admitted that “in the cloud is our version to aim for” when it comes to getting customers onto S/4HANA.
SAP has slowly come around to the idea that cloud deployments of HANA and S/4HANA are the future.


Franck Cohen, SAP president for Europe, Middle East and Africa told Computerworld UK: “I am a firm believer that the future is public cloud. It is not public cloud for some companies, it is public cloud for everybody, and it is a matter of time.”
“I have no doubt that the cloud will surpass the on-prem revenue very soon. If you look at the growth rate and the curve for the cloud revenue vs the on-prem you can already predict when it is going to happen, it is very simple. It is clear for me that the cloud will surpass the on-prem in the next few years.”
Volume 0%

What's SAP?

What's SAP? And why is it worth $163B?
Every year companies spend $41B on enterprise resource planning software, commonly known as ERP. Today, almost every large business has some sort of ERP system implemented. But most smaller businesses generally don’t purchase any ERP system off the shelf, and most engineers probably haven’t seen them in the wild. So for those of us who haven’t used an ERP system ourselves… what’s the big deal? How does a company like SAP sell $25B worth of ERP software every year? And how does 77% of the world’s transaction revenue, and 78% of the world’s food all flow through SAP?
ERP is where companies store their core operational data. We’re talking about sales projections, purchase orders, and inventory, as well as the processes that act upon that data (e.g. paying out vendors when a purchase order is issued). In a sense, ERP is the “brain” of a company — it stores all important pieces of data and all of the actions possible in data-driven workflows.
But before taking over the modern business world, how did ERP software get started? The story of ERP begins with major automation efforts of the 1960s: while the 1940s and 50s were focused on mechanical automation of blue collar work — think General Motors establishing their automation department in 1947 — the automation of white collar work (often via the computer!) began in the 1960s.

Midcentury automation: Computers enter industry

Payroll and billing were among the first business processes that computers automated. Employers needed armies of white-collar labor to manually tally employee hours in ledgers, manually multiple hours with hourly rates, and manually subtract taxes and benefit deductions… all just to run a single month of payroll! This time-consuming, repetitive process was error-prone for humans, and was a natural fit for computerized automation.
By the 1960s, many companies used IBM computers to automate payroll and billing tasks. Data processing – an outdated term whose lasting legacy is
Automatic Data Processing, Inc’s name – is what we’d call IT today. Software engineering wasn’t yet a discipline, so these departments often took employees from analytical backgrounds taught them to program on the job. Purdue had just formed the first Computer Science department in the U.S. in 1962, and the first CS grads started appearing a few years later.

Programming for automation/data processing was challenging in the 1960s because of memory constraints. There were no high level languages, no standardized operating systems, and no personal computers – only big expensive mainframes with little memory running programs on reels of data tape! Programmers often developed at night in order to maximize compile time. It was common for companies like GM to write their own operating systems to get the most out of their mainframes.
While today we run application software on top of a few common operating systems, this wasn’t the case until the 1990s. During the middle ages of computing on mainframe machines, 90% of all software sold was custom-built; only 10% was purchased off the shelf.
This landscape deeply influenced how companies developed their technology. Some imagined that the future of software would involve industry-standardized hardware, OS, and programming languages, like the SABRE system for the airline industry (that’s still used today!). Most companies stuck to building their own completely isolated software, often reinventing the wheel.

The birth of standard software: SAP’s extensible development

In 1972, five engineers left their jobs at IBM to pursue a software contract with a large chemical firm called ICI. Their new company, SAP (Systemanalyse und Programmentwicklung, or System Analysis and Program Development in English), like most software companies at the time, was essentially a software consultancy. SAP would embed themselves in their customers’ offices and develop on their customers’ computers, writing mostly logistics management software.

Business went well: SAP ended their first year with DM620,000 in revenue, a little over $1M in today’s dollars. Soon, they started selling their software to additional customers, porting it to different operating systems when necessary. Over the next four years, they acquired over 40 customers, 6x-ed their revenue, and grew from 9 to 25 employees. This might be a far cry from today’s coveted T2D3 growth curve, but SAP’s future was bright.
SAP’s software was special for a few reasons. At the time, most software ran overnight and produced output on paper data tapes, which you’d check the next morning. Instead, SAP designed their software to produce output in real-time for customers, and ran it on computer monitors (which cost around $30K at the time).
But most importantly, SAP’s software was designed to be extensible from the start. For SAP’s original contract with ICI, SAP didn’t build software from scratch, as was the norm at the time, and instead built on top of a previous project. When SAP released their financial accounting software in 1974, their intention was to build additional software modules on top of it and sell them in the future. This extensibility was SAP’s defining feature. The interoperability across client contexts was considered radical at the time because other approaches started from scratch for every client.

The importance of integration

When SAP introduced their second software module for manufacturing to go with their first finance module, the two modules were able to seamlessly interact with each other since they shared the same database. This integration made the combination of the two modules significantly more valuable than the individual pieces of software.
As software automated particular business processes, its impact was highly dependent on access to data. Purchase order data sits in the sales software, inventory data sits in the warehousing software, etc. And because these systems don’t interact, they needed to be synced regularly, and that often meant having a human manually move data around.
Integrated software solves this by facilitating communication across company systems and enabling new kinds of automation. This kind of integration – between various business processes, as well as data sources – is a key feature of ERP systems. This became especially important as hardware spoke more to software, opening new automation opportunities; and ERP shined.
The speed at which data can be accessed with integrated software empowered companies to completely rehaul their business models. For Compaq, ERP allowed them to shift their distribution strategy to a made-to-order model (i.e. building a computer only once the order is explicitly placed). This model saves money by eliminating inventory cost, but relies on a speedy turn-around time — precisely what a good ERP implementation helps with. When IBM underwent a similar effort, it reduced replacement part shipping time from 22 days to only 3 days!

What ERP software actually looks like

The words “enterprise software” don’t provoke images of slick, user-friendly UIs, and SAP’s ERP software is no exception. A basic installation of SAP has 20,000 database tables, 3,000 of which are configuration tables. In those tables, there are ~8,000 configuration decisions you need before even getting started. And that’s why SAP Configuration Specialist is an actual job title!
Despite being difficult to set up, SAP’s ERP software delivers on its key value of broad integration across multiple business processes. That integration leads to thousands of use cases in an organization. SAP organizes these use cases into Transactions, which represent business actions. Some example transactions include “create an order” and “display a customer.” These transactions are organized in a nested directory format. So to find the Create a Sales Order transaction you’d navigate to Logistics and then Sales, and then Order, where you’d find the actual transaction.

Calling ERP a “transaction browser” would be surprisingly accurate. It very much looks like one, complete with a back button, zoom controls, and a text box for “TCodes”, the equivalent for URLs in a web browser. SAP has over 16,000 different types of transactions, so navigating through the tree of transactions can be daunting without these codes.
Despite the dizzying number of available configs and transactions, companies still have unique use cases and need highly customized actions. To handle such unique workflows, SAP also has a built-in programming environment. Here’s how it each part works:

Data

Developers can create their own database tables using the SAP interface. These are relational tables, with the feature you come to expect from a SQL database: columns of various types, foreign keys, value constraints, as well as read/write permissions.

Logic

SAP developed a language called ABAP (footnote: Advanced Business Application Programming, originally Allgemeiner Berichts-Aufbereitungs-Prozessor, German for "general report creation processor") that lets developers execute custom business logic in response to certain events or on a timed schedule. ABAP is a verbose language, with about 3x the number of keywords compared to JavaScript (here’s a 2048 implementation in ABAP). Once you’ve written your program (SAP provides an editor), you ship it as own transaction, complete with its own TCode. You can also customize existing behavior through an extensive system of hooks called “business add-ins”, where you can configure your program to run when a certain transaction executes – similar to SQL triggers.

UI

SAP also comes with a drag-and-drop form builder for creating UIs. It comes with handy features like generated forms based off your database table, but it’s fairly difficult to use. My favorite part of the form builder is drawing out the table columns:

Challenges with Implementing ERP

ERP isn’t cheap. A large multinational company may spend $100 million to $500 million in total on implementation: $30 million in software license fees, $200 million in consulting fees, millions for hardware, and millions more to train managers and employees. A full implementation takes four to six years. A CEO of a large chemical firm was quoted as saying, "competitive advantage in this industry might just come from doing the best and cheapest job at implementing SAP.”
And it’s not just about money — implementing ERP is a risky undertaking, and the results vary wildly. A best case scenario looks like Cisco’s ERP implementation, which took them 9 months and $15 million. In comparison, Dow Chemical’s implementation, for example, took $1 billion and 8 years; the U.S. navy spent $1 billion on four different ERP projects that all failed. A whopping 65% of executives believe ERP implementations have a moderate chance of hurting their businesses (which isn’t something you’d typically hear when evaluating software!).
The integrated nature of ERP makes adopting it a company wide effort. And because companies only extract the value once ERP is adopted everywhere, it’s particularly risky! Implementing ERP isn’t just a purchasing decision: it’s committing to redoing how you handle operations. Installing the software is the easy part; adjusting the whole company’s workflow is the most of the work.
A company implementing an ERP system oftentimes hires a consulting firm like Accenture and pays them millions of dollars to work with individual business units and figure out how to integrate ERP into their processes. And once the integration is underway, the company has to start training all the employees on how to use the system. Gartner recommendsreserving 17% of the budget just for training!
Despite all the hassle, most Fortune 500 companies had ERP systems implemented by 1998, a process that was accelerated by the approach of Y2K. ERP has continued to grow and is a >$40B market today, one of the biggest segments in the software industry.

The modern ERP software industry

The largest players in ERP today are Oracle and SAP. While both are market leaders, their ERP products are surprisingly different. SAP’s product has been largely built in-house, while Oracle has aggressively acquired their way to the front of the pack, buying out competitors like PeopleSoft and NetSuite.
Oracle and SAP are so dominant that even Microsoft uses SAP instead of their own ERP offering, Microsoft Dynamics.
Because most industries have fairly specific ERP needs, Oracle and SAP have pre-built configurations for many industries, such as food, automotive, and chemical, as well as vertical-built configurations, such as sales organization specific processes. Nonetheless, there’s always space for niche players, which are generally vertical-focused:
  • Ellucian Banner is specifically for higher education
  • Infor has partnered with McKesson to build specifically for healthcare
  • QAD is specifically for manufacturing and supply chain
Vertical specific ERPs can specialize through integrations and workflows that are specific to their target market: healthcare ERPs, for example, can implement HIPAA protocols.
Specialization isn’t the only differentiator, though: a few startups are bringing more modern software platform practices to the ERP “table.” An example is Zuora, a platform specifically focused on enabling companies to integrate (with ERPs!) and manage their subscription businesses. Others like Anaplan and Zoho are doing the same.

ERP on the rise?

It’s 2019, and SAP is a giant: they had $25B in top line revenue last year, and have a market cap of almost $150B. But the software world isn’t what it used to be. When SAP first came out, data was siloed and difficult to integrate; storing it all in SAP was the obvious answer.
That’s now rapidly changing; on the back-end, most modern enterprise software (e.g. Salesforce, Jira, etc.) now have good APIs for exporting data. ETL + data lakes are on the rise: Presto, for example, facilitates cross-database joins that weren’t possible just a few years ago.

by https://retool.com/blog/erp-for-engineers/

6/04/2020

Agent Data in the SAP Solution Manager LMDB

Agent Data in the SAP Solution Manager LMDB

Many applications of SAP Solution Manager workcenters use data from managed application systems and the hosts where they are installed on. Such information is about details of the application system landscape, configuration settings as well as logs or performance metrics.
Figures 1a, 1b, and 1c show a Technical System in the LMDB, where agent data has been added to the information sent via SLD Data Suppliers:
Technical System in the LMDB with host data
Figure 1a: A Technical System in the LMDB – selection of host data display.
Technical System in the LMDB and host editor access
Figure 1b: A Technical System in the LMDB – host data and opening of the host editor.

Technical System in the LMDB with host data in the host editor
Figure 1c: A Technical System in the LMDB – host data in the host editor.

You see that the Diagnostics Agent itself is also handled as a Technical System and shown next to Technicla Systems of type AS ABAP and AS Java.

Setting Up Agents in the SAP Solution Manager

To be able to use agents’ data, you need to configure them. This is done in SAP Solution Manager.
There are two steps you have to perform:
  • Registration of Agents in the SAP Solution Manager (see section Landscape Data and Outside Discovery). This is done in step System Preparation in transaction SOLMAN_SETUP.
  • Assignment of the Diagnostics Agent(s) to a Technical System. This is done in step Managed System Configuration in transaction SOLMAN_SETUP.
Once these steps have been performed, your Technical System has been set up to be managed by SAP Solution Manager.

Agent Types

There are two agents which need to be installed for better system management:
  • Host Agents
  • gather information about the host’s operating system
  • important to have at least the minimum version of the host agent installed (For more information refer to SAP note 1365123, which contains a detailed presentation as an attachment. The setup of the automatic update process is described in SAP note 1473974.)
  • Diagnostics Agents (formerly called Solution Manager Diagnostics [SMD] Agent)
    • gather information of the managed application on the host systems
    • send it together with the data collected by the SAP Host Agent to SAP Solution Manager
Figure 2 shows the two agent types and how they are installed on the physical or virtual hosts (both can be installed with the same installer):
Agents: SAP Host Agent and SAP Diagnostics Agents on physical and virtual hosts
Figure 2: Agents: SAP Host Agent and SAP Diagnostics Agents on physical and virtual hosts.
One Host Agent must be installed for each physical host and one Diagnostics Agent for each “managed host” represented by physical, virtual or logical host name. One Diagnostic Agent can support multiple managed system components running on the same named host.
In a 3-tier system landscape additional Diagnostics agents need to be installed as one Diagnostics Agent can only report to a single SAP Solution Manager. Thus each managed host would need an own Diagnostics agent reporting to the SAP Solution Manager installation of the development or quality assurance landscape.
Note: In addition to the SLD Data Suppliers being part of the technical system itself, as of SAP Solution Manager 7.2, SPS06 the SLD can be a target for agent data – see SAP Note 2556432 – Switch Outside Discovery from Diagnostics Agent to SAP Host Agent. So you can address this issue using the mechanisms in the SLD – for details, see SLD Topology: How-To Gather and Distribute SLD-Data in Your IT-Landscape?

Data collected by the Agents

Landscape Data and Outside Discovery

Most of the landscape data application is already sent by the managed application systems to the System Landscape Directory (SLD) and from there synchronized to the Landscape Management Database (LMDB) of the SAP Solution manager 7.1. However, in some cases this data needs to be enriched by data which has been collected by agents and written directly to the CIM model based LMDB.
As the agents are neither part of the operating system nor of the installed application system of a host, the term “Outside Discovery” is used for this kind of data collection. In “Outside Discovery” both agent types work together in the gathering and sending process to SAP Solution Manager. Outside discovery works on three different areas:
  • OS discovery provides details about the operating system
  • DB discovery provides details about installed database software(s)
  • MS discovery provides details about Microsoft Internet Information Services on Microsoft operating systems.
Figure 3 shows different agents and their connections to the SAP Solution Manager:
SAP Host Agent gathers information on the host’s operation system
Figure 3: Agents: SAP Host Agent gathers information on the host’s operation system.
The Diagnostics Agent sends data on database or IIS to the SAP Solution Manager. Available Diagnostics Agents can be registered in the SAP Solution Manager directly (Host A1) or via the System Landscape Directory (B1).

Configuration Data

Besides the more static landscape information some functionality of the SAP Solution Manager may also rely on configuration data, which may change over time. Such configuration information (for example environment settings) is important in the configuration and change analysis or also in root cause analysis applications. Amongst other sources configuration data is frequently collected by the agents and persisted in tables on the managing SAP Solution Manager system.

Logging and Tracing Data

The Diagnostics Agent is able to collect logging and tracing data from the applications installed on a managed host and sends it to SAP Solution Manager for storage. This data is used for monitoring and alerting, root cause analysis, reporting and E2E tracing applications.

Monitoring Data

Another usage of agents is to collect monitoring data on OS level as well as on application system level from the agent host. This data is either sent to the directly to the SAP Solution Manager (such as availability data or file system monitoring) or to an Introscope EM (e.g. OS or application performance metrics) and processed further to SAP Solution Manager applications.

Data Flow in Outside Discovery

The data flow between hosts and the SAP Solution Manager is as follows:
  • Host Agents collect data and exposes it via web services to the Diagnostics Agents.
  • Diagnostics Agents process the data from SAP Host Agents and write into LMDB
Figure 4 shows the architecture of connections from hosts to the SAP Solution Manager and the consumers of such data:
Architecture of agents and data flow from agents to SLD, LMDB and consumers
Figure 4: Architecture of agents and data flow from agents to SLD, LMDB and consumers.
The SAP Host Agent on physical host B connects to the Diagnostics Agent running on the virtual host B1. In parallel, data from data suppliers is sent to the LMDB via the SLD.

Installation of Agents

There are two scenarios, when installing and configuring Diagnostics Agents. This depends on one hand side whether during installation of the Diagnostics Agent you know or do not know which SAP Solution Manager System you’re going to use to manage the system:
  • Usually the first happens when the agent is installed by using a Diagnostics Agent installation package.
  • The second scenario happens normally when the agent is installed silently during the setup of the managed application system.
Both installation scenarios may also be used in an unattended mode. The unattended mode allows the Diagnostics Agent installer package to be used in silent mode to automate the installation of a higher number of agents (please consult SAP Notes 1294713 and 1486330).
Similar to the Diagnostics Agent the SAP Host Agent can be installed in an attended and an unattended mode. It is part of the Diagnostics Agent installation package.

Agent Registration

In order to have a fully functional agent, two registration steps need to be done.
  1. The Diagnostics agent need to be connected to a SAP Solution Manager to download the latest applications from the managing system
  2. The managed systems need to be connected to the Diagnostics Agent(s)
For the first step depending on the installation strategy the agent is either registered directly to the SAP Solution Manager (mainly during the agent installation) or by usage of the agent candidate management during the SAP Solution Manager setup (when the agent has registered to SLD).
  1. During Diagnostics Agent installation, the SAP Solution Manager system is known:
    a. The Diagnostic Agent is already connected to SAP Solution Manager (the direct registration can also be performed after the agent installation using a configuration script on the agent host).
    b. Data is available in SAP Solution Manager directly and information about the existence of a Diagnostic Agent is optionally written to an SLD (in an SLD the agent itself is considered as a SAP technical system. Please note that the SLD must not necessarily be the same as used for the content synchronisation to LMDB).
    c. During managed system setup, the system(s) running on the host with the Diagnostics Agent is (are) connected to the SAP Solution Manager and therefore can directly be linked to the managed system.
  2. During Diagnostics Agent installation, SAP Solution Manager is not known:
    a. The Diagnostics Agent is registered in an SLD (setting is done during installation).
    b. SAP Solution Manager in Solution Manager Setup during phase Preparation for SLDs and registered Diagnostics Agents.
    c. Available (not already used) Diagnostics Agents are connected to the SAP Solution Manager.
    d. During managed system setup, the managed system running on the host with the Diagnostics Agent is connected to the SAP Solution Manager
The host agent does neither register itself to an SLD nor directly to SAP Solution Manager. The communication to the SAP Host Agent is managed via Diagnostics Agent.

Agent Upgrade

Diagnostics Agents are taking their business logic (software) from the SAP Solution Manager system, which they are connected to. Therefore, all Diagnostics Agents in the landscape (that are running and connected) could be patched centrally, by applying an LM-SERVICE Java Software Component Archive on the Solution Manager System
In case a Diagnostics Agent has to be nevertheless upgraded, perform an uninstallation of the old release and do a fresh installation.

Connect SAP Diagnostics Agent to Solution Manager using SSL

Skip to end of metadata
The aim of this wiki is to help in enabling the configuration to connect the Diagnostics Agents to the Solution Manager 7.10 using SSL, as described in note 1898685. Actually, the focus is narrowed down to prerequisite #2 of step #2, described in the same note.
This configuration is not valid for Solution Manager 7.20.

Prerequisites

The prerequisites are the deployment of the IAIK libraries in the Diagnostics Agent, as described in note 1898685  and the SSL configuration for the Solution Manager Message Server and P4 ports.

Solution 

Configure transport layer security on Solution Manager JAVA Stack

The configuration of the Solution Manager Java Stack to enable secure communication is described in detail in the following guide: 
The following setup step needs to be performed to enable secure communication on the Solution Manager Java stack:
Configure SSL on AS Java:
  1. Create SSL Credentials: in the Visual Admin(/usr/sap//DVEBMGS/j2ee/admin) of the Solution Manager, select the Key Storage, under Server > Services. Create new credentials or check the validity f the already available credentials for service_ssl:

    Detailed information and the how to guide is available under: http://help.sap.com/saphelp_nw70ehp2/helpdata/en/a6/98f73dbc570302e10000000a114084/content.htm.
  2. Assign SSL Credentials to HTTPS communication port: Access the SSL provider with the following path: Server > Services > SSL Provider. Select the configured HTTPS port (default is 5xx01) and assign the SSL certificate created in the previous step as "Server Identity".
     
  3. Assign SSL Credentials to the P4S communication port: Access P4 provider with the following path: Server > Services > SSL Provider. Select the configured P4S port (default is 5xx06) and assign the SSL certificate created in the frist sttep of this section as "Server Identity".

    Further documentation about SSL configuration for Solution Manager Java Stack is available in the following documentation:  http://help.sap.com/saphelp_nw70ehp2/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm.

Configure SSL on Message Server for Solution Manager ABAP and JAVA Stack

This section is relevant if you want to use MS HTTPS and P4S connection.
The executable directory of the message server needs the SAPCRYPTO libraries installed. For a message server running as part of Central Instance of ABAP stack this is already performed in step ”Install SAP Cryptographic Library and set Profile Parameters”. For Message Server on Java Central Service Instance (SCS) and ABAP Central Service Instance (ASCS) execute the same procedure. Also make sure a valid server identity is available in $DIR_INSTANCE$/sec that a valid SAPSSLS.pse. For simplification it is possible to reuse the server identity as created for the Solution Manager ABAP Stack.
Add the following parameters to the Central Services Instance Profile to enable Message Server HTTPS port:
ms/server_port_1 = PROT=HTTPS,PORT=444$$

Popular Posts