In this post, we will go over the steps involved in creating an iView from scratch. The detailed description of what all options you have when creating an iView are out of scope for this discussion as typically a security administrator is not likely to be asked to create iViews for a productive system. However, like most other posts on this blog there is enough information to get you started and help you understand what all options are available for a portal developer.
The first step while creating new content (iview/workset/role/page) for Portal is to decide the folder in the PCD where your custom development is going to be stored. On right clicking on the appropriate directory you get the option of creating new content. We chose the option of creating a new iview.
The create iview screen gives you a few options – Create iview from template or for a java webdynpro or for an ABAP webdynpro. Each of these options will have their own configuration options.
In our case we chose the option of creating an iview from an iview template. This in turn opens up a new page with lots more options. For example iview templates are available for BEX queries, SAP transactions, etc.
In the next post we go through the individual steps for creating an iview based on a SAP transaction
Security for Enterprise Portal is based on Portal Roles. Portal Roles are created in the Portal Content Studio and are meant to structure the content displayed to a user on the Portal. Portal Roles are assigned to users through the identity management component of the portal just like UME roles. Multiple Portal roles can be assigned to a user which will impact the display of the enterprise portal for him. We look at structure one of the standard portal roles below
Content in a Portal Role is organized in a hierarchy of folders as shown above as worksets, iViews and pages. The folders in a portal role are called worksets. Worksets can be used across many portal roles. Also there can be multiple worksets under a workset. The lowest level of content are iViews. The screen above gives an example of Portal role in the PCD and the role structure showing both worksets and iviews. Also the same role “Content_Admin” is also assigned to my user id in the system. The top level navigation showing the different tabs like Content Administration > Portal Content> Multiple Property Replacement gives an idea of how a role looks when assigned to a user.
The behaviour of the role or workset can be changed by modifying the property editor settings shown on the far right. Also important is the permissions that can be modified in the property editor settings. An example of the permissions that can be set on the property editor for Content Admin role is copied below.
SAP Enterprise Portal (EP) as a component can only be installed on AS Java. Till now our discussion on AS Java security has exclusively dealt with security using the User Management Engine. We have talked about UME users, roles and groups. However, in addition to UME roles, we can also create roles for Enterprise Portal. Before we start our deep dive into security for the enterprise portal lets take a brief tour of the Enterprise Portal solution.
To a large extent the Enterprise Portal to support display of content on the various corporate intranets (portals) of SAP customers. Thus the security framework for EP is also geared towards display of static or dynamic content rather than on granular security. To look. To get an idea about the look and feel of the Enterprise Portal just log in to the SAP Service Marketplace which is also built on EP.
To create content for Enterprise Portal, you need access to the Portal Content Studio shown below. You would also need access to the content_admin portal role.
Most of the Employee Self Service, Manager Self Service Applications are based on the Enterprise Portal. In addition, EP developers also can create portal applications for displaying BI dashboards, BW reports, webviews for SAP transactions and just simple static pages.
Most clients have a dedicated portal team instead of having security develop applications for portal. But I still feel that having some knowledge of portal is always helpful. Portal development normally starts by accessing the Portal Content Studio through the Portal Content Directory (PCD). Double clicking any content – iViews, Worksets, Roles opens the content in the right hand window for modification.