The performance gains from the use of the navigation cache, short URLs and resource-sensitive page builder can be used in any portal implementation.
The light framework page is designed for use in an external-facing portal.
init (), service (), destroy ()
SAP Note 877188 and SAP Note 853509.
SAP provides tools for creating and developing portal content â€“ depending on the target group and the complexity of the applications.One distinguishes between
Portal Content Studio: An administration environment integrated in SAP Enterprise Portal that is used for code-free development of portal content using wizards.
SAP NetWeaver Visual Composer: Model-based development of portal content by simply using graphic tools.
SAP NetWeaver Developer Studio (Web Dynpro perspective): Based on the powerful Web Dynpro programming model, application developers can develop Web user interfaces for professional business applications.
SAP NetWeaver Developer Studio (J2EE + PDK perspective): The SAP NetWeaver Developer Studio offers complete support when developing Java projects.
SAP ABAP Workbench: The ABAP Workbench provides the Business Server Page (BSP) technology for creating Web user interfaces.
All the portal content created using these tools can be seamlessly integrated in SAP Enterprise Portal using the portal services already presented.
Yes. Since navigation links in an external-facing portal include a complete URL that uniquely identifies a specific navigation node, search engines will be able to index portal pages.
However, KM content contained within KM iViews is not indexed.
For further information on how to make your portal searchable, refer to the search engines Web master guides.
The portal user management is very flexible and allows you to use a variety of repositories for storing and retrieving user data. In particular, it allows you to leverage existing user repositories in your system rather than having to set up a new user repository.
For example, if you are using your portal in a system landscape that includes many non-SAP systems, you can provide a central user base using an LDAP directory and configure the portal to use the LDAP directory as its user repository.
On the other hand, if you are using your portal in a system landscape that consists of SAP systems only, you can set up Central User Administration (CUA) on one of the ABAP-based systems and configure your portal to use the ABAP user management as its user repository.
The portal uses the 'User Management Engine' (UME) which is an integral part of SAP Web Application Server Java. The UME manages user and user-related data (roles, groups) which can be retrieved from an LDAP directory, a SAP Web Application Server Java, a database, or a combination of these. Administration tools allowing you to manage users, groups, and roles are integrated in the portal user administrator role. A configuration tool for configuring the UME is integrated in the portal system administrator role.
In addition, the UME provides many features such as self-registration with approval workflow, notification emails, and so on.
get Property (String)
User management is configured just as in a standard portal implementation, except that anonymous users are given access to content.
In an external-facing portal, administrators must do the following:
Typical examples for the integration technology are:
Client Eventing: Enables iViews to communicate with one another at the client side and to communicate with the portal itself.
Work Protect: Function providing an infrastructure for handling unsaved data in portal applications, for example if users navigate in the portal without first having stored their entries in an application.
Session Management: Contains in particular the session persistence to retain the last session status of the user (for example when navigating to another portal page) as well as a server session termination function for releasing resources on the back-end system (for example when closing the browser).
Portal Navigation: SAP Enterprise Portal offers more than simply navigation between individual portal pages, in particular.
Object-based navigation (OBN): It provides users with a navigation feature based on the actual business objects from productive back-end systems.
Drag & Relate: iViews can contain objects representing business elements of a back-end application (for example customer). If users pull such an object, as with Drag & Drop, and relate it to another object in the Drag&Relate target object area, they can navigate between different applications containing similar, but not identical business objects.
Dynamic Navigation: The portal enables you to assign navigation objects to pages and iViews as context sensitive dynamic navigation iViews. This means that navigation targets are provided dynamically depending on the action selected.
Yes, however, the portal will not enjoy the performance benefits from the light framework page. The performance impact from HTMLB is much more significant than from client-side eventing.
String, Date, Select, Boolean.
Portal roles are a central element of SAP Enterprise Portal. They structure the content and are defined for specific end users.
A role is a collection of task-specific content. Roles are defined based on responsibilities and areas of interest, and are created by a role administrator. A user can be assigned one or more roles (for example, the roles employee and staff). The roles define the content of the portal navigation as well as the content of the portal. Role assignment can therefore be seen as a pre-personalization of the portal - a personalization that is performed by the administrator and not by the user (personalization level 1). Depending on their permissions, users can also adjust the look and feel of the portal, maintain user-specific attributes (personalization level 2), change portal pages by adding or deleting iViews (personalization level 3), and personalize individual iViews (personalization level 4).
get Page ();
IPageContext myContext = PageConectFactory.createPageConext(request, responce);
Event = myContext.getCurrentevent();
True, Authschemes.xml is modified to get custom log on component.
Web Dynpro is Sapâ€™s programming model for developing professional and interactive Web user interfaces for business applications.
An iView is a logical portal content module representing a visual application or part of one. One or more iViews are combined on a portal page, which is then assigned to users by the role definition. Web Dynpro UIs are integrated in SAP Enterprise Portal with iViews.
Visualization and business logic are not separate
Development has to take care of different web clients and versions
NamesSpace conflicts with form elements
Property name = “JSP”
Property name = “ComponentType”
Model View Controller
IGroup, IRole, IUser, IUserAccount, IUserMaint.
Level = 1 ----only by browser (java Script)
Content within an external-facing portal must be supported by the light framework page. And in order to get the full performance benefits of an external-facing portal, content should also be “light”.
The light framework page does not support the WorkProtect mode and session termination features.
Therefore, applications that require these features – including Web Dynpro applications – may not operate properly in an external-facing portal.