Migration of SAP Roles to the Enterprise Portal (SAP Library

Migration of SAP Roles to the Enterprise Portal

Use

You can migrate existing single and composite roles with all their contents from the SAP R/3 System to the Enterprise Portal.

The following objects are migrated:

Single roles and composite roles
Role name and title
Description
Logical system of the role
User assignment
MiniApps assigned to the roles
Contents of the role menus, that is the metadata of services (such as SAP transactions, IACs, Web URLs)

The authorizations are not migrated. They remain in the R/3 System and continue to be maintained there. To find out about the relationship between portal roles and R/3 authorizations read Enterprise Portal Roles and User Distribution.

Prerequisites

The role migration tool requires a fully configured system infrastructure. The RFC destinations also have to be set up to ensure a connection from the Enterprise Portal to the corresponding R/3 Systems. The role data is obtained from this system and the corresponding roles and External Services are created in the PCD. Read also Defining JCo Destinations.

All R/3 component systems require that the Enterprise Portal plug-in be installed. Migration is supported for R/3 Systems of Release 4.6x and higher.

Before starting the migration, make sure that the PCD is fully configured. Read also Maintaining Parameters for the PCD. To migrate all the languages of the roles into the PCD, call file text.properties. Make sure that parameter TextMaintenanceLanguage=all is set. Read also Checking the Location of the PCD.

Features

You can define exactly the roles you want to migrate to a specific logical system.

Single roles are created with the corresponding menu hierarchy in the PCD, the same as the metadata of the corresponding External Services (such as R/3 transactions).

Composite roles are also created with their corresponding menu hierarchy in the PCD. The single roles that are assigned to the composite roles are migrated together with the composite role. The menu of the single roles must be read into the composite role. An exception is the migration of roles from a mySAP Workplace system landscape. Read the section further on.

External Services contained in roles are automatically created in the PCD during role migration. This is true for example for the following services: SAP MiniApps, SAP transactions, BEx Web applications, IACs and URLs.

If a role is migrated to the PCD a second time, you can define whether or not the existing role should be overwritten.

Activities

Call the Role Migration entry in the portal from the administrator role.

You see the screen where you can enter the criteria for the migration:

Enter the following data:

RFC destination for the migration.

Role filter, where you can enter the role name generically with '*' (for example SAP Portals_BC*). R/3 roles are only available in uppercase. You should therefore only enter uppercase here.

Decide whether or not existing roles may be overwritten in the PCD.

Decide whether or not the External Services contained in the roles should be migrated from R/3.

Decide whether or not existing External Services may be overwritten in the PCD. Note that this does not work for MiniApps from R/3. Migrated MiniApps are only available as Java iViews in the iView Editor in the Enterprise Portal. Delete MiniApps that were already migrated before migrating again. You can find out how to delete MiniApps or Java iViews in Deleting Java iViews.

Decide whether or not the user assignment should be migrated. Note that only the roles whose validity for the use assignment has not expired (the to-date must be valid) are migrated. The user assignment is then valid indefinitely in the Enterprise Portal.

Decide whether or not the folders on the first level of the menu hierarchy should be marked as entry points for portal navigation. For more information, see Defining Top-level Navigation and Entry Points. If an R/3 role has a large number of folders on the first level of the menu hierarchy, you should only mark the entry points in the Enterprise Portal later on.

Default language: If there is no master language for a role in the R/3 System, the role is migrated in the language that is specified here. If you do not enter anything here, the portal displays the role in the logon language of the portal. Note that only ISO codes are permitted to define the languages.

Choose Continue.

You see a list of the roles that are available for the migration for the given RFC destination.

Select the roles you want to migrate. If you migrate roles with very complicated menu entries, you should not try to migrate too many roles at one time.
Choose Continue. The migration is performed. You can now look at the log file for the migrated objects:

Result

The R/3 roles are now available in the PCD. You can call them from the Role Editor and edit them from there in the same manner as portal roles. You recognize an R/3 role in that it has the name of the logical system as prefix:

The migrated External Services are available in the view area of the Role Editor under object type Migrated Services. You can add these services to roles just like other objects (pages and worksets). Also read Using Migrated Services in Roles and Worksets.

You can restart the migration at any time if it fails.

The PCD understands the letters A to Z (uppercase and lowercase), the digits from 0 to 9 and the special characters "-" and "_" as characters. If the migrated R/3 roles contain characters other than these, they are replaced with hexadecimal code in the PCD.

From MiniApps to Java iViews

Note that MiniApps that you added to the R/3 roles can be found in the iView Editor as Java iViews after the migration. You can find them there in a channel whose name is defined by the logical system and the name of the R/3 role, e.g. QW3CLNT100_SAP_BC_EMPLOYEE.

Proceed as follows:

Using the Page Editor, create a page and assign it your old MiniApps and/or current Java iViews.
Assign this page to the migrated R/3 role in the Role Editor. You have now created the link between the former MiniApps and the R/3 role in the Enterprise Portal.

Migration of Roles from the mySAP Workplace

If you are using the mySAP Workplace, you have the following constellation in your system landscape: Your composite roles can be found on the Workplace Server and your single roles in the component systems. The composite roles contain links to the single roles.

Note that only the menu of the single roles is migrated when you migrate composite roles from the Workplace Server to the Enterprise Portal. The services contained in the single roles are not migrated and stored in the PCD.

You therefore have to migrate the single roles from the component systems separately in order for them to have a functioning role in the Enterprise Portal.