Showing posts with label SSO. Show all posts
Showing posts with label SSO. Show all posts
Friday, July 8
Major Facts on SAP NetWeaver Portal Implementation
Whenever you start your work on end-to-end SAP Netweaver Portal Implementation project, there is one question you will. What is that which takes in the Whenever you start your work on end-to-end SAP Netweaver Portal Implementation project, there is one question you will. What is that which takes in the making of a successful SAP NetWeaver Implementation? The required things for successful SAP NetWeaver Implementation would be Usable screens, security, landing pages, rich user experience, stable server landscape etc...
The time for loading the home page or landing page is a major factor that your end users can consider to judge the performance of NetWeaver Portal . The navigation clicks are another important factor which is the number of links that are used to open the required page or an application. Almost every website takes these two factors into consideration.Here comes the role of usability specialist who takes care that the Netweaver has both these factors in favour. Still, mosty 3rd party design firm is used to out sources design documents and wire-frames of the portal page structure.
One other mistake which a portal consultant generally tends to over look is the use of PAM (Product Availability Matrix), which is the most handy tool that helps in hassel free implementation. Few of its features are that it list outs major version dependencies, supported and unsupported features and SP level informations. With the use of PAM, Its advisable to determine the complexity and understand scope of implementation .
Some major facts on NetWeaver Portal Implementation:
Be sure that the homepage images are not heavy.
Use of static pages which consume fewer resources in case you have SSO implemented.
Horizontal scroll bars are best avoided. Minimizing of scrolling effects and scroll bars should be done.
User navigation should be made easy with fewer links.
Make use of cache for improving page load time and performance .
To make it easy for users you can enable help, forgot password links on homepage..
Do not use KM object rendering on homepage whenever possible.
Ensure that server is load balanced and there are properly sized mirror nodes. You can increase virtual memory whenever you have good a RAM.
Excessive use of delta links that navigates deeper in hierarchy to be avoided. Portal renders each object by navigation node. More is the page load time when there are more number of nodes.
While using KM for document management and storage, proper taxonomy should be used. Never stuff documents in a single folder . not more than 50 documents are recommended in one folder.
For the iViews that are relatively slow It is recommended to have iView isolation method as “URL” . This isolation method decreases the usage of portal application thread and eliminates the page load errors .
Hoping that this post would be of some use for smooth and error free end-to-end SAP NetWeaver Portal implementation.
Tuesday, June 28
Single Sign On for Non-SAP Applications
Single sign on is possible for external applications also. By external applications, I mean non sap Application. So the scenario is that a user wants to logon to a non sap application from SAP EP without entering user ID and password. Is this possible? The answer is yes. This is possible by implementing SSO for external usage.
There are 2 ways to implement SSO for external usage.
The Dynamic link library SAPSSPEXT is a very intelligent library. It can extract user id and password from the logon ticket issued by SAP EP. So by using this library logon to external or non sap applications is possible. This library has 2 interfaces viz: JNI Java Interface and a COM(Windows) interface. It is available to be downloaded on the sap service marketplace.
Now suppose you have a non-sap applications which is web based and it supports authentication using a HTTP header variable, Web Server Filter method of single sign on is the best for you. This filter studies the logon ticket using a public-key certificate and tries to extract the name of the authenticated user from the logon ticket. This name is then written in the HTTP header variable. Thats it !
Only few web servers support this method of logon. Some of them are Apache Web Server, Microsoft Internet Information Server (IIS), Sun Java System Web Server.
Subscribe to:
Posts (Atom)