Recently, our team has seen a lot of staffing requests for SAP Basis expertise with buzz words like "Must have at least X S/4HANA project/deployment Experience". So we set out to bust the Myth of S/4HANA installation and configuration as something significant that requires special experience and skills beyond Netweaver Basis and HANA. We'll leave the judgment up to you if warrants some special skill or is it just like most new SAP products that came along for Basis over many years. Interestingly, S/4HANA is not much different in dictionary and codebase savings when compared to ERP 6.0 EHP7. We're publishing this blog to show you what it takes to get a small S/4HANA environment installed (e.g. IDES S/4HANA 1610 release), and more importantly how to use SAP monitoring to manage SAP performance as soon as it's up and running. Bear in mind, this is not about migration to S/4HANA which would be a complex discussion.
This week we look into configuring the S/4HANA Monitoring scenario as the final part of the Solman 7.2 SAP Monitoring installation and setup procedure. You can download the complete SAP Solution Manager 7.2 Getting Started with Monitoring eBook below if you choose to set up your own environment. Prior parts are listed below
The two prior parts pertained to the installation and configuration of the SAP Solution Manager 7.2 technical base:
- Solution Manager 7.2 SAP Monitoring - Part 1 (Setup)
- Solution Manager 7.2 SAP Monitoring - Part 2 (Configuration)
In this part, we finally connect the managed system's agents to Solman. This phase needs to be repeated for each system to be monitored, in this example HANA, but similarly for other system types like SAP Netweaver, S/4HANA, etc. This precedes the assignment of monitoring scenario (application stack).
Last week the SAP Solution Manager 7.2 Roadshow visited Northern and Southern California. There is a lot packed into Solman 7.2, and it's here whether you're ready or not. SAP will end maintenance support of Solman 7.1 in December 2017, so we expect a flurry of installations and/or upgrades in the next 6 months. Depending on your usage scenarios, neither the upgrade nor the clean installation and configuration are trivial. The main changes to Technical Monitoring is the UI which is now based on SAPUI5, no more standalone mobile apps and a cleaner GUI without dependency on Adobe Flash.
If you've attended or planning to attend the ASUG SAP Solution Manager Roadshow, you can learn about SAP Solution Manager 7.2 capabilities and roadmap. However, if you want to see for yourself what Solman 7.2 can do or can't do, as well as gauge the level of effort for your Solman 7.2 project, you would probably install and connect to your environment. Alternatively, there is a SAP Cloud Appliance Library version for demo purposes.
This is a continuation of the first blog, SAP HANA Dynamic Tiering Test-drive, as we cover improvements in extended storage features of HANA 2.0, how to deploy, create multi-store table using HANA Studio, then perform SAP HANA Monitoring of Extended Storage server and services.
According to SAP, Process Orchestration (SAP PO) is a tool to model and design business processes, primarily used to integrate SAP systems and external systems. There can easily be confusion with interchanging terms used, XI (Exchange Infrastructure), PI (Process Integration) and PO (Process Orchestration), but really they are all the same thing, just SAP evolution over time with increased functionality. In this publication we will summarize the main difference and how to simplify the SAP monitoring of this increasingly important glue that holds together a SAP-based ecosystem.
It's time for the SAP Monitoring challenge! How to monitor ANY and ALL of the following in minutes, WITHOUT knowing anything about SAP Solution Manager, CCMS or any vendor tools? Simple, IT-Conductor does all the work using cloud-based automation, so you don't have to, YES, we'll even manage the monitoring services so all you have to do is relax and use it!