System Refresh: Impact on mapping of portal roles to UME groups(ABAP Roles)

[Former Member]

Hi ,

We have a scenario here where a system(Backend of portal) is getting refreshed. We would like to know what would be the impact on the mapping of portal roles to UME groups(ABAP Roles). Do we need to perform this mapping one again after the system is refreshed.

We have already exported the user master data and after refresh we will re-import this user master data. Will this re-import of user master bring back the mapping of portal roles to UME groups(ABAP Roles).

Please let us know if any one has faced this issue earlier.

[Former Member]

For clarity (?) you are refreshing an ABAP test system from an ABAP production system, and the ABAP test system is the UME for a test portal environment?

Assuming that your Change Control landscape is intact, your production ABAP system would have additional users but no additional ABAP roles for the UME which do not exist in the ABAP test system already beforehand. If you have custom roles and custom mapping in the portal, then this should be the same as well (transporting the UME roles).

So, you are restoring the user master records and for the same user ID name they will now have the same UME roles as that which they had in production ABAP beforehand, but with the test portal mapping. The mapping is on the portal side; the assignment to the user on the ABAP side.

Or are you refreshing the portal as well?

Perhaps I have completely misunderstood??

Cheers,

Julius

PS: Also if it is a system copy, then you should take care of your various connection data and other things which are "alive" in the background of the system and will start running in your test system as well.

[Former Member]

{For clarity (?) you are refreshing an ABAP test system from an ABAP production system, and the ABAP test system is the UME for a test portal environment?}

Yes

Actual issue is, theABAP role in test system which have the mapping with test portal roles are not the same as in production. The ABAP roles in test system were created in test directly. Now if the refresh is done what will happen to the mapping once we re-import the user master data?

Also portal is not getting refreshed,its just an ABAP refresh.

[Former Member]

> The ABAP roles in test system were created in test directly.

Then they will be toasted in the refresh, unless you export them and import them again as well after the refresh.

Of course a nicer way of doin this is to create them in DEV and transport them as well - then only refresh your test system when all to-be-tested goodies are either imported into PROD as well, or rejected back to DEV... or you have a export/import procedure ready for them as a part of your after-refresh tasks.

Basis should have such a "to do" list anyway for system copies.

Cheers,

Julius

[Former Member]

> ... but with the test portal mapping. The mapping is on the portal side; the assignment to the user on the ABAP side.

Note: This may still differ on the portal permissions side even after you syncthe ABAP UME roles and map the old role name to the new one (in production).....

It might be that to overcome this they created ADDITIONAL roles on the ABAP side. Please check it first in the Java AS. If this is true, then you can export the roles and import them again to give the support users their "testing access" back again.

If they have "hacked" the portal permissions as well, then you have inconsistencies on both sides.

Cheers,

Julius