AccApp Delivery

Finally we hear the scream of relief for running web dynpros and heavy HTML objects for a global implementation...
Accelerated application delivery is finally here after years of people talking about how this would change the way portal can be efficient outside your LAN.

Check this video

Thank you once again SAP !

Thank you for bringing my article on the home page again...
To read the second part click here..

Themes for Anonymous KM iViews

Follow the below rules to display the themes for KM anonymous iViews..
I figure this is one concept not mentioned as a document in any of the sites sdn,help or even service market place .... woohoo !!

1.Assign the default Portal desktop in Portal Content > Portal users > standard portal users > default portal desktop the everyone user group permissions.
2.Create a folder called desktops in the portal content of Content administration.
3.System administration > Portal display > desktops and display rules > portal content > right click on the desktops folder and create a portal desktop >
4.Add the framework page after modifying it in the content administration.
5.Add the theme to the desktop as well.
6.Check permissions on the newly created desktop and assign the everyone user group permissions.
7.Check for permissions in the system administration > permissions > portal content > portal users > standard portal users > default portal desktop > check for everyone permissions.
8.Under themes in the portal content catalog check for the theme and its permissions.
9.Check for permissions on the newly created portal desktop and assign the everyone permissions.
10.Make sure that the framework page that is included in the portal desktop has the everyone user group permissions with end user ticked.
11.Any change in the framework page has to be done in the content administration and not in system administration.
12.For the rule collection use the following expressions:
If URL Alias = portal/anonymous
THEN Portal Desktop = (the portal desktop that you created).
13. Test it and it has to work!!

Everyone User Group

A user accessing the backend SAP system requires the “everyone” permissions on the system object connecting the SAP system. The end user permission has to be granted which will open the doors for the portal to access transactions in SAP. The everyone user group contains 2 types of users: Authenticated users and Anonymous users.












Any user accessing the Portal belongs to the authenticated user group by default since he is authenticated to access the portal. If the permissions don’t list the everyone user group in the system object the user being authenticated cannot access the SAP system. This is a very logical explanation for many folks struggling to connect Portal to a SAP system without giving the super admin role or belonging to the administrator’s user group. When a user is granted the super admin role or belongs to the administrator’s user group he/she can access anything on the backend SAP system. If the super admin role is removed or removed from the administrators user group the user is unable to access the backend system. This is a very common issue and learning more about this everyone user group can give you a logical explanation for this problem.

Check List

Consider the below as the possible items to check before completing the user access
to backend SAP System.

End user access consideration:

Check if the user ID is the same in the backend ECC and Portal.
If the user ID is different perform User mapping.
Check the backend ECC role and access the transaction in ECC.
If it fails check for authorization Issues in SU53.
Check the right role in the portal that has been assigned to the end user.
Check if the user is assigned to a user group which has the right Portal Role
that the user is accessing.
Check for permissions in the system object that is connecting the ECC system.
Check if everyone user group has end user permissions for the system object.
Check if the user group has the end user access assigned in the system object permissions.
Check for the language in the user ID in identity management of the user administration in Portal.
Check for the iView properties to determine the right client name and the system number of ECC.
Check for browser issues such as popup blocker.
For iViews broadcasted from WAD determine the type of alias to be mentioned in the system object properties of the iView.
Try SAP_LocalSystem or delete it completely (Depends on the SP)

Business Explorer Explored !

read more on SDN Wiki
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/EP/Business+Explorer+Explored+with+a+Fleaxible+KM+User+Interface

BI WAD common error

This is one of the most common errors with Broacasting Reports to the portal from the WAD tool...
depending on the SP level modifying the system alias on your broadcasted iView can help
you fix this confusing scenario...







CLICK HERE TO READ MORE.......

Commonly used Portal Development files

For most Portal landscapes the above picture should summarize all the possible
files that can be possibly used...

Visual Composer for Dummies part 2

Load Balancing the Portal Server

C 2 concepts in load balancing:
Scenario 1:
You can start a system with many Java dispatchers, for which the SAP Web Dispatcher or a different load balancer is already activated as a Web switch.
Scenario 2:
In the Java Instance the Java Dispatcher distributes the inbound requests to the server processes to which it is connected. The Java dispatcher runs the load balancing when the first session request arrives. The dispatcher ensures that subsequent requests get to the server process that is processing this session.


Now consider a scenario where the CI or the central instance and the dialog instance are in different Operating systems, the portal needs some work and I think this is a very rare scenario where not many clients would adopt this system landscape.
lets consider the possible issues faced on the Portal in this heterogeneous system landscape and provide solutions.
Problems and solutions:
The KM iViews are severely affected and the solution is mentioned below :
Make sure the settings for the cluster environment is not deselected. System Administration > System Configuration > Knowledge Management > Content Management > Global Services > system landscape services.

the secret is here...

· In the portal, choose System Administration ® System Configuration ® Knowledge Management ® Content Management ® Repository Managers ® File System Repository.

· Open the etc entry, and then choose Edit.

· In the Root Directory parameter, enter the following value:

· $(sys.global.dir)/config/cm/etc

· Save your changes by choosing OK.

· To check the changes, open the configuration of the /etc file system repository again. The new operating system-specific path is displayed below the Root Directory parameter.

Restart the portal.