Skip to Content
Author's profile photo Aviad Rivlin

Leverage existing SAP NetWeaver Portal content in Enterprise Workspaces

Hello All,


In the coming few weeks, we would like to share with you some more information about SAP NetWeaver Portal, enterprise workspaces via a series of SDN blog; one topic per week.

This week we would like to start the blog series and answer the common question: How can I leverage existing SAP NetWeaver Portal content in Enterprise Workspaces?


Let’s start with understanding where do modules (our new name for the applications running within the workspace) come from:





















Now, let’s have a deeper look into the most common scenario used by customers: re-using existing SAP NetWeaver Portal content within Enterprise Workspaces.


In order to create an Enterprise Workspaces module based on an existing iView, the Enterprise Workspaces content administrator should follow the following 4 steps (that’s it, four steps and we are done!):


1.       Select the iView from the PCD tree

Within the Module Templates page, select the option to create a new module template from the portal content and select the iView you would like to re-use from the PCD tree.



2.       Provide the general properties required for the module such as, name, description and  icon

The next step is to set the general properties required for the module template. The name is inherited from the iView name, and you should go ahead and add the description, the icon which resembles the module, the availability of this specific module for Personal workspaces, Shared workspaces or both, and so on.


























3.       Set additional properties for the module [optional step]

In the third step, the content administrator should set the additional parameters of the module. For example: exposing a specific parameter to the end users (such as transaction ID in case of a module pointing to an SAP transaction).


























4.       Set the permissions model of the module

In this step you should define the permission model of the modules. In order words, which users will be able to use this module in runtime. You can assign permissions to a specific user, to a group of users (out of the UME repository) or the set of users assigned to a specific portal role.


























That’s it, we are done! The module is ready to be used by the end users. Let’s have a look at the module in runtime:






Next week we will talk about Personal and Shared workspaces. See you then…




Aviad Rivlin

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      Grate Blog. The UI of EW looks very promising. I would like to confirm the upgrade path or method to EP/EW 7.3 from NW2004s SP05? is this achieved with SAPEPHi or simply an sda file on sdm/jspm?
      Author's profile photo Aviad Rivlin
      Aviad Rivlin
      Blog Post Author
      Hi James,

      The Enterprise Workspaces installation is done with the JSPM tool on top of NetWeaver Portal 7.0 EhP1 SPS5 (this is the minimum version).


      Author's profile photo Former Member
      Former Member
      Hello Avaid,

      SAP might consider doing a serious of how-to videos on a dedicated channel on YouTube, just like the other SAP BOBJ products.

      Given the relevance and applicability of EWS to a lot of customers these videos will prove to be extremely important.

      Just some thoughts..


      Author's profile photo Tobias Hofmann
      Tobias Hofmann
      The iView creation wizard looks really nice, can't wait see the new portal.

      About "leverage existing SAP NetWeaver Portal content":
      - Can I also create pages/worksets that will get integrated as-is?
      - How about remote content (FPN, WSRP)?
      - How will the content be integrated? iFrame, AJAX?
      - Any dependencies due to EHP / SPS differences?

      br, Tobias

      Author's profile photo Former Member
      Former Member
      Hi Aviad,
      Great blog. The info on EWS is good. Quick question.

      What is the feasibility of implementing and sharing of EWS in a FPN scenario with different versions of EP. For ex. having EP 7.0, EP 7.01 and so on ?