Configuring Master Rule collection in Netweaver Portal
December 8, 2008
With the help of the master rule collection which, the portal at runtime analyzes to determine which portal desktop should be displayed to the user and there by determines which contents to display to user. Master Rule collection is on of the main configurations of Netweaver Portal. There are ample of configuration options avaialble like you can configure the master rule for any specific individual user or you can configure it for URL, This means, if user is accessing the URL http://myportal.mycompany.com then upon verifying this URL, light contents should be displayed to the user. Your corporate or internal portal might contents 1000s of users and if we start configuring the master rule for all these users then this configuration will never end and thereby increases the load on the system. So it is better to configure the master rules for URL alias instead of User.
- Go to System Administration –> Portal Display –> Desktop –> Display Rules
|
SAP Netweaver Portal |
System Administration –> Portal Display –> Desktop & Display Rules |
- Expand Portal Content –> Portal Administrators –> Super Administrators
- Double-click Master Rule Collection.
- Choose Add If Expression button.
- Choose Group in the 2nd drop list menu.
- Enter the Group (for example vendor)
- Choose Apply.
- Select THEN Portal Desktop = pcd:portal_content/every_user/general/defaultDesktop corresponding to the If statement you created.
How to implement Single Sign On
November 26, 2008
Single Sign-On (SSO) is a key feature of the SAP NetWeaver Portal that eases user interaction with the many component systems available to the user in a portal environment. Once the user is authenticated to the portal, he or she can use the portal to access external applications. With SSO in the portal, the user can access different systems and applications without having to repeatedly enter his or her user information for authentication.
The portal SSO mechanism is available in the following variants depending on security requirements and the supported external applications:
● SSO with logon tickets
● SSO with user ID and password
Both variants eliminate the need for repeated logons to individual applications after the initial authentication at the portal. Whereas SSO with logon tickets is based on a secure ticketing mechanism, SSO with user ID and password forwards the user’s logon data (user ID and password) to the systems that a user wants to call.
Single Sign-On with Logon Tickets :
Logon tickets contain information about the authenticated user. They do not contain any passwords. Specifically, logon tickets contain the following items:
· Portal user ID and one mapped user ID for external applications
· Authentication scheme
· Validity period
· Information identifying the issuing system
· Digital signature
Download SAP Enterprise Portal Themes
October 21, 2008
Adapting the visual appearance of SAP Enterprise Portal to the customer’s Corporate Identity is very important. The portal is always there; it constitutes the frame in which users work. Designing this frame to effectively convey the company’s management view helps confirm that it recognizes and agrees with certain values.
Using the Theme Editor, an administrator can easily change a few colors, replace the graphics files for some interaction widgets, and create new styles. The styles are then published and can be used throughout the company. However, designing a portal theme is a bit hectic job and usually takes weeks to design full fledge theme. Also EP themes are not like typical wordpress or mobile themes that we get everywhere. But!!!!!! You will get few template themes right here. These themes are designed and configured 100% i.e. every single portal component is designed with the new theme. I think this is a great opportunity for you people to grab these themes and give your portal a new look. I have taken real efforts to present these themes to you. So if you are visitor then kindly register yourself in the forums and get the themes downloaded right away.
SAP ABAP Transaction Variants
September 1, 2008
- L&T Infotech
Many times people get struck with some kind of requirements in their SAP ABAP Implementation projects and do not know how to proceed further. One of such requirement is “Changing the layout of the standard screen”. These changes may include hiding the existing fields, display default values, etc., Here comes the need of Transaction Variants for such type of requirements.
This article will provide you what all we can achieve through the transaction variants, and a link is provided at the end of this article which demonstrates step by step procedure to create a transaction variant with example and screen shots.
Transaction variants are very efficient & simple method provided by SAP for customizing the standard screens according to our business needs and implemented using SHD0 transaction. Transaction variants are actually made up of a set of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Transaction and screen variants may be created for all dialog and reporting transactions. Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).




