com.sap.ip.bi.web.portal.integration.launcher slow in Portal

[Former Member]

Hi experts,

com.sap.ip.bi.web.portal.integration.launcher is consistently showing as one of the slowest-running in our NW2004s SP16 Portal (non-Federated). Even the report variable screen is slow to load especially on first-time access. E.g., 31.8 seconds first time, 5.9 seconds second access in same session.

But what is curious is that it sometimes the variable screen load time goes as low as 350ms if you keep trying within the same session.

We've done the obvious - patching the BI Web App components, tuning the portal & Java runtime, checking the JCOs, load-balancing, tweaked the BI backend... but without being able to impact the performance of this application substantially.

So I would value any suggestions for improvement! Any tables we can cache? Any SAP Notes to shed some light on this area? Any Portal settings to tweak?

Thanks, Marc

[Former Member · Accepted solution]

Hi Marc,

Slow point are to com.sap.ip.bi.web.portal.integration.launcher and

JCO connection. Would you please check CPIC_MAX_CONV in SAP Note 314530?

-Regarding of BI java on Web performance, would you please check the

SAP Note 1022930?

SAP Note 1025307 is a summary notes for performance on Web.

Do you use antivirus software with a javascript scanner, but still would you please also check the SAP Note 983066 because sometime this also may responsible for slow performance.

SAP Note 948158: Performance problems/measuring BI Java Web runtime

One more thing would like to highlight:

In first acess it's slow because OLAP cache was not in use, but after the first execution it's loading the variable from the cache so it's comperatively fast then the previous acess.

Let me know, incase any confusion..

Thank you,

Tilak

[Former Member · Accepted solution]

We've reviewed the noteware as I said and run traces on the BI web application which appear to indicate high runtimes and database query times just for displaying the variables screen - usually 20+ seconds on the first call to buffer metadata etc and then 2-3 seconds subsequently. We also notice RFCs being invoked many times e.g., BICS_PROV_GET_MEMBERS.

Any way to pre-buffer the variables/metadata you're aware of?

[Former Member · Accepted solution]

Initial cause

Message:

Exception condition "DB_READ_PROBLEMS" raised.

Stack trace:

com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Exception condition "DB_READ_PROBLEMS" raised.

Message:

Error while executing function module: BICS_PROV_OPEN

Stack trace:

com.sap.ip.bi.webapplications.runtime.controller.MessageException: Error while executing function module: BICS_PROV_OPEN

MY Sytem package had patched 9

help me to solution ,please!

thank you!

[Former Member · Accepted solution]

Good morning,

It looks very much like an ABAP error here, BI backend is the first place I would be looking. Please check or have your Basis team check for you:

- ST22 for any short dumps

- take a look at SAP Note 1048691. Taking an RSTT trace may help you isolate what the problem is

- you can also check STAD to see what is happening while you run a report. This may help you isolate problems such as memory consumption, slow dialog response times and slow table reads

- generally, are your RFC-related backend parameters correct in RZ11?

- any general problems with ABAP connectivity to database or database tables full etc?

- on the Portal side check your RFC connections to the BI backend. Go to your WebDynpro console and test each of the connections

- use the BI Support Desk (SAP note 937697) to check if all your connectivity is right between Portal and BI. Remember you need an admin user to run this.

Let me know if this helps!

Marc