Skip to Content

The SAP Portal has the capability to assigned a portal desktop to a user based on the several aspects like group, user ID or the URL used to access the portal. To give the end-user not only a different desktop but also a different navigation based on the assigned desktop you can use the filter ID feature. This gives the content administrator control over what the user can see. For instance, he can use this feature to enable / disable certain navigation points. An employee accessing the portal from outside the company won`t be able to see the same links as when being inside the company. These way users can get an adjusted navigation based on their location or the device used. In this blog I will show how to configure your portal so that a user will have a navigation based on the URL alias.

Assume your portal users are accessing the portal via the portal URL /irj/portal. You now want to differentiate between internal users and external users. To do so, the users will access the SAP Portal by 2 different URLs*:

URL:

/irj/portal/internal

image

URL:

/irj/portal/external

image

(*The task for assigning the user to the correct URL should be of the proxy, firewall or VPN)

To achieve this behavior you need to carry out some configuration on the portal:

  1. Activate the filtering feature
  2. Configure the portal URLs
  3. Create the desktops
  4. Assign URL to desktop
  5. Assign entry points to desktops

1. Activate the filtering feature
The filter URL feature allows you to assign an entry point an ID and associate this ID to a desktop. The desktop will only show the roles with that ID (therefore: Filter ID). SAP Help. The parameter that has to be enabled is: FilterbyDesktopView.

image

This service offers more interesting configuration properties like:

  • ContentArea
  • InnerPage
  • SortTypeOfInitialNodes

2. Configure the portal URLs
Create the URL aliases for internal and external access. This is done on the filesystem for your portal. You have to modify the web.xml of the portal (IRJ). The web.xml can be found at:
/netweaver/sap/SID/INST/j2ee/cluster/serverN/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/web.xml
Insert the following configuration:

For the internal URL

portal/internal
anonymous=0,proxy=0,low_bandwidth=0,include_in_url=1,include_application_name_in_url=1

For the external URL

portal/external
anonymous=0,proxy=0,low_bandwidth=1,include_in_url=1,include_application_name_in_url=1

Restart you portal. Afterwards you have two more URL aliases that users can use to connect to your portal.

3. Create the desktops
As the desktop is responsible for filtering the entry points, you need to create a desktop for each Filter ID. For the external users, create a desktop and assign the filter ID “External”. You need to create a desktop for the internal URL also (Filter ID: Internal)

image

4. Assign URL to desktop
The new portal aliases (created in step 3) can be used in the portal rules to assign a destop.

image

5. Assign entry points to desktops
For external and internal users there are different roles:

image

Filter IDs work on entry points. To assign an entry point to a desktop it is necessary to configure the property Filter ID.

image

This filter ID assignes the entry point (folder) to the internal desktop. The user in this example works normally in the office and occasionally is a road warrior. Therefore, he has both roles assigned:

image

When the user now accesses the portal using http://server:port/irj/portal/external he will get presented with the entry points for external users:

image

To report this post you need to login first.

10 Comments

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

  1. Owen Carnes
    I just implemented these things last week, but there weren’t any good instructions out there like you have provided!

    We are using this for several of our companies to have “their own portal”, even though they are technically using the same portal instance.  Now overlapping users can still log into both sites and receive different content based on the URL they navigated to.

    One question I have Tobias:
    We are accessing the multiple URLs through external access using Web Dispatcher.  For example: http://www.companyone.com and http://www.companytwo.com.  If we map these URLs to redirect to http://www.companyone.com/irj/portal/urlalias1 and http://www.companytwo.com/irj/portal/urlalias2, will we still be able to use the URL Alias feature to filter the portal desktops?

    Thanks,
    Owen

    (0) 
    1. Tobias Hofmann Post author
      Owen,

      the URL alias rule applies for the portal/[alias] part, not for the FQDN. As long as the user uses the right alias, this will work.

      But when you are already using different companies, you can also filter on role or group of these users. Filtering on one of these properties also means that the user can use the same URL to connect himself to the portal.

      br,
      Tobias

      (0) 
  2. Nathan Yaa
    I followed this blog,when finished there is a litter problem.

    I have 2 url :
    /irj/portal/pes
    /irj/portal/pd

    when I logon,the navigation is filter.the different url see different navigation .

    but the iview in Content Area is always display
    the first role’s iview!

    did you have this porblem?
    how can i do something?
    thanks

    (0) 
    1. Owen Carnes
      I have the same issue when accessing the filter ids with an anonymous user.  I think it is due to me having a custom layout built.
      (0) 

Leave a Reply