cancel
Showing results for 
Search instead for 
Did you mean: 

Do we need a landscape PRD QUAL DEV for Solution Manager himself?

BlaiseF
Explorer
0 Kudos

hello,

We provide support to several customers.

We are going to install Solution Manager to connect all the systems of the various customers.

Do we need a landscape PRD QUAL DEV for Solution Manager himself?

A single server is sufficient?

I found no information about this subject in the installation and the parameter setting of Solution Manager.

Thank you

Best regards

Frédéric Blaise

e-Kenz S.A.

Luxembourg

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Frederic,

Your question is answered in the FAQ section on www.service.sap.com/solutionmanager :

4. What system landscape is recommended to run SAP Solution Manager?

To run SAP Solution Manager for minimal operations (i.e. Maintenance Optimizer, EarlyWatchAlert) a one-system landscape is sufficient. For mission-critical operations (Change Request Management, System Monitoring) the SAP Solution Manager is best run on a 3-system landscape (DEV, QAS, PROD).

Regards

Amit

Answers (4)

Answers (4)

BlaiseF
Explorer
0 Kudos

Hello,

And the winner is:

Amit Devale

because the answer is effectively in the FAQ of Solution Manager.

But thanks to all the participants because I am going to be able to explain needs to my leader.

Best regards

Frédéric

jon_friesen2
Active Participant
0 Kudos

Hi Frédéric,

My rule of thumb is:

- if you are just doing monitoring, EWA reports and RCA - then just one solman is fine

- if you are doing anything which requires transportable customizing, such as service desk, charm, etc then you definitely need a Dev as well as a QA system

- if you are doing anything which requires custom code, such as custom reporting, BAdI enhancements, custom data collectors or autoreaction methods, etc, then you may benefit from a QA system as well as a Dev system. This is especially true if your custom code depends on quality transactional data (for example custom reporting). A QA system will only be as useful as its ability to reproduce production scenarios, which means you should refresh QA with good transactional data from Prod on a periodic basis.

If you need a QA SolMan then you will also probably need proper simulated satellite systems (for example if you are developing custom code for the ChaRM scenario you should consider building Dev/QA/Prod test satellite systems instead of trying to simulate them with clients in the SolMan).

Jon

Former Member
0 Kudos

I would definitely recommend a 3 system landscape if you are supporting others. As Prakhar said, you'll be implementing some things that you would not want to mess with in a live prod system.

prakhar_saxena
Active Contributor
0 Kudos

Hi

Yes you can have the 3 tier landscape for Solution Manager.

It is very helpful to this way because there are several settings required based upon the scenario configuration like Service desk or Change management or Project management

so you can create configuration for solman in Dev and then test your config in QA later on move to PRD.

In addition you can train all your end users in solman QA itself instead of creating TEST MESSAGES in PRD.

Hope it helps.

Regards

Prakhar

Edited by: Prakhar Saxena on Jun 16, 2011 4:46 PM