I have been working for SAP Basis arena since 1998, and I’m wondering in the 12 years or so what has changed in the job. For sure Solution Manager is now a major component in the SAP landscape – the idea you can central monitor the whole landscape from one place, have alerts on almost anything including a heartbeat if the system should fall over.
Self-healing software was a paradigm that I first heard about back in 2005. IBM and other vendors were placing vast amounts of money and research in trying to have software automatically fix its own identified problems. For example an RDBMS would run out of memory, and so it would automatically increase the database cache and with the potential developments would have the memory available hot. But things have gone quiet…
In order to run SAP, this uses many of the OSI layers, and therefore one self-healing solution would be complex in order to manage the application and the platform (both OS and RDBMS); so possible the SAP Basis career is safe for now?
Software Lifecycle Manager sounds an interesting concept, that could be enhanced to where an end-user has a short dump and automatically SAP Solution Manager would review the vast amount of OSS Notes and where it sees a predictable (AI like) success rating and automatically apply the OSS Note to the connected development environment, with workflow generated to the system administrator / end-user to re-test in development. This then can be transported into QA (for UAT) and Production for final conclusion.
Solution Manager is definitely the way to go, in the 12 plus years I’ve experienced then centralisation is definitely the key to improving system reliability and reducing Basis resource, time and money for system monitoring. Whether Solution Manager will adapt further and be able to address the OS and RDBMS, as well as the application is something that I will keep looking for.