Exposing WSRP iViews on the Producer for
Non-SAP Consumers
Applicable to: WSRP application sharing
Use
Non-SAP portal vendors and the WSRP standard do not support the NetWeaver permission mechanism in the portal and its user management framework. Furthermore. the non-SAP consumer portal may not necessarily be using the same user base as the one used by the NetWeaver producer portal. Nevertheless, you still need to set permissions and configure some iView properties to expose your WSRP-compliant applications to non-SAP portal consumers.
This topic provides portal permission and property configuration guidelines for the content and system administrators on a NetWeaver producer portal exposing WSRP-compliant iViews as applications to a non-SAP consumer portal.
For information on the type of content you can expose through WSRP, see 'WSRP Application Sharing' Mode.
Prerequisites
● You have created a portal user for the consumer (see Creating Users for Non-SAP Consumers).
● A NetWeaver iView representing the deployed WSRP-compliant application exists on the producer portal.
● To set permissions:
○ You have owner permission in the iViews and folders you want to expose.
○ You have access to the Permission Editor in the portal.
● To set iView properties:
○ You have permission to edit iViews.
○ You have access to the Portal Content Studio in the portal.
●
The iViews you are
exposing are WSRP-compliant (refer to
Developing
WSRP-Compliant Applications).
Procedure
Setting Permissions to Portal Content
In the Permission Editor on the producer portal, assign the following users and permission levels to the WSRP content objects and folders you want to expose:
Object (on NetWeaver Producer) |
Target User (on NetWeaver Producer) |
Permission Level |
Description |
Portal component |
Consumer's portal user1 |
End user: enabled |
Assign end-user permission to the consumer's corresponding portal user to the iView's portal component on the producer portal. Portal components are located in the Security Zones folder in the Portal Catalog.2 |
iView3 (or folder4 containing iViews) |
Consumer's portal user1 |
Administrator: read |
Allows all content administrators on the non-SAP consumer to view the iViews to which you assigned permission. |
|
|
End user: enabled |
Allows all users on the non-SAP consumer to execute the iViews at runtime. |
1 Refers to the portal user you created for the consumer (see Creating Users for Non-SAP Consumers).
2 In most cases, there should be no need to modify the already set permissions in the security zone. Most content is assigned to the Low safety level, for which the Authenticated Users group is already given end-user permission. Since all non-anonymous users logged on to the portal belong to the Authenticated Users group, they are already permitted to use this content.
3 iViews must be WSRP-compliant.
4 The folder must be either the folder a sub-folder under it that you already defined as the root folder from which non-SAP consumers receive WSRP content (see Setting the Root PCD Folder for WSRP-Based Browsing).
Configuring the Authentication Scheme in iViews
In the iViews you are exposing to non-SAP consumers, set the Authentication Scheme property to Anonymous Use the Property Editor in the Portal Content Studio to modify iView properties (refer to Property Editor).
Making WSRP-Compliant iViews Available to Consumers
Each iView contains a default property called Expose as WSRP Application, which specifies if the application is WSRP-compliant and if the iView is exposed as an application to a non-SAP (or SAP NetWeaver) consumer portal via the WSRP protocol.
The default value of this property is No, which means that by default no iViews are exposed to any consumer portal connecting via WSRP.
Therefore, for each iView that you want to expose as a WSRP application to a content administrator on a non-SAP consumer portal, a content administrator on the producer portal must change the value of this property to Yes. Use the Property Editor in the Portal Content Studio to modify iView properties.
Additional Tips
● By default, when a non-SAP consumer registers with your portal, the consumer's corresponding user is assigned to an out-of-the-box group, named DEFAULT_WSRP_GROUP. Using this group, you can automatically expose generic content, such as demo applications, to every non-SAP consumer that registers with your portal without having to explicitly assign permissions to the consumer. To do so, assign the out-of-the-box group DEFAULT_WSRP_GROUP to a Portal Content folder containing the generic content.
● If you want to collectively expose generic content to a number of consumers, you could also create your own generic user group, such as WSRP_ALL_CONSUMERS, and assign permissions to it in a Portal Catalog folder of your choice. For example, this folder could be the root search folder you have defined for all non-SAP consumers (see Setting the Root PCD Folder for WSRP-Based Browsing).