Skip to Content

SAP NetWeaver Portal Web Resource Repository (WRR)

Your new way to manage your application styling assets


The Web Resource Repository (WRR) is a new feature implemented in SP8 that provides a single storage location for portal application resources (.less files, .css files, and image files). WRR allows you download, upload, view and modify those resources, and then reference them from multiple applications.

The WRR is your easy and new way to modify application assets/resources, without the need to redeploy the applications. The Content Administrator can easily change the look and feel of applications.

Portal mobile framework page (MFP) resources are also stored in the WRR. For more information on MFP, see: Implementing Portal on Device

This fact allows you easily modify or use these resources to brand your portal for mobile devices. For more on this topic, please refer this blog: Easy Branding Using SAP NetWeaver Portal Web Resource Repository (WRR) In this blog you will be introduced to the Web Resource Repository and its advantages.

Where can I find WRR in Portal?

  1. You have been assigned the Content Administrator role.
  2. Log in to portal.
  3. Choose Content Administration -> Web Resource Repository.

What can I see in WRR?

In WRR you can find structured nodes of folders and resources (.less files, .css files, and image files).

MFP resources are also stored in WRR. You can find them in the following folders:

  • Web Resources/Application Branding/
    Contains the resources included in MFP (logo, buttons, icons, css etc.)
    For more info about MFP resources structure, see blog Mobile Framework Page Branding Using the Palette File
    Note: Portal applications that appear under Application Branding have a prefix ‘~’ that allows transporting portal resources between systems.
  • Web Resources/Resources Provided by SAP/Mobile/Application Icons
    Contains application icons which are used in MFP, i.e. for Favorites and Portal Explorer

Important: Never delete the ‘Application Branding’ folder. Otherwise you will need to redeploy Portal Initial Content ( and restart the application.


Why? – WRR advantages

  • A single storage location for portal application resources – allows referencing them from multiple applications, in different ways (reference from code i.e. using WRR public APIs, reference from other Web resource e.g. from css file, reference from portal component using Icon URI).
  • All WRR objects (resources/folders) are saved in the Portal Content Directory (PCD) and are also copied to the file system of the portal server (within the same folder hierarchy, and synchronized with any changes) This allows the consumption of resources at runtime inrelative way (for example: a .css file, which is saved in the WRR, can relatively use a resource, which is also saved in the WRR, by writing in one of its classes: background: url(‘../images/logo.png’)).
  • As in other PCD catalogs, the WRR Catalog also allows a content administrator to perform familiar operations such as Copy, Cut, Find, Open Properties editor, Open Permission editor, Delete resources/folder etc., with additional new operations such as Upload and Download Resources.
  • It is a powerful feature that allows the modification of application assets without the need to redeploy the application.

How? – WRR operations

  • Download single/multiple resources by selecting a resource or folder in the Portal Content Catalog (right-click and choose “Download Resource/s”). A browser prompt will display in which you can choose to open or save the file.

Note: When downloading a folder (multiple resources), the contents of the folder are added to a compressed (.zip) file. The compressed file will have the same name as the selected folder, and contains the folder contents within the original folder hierarchy.

  • Upload single/multiple resources by selecting a folder in the Portal Content Catalog (right-click and choose “Upload Resources”). An Upload Resources wizard appears. Follow its instructions. Use the Browse button and select the file that you want to upload from your local file system.

Note: If you want to upload multiple resources simultaneously, you can add them to a compressed (.zip) file and then upload the compressed file. The contents that will be created in the Portal Content Catalog will have the original uploaded files hierarchy.

  • View single resource – for briefly viewing a resource before downloading it. Select a resource in the Portal Content Catalog (right-click and choose “View Resource”). It will open an operating system application that was set on your local file system to use for opening this type of resource (e.g. Notepad for css file).
  • CRUD operations (copy, read, update, delete) on folders and resources. As in other Portal Content Catalogs, the WRR also provides CRUD operations you can perform on resources and folders, but with some intentional limitations (e.g. copy – is allowed only as copy and not as delta link)
  • Copy ID of resources – for using it as an Icon URI value. See: Configuring the Launcher (Procedure – 5.2.)

Note: in SP8 there is a new way to custom icon for an item: Using Copy ID operation on selected resource in WRR and paste it as a value for the Icon URI property of a portal content.

  • Transport between systems – You can transfer resources between systems by adding the entire Web Resources folder or subset of it to transport packages (EPA files) in the same way as you add other objects to transport packages. For more information, see Adding Content to a Transport Package.

Conclusion & Outlook:

In this blog we’ve introduced the Web Resource Repository which is new powerful feature implemented in SP8. We learn where it’s located in the portal, what it contains, what a Content Administrator can do with the resources that exist there, and the benefit of using it to manage applications assets from now on.

If you would like to brand your portal for mobile devices you can refer this blog: Easy Branding Using SAP NetWeaver Portal Web Resource Repository (WRR)

You must be Logged on to comment or reply to a post.
  • Hi Liran,

    Thanks for this blog.

    Is there any way of changing JavaScript libraries through Web Resource Repository?

    I'd like for example to upgrade JQueryMobile version that is being used on Portal on Device.



    • Hi Marco,

      Thanks for your feedback,

      Sorry, but only less, css and assets files are managed via WRR.

      Scripts (JS, HTML) can be updated only by code (and deploy by portal component)

      Best regards,