The fourth is a wider array of application and cross-application dashboards for monitoring metrics such as system security, changes, events, incidents, availability and performance.
Customers can also leverage custom dashboards using predefined templates available from Focused Insights. This includes dashboards for monitoring not just technical but business metrics. Focused Insights include over best practices KPIs that can be deployed in minutes without programming. The fifth is an enhanced Custom Code Management application to enable customers to optimize the quality, performance and security of custom developments.
SAP has also made the effort to reach out to the functional side of the ALM wheel by providing tools to the business that are clear and simple for anyone in the organization to use. This eliminates the requirement to engage the technical team for assistance by allowing the utilization of the new user interface enhancements that are integrated into Solution Manager 7.
Among a variety of tools, a few of them stand out above the rest. SAP has significantly improved Solution Documentation , utilizing a web based portal for creating all of your business process documents as well as a graphical modeling tool for designing and mapping out any business process.
This acts to support business process that require multi-level hierarchies. To simplify the process of mapping business processes, SAP has introduced the ability to use a library of reusable objects that can be manually and automatically generated. This greatly reduces the effort required to create and maintain business processes in Solman.
For this firstly I will clarify what is an IBase, text and object component, how to create Ibase components, and how to check if the Ibase component used in an Incident Management scenario is linked with the LMDB product or not. An IBase component represents the exact point where the incident, for example, is detected. Before Solution Manager 7. With Solution Manager 7. With 7.
You can enter a Component or a Configuration item in the Reference Objects area in the Details assignment block:. The users used in the RFC connections differ which means you should redo all the connections in order to use the "new" user-id's. That's rework needed to be done. Many customers don't have diagnostics and host agents installed by default on their managed SAP systems so that's already adding to the cost really.
You need to install those agents to get your managed SAP systems in properly. Once you start moving your SAP systems about the "system" fails dramatically. It's not properly geared towards handling fully virtualized environment and customers that move SAP systems about frequently. I have experienced this first hand. At the moment we are handling over two-hundred SAP systems. There is a lack of intelligence in the system landscape maintenance.
Was it copied, was it moved If it could do that, a lot of additional maintenance could be avoided. Or even having to remove the SAP system from the Solution Manager and reinserting it could be avoided.
Pre SP5 I've seen green lights on the verification and then red lights in the managed system setup The result is the connection is there green light but it fails resulting in short dumps in the managed SAP system.
The logging of the action bottom of screen does show that no roles are assigned but right after the execution is performed creation to screen focusses on the top which makes the end-user see a green light. To see the error, you would have to go back down and scroll through the logging of the action.
This might be something small, simple but it's things like this that in the end make the features look "unfinished".
That's exactly my point though. You have more than one repository that holds the same data, why? That doesn't make sense. Why not only use LMDB, right? A survey amongst system administrators would definitely show that the system landscape maintenance score badly at the moment.
I'll set one up to see to what extent this is true. On the other hand, it does require Diagnostics and Host Agent as well so there are more prerequisites to get it right. Progress is rather slow though if you ask me. I wonder how long it will take to get things right. The need to hit a save button on top of the wizard for example is something I personally dislike. MOPZ has been enhanced some time ago to also be able to include Java patches.
But if you have the system select the java patches automatically, what do you see? It gives a warning that if you include these java patches into the XML file, you are responsible for the consistency of the XML file yourself. That doesn't make sense at all. They should have just left out the integration into the XML file in this case. It's like shipping a product to someone and saying: "If it's broken due to the shipment, it's not our problem".
Being positive matters to me. This blog post is not meant to harm Solution Manager in any way. I like Solution Manager but I see a lot of room for improvements. This means that I believe Solution Manager holds value and can provide added value but I also do believe that in order to use Solution Manager to it's full extent you need to threat it like a business system much like you do with a ERP SAP system and put one or more resources on it instead of doing "single shot projects" to keep it maintained properly.
I hope SAP reads these blog posts and acts upon them. The idea concept of LMDB is good but so far it has been too messy. LMDB is good, but needs to be only better in al the way!!!!! Thanks for the time taken Skip to Content.
0コメント