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.
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!
We have been publishing extensively with more than a dozen articles on How to monitor your SAP environment using SAP Solution Manager, but what happens when Solman itself is suffering from Performance and Availability issues? Solman has widen its footprint at enterprises, some mandatory uses of functionality such as Maintenance Optimizer, and Remote Support, while others include Technical Monitoring and Change Request Management (ChaRM). Given such dependencies of many SAP customers on their Solman, shouldn't it be monitored and managed as a business critical system?
Announcement: For latest update and webinar recording, visit Centralized SAP SLT and RFC Connection Monitoring publication
I'm glad to be finally back from a very successful customer Go-live of an SAP ERP 4.7 to ECC 6.0 Ehp7 Near-zero Downtime (nZDM) upgrade, combined with a database upgrade and platform migration from AIX/Oracle 11g to Linux/Oracle RAC 12c over the President's Day holiday. There were plenty of sleepless nights during go-live but the client was very happy with the performance of the new system. It was good to be prepared for performance comparisons mentioned in our last blog post about Crucial Performance Tips for Upgrades & Migrations. On average, Batch workload ran twice as fast, and Dialog rocketed to three times the speed compared to the old system. The increased speed and capacity will allow this customer to drastically improve the way business is done in the near future, including the ability to replicate and report near real-time using a combination of ECC, BW on HANA and SAP LT Replication Server (SLT - SAP Landscape Transformation), otherwise known as a Sidecar scenario. SAP SLT is enabling customers to replicate business data across their system landscape at the database trigger level, thus allowing high speed data synchronization between similar or disparate database platforms. For the Basis team, this is another technical scenario to monitor to ensure the availability and performance of SLT meets the business demand for near real-time information. See SAP Operations Guide for detailed information about SAP Landscape Transformation Replication Server.
Let's look at existing ways we can perform SAP LT Monitoring:
- In the SLT Server using transaction LTR (Configuration & Monitoring Dashboard) which launches a web-based SAP Netweaver Business Client. You will need to assign the role SAP_IUUC_REPL_ADMIN to your user's profile
- In the SLT Server using LT Replication Server Cockpit (LTRC) to check and monitor a single configuration at a time for transfer status, analyze errors, and manage the load and replication
- In the SLT Server using LT Replication Server Monitoring (LTRO) which is relatively new and can monitor and manage multiple configurations
- In the SLT Server using Migration Workbench (MWBMON) to monitor and analyze Mass Data Transfer
- In SAP Solution Manager 7.1 (at least SP05, and DMIS_2010 SP07 on SLT Server). SAP Note 1558756 – ‘Solution Manager 7.1. – BI Monitoring: Prerequisites’ describes the prerequisites to be met and the necessary configuration steps in order to integrate the SAP LT Replication Server Monitoring Information into the SAP Solution Manager E2E Alerting Infrastructure
See more details below, but unsatisfied with set of manual methods above, we started to develop our own SLT Monitoring solution add-on to the SAP Management Pack for Microsoft SCOM, capable of monitoring health, availability and performance of SLT configurations down to each table level.
A pulse check with our SAP subscribers to see if they have implemented SAP Solution Manager 7.1 technical monitoring or are folks still waiting for the promised SAP Solution Manager 7.2? Well if you're waiting, then maybe you shouldn't because according to this SCN blog Whats new in SAP Solution Manager 7.2? it's been delayed until at least Q2 2016, and it doesn't look like there's much in the roadmap that greatly enhances technical monitoring or automation.