For the SAP blogger/analyst/dude on the ground, there’s nothing more frustrating than a content backlog. I’m hoping to play catch up the next few months and share a few crucial ditties on this blog, but bigger promises have been broken, so one blog at a time. This one is our first installment of the semi-regular “Sol Bros” Solution Manager podcast series. The SolBros came about simply because I wanted to do a podcast on Solution Manager that took an honest look at the pros and cons of this important but controversial SAP product. So I pulled in some of the most frequent tweeters on the topic. The guys got along, so we continued to tape.
Each time, a different person from the group plays “point,” and organizes the podcast and the content. This time it was my turn, which was great because for almost a year now I’ve been hearing analysts hammer Solution Manager for being “a mile wide and an inch deep.” I don’t happen to think that’s the best way to criticism SolMan, but I really wanted to find out what the other “bros” though about this topic.
So I got my chance to ask, and we covered that and quite a bit more in an hourlong session for the real SolMan gearheads – if there is such a thing. And yes, we answered listener questions so that’s incentive for you to post a comment to this blog because we WILL definitely dig into it the next time we tape.
We tape our calls in a variety of formats, usually connected to a WebEx session, and the logistics of the taping usually involve an evening call for Phil/Jim/myself, which is the next morning for Tony. In this case, it was Friday night on the east coast and Saturday morning for Tony, so there’s a Friday night party theme on this one – as much as talking about SolMan on a Friday night can be called a party.
Here’s the basics:
Podcast links: SAP Press SolMan System Monitoring, Solution Manager Service Desk – Change Management Integration by Tammy Powlas, SAUG Summit 2011, SAP Service Marketplace SolMan Info (log-in required), ASUG Annual Conference (Orlando)
Podcast Structure: I. Intro chatter, II. (2:40) SolBros reader questions, III. (21:55) SolMan – “A mile wide and an inch deep?” – discuss! IV. (36:05) Individual updates: Jim Spath – SolMan and ASUG, Phil Avelar – CHARM lessons learned, Tony D – SolMan consulting, customer value and learning tools.
(If for any reason the player doesn’t work, you can download the podcast using the “download media” link on the right hand side).
(Trouble downloading? if for some reason it’s not playing in its entirety for you, check out the version on JonERP.com in the meantime.
Usually when I post a podcast on SCN, I include a summary version of the detailed notes I post on JonERP.com. In this case, I’m going to do something different, so you can go to my site if you want to skim the detailed SolMan 5 show notes.
However, since we had two reader questions from SCN, here’s that section’s notes in its entirety:
Part II. (2:40) Reader Questions
Question #1: From Arundeep Singh
“Hi Tony and other SolBros,
Thanks for reflection on agent and plug-in maintenance. If would eagerly accept the eating habits as a trade-off to clone Tony 🙂
I have read about Landscape verification. It is a new and seems good tool. But this is to find and correct the wrong configuration. My question was on a regular maintenance to keep it up-to-date. It becomes a big effort and especially with Wily agents the application systems needs restart and it is not easy to get agreement for downtime for multiple systems. And with unavailability of non-cloned Tony, it becomes even more challenging :). Just as an example a team took about a year to configure agents for MDM system and it is still not generating EWA. Imagine when the whole infrastructure calls for maintenance!!! Anyhow, my belief is that without good people no strategy/tools/processes can work.”
Tony: Every company should have a release strategy that they should agree on – breaking a year into quarters to apply maintenance across a landscape and minimize disruption. Being pro-active tends to work better than waiting till an OSS note problem hits you.
Jim: I see this question as similar to questions of the timing of patching core systems like routers or network switches. Any kind of control system that you depend on for the rest of your environment, you have to approach very gingerly, and patch it off cycle from the rest of your landscape.
Phil: When it comes to the production box, a quarterly schedule for Solution Manager updates would be ideal, but I find most companies aren’t able to make that happen and a yearly update schedule might be more realistic for them.
(Discussion of pros and cons of Solution Manager patch scheduling versus other landscape management priorities).
Tony: Patching Solution Manager is never done in isolation, so if you patch Solution Manager frequently, you’ll have to patch your satellite systems more frequently as well. A decent testing strategy with proper tools and documentation is essential. Phil: ASUG has valuable content when it comes to planning upgrades and patches and managing release schedules. Jon: “Isn’t the bottom line that support packs are kind of a pain in the *ss? I talk to customers that have trouble getting them in once a year.”
Tony: “If you’re not on top of support packs by now, when are you going to get on top of it? We’ve been used to applying support packs since the R/2 days…Welcome to IT, guys – this is what we live and breath.”
Phil: It’s the testing that’s the challenge – sometimes you don’t have the manpower. I have customers who haven’t applied support packs since they went to ECC.
Jim: getting permission to make patches and changes is non-trivial but it needs to be done…Let’s go on to the next question.
15:15 Reader Question #2 – emailed to Jim Spath (looong question).
Jim: question was inspired by a wiki page I put up to get Central Performance History running which has not been completed yet. The question is almost identical to the snag I ran into where the BI portion of the CPH looks like it was set up, but it isn’t really functional. I thought it was indicative of the complexity and the layering of products like SolMan as they have evolved. Problems can be difficult to resolve with so many layers in the mix. Post it was a a reply on the wiki or the blog so that it isn’t just me trying to solve it. Or, open a ticket with SAP.
Tony: if he’s a BI guy, generally these things can be fixed by running the SolMan setup again. Or looks through the RSA1 logs in SolMan. Search SCN forums. Check the SAP Press books on SolMan also a “TDT approved method.”
Jim: By talking about this I often get questions directed to me – restate them and put them in a public forum so the next person can find it also. Warning: “AskJim.com”, Tony’s suggested site for SolMan questions, doesn’t really exist.
Phil Avelar has the point role for the next SolBros podcast, so Phil, here’s the baton.