Transitioning from the Portal Service to the Launchpad Service – How to Guide
I’m Dana, a Product Owner of the SAP Cloud Portal service (Portal) and the SAP Launchpad service (Launchpad) on the SAP Business Technology Platform (SAP BTP).
In this series of blog posts I would like to share some insights and recommendations to guide you step by step regarding how to move from your existing SAP Cloud Portal service to your SAP Launchpad service with minimal efforts and optimal reuse of your portal investments such as content, user role collection assignments, destinations, cloud connector, HTML5 apps, plugins, custom themes, content providers and more.
Whether you are considering using the Launchpad service in the same subaccount as the Portal or in different subaccounts, this blog post will assist you in understanding what’s the effort required by each alterative. The idea is to maximize the reuse of existing configuration and content, to avoid the need to configure everything from scratch as a result of this transition from the Portal service to the Launchpad service.
! Please note that as the Launchpad service does not support Freestyle sites, your Freestyle sites and content won’t be available in the Launchpad service.
My 3 blog posts cover the end to end process which composed of the following steps:
- A fully configured and running SAP Cloud Portal service enabled
- SAP Launchpad service enabled and configured (please follow initial setup)
- If you developed on the Portal subaccount custom launchpad modules and consumed them as a content provider, you should keep your custom solution in the Portal service; Content consumers can subscribe to/enable your solution and consume its content via Portal service or Launchpad service.
- You should avoid manual content creation before import.
- Define your environment:
- How to move Portal service to Launchpad service in the same subaccount TIP! This option is recommended as all destinations, cloud connector, custom themes, HTML5 apps and user collection assignments are configured in subaccount level, hence, you could re-use them in Launchpad
- How to move Portal service to Launchpad service in the different subaccounts
- Start with the Portal service
- Export Site/s + Content; Export Selected Content
- Export Destinations (Only for different subaccounts)
- Export Custom themes (Only for different subaccounts)
- Move to the Launchpad Service
- Import Destinations (Only for different subaccounts)
- Import Cloud Connector (Only for different subaccounts)
- Deploy HTML5 apps (Only for different subaccounts)
- Subscribe to all SAP/Custom Launchpad modules solution (Only for different subaccounts)
- Add Content Providers
- Import Sites/Content
- Assign users to Role collections (Only for different subaccounts)
- Import Custom Theme (Only for different subaccounts)
- Content import validation
- Run your site/s
- Custom themes
- Move back to the Portal service off-boarding
Important Point: If you want to keep the Portal role collections and re-use them in Launchpad service, you should avoid manually delete the role from portal, you should un-subscribe Portal. this will keep the role collection as they are.