Skip to Content

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.

The maintenance of SAP NetWeaver Java ends officially in 2024, which gives customers still some time to consider about their Portal strategy.

We observe that more and more customers already consider to move their on-premise Portal to SAP Cloud Platform Portal, which allows to create engaging business sites providing a responsive, web-based access to your business processes and content. Transitioning the on-premise SAP Enterprise Portal to the SAP Cloud Platform Portal will provide customers a flexible, multi-channel, modern business portal.

In this blog I would like to make you familiar with the Portal Content migration tool that supports the transition to the cloud. Note that there is not this “one and only” tool that migrates your on-premise Portal completely to the cloud. The transition is a complex project depending for example on the analysis of customers’ current on-premise SAP Enterprise Portal’s content, UI technologies and functionalities that are used. Depending on the outcome of this analysis the solution might result to recommend a hybrid approach instead of a complete migration to the cloud.

The Portal Content migration tool is valid for SAP Enterprise Portal on 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.

This is the process for Portal administrators:

  1. Download the Portal Content Migration tool from SAP One Support Launchpad

2.  Export Portal Content from SAP Enterprise Portal into an mtar.file
The file comes with a standard CDM (Common Data Model) structure, and includes all roles and their assigned iViews in a flat structure. The tool extracts the content from a selected folder in the Portal content hierarchy. The folder can be an existing folder or a new folder you prepared for the migration. iViews that are not assigned to a role can also be exported and are mapped to a general role.

3. Import Portal Content to SAP Cloud Platform Portal
You can do this via the site directory in SAP Cloud Platform Portal, which creates a new site. You can also import via the Transport Manager service on the SAP Fiori configuration cockpit to an existing site. During import each role is mapped to a catalog and each iView is mapped to an app in the SAP Fiori launchpad configuration cockpit.

4. After the import is done you have to do some general configuration for the Portal site what was created. You can then preview and publish the site, which contains the former Portal content as apps on a SAP Fiori launchpad site.

Watch this video, which shows the complete migration process:

For more information about the Portal Content migraton tool, see also the relevant section in the SAP documentation.

For more information about transition to the Cloud, read the blog Pack your stuff, let’s move to the cloud and check out this webpage.

 

 

 

 

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Vinod Patil

    Hello Vera,

    Thank you for blog and introducing this migration tool  it will save some effort

    Many Customers are still using – Custom Portal Applications (Abstract Portal components), J2EE applications, ESS MSS based on WD Java, UWL, Guided Procedures. They will have to find alternatives to all these applications during migration.

    Is there any integration between Cloud Portal and BOBJ?

     

    Regards,

    Vinod Patil

     

    (0) 
    1. Vera Gutbrod Post author

      Hi Vinod!
      Yes, you are right there are content types that can be integrated (=runtime remains on the remote system on-premise or cloud) easily into Cloud Portal such as Web Dynpro ABAP, Web Dynpro ABAP, SAP GUI for HTML, BEx reports, BSPs. Applications however such as Web Dynpro Java or HTMLB need a redevelopment in SAP UI5. It is always necessary to make a detailed analysis of the customer’s landscape of content types and UI technologies and then make a plan how the migration could bel done. It is not possible to give a general recommendation which fits for all customers.

      UWL for example can be migrated to My Inbox. For more information, go to SAP Note 2538184.

      In case the redevelopment would need a big effort, it is always possible to use Enterprise Portal as a content provider for Cloud Portal. This a hybrid scenario for customers who are not planning a full migration.

      Concerning BOBJ, I have to ask some other experts in our team, I will come back to your question, when getting an answer.

      Best regards
      Vera

      (2) 

Leave a Reply