Maintain and Support Your SaaS solution

You can update your solution with patches, support packages, or new releases. Create a new branch from the main branch in test system TST in your 01 Develop subaccount for every support package or new release. For minor changes, continue developing in the respective active maintenance branch.

Navigate to the Landscape Portal as a Landscape Portal Admin.

1. Open the “Update Product Version” app

2. On the right side of the screen, you can see the Planning Calendar. The planning calendar gives an overview of planned and unplanned downtimes of service-relevant infrastructure as well as already scheduled product version updates. You can use the calendar to help you find a fitting time slot for your product version update so as to make sure that it doesn’t conflict with other downtimes

3. On the left side, under Product and Product Version Selection, select which product and version you want to update from the drop-down menu.

   The product version can only be updated to a higher version. It is not possible to update the product version to a lower version

4. In the Available Systems section, select at least one system in which you want to update the product version. You can also select multiple systems at once

   

5. Click the Update button. Fill in the required details in the dialog

6. Click Schedule

1. Navigate to the “Systems Overview” app in the Landscape Portal

2. Click on the entry for the system that was created for your SaaS application You could identify it from the system description “ABAP Solution System for appname” or via the SID. If a sap_system_name was defined in the configuration of the ABAP solution, systems are provisioned with same SID. If no sap_system_name was defined, systems are provisioned with SID = AST or SID = AMT, depending on whether the solution was created with tenant_mode= single or tenant_mode= multi.

3. Once the update scheduled in the previous step is complete, the “Software” section should reflect the new product version for the add-on

   

4. Under the “Requests” section, you could monitor the update process

To monitor operations processes like add-on update or tenant provisioning in your system landscape

1. Open the “Operations Dashboard” app of the Landscape Portal as a Landscape Portal Admin
2. Use the dropdown to select the system(s) for which you want to monitor operations.
3. The Requests section displays a list of all requests triggered for your systems as well as their current status.
4. In the Active Requests section, you can view all active processes, their request IDs, execution date, systems, and their progress bars
   

When a quarterly platform upgrade of the ABAP Environment is planned for your systems, the “Register Systems for Pre-Upgrade” app of the Landscape Portal allows you to select specific test or development systems for an early upgrade. These systems will be upgraded two weeks before the official roll-out, giving you ample time to test your solution as a provider prior to the actual upgrade.

Only pre-upgrade dedicated test systems. Pre-upgrading development systems or systems used for add-on build could result in issues with minimum platform version determined for add-on product versions.

1. Select the system that you want to register for a pre-upgrade.

2. Click the “Register System” button.

3. Refresh the page by clicking on the Refresh button. The status of your system has changed from “Not registered for pre-upgrade” to “Registered for pre-upgrade”.

4. If you change your mind and want to undo the registration of a system for pre-upgrade, simply select the system and click the “Un-Register System” button.