cancel
Showing results for 
Search instead for 
Did you mean: 

Merging 2 roles

Former Member
0 Kudos

Hi all,

Trying something fairly simple here, i'm merging 2 roles which have the same navigational structure, except the second role is complementing an additional item to role 1 (more advanced user).

Problem is, as soon as those get merged, and I log in with the respective user (with the 2 roles) the portal it seems doesn't know which one to display first and the navigation stays unselected and an error is displayed.

I recall having this problem in the past and it had to do with the fact that each role has a defined Entry Point, but I don't recall the solution.

I've set priority on the entry points to be different. One is 100 the other is 40 but it makes no difference..

Anyone recall troubleshooting this ?

++

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks for the link George, eventhough I had not looked at that specific document, I did follow the same logic in my definitions.

Detlev, this is the java error displayed in the content area instead of the first node (page) of the merged result :

-


Portal Runtime Error

An exception occurred while processing a request for :

iView : pcd:portal_content/com.bd/desktops/BDDesktop/frameworkPages/frameworkpage/com.sap.portal.innerpage/com.sap.portal.contentarea

Component Name : com.sap.portal.navigation.contentarea.default

com.sapportals.portal.pcd.gl.PcdGlContext.

-


If I would then look into the portal_logger I see the following java exception :

-


com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component

Component : pcd:portal_content/com.bd/desktops/BDDesktop/frameworkPages/frameworkpage/com.sap.portal.innerpage/com.sap.portal.contentarea

Component class : com.sapportals.portal.navigation.workAreaiView

User : BDMKTPLN

at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:863)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:143)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:325)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:337)

at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)

at java.lang.Thread.run(Thread.java:479)

Caused by: java.lang.ClassCastException: com.sapportals.portal.pcd.gl.PcdGlContext

at com.sapportals.portal.pcd.pcm.roles.RoleNavigationConnector.getNodes(RoleNavigationConnector.java:225)

at com.sapportals.portal.navigation.NavigationService.getNavNodesByConnector(NavigationService.java:477)

at com.sapportals.portal.navigation.NavigationService.getNodes(NavigationService.java:452)

at com.sapportals.portal.navigation.NavigationEventsHelperService.getNavNodesListForPath(NavigationEventsHelperService.java:277)

at com.sapportals.portal.navigation.workAreaiView.doContent(workAreaiView.java:88)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:143)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:325)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:337)

at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)

at java.lang.Thread.run(Thread.java:479)

com.sapportals.portal.prt.connection.ContentExceptionHandler@57fafa #

-


The portal is an SP2, I think the problem does not occur on NW04 portals, though I need to test that to be absolutely sure.

detlev_beutner
Active Contributor
0 Kudos

Hi Dimitar,

on what PatchLevel are you? Comparing against my P34 code, the code in the corresponding class has changed at least a bit, so if you are on a lower version, upgrading to P34 or 35 might help. Give it a try...

Hope it helps

Detlev

Former Member
0 Kudos

The portal was patch 1 ! Upgrading to patch 2 already solved the issue, thanks for the tip Detlev.

Cheers

detlev_beutner
Active Contributor
0 Kudos

Hi Dimitar,

> thanks for the tip Detlev

You're welcome. Please consider rewarding points for helpful answers on SDN!

Thanks in advance

Detlev

Former Member
0 Kudos

Hi Dimitar,

Try out this link.. It will be helpful...

http://help.sap.com/saphelp_nw04/helpdata/en/53/89503ede925441e10000000a114084/frameset.htm

Regards

gEorgE

Former Member
0 Kudos

Dimitar,

Have you set merge ids for the contents of the roles being merged?

Steve

Former Member
0 Kudos

Sure, normally it's necessary to set merge IDs on the visible elements (entry points) only. As this gave me back that error, I actually tried and set merge IDs on every object, including the iViews. Same.

detlev_beutner
Active Contributor
0 Kudos

Hi Dimitar,

> the navigation stays unselected

> and an error is displayed

What kind of error? Referring to the logs? If yes, additional information from the logs?

Best regards

Detlev