cancel
Showing results for 
Search instead for 
Did you mean: 

Portal Alias + Master Rules + Portal Desktop + Filter Entry Points

Former Member
0 Kudos

Hi

We have a single Portal Installation, but we need to have different Portals for different companies of the same group, so we decided to use Portal Alias, this way we can apply different rules (Portal Desktop) depending on the alias (unfortunately the SAP Portal does not support ServerName as a property), and also filter the TLN entry points (once the same user can access different portals, but depending the portal he is navigating, we should only get the entry points of that portal).

The problem starts when inside the same Browser session, the user decides to jump from one portal to another, at first jump, everything looks ok, the change of portal theme, the framework and the TLN, but if the user decides to jump to another portal or to the first one, at some point, everything starts to get mixed, the theme and framework from one portal and TLN with entry points from all visited portals.

Anyone has an idea how can this be fixed?

To test the scenario just follow this steps:

- Create two Portal Alias (portal/sitea and portal/siteb) in web.xml;

- Create two different Portal Frameworks, for one of them, put TLN with a single level;

- Create two Portal Themes, different colors to get the difference when testing;

- Create two Roles, one for sitea and another for siteb and add some pages (different) to them. For the entry points of the role of sitea, add to the filter property the value "com.sitea" and for siteb entry points "com.siteb";

- Create two Portal Desktops, add the framework and theme of each site and specify the respective filter value

- Add two expression to master rule, using portal alias of each site and the respective portal desktop;

- Create a test user, for example "John", add both roles to the user;

- Access sitea http://www.server.com/irj/portal/sitea --> should work ok (correct theme, correct framework, correct TLN entry points);

- Inside the same browser session, change the url to http://www.server.com/irj/portal/siteb --> sometimes it works fine for the first change, so change to sitea again (inside the same browser session), and suddenly everything starts to get mixed.

Thanks & Regards,

John

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi John ,

You may also want to take a look at SAP note # 1423758 . I am curently facing a similar issue at my end . Upgrading to PL3 for SP19 did not help my cause . After upgrading, you also need to disable caching at the Load Balancer level (in case you are in a clustered environment) . Please do post the solution once you resolve , as even I am in search of it .

Regards

Mayank

Former Member
0 Kudos

Hi John,

this sounds like the behaviour described in OSS Note 1162644. Have a look and check whether your are using a Portal version that is affected.

Regards,

Tanja

benjamin_houttuin
Active Contributor
0 Kudos

At my before-last customer we had the same issues as described by John.

Reading the OSS Note 1162644 as mentioned by Tanja, I think its definitely the solution.

Kudo's for Tanja

Cheers,

Benjamin

Former Member
0 Kudos

Hi Tanja and Benjamin,

After reading the OSS note 1162644, it sounds it is the solution to the behaviour described, and in fact our current Portal release is 7.00 SPS17, bellow from 7.00 SPS19, where the issue starts to be solved.

We are planning an upgrade for soon, hope it solves our problem.

Thanks for your help.

Regards,

John

chintan_virani
Active Contributor
0 Kudos

Check below blog and see if it helps.

[Filtering navigation by desktops|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13178] [original link is broken];