Showing results for 
Search instead for 
Did you mean: 

Solution Manager 7.2 SPS 10 - Development/Sandbox Refresh

0 Kudos


We currently have a solution manager at:

  • SAP SOLUTION MANAGER 7.2[ SPS 10 (12/2019) FPS ]
  • SAP NETWEAVER 7.4[ SPS 21 (01/2019) ]
  • Windows/SQL Server 2016

We have an old development/sandbox solution manager that we want to update, or refresh, from our production solman.

We are having trouble finding the best path for refresh. I found a number of threads and note that reference "System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.5, and SAP Solution Manager 7.2 SR2 Java, on Windows". Is this the guide best to use to update our sandbox Solution Manager? Or is there a better route?

Also, we want to maintain as much of the java configuration as possible and SWPM the best tool to use?

Any advice or direction would be appreciated.

Thank you,


Accepted Solutions (0)

Answers (2)

Answers (2)

Active Participant

Hello Bennett,

first of all: unfortunately there is no official method/procedure to update a SAP Solution Manager system. From a technical perspective a system copy would be the proper way to perform this.

Unfortunately it is extremely complexe to copy a productive SAP Solution manager system to update/refresh a non-productive SolMan instance. The critical point is the usage of your current SAP Solution Manager and especially the managed system configuration.

An example: If your SAP landscape is connected to your productive SAP Solution Manager (via SLD->LMDB or direct LMDB data supply and the managed system configuration) and if you are using something in the functional area of Application Operations (so some monitoring functionalities) -> every prerequisite is configured: data collection; extraction, SMD Agent assignment and so one. If you would copy this productive SAP Solution Manager system, these configurations would be copied as well. So in a worst case scenario a managed system would try to send collected data to two SAP Solution Manager. Even other scenarios like ChaRM, ITSM, Test Suite would be affected. Next to this: only one SAP Solution Manager can be used as a productive one in regards to data synchronisation to the SAP (support hub) backend. E.g. data synchronisation by two SolMan systems can cause inconsistencies in the Maintenance Planner.

At the end there are many dependencies which make a simple SolMan system copy difficult. In fact the complexity of your plans cannot be answered in a simple tool or method decision.

BR Tim

Active Contributor

To keep as much of possible of the JAVA configuration, use the save function of the SAP EXCHANGE PROFILE from the source and then import it on the sandbox: HELP PORTAL

The SWPM is the best tool, search for the 2 manuals SystemCopy_71X_WIN for ABAP and JAVA.