Thousands of customers around the world run SAP Enterprise Portal successfully to provide their employees, customers, and partners a central and intuitive access point to business applications, information, and services. With the public cloud offering SAP Cloud Platform Portal, you can quickly create engaging business sites providing a responsive, web-based access to your business processes and content. SAP Cloud Platform Portal service combines a lightweight, low learning curve of site authoring with the full power of enterprise-grade business process integration and access management.
With the Portal offering on the SAP Cloud Platform, the SAP Portal product directions are following SAP's cloud strategy. SAP recommends adopting SAP Cloud Platform Portal for new projects, and for existing SAP Enterprise Portals customers we recommend considering a transition to SAP Cloud Platform Portal. Transitioning your on-premise SAP Enterprise Portal to the SAP Cloud Platform Portal will provide you a flexible, multi-channel, modern business portal, enabling you to outperform business goals.
This wiki page covers the most important FAQs, that customers might have, who are considering to start with a cloud strategy for their portal scenarios which will also include moving their Enterprise Portal to SAP Cloud Platform.
Maintenance of SAP Enterprise Portal
|When is the end of maintenance of SAP Enterprise Portal?|
SAP Enterprise Portal is following the general SAP NetWeaver maintenance strategy:
For more information, see SAP note 1648480.
About SAP Cloud Platform Portal
|What is SAP Cloud Platform Portal?||SAP Cloud Platform Portal enables lines of business to quickly and easily create and publish secure, scalable and attractive business sites (e.g. extranets for suppliers or partners) by providing a central access point to business content such as applications, reports, web content, videos, and more. SAP Cloud Platform Portal supports Fiori launchpad as an entry point for SAP Fiori apps as well as freestyle portal sites based on Web 2.0 technologies, predefined templates, and extensions.|
|What is the SAP Portal offering of today?|
SAP’s portal offering has evolved from a single product to a portfolio of products available via various deployments options to address your specific business needs.
|How fast is the functional scope of SAP Cloud Platform Portal evolving?||SAP Cloud Platform Portal is evolving quickly and delivering new capabilities based on a bi-weekly release-cycle. Majority of the capabilities you know from the SAP NetWeaver Portal have similar counterparts in the cloud. You may check the roadmap, learning journey and documentation to learn more about available capabilities and upcoming enhancements.|
|Which applications can be integrated into the SAP Cloud Platform Portal?||SAP Cloud Platform Portal integrates SAPUI5/Fiori cloud apps, common on-premise UI technologies: Web Dynpro ABAP, SAP GUI for HTML, Screen Personas and Business Explorer (BEx) as well as to Cloud LoB solutions like Hybris Cloud for Customers and SAP SuccessFactors. In addition, the SAP Cloud Platform Portal can integrate with third-party solutions via URL, Dynamic URL, and API calls.|
Planning the Transition
|What should be done in the planning phase?|
In the planning phase you should start with an inventory of your current on-premise SAP Enterprise Portal content:
This inventory should be documented and be ready for comparison with the applicable solutions in the SAP Cloud Platform Portal.
Ways to transition your SAP Enterprise Portal to the Cloud
|Is it necessary to move your SAP Enterprise Portal scenarios and content completely to SAP Cloud Platform Portal?|
Performing a transition is very customer-specific and depends on the required use cases, used portal capabilities, business requirements for the new portal, and your cloud strategy. There are options for a full or partial transition with a hybrid approach.
If customers are not yet ready to completely embrace the cloud-based portal service due to complex on-premise scenarios or unsupported applications that will require some re-development, they can take the first step in direction of the SAP Cloud Platform Portal with a hybrid portal approach. They can keep their on-premise Portal and create a hybrid environment with SAP Enterprise Portal as a content provider for SAP Cloud Platform Portal and bypassing a full transition.
In cases of complex on-premise portals we recommend planning a transition to the cloud as a gradual move in a scenario-oriented approach. You could start for example with the external facing Portal scenario (supplier portal, dealer portal) etc. and later implement the Employee Portal scenario. Check again the Portal deployment guide which outlines the recommendations for typical Portal use cases.
The transition of Applications and UI Technologies to the Cloud
|Which UI technologies are supported on SAP Cloud Platform?|
The SAP Cloud Platform Portal is built upon two architectural principals. First, we have the Fiori Launchpad that has the same standard and look/feel as the on-premise Fiori Launchpad. These UI technologies are based on Fiori, the tiles, and the home screen.
Secondarily, we have the SAP Cloud Platform Portal - freestyle edition that is based on a responsive Web 2.0 technologies. A rich set of widgets allow you to build out a consumer-grade portal.
To easily modernize user experience, it is recommended to use standard SAP Fiori Cloud applications when available. These can be integrated into to both the Fiori Launchpad or the freestyle edition. A list of available standard Fiori apps is available from the Fiori Apps library.
You should also consider developing frequently used custom apps as SAP Fiori/UI5 apps.
Some UI technologies such as Web Dynpro ABAP, SAP GUI for HTML or SAP Screen Personas are supported and can be integrated into the cloud. In such cases, the runtime remains on the remote system. Read also Working with Backend Apps.
Which UI technologies are not supported on SAP Cloud Platform?
Usage of Web Dynpro Java (e.g. custom development) or HTMLB is not supported. It this case a redevelopment to the supported cloud technologies would become necessary. Also, capabilities such as OBN or dynamic runtime URLs are not supported.
If you prefer to avoid a redevelopment, the scenario "Use SAP Enterprise Portal as a content provider for Cloud Portal" would be a solution for you during the period of developing a new strategy for the unsupported technologies. In this case, you keep your SAP Enterprise Portal, the on-premise apps are exposed and can then be added to a launchpad site on SAP Cloud Platform Portal.
|What is important to know about SAP UI5 ?||SAP UI5 applications can be integrated directly into SAP Cloud Platform Portal. They are deployed directly to the SAP Cloud Platform HTML5 applications repository within a subaccount and can then be consumed in a portal site. If you are migrating your SAP UI5 applications from an on-premise server, e.g. an SAP Netweaver ABAP, it is recommended that you use SAP Web IDE to migrate the applications to SAP Cloud Platform.|
|What is important to know about SAP classic UI technologies, which are hosted on SAP Netweaver ABAP servers?|
SAP classic UIs include SAP GUI, Web Dynpro ABAP, and Business Server Page (BSP) applications. These UI technologies, which are hosted on SAP Netweaver ABAP systems, can be integrated directly with SAP Cloud Platform Portal by creating a connection between their on-premise host system of the application and the SAP Cloud Platform Portal. This is done by creating a destination in the SAP Cloud Platform Subaccount that points to the respective backend. You can choose to expose these UI technologies from the internet or only make them accessible within your intranet. This is determined by the access type, which can be set to either external or internal.
This table shows the UI technologies and how you can consume them in the cloud:
|UI Technology||How to transition to cloud||Running in-place|
|Web Dynpro ABAP|
|SAP Screen Personas||integrate or|
|SAP GUI for HTML|
|BI Java Reports (BEx)|
|Web Dynpro Java|
Re-develop in SAPUI5 or
Integrate (via URL)
Re-develop in SAPUI5 or
Integrate (via URL)
Re-develop in SAPUI5 or
Integrate (via URL)
Re-develop in SAPUI5 or
Integrate (via URL)
SAP Enterprise Portal Components and Functions and their Counterparts in the Cloud
Universal Worklist Workflow support?
Universal Worklist is an SAP Enterprise Portal component that allowed users to see the tasks they needed to work on and had to complete. For example, approve a leave request or other transactions. Universal Worklist has been replaced with the Fiori My Inbox application in the cloud that allows for the display of notifications and tasks that needs to be completed by the user. For more details about how to migrate from Universal Worklist (UWL) to My Inbox go to SAP Note - 2538184.
Workflow is an old concept in SAP and Fiori applications support workflow as it is configured in the backend systems. This is, of course, supported when executing the Fiori Applications in the SAP Cloud Platform Portal. In addition to the backend or LoB application's workflow SAP Cloud Platform has a workflow service that is supported and can be used in the SAP Cloud Platform Portal. An example of this would be self registration and approval before allowing a newly self registered user to access the portal.
|SAP business packages and pre-packaged content?|
With SAP Fiori Cloud and its pre-packaged SAP Fiori apps for SAP Business Suite and SAP S/4HANA, SAP provides a rich set of out of the box apps that can accelerate your transition to cloud. This pre-packaged, cloud-based business content is delivered for various lines of business and customers benefit from automatic updates and maintenance of the frontend UI parts. Check the available applications in the SAP Fiori Reference Library.
Existing SAP EP business packages cannot be consumed if they are Java based. Web Dynpro ABAP can be integrated (see the section: How to transition UI technologies). You can also use EP as a content provider scenario to be still able to use your existing business packages.
In addition, the SAP Cloud Platform Portal comes with pre-defined templates or starter portals that can give you a boost on creating your portal but these pre-defined templates do not contain the applications, but rather a shell for you to get started with.
|SAP Knowledge Management?||SAP Document Center is available as a SAP Cloud Platform service, and it can be used as a cloud-based document management solution. If advanced document management capabilities are required, such as auditing, versioning and other capabilities, you may move to a third-party document management tool such as SAP Partner Egnyte and their offering Egnyte Connect. They also offer a migration tool to support the migration of Knowledge Management content from SAP Enterprise Portal to the cloud.|
|Collaboration / Wikis / Forums?||SAP JAM is the collaboration tool of SAP. You may use SAP JAM for blogs, creating a knowledge base and posting questions and collaborate with end users. SAP Jam is delivered as an on-premise solution and as a cloud solution so it gives you the freedom to also migrate and move these capabilities to the cloud.|
|Web Page Composer?||SAP Cloud Platform Portal offers web content editing capabilities including a rich out of the box widget gallery, the ability to write custom web content widgets and a dedicated tool for web content editing. |
Customers can also implement advanced Web Content Management through the partnership with Contentstack, that offers headless web content management capabilities.
|UI Theme Designer?|
Customers can brand SAP Cloud Platform Portal sites using the UI theme designer on SAP Cloud Platform to update all colors, corporate brand, fonts, and more. Advanced branding can be done by updating the CSS.
|Reports integration?||SAP Cloud Platform Portal can integrate with Fiori analytics tiles and Bex reports. Additional reports can be integrated via a simple URL integration.|
|Development Environment?||You can use SAP WEB IDE to develop new SAP UI5 applications including Fiori Apps, page themes and portal widgets. In addition, you can use Eclipse for classic java development.|
|What happens with the SAP Enterprise Portal navigation (L-shape) in SAP Cloud Platform Portal?|
You might be familiar with the traditional L-shape navigation, which can be used for a complex role structure in SAP Enterprise Portal. In addition, the Fiori Framework Page was also introduced to SAP Enterprise Portal in order to renovate Portal UX according to modern SAP Fiori design.
In addition, there are freestyle sites, which are also based on templates. The templates are either provided out-of-the-box from SAP or they may be created by your developers in SAP Web IDE. You can also use a mixture of freestyle and SAP Fiori launchpad sites.
Depending on the selected UX approach of launchpad or freestyle sites, you have to define the relevant content and permission structure. The best practice is to simplify current information architecture to fit modern UX approach and achieve a more intuitive portal with easy to consume content hierarchies and navigation.
Migration of Some Portal Content Types and Knowledge Management
|Is there a migration tool supporting the migration of SAP Enterprise Portal content to the cloud?|
SAP Enterprise Portal offers a migration tool to support the transition process (this tool is valid for SAP NetWeaver 7.3 and higher). This migration tool can be downloaded from SAP Software Download Center and it supports the following iViews types: Web Dynpro ABAP, SAP GUI Transaction, BEx Web Application, and Web-Based URLs. In addition to iViews, the migration tool will migrate the roles and system objects used in the folder structure you would like to migrate.
|Is there a migration tool that supports migrating KM repositories, documents from KM and the metadata from KM?||SAP Partner Egnyte supports the migration of Knowledge Management content from SAP Enterprise Portal to the cloud. Learn about the partnership of Engyte and SAP. Watch this video showing how KM content is migrated from SAP Enterprise Portal to SAP Cloud Platform Portal.|
SSO on SAP Cloud Platform?
|How does SSO work on SAP Cloud Platform?||For a cloud only landscape our recommendation is to use SAML 2.0 for identity federation, for more info go to Configure Trust to the SAML Identity Provider.|
Customers can use any SAML2 based Identity Provider (IdP) to authenticate users who are accessing SAP Cloud Platform Portal. Trust needs to be configured between SAP Cloud Platform and IdP for SSO to work.If you use an on-premise user store such as SAP Single Sign-On or Microsoft Active Directory, go to Identity and Access Management and Connectivity Service - HTTP Destinations, to learn more about the different options to configure your SSO.
Can I use my existing user stores in Cloud Platform Portal? Do I need to migrate users to the cloud?
|Customers can use their existing user stores (like Active Directory, LDAP etc) when working with CPP. There is no need to migrate all the users to the cloud. If you have an existing on-premise user store, you can configure Identity Authentication service to use the corporate user store. This integration allows users to authenticate with their corporate credentials from the corporate user store, without the need to use another set of credentials for their cloud access. Learn more about this scenario in SAP Documentation about Corporate User Store.|
|Is there still a role-based access in SAP Cloud Platform Portal?||SAP Cloud Platform Portal has a simplified role-based authorizations concept that allows managing user access permissions at site and page levels. The user authentication process determines the assigned groups in the Identity provider and maps the relevant SAP Cloud Platform roles to the end users, thereby enabling them to see the relevant pages/apps on the portal site.|
Authorizations are always maintained in the respective backend system as PFCG roles. SAP Cloud Platform Portal provides options to determine which authorizations are required to run back-end content from the SAP Fiori launchpad on SAP Cloud Platform, see also on SAP Documentation.