Sap product roadmaps upgrade#
Sap product roadmaps series#
Sap product roadmaps download#

This is similar to the way the SLD content is distributed. It consists of two main parts – the Engine and the Content, both separately deliverable with their own life-cycles. The TMC seems to have been around since mid 2018 for customers to implement at version 1.5.0 and has only recently been improved in version 2.0.0. Introducing, the SAP Technical Monitoring Cockpit (TMC): If we were to turn off the Java stack of Solution Manager, we immediately lose the technical monitoring capability therefore, what we should be looking for, are any signals from SAP that the area of technical monitoring is being migrated off of the Java stack. These Agents pass the gathered raw monitoring metric data, to the Java components of Solution Manager, for aggregation, interpretation and alerting inside Solution Manager. Each of the SAP Diagnostic Agents (I’m sure I’m not the only one who dislikes these) installed at the SAP instance level, talks back directly to the SAP Netweaver AS Java of the Solution Manager system.

Sap product roadmaps series#

The Java stack was only recently added (in relative Solman version terms), in the 7.x series of Solution Manager (Solman never used Java in the 6.x Netweaver stack, which equated to Solman 3.x), and the main usage for the Java stack seems (in my eyes) to be for the technical monitoring function of Solution Manager. This leaves one big question, what is the future for SAP application monitoring, if there is no SAP Solution Manager? I guess the answer partly lies in the usage of Java within SAP Solution Manager. If we check SAP note 2577037 “Does Solution Manager 7.2 need ABAP and JAVA stack?” we get confirmation that Solution Manager requires both ABAP and Java stacks in order to function. All versions of SAP Solution Manager before 7.2, have been out of mainstream maintenance since the end of December 2017. SAP Solution Manager has been running in a dual stack (previous incarnations before Solman 7.2 could be run with one SAP system that consisted of both ABAP and Java stacks under one system identifier), and since 7.2 with ABAP and Java separately installed under different SIDs. Some are not even that new, and have just been uprated to be brought into line with a new UI5 interface. But, you could argue these are enhancements to the existing capabilities of the tool. Yes, we do have a lot of “new” capabilities (licensed separately), recently added to Solution Manager 7.2, such as the “Focused” solution toolset (Focused Run, Focused Insights & Focused Build) – these are meant to provide ready-to-run (oven ready?) capabilities for customers.

The System Landscape Directory… let’s save that for another post!.

Sap product roadmaps download#

Download Basket authorisation is now purely controlled in the SAP Launchpad/Support Portal.

Maintenance Optimizer is now Maintenance Planner.

SAP have a SAP Solution Manager roadmap and it’s probably “the cloud” just look at what has been migrated over-time, out of Solution Manager to the cloud: There are still many, many customers who only use Solution Manager for the System Landscape Directory (SLD) and basic monitoring, and some that even use it for hosting smaller products such as Adobe Document Services (ADS). Back then, the functionality of Solution Manager was fairly limited the enabling of the download basket was the main usage.

Sap product roadmaps upgrade#

I remember being sat in an upgrade conference in 2005, where SAP clarified that the SAP Solution Manager Roadmap for Solution Manager 3.2 was to become mandatory for customers to install, in order to receive support from SAP. There is, however, one tool that is common to all SAP customers. For SAP PO, there is already a cloud based SAP integration/middleware product (SAP Cloud Integration) which I see as signalling the end of on-premise SAP PO. This, I’m sure will become clearer over the next 5 years, but with the current drive to cloud we can probably make a good guess where these products will end-up. We don’t yet know for certain, the paths of the above mentioned products. These products are not particularly common in most SMEs, so the impact is limited.

What possibilities does the current SAP Solution Manager Roadmap bring?Īs many will come to appreciate, the end of the Java stack is significant, with many SAP products utilising Java, such as SAP PO (Process Orchestration) and SAP BPA (Business Process Scheduling).

With the closing of 2019 and the opening of 2020, we are now 5 years away from the end of the NetWeaver Java application server (see note 164480). Editor note: following the announcement made by SAP on February 4th, please review article SAP Business Suite 7 To Go To 2027.