Portal Performance

[Former Member]

Hi Experts,

I am currently supporting Ep7.0 SP 10.

In the portal we have only webdynpro applications.

We have a severe performance issues in portal. I am trying to figure out the root cause of it.

One thing I noticed here is that, the first run after the user logs in, takes a lot of time and that too 5-10 min if they run any transaction which process multiple units.

Do you think there is something wrong with the initial logon to the SAP systems from the portal, Network latency etc?

Please give me your comments.

AM

[Former Member · Accepted solution]

Hi,

Hope following solution will help you in getting better solution while loading.

1) Apply SAP Note# 723909 and 716604 if your database is Oracle

2) Once you are done with all the changes in the Portal, Logged in to the portal using Admin Role and go to System Administration-->Navigation.

Here you need to clear all the Caches and then Click on the Enable All button.

For better understanding , refer to the following links:

http://help.sap.com/saphelp_nw04s/helpdata/en/a2/19edcf16474a9798a5681ce4fe4b25/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/3e/43ace6ea8a41f9aa70a3a0e33ca0f2/frameset.htm

-Thanks-

Mihir

[Former Member]

As I mentioned, we have a lot of webdynpros.

And we use web service for the connectivity with the back end systems.

And first time if you try to process multiple units, (10 units) the whole process takes a longer time may be more than 10 min.

So i believe there is something wrong with the connection to the systems. is there any way to diagnose this.

AM

[hofmann]

Hi,

the way to diagnose the portal is to use E2E RCA. If you don't have this tool ... try to use jconsole and connect to the JMX port of your java server.

Can you check your log for an error? Maybe your portal/webdynpro tries to connect to the backend but is receiving a connection error? 10 minutes is a long time ... Some timeout has to be happening and when the timeout is occuring between your portal/webdynpro and the backend the timeout should appear in the logs.

br,

Tobias

[Former Member]

Hi,

Thanks for the suggestions..

After getting the test reeults from different locations, i came to know that the result vary from location to location.-can this be related to network?

also time to time.-can this be related to the data the user enter? or the portal landscape.

Regards

AM

[hofmann]

Hi,

portal performance can be affected by many factors. If you don't have access to E2E RCA and the tools, try the following:

1. Test the network: verify with a ping (ping server) your network. Also try a bandwith ping (ping -l 10000 server). No packet should be lost and the response time should be nearly the same.

2. Verify the server node. Take a look at the JSESSIONID and saplb_* cookie. If the long response time always is occuring on the same Server (saplb_*) + Servernode (JSESSIONID) you can narrow it down to a specific servernode. Maybe the sessions to the backend are not closed on this server node.

3. Take a look at the backend. If it is ABAP you can take a look at the workload, user trace, log files, etc.

br,

Tobias

[former_member195896]

Hi Anoop,

I have gone through this situation many times at different client's location. The best bet is to use a program called HTTP Watch or a similar freeware program. This will give you the exact part of the request which is being delayed and will also let you know why an application is slow, whether a server processing time, network latency, DNS resolution issues. etc.

cheers,

Shantanu

[hofmann]

Hi,

do you have access to Solution Manager Diagnostic with Wiley Interscope? These tools are recommended by SAP to do an End-to-End analysis of your portal landscape. This would allow you to trace an user activity from the browser up to the backend and to find out, where exactly the error is occuring.

To test your network, you can try an bandwith-test (bing). Also, you should always use the latest JDK version recommended by SAP for your system. To speed things up you should also consider upgrading your SP10 to the latest one (>= SP16).

Chekc your JVM parameters, are there any Out of memory errors occuring. In this case, increase your Java heap size (2GB) or add more server nodes.

br,

Tobias

[Former Member]

Hi Anoop

Could you elaborate your performance issue there? And also hardware info of EP host, CPUs, RAM, what kind storage, how many end users need to login, how many server nodes you have right now, etc.

Thanks,

Effan

[Former Member]

is there any way to find out if something is wrong with the first login.

AM

[Former Member]

Hi,

Check this link

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d164c5ee-0901-0010-4fbf-d0856b5c...

John

[Former Member]

Hi,

At first point, you can check logs for possible reasons. If reqd, you can change the trace level of portal logs and check the reason. You can also check Performance Tuning documents to fine tune your portal. Search for "Performance Tuning" in SDN.

Regards,

Harini S