Landscape to connect to SolMan DEV

[Former Member]

Hi, A very basic question for setting up SolMan. We already have a SolMan system that is connected to our productive D-Q-P landscape. We now want to setup a SolMan DEV so that we could test patches, security changes etc to our SolMan Prod system. The question is what landscape do we connect to SolMan Dev. We were told that we cannot connect the productive D-Q-P again to this new DEV. What is the best practice. Any thoughts? Setting up new systems just to support SolMan Dev does not seem a great idea?

We have 2 BW, 1 ECC and 1 Portal environments currently connected to the SolMan Prod.

Thanks

[Former Member]

Hi.

Just for testing patches in Sol Man you do not need a system landscape connected.

It is correct that - for some scenarios - you can not connect a second Sol Man to your landscape.

If you really need a system landscape connected and depending on the things you want to do with it, you may create empty clients in your DEV system (lets say 101, 102 and 103) and set up those clients in TMS to be developement, consolidation and delivery system. But be warned that you still can not make use of all Sol Man scenarios using this setup. Change Request Management for instance is still a risk to use since abap programs are client independent and might mess up your system when changed by two different Sol Mans.

To be on the safe side you should just install a small Netweaver WebAs, create different clients and set up this clients as three-tier system landscape.

This way you are able to use Sol Man functionality without the risk to mess up your productive landscape.

But in the end it is all up to you and your requirements.

/cheers

[Former Member]

Hi Christian,

Thanks for the coments. Yes, the Solman Dev box would be testing of patches, etc. But that testing is incomplete without actually moving a transport. Also, we current use just the ChaRM functionality in SolMan but would like to start using diagnostics, etc too.

On, dummy clients, two of our landscapes connected are BW ones and so that would not work, as like ABAP objects.

On using WebAS, again our users would not be comfortable to move transports in some dummy systems to see that the process works.

Has anyone connected the same productive landscape to more than one Solman systems. The reason for asking is that the transports that we would move via Solman Dev would be very controlled one and never ever conflit with objects at any time that are in use on transports in Solman Prod.

Thanks..