Landscape Strategy for SM1 & SM2

[Former Member]

Hello all,

I am new to Solution Manager (and SAP in general) so I came here to seek for your opinions.

I have SM1 and SM2 installed in one box. SM1 serves as our playground (sandbox) and SM2 serves as the semi-prod.

SM1 is in Solution Manager 7.0 EHP1 SPS 20 while SM2 is still in Solution Manager 7.0 SPS 16.

Currently, I have 11 other systems as follows:

- ECC 6.0 (1st and 2nd instances)

- PI (with SAP NetWeaver 7.1)

- XI (with Netweaver 04)

- EP with NW 7.0 (1st and 2nnd instances)

- BI with SAP NetWeaver 2004s (1st and 2nnd instances)

- SRM 7.0 EHP1 SPS 03

- APO (SCM 5.00) (1st and 2nd instances)

• all 1st instances are treated as dev systems while 2nd instances are treated as semi-prod systems

How can I go about the Landscape stategy for the two? That is, which systems to connect to SM1 and which sdystems to Connect to SM2?

i was thinking of the following concepts:

1st option:

#1 SM1 (dev't) - only satellite systems that are NOT on the path to production would be connected here - such as a sandbox. This solman system would be used for configuration of solman itself example, your solman team would configure solman functionality here. It is also a good practice environment for PM's because it would have a small landscape attached to it your sandboxes, remember? Migrations start here for solman functionality...

#2 SM2 (semi-prod) - ALL path to production satellite systems are connected here, except your sandboxes which were connected to SM1. This system also serves as a target system for migrations that came from the dev system (SM1) for solman functionality itself. This is the main solman box that most users will access for project management, blueprinting, config, charm, and so forth.

can this be possible?

2nd option:

#1 Sandbox Solman - no satellite system connectivity; open access; used for the purposes of testing patches and exploring solman functionality - mostly for basis' purposes.

#2 'Development' Solman - only satellite systems that are NOT on the path to production would be connected here - such as a sandbox. This solman system would be used for configuration of solman itself example, your solman team would configure solman functionality here. It is also a good practice environment for PM's because it would have a small landscape attached to it your sandboxes, remember? Migrations start here for solman functionality...

#3 'Production' Solman - ALL path to production satellite systems connected here, except your sandboxes which were connected to #2 remember?. This system also serves as a target system for migrations that came from #2 for solman functionality itself, This is the main solman box that most users will access for project management, blueprinting, config, charm, and so forth.

• for the 2nd option, I will have to install a new SolMan system to have a three landscape.

please advise.

your insights will be very much appreciated.

thank you.

charisse

[stuart_campbell]

Hi Charissma

It is generally recommended to have 1 PRD Solution Manager for your entire system landscape

- the 3 tier landscape is not necesarily applicable to Solution Manager particularly as

I am not sure how feasible it is to transport between DEV/TST and PRD

- which is usually the key reason to have a 3 tier landscape - although I can see why having DEV/TST

would help - particularly in learning,proof of concept or testing implementation or scenarios.

Possible issues of having multiple Solution Manager systems include

The PRD Solution Manager will not have a complete overview and management of the whole landscape

Threre could be issues having 1 satellite system connected to 2 Solution Manager systems

Best wishes

Sturat

[Paul_Babier]

Hello Charisse,

I am not sure you are understanding the use of Solution Manager to manage your system landscape.

Typically one Solution Manager will manage the entire system landscape, and systems of all types, PRD, QAS, DEV, SANDBOX, TRAINING, etc.

You can still have DEV and TEST and Sandbox Solution Manager systems, but they would be for those functions, developing, testing, learning and would not be managing your system landscape as that would be the role of a production Solution Manager system, normally.

You should start here - https://websmp207.sap-ag.de/solutionmanager, then also navigate to the "Media Library" where you will find a collection of Presentations, Articles and Brochures, Documentation, Technical Papers and How-To's.

Of course you will find the Knowledge Transfer Ramp-up Kits very helpful - http://service.sap.com/rkt-solman

And also the help library is often quite useful - http://help.sap.com - select the Solution Manager product and then select the applicable version.

You should find these resources quite helpful in determining a strategy for your system landscape and grow your Solution Manager knowledge.

Regards,

Paul