Solution Manager 7.1 - Advice Needed

[Former Member]

Hi Experts

I would like some advice regarding Solution Manager in our environment.

We are experiencing issues regarding maintenance and hardware limitations on our current Solution Manager Server which carries the Central SLD and is connected to all our ECC and Portal Servers.

Background:

We already have Solution Manager 7.1 with DB2 9.7 (SID=OLD) (Central SLD is here) installed and we monitor and administer about 45 SAP Managed Servers.

The Diagnostics Agents etc are all installed and operational.

Goal:

Re-Install Solution Manager 7.1 on another Server with DB2 10.1 (SID=NEW) and connect to Central SLD on OLD

We will be re-doing all the configuration from scratch and we will not be copying the current Solution Manager Config.

Questions:

1.) Would we be able to install the new Solution Manager (NEW) and connect to the old SLD which is on OLD?

2.) Would we be able to in parallel technically monitor all the managed systems from both Solution Managers?

3.) Is this a wise decision above or should we migrate servers one by one to the new Solution Manager Managing System?

4.) Is there any way if we proceed with step 3 to then only leave the Central SLD on the old Solution Manager Server (OLD) and use that as the central SLD?

5.) Would both the SLD's need to have same CR and CIM Content etc so that we can setup the bridge from OLD to NEW SLD

6.) Is there a way of splitting / deleting the existing old Solution Manager (OLD) ABAP Stack so that we only have a Central SLD on the server with no ABAP Instance so that we could reclaim some resources?

6.) Would we be able to turn off Wily Introscope on the OLD Solution Manager or perhaps remove it completely once we have migrated to the NEW Solution Manager?

7.) Is there perhaps any other issues / problems that we would need to consider beyond what i have mentioned above?

Any advice would be greatly appreciated.

Thanks so much.

[Former Member · Accepted solution]

Hi Solly,

A lot of questions, I'll try to answer them

1. No problem, you can connect your SolMan to any SLD.
2. Perhaps, but not in your current config. You can only connect an agent to one system.
   So to be able to monitor eveything in both systems you'd have to install an additional agent on every system.
3. As you can probably guess, it's not something I'd recommend. Transferring your systems to your new SolMan would probably be a better plan.
4. You could, but then you have a SolMan system running only for the SLD....
5. I don't think they need to be on the same level, but I'd keep it synchronized
6. I wouldn't recommend that either, I don't know if it's possible but if it is, it will take you a lot of effort. Why not simply register all your systems in the new SolMan. Or, even better, install a standalone SLD as "master" and use that to bridge to your SolMan and PI systems.
7. (6.2) Once you've migrated everything to your new system, you can turn it off and even remove it. Maybe you want to save your historical data, you will find how to in the install/upgrade guide. (copy a few folders)
8. In general, I'd advise to install your new SolMan, start migrating all your systems to the new one, install a standalone SLD, migrate your systems from the old sld to the new one, and shutdown/remove everything from your old system.

Hope this helps!

Regards,

David

[Former Member · Accepted solution]

Hi David

Thank you very much, it helps immensely. It confirmed all my doubts.

Have a super weekend mate, thanks for the help.

Cheers

Solly