Quantcast
Channel: SCN : Unanswered Discussions - BI Platform
Viewing all articles
Browse latest Browse all 5661

Advice needed to host BEx apps in BI launch pad

$
0
0

Dear Experts,

 

I am new to BO and appreciate your help to offer me some advice; links & URLs are also welcome.

 

Our goal is to deploy BI launch pad to users to let them access BEx queries, Dashboards, and crystal reports from it.  Our BO is 4.0 SP8.

 

I have followed this link:

http://wiki.scn.sap.com/wiki/display/BOBJ/Configuration+steps+to+integrate+BEx+Web+applications+into+BI+4.x

and this link:

http://wiki.scn.sap.com/wiki/display/BOBJ/Permissions+and+authorizations+requirements+for+BEx+Web+into+BI+4.x

to configure BEx web application access in BI Launchpad.

 

But the performance is really bad. After I clicked on the Bex web application icon, the loading icon loops for a long time and then it time-out the session.  I don't even get a chance to select the queries.

 

I googled a lot and got a lot of information.  Some said it may be the time to move on to Analysis for OLAP; some suggested to host the BEx queries in portal and then use BI launchpad to refer to the link.  I am quite confused and I don't have sufficient time to try each scenario.

 

I would appreciate if anyone can provide me some info on:

 

1.     What should be the best option to show BEx queries on BI launchpad in terms of performance and maintenance effort? BEx web application on BI launchpad or Analysis for OLAP? Or there is a 3rd better option?

2.     If the best option is not BEx web application, then any links to show me the details to configure it?

3.     If the best option is still BEx web application, then any links on the "Best practices" and "Optimization"?  Right now it is just unacceptable to let the session time-out itself.

4.     Any other advice is welcome and much appreciated!

 

Thank you.

 

Brian H.


Viewing all articles
Browse latest Browse all 5661

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>