Internet Explorer 8 suffers from compatibility problems with Web
standards such as CSS, HTML4 and XHTML, according to the results
of The Web Standards Project's Acid Test 3.
The Acid 3 test for compatibility ensures that the browser works well with technologies such as CSS, HTML4 and XHTML. However, the test reveals that IE8 falls far short of scores delivered by other new browser software from Google and Mozilla
Microsoft Corp is boasting about the performance speed of the IE8, but the new browser remains the slowest of the top five on the market.
According to the test findings (which appeared in Computerworld) Google Inc's Chrome led all browsers in the SunSpider tests, making it more than four times faster than IE8. Second was Mozilla Corp's Firefox 3.0.7, followed by Apple Inc's Safari 3.2.2 for Windows and Opera Software's Opera 9.63.
Firefox proved to be 59 per cent faster than IE8, while Safari was 47 per cent faster. Opera, the slowest non-Microsoft production browser, was still 38 per cent faster than IE8.
Walt Mossberg, the personal-technology columnist for The Wall Street Journal, criticised IE 8's performance in an All Things Digital post, "Microsoft claims IE 8 is very fast, but in my tests, speed and performance were its worst attributes. Using two computers, one running Windows XP and one running Windows Vista, I timed the loading of a half-dozen popular Web sites, plus two folders containing numerous news and sports sites. I repeated the test in IE 8, and in Firefox, Safari 4, and Chrome. In every case, IE 8 loaded the pages and folders more slowly than most of the other browsers, and in most cases, it came in dead last."
IE8 beefs up protection against malware and known phishing scam sites. However, the new browser suffered its first hack just days after its official launch (along with Safari and Firefox browsers).
At a security conference last week in Canada, a hacker exploited a security hole in Microsoft's new Internet Explorer 8 in under two hours, taking control of a Sony laptop running an internal build of Windows 7.
I am going to give a typical SAP professional answer : IT DEPENDS !
well ...all jokes apart looking at your siutaion, since you already have a add-in installation or what some people call it dual stack system to run ESS in your company here is my advice :
you will face some disadvantages especially when restarting the dual stack system as you have to wait for java to completely start and only then wait for the ABAP stack to restart as well....I mean it becomes very difficult to restart ABAP quickly. a dual stack system is ideal for solution manager and in my recommendataion and experience DO NOT use this on the portal environment. consider a scenario when in future your CIO decides to have the user management by the desktop folks who only use active directory and do not wish to give them SAP access since a dual stack system uses SU01 to lock/unlock users on the portal it becomes quite a nightmare to move to the active directory as your UME....with the central system with AS JAVA only you can have the benefit of choosing ABAP or JAVA initially while installing the system and then doing the right choice of picking JAVA and then moving the UME to the active directory. it also makes things simple when you have SSO with SPnego when a user logs on to the portal and he single signed on and if his password changes on the network he only needs to call helpdesk and change his password which makes life easy.....versus having a dual stack system where ur user management is tied to the ABAP system and you will be left wondering how to resolve the user lock and unlock issues !!!
since you already have this scenario and you plan to do a BI Portal integration use a central system with usage types AS JAVA , EP, EPC. I understand that this is more expensive since you will now have 2 portal systems, but this again DEPENDS if you have a FPN with the producer and consumer portal synchronization is best suited using a central system and NOT the dual stack system.
again there is downside to this as well.......you have to ensure that the service pack for BI JAVA and EP are the same and if there is some patching to be done there will be severe downtime in both the environments and that is something most companies frown upon......but this is something to keep in mind...the key in integrating BI and Portal is the memory and you have to make sure sizing is done correctly along with the memory usage on the BI reports as well as sufficient load balancing in terms of defining how many server processes are necessary to run it efficiently ....there are certain notes that i can guide you...723909 - Java VM settings for J2EE 6.40/7.0 and Note 1044330 - Java parameterization for BI systems
so in the end it depends on the number of users using ESS and number of users using BI reports.......but I would still go for a brand new server (Central system with Java only and AD as your UME) and avoid the dual stack system....
Ways to control this situation and RISK factors
The &SAP_EDIT is controlled via auth object S_DEVELOP…..Look for DEBUG: Debugging (activity 01=system debugging, 02=replace in ABAP/4 programs, 03=debugging for ABAP/4 programs) and remove the values 01, 02 and 03 from this auth object. Read all about security restrictions here
RISK FACTORS:
Lets assume u have access to the command and can access SE16N, What could go wrong ?
Updating SAP tables directly has always proven expensive to any company especially with the amount of downtime as the tables are interrelated and unknown error messages will cause more confusion in resolving the problem. Data has to be updated either by a function module or by the transaction code. Deleting the rows and columns can cause more problems with the several programs that use the tables. ABAP programmers will love this command as they can always manipulate the tables to prove their results, but with a transport imported in QA and Prod several issues can bring system downtime. Data backup will not help in recovering the situation since the standard tables have been manipulated and you probably have to re-write the entire application from scratch…..
Reference:
http://weblogs.sdn.sap.com/pub/wlg/16205
http://www.kowboyz.nl/blog/edit-sap-tables/
Ideas ! :
Check whether all the repository services and the functions they provide are required
for the different repositories. Deactivate unnecessary repository services to improve performance or activate certain repository services for enhanced functions.
Implementation: You can check which repository services are currently activated as follows:
1. In the portal, choose "System Administration System Configuration Knowledge Management Configuration Content Management Repository Managers". If the "Show Advanced Options" link is displayed, click it to fully expand the list of available repository types.
2. All the possible repository types are listed under "Topics". Choose "Repository Type". A table is displayed that lists all existing repositories of that repository type.
3. The "Services" column of the table shows the repository services that are activated for each repository listed.
the favorites concept is a Knowledge management feature where the user can basically store
links,docs etc in a folder and can retrieve his own docs whenever he can...
so the user needs a user specific folder where he can pull only his docs saved
and not somebody else !!
when the user data store is set up Knowledge Management creates a user specific
folder under the below path.
Content Admin > KM Content > "\userhome\
in this folder you have "my documents" and the "favorites" folder. the "my documents"
was introduced for BI users when the idea of BEx Web Analyzer was built and there
is a link in the Business Intelligence role calles My Portfolio which is nothing
but docs stored in personal docs. there is another folder called Bex Portfolio which
is the Public documents where everyone can access these documents.
so that was the secret....
coming back to Favorites... if you have issues trying to access the docs stored in
the favorites or unable to delete or add etc make sure the component monitor
shows green for every single repository.... now how do we access the Component
Monitor ??? System Administration -> Monitoring -> Component Monitor
you should be able to resolve it from here but if you still have trouble here is the
ultimate secret....
make sure your eu_role has the right permissions....
pcd:portal_content/every_user/general/eu_role/com.sap.km.home_ws/com.sap.km.hidden/com.sap.km.urlaccess/com.sap.km.docs
this path should have the everyone user group and end user permissions ticked.
