SAP Solution Manager migration to Tosca Cloud
If you use SAP Solution Manager with Tosca on-prem and migrate to Tosca Cloud, we preserve your SAP Solution Manager integration. This topic explains what transfers automatically and what you need to verify afterwards.
Before you start
Make sure you've integrated Tosca Cloud (opens in new tab), and that you haveSet up the local environment for the SAP Solution Manager integration in Tosca Cloud.
Migration behavior
When you upload tests from Tosca on-prem, Tosca Cloud automatically keeps the following SAP Solution Manager data:
-
Test cases: The BlobId and BlobVersion tags are automatically applied to migrated test cases. This keeps your test cases connected to SAP Solution Manager without manual reconfiguration.
For more information on uploading tests from Tosca on-prem to Tosca Cloud, see Use uploaded tests.
-
Execution Lists: The test package and folder structure automatically transfer and convert into playlists. This way they remain connected.
Required actions after migration
When the migration in Tosca Cloud is complete, we recommend you to check that the following are correct:
-
Your test cases are available in Tosca Cloud's inventory and confirm the BlobId and BlobVersion tags are there.
-
Your playlist's folder and entry structure matches the original test package structure in SAP Solution Manager.
Limitations
-
You can run a migrated playlist directly in Tosca Cloud, but its results don't transfer back to SAP Solution Manager yet. If you need those results in SAP Solution Manager, keep running your tests from there until this becomes available.
-
We recommend you keep only one test case in each folder, or migrate the one you want on its own first. This is because, if a folder has more than one test case, only one of them migrates correctly with its BlobId and BlobVersion tags and the rest get a SAP Solution Manager migration rejected tag instead.
What's next
Now that you understand how your SAP Solution Manager migration works, here's what you can do next: