Solution Manager Version

[Former Member]

Hi all - quick question.

We have an old version of solution manager that is no longer supported, can I put up the latest version as a stand alone in the same production environment and slowly migrate setting and configuration from the older version to the newer version with out conflicts?

Thanks

Robert

[Former Member · Accepted solution]

>

> Hi all - quick question.
> 
> We have an old version of solution manager that is no longer supported, can I put up the latest version as a stand alone in the same production environment and slowly migrate setting and configuration from the older version to the newer version with out conflicts?
> 
> Thanks
> 
> Robert

Hi Robert

As long as your Hardware supports it , I dont think there should be a issue in running 2 instances of Solution Manager on the same host. The only precaution you will have to take is for the RFC's that you create. Make sure that they are pointing to the right system id and system number.

More better if you could use a different system id so that there is no confusions.

Regards

Amit

[Former Member · Accepted solution]

Thank you for the information, I will bring this and other responses to our team to consider.

[former_member209604]

>

> We have an old version of solution manager that is no longer supported, can I put up the latest version as a stand alone in the same production environment and slowly migrate setting and configuration from the older version to the newer version with out conflicts?

Quick question. What's the current support package level of software component ST?

Is it 400, 320, 310, ...?

Based on my experience, the decision between

- upgrade a Solution Manager system (2.1, 2.2, 3.1, 3.2) to current version (7.0 EhP1)

- or start from scratch with a new installation and configuration

depends on the release and usage of your current SolMan system.

- Which scenarios / functionalities have been used?

- Which data, configuration should be available again in the new SolMan system?

- How many systems are connected, how many RFCs to managed systems exist?

Data migration is not supported within all scenarios.

Best regards,

Ruediger Stoecker

[Former Member]

Hi

Are you looking for migration to different OS? r you just want to update your solution manager to new one?

Does your goal point to both? then you can first initiate migration and update your solution manager latest version that would be fine.

other hand you can update your solution manager to latest version then you proceed for migrate.

Sap notes for both the options [1238351|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1238351]-for nw 7.01

[1120872|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1120872]-for solman 4.0

thanks,

Jansi

[Paul_Babier]

Hello,

Robert, is migration not an option?

You can have multiple solution managers in a solution landscape, if that is your question?

So customers will have a System dedicated to Service Desk and other for Change Management and still another for EWA, and monitoring, because the load needs to be distributed by function.

However it could be a lot of work when you want the new system to take over a certain functionality from the old one, and have to duplicate RFC's on the managed systems, etc.

Typically when you have an old system that needs to be updated to a new one the process used is migration.

But you can have more than one Solution Manager system in your landscape.

And you could use the approach you suggested. But I would recommend Migration.

Regards,

Paul

[Diggeshhjoshi]

Hi Robert,

If I were you, I would just upgrade Solution Manager. I had Solution Manager 3.1 and upgraded to 3.2 and later on to 7.0.

You could also install another stand alone solution manager and reconfigure if you have constraint with hardware on old solution manager.

Good Luck,

Digesh Joshi