SAP Business Objects Explorer

Tuesday, August 25, 2009


This is definitely the first blog which is drifting away from SAP portal but this is the future web application for analyzing data ! SAP BEx could not do this with such ease ...now we know why they merged with BO...read all about it here SAP Business Objects Explorer

and check this out fellas ...i used an excel file in the instructions mentioned in this link BUSINESS OBJECTS EXPLORER and i could not believe this !!!

EXAMPLE BUSINESS OBJECTS EXPLORER

also check this article on BO Explorer i found in SDN

Twitter !

Monday, August 24, 2009








Welcome to the world of Twitter on SAP NW Portal. please follow us on some useful tips and tricks which will help us collaborate better..

http://twitter.com/SAPNWPortal

New Design!!!

Sunday, August 23, 2009


Hello folks..

The old template started to look like an ancient website built in 1999 and hence I have a new template. with new features from "blogger" make use of the comments section and the new Polls ! hope you guys like the new design.

System Users Created during a NW (Portal) installation

Thursday, August 20, 2009

SAPinst creates the following users during the installation process :

SIDadm : This ID is used to logon to the physical server which connects to the Instance that is being
installed which inturn connects to the ABAP/JAVA schema. This ID is also used for administrating the SAP system.

SAPServiceSID : User id required to start the SAP system internally which has the local user right to log on as a service.

SAP_SID_GlobalAdmin : domain level admin group to group users at the domain level so that
the global domain and users can be placed in the right local groups.

SAP_SID_LocalAdmin : local admin group available only in the local machine. this contains the global admin group
of the domain to which the system belongs.

SAP_LocalAdmin : users in this group have full control of the usr/sap folder. SIDadm and SAPServiceSID are
members of this group.


SID: system ID.

Portal KM Repository Services

Wednesday, August 19, 2009

Repository services provide general functions for repositories. In a standard KM installation, certain repository services are activated by default for each repository type, whereas others can be activated explicitly if required.
Each repository service that is activated is loaded when the CM starts up, however
this initialization process results in load consumption, allocates memory and determines whether the repository service is being used and whether it is useful. You can, therefore, improve performance and reduce memory consumption by reviewing the repository services for each repository and only activating those whose functions are actually required

READ MORE......

Portal Navigation Cache Quality Check

Tuesday, August 18, 2009

Consider activating the cache as well as tuning the cache size
and caching time for the "ROLES" navigation connector for better performance.

Implementation: To activate the navigation cache for the "ROLES" connector, refer to the "Enabling/Disabling the Cache" section at:
http://help.sap.com/saphelp_nw70/helpdata/en/a2/19edcf16474a9798a5681ce4fe4b25/frameset.htm

Check the cache quality regularly as follows:

1. Log on to the portal with a system administrator role, choose "System Administration Navigation  Navigation Cache", and under "Navigation Connectors" choose "statistics" in the "ROLES" row.

2. Check the "hit rate" for both "Navigation Entry Points" and "Navigation Node".
If any of the hit rates is not optimal, for example much less than 100%,
choose the following link for information about adjusting the configuration of the "ROLES" navigation connector:
http://help.sap.com/saphelp_nw70/helpdata/en/a2/19edcf16474a9798a5681ce4fe4b25/frameset.htm

Background: To improve performance, the portal caches each set of navigation nodes required by a user.
If a user has access to the same navigation hierarchy as a previous user, the portal
can retrieve the navigation hierarchy from the cache instead of generating it again.