Netweaver Portal Optimization Tricks: Delta Links

Most of us use this, ain’t we ? Whenever we have to assign an iView to a role, we simply delta link it. Ever wondered delta links could hamper your Netweaver Portal’s performance? No? Then you should read on..

Delta links should be used cautiously when you are after role and worksets. Especially when you are creating nested relationships between objects. For e.g. an iView can be a source as well as target. If a target is a source of another delta link, while rendering the hierarchy, rendering consumes huge chuck of time. Following image shoes typical example of such hierarchy. 

Therefore, we should avoid deep hierarchies and use the delta link only when the object is going to be reused.

Always keep the source template intact. This means, you may change it but change it few times. This stabilizes the source of a delta link

Use delta links only for commonly used objects. If you know a certain iView is going to be used few time, it is better to copy them instead of delta link. This helps performance greatly. Such a small unit can get stored in cache easily and can we rendered in no time.

I hope this helps you in fine tuning the performance of Netweaver Portal. I know there are various other configurations that can affect the performance but knowing such a small utility is always handy.

If you have any doubt or concern on this, please feel free to contact me or comment here.

Ameya