Skip to Content

I recently faced a problem which almost jeopardized our production installation. I want to share the same problem and its solution, via this blog.

My client decided to upgrade the portal form 6.4 to 7.02. All was set and everything was in place until we found that the BW reports do not work in the new portal.

A little bit of background scenario: My application uses BW report iviews to display the content fetched from BW as the backend. The content is processed via web templates which is used by the portal through appintegrator. At the frontend, ExtJs is used to formulate the content in a proper grid and then display the same.

After the portal installation, BW report iview did not load at all. On comparing the old and new systems, I could see that the URL for the BW reports were getting generated differently in the old system. I tried different ways to handle this URL and then manipulate it before loading the web templates, but it was not as feasible as final solution, which I discovered later. Before that, I also toyed with the page/iview properties and found that the isolation method of the BW report iview is set to URL which cannot be changed. This property of page when set to embedded, somehow corrupts the BW iview URL internally, which in turn does not load the page. When the property was set to URL, the reports were getting displayed but it had its own framework. Actually, the URL method renders the page as the HTML output whereas the embedded method generates the iframe and renders the page onto it. Had it been the case that the page was getting displayed with the embedded property, we could handle the look and feel via customized css. But here it was with URL property, and the complete look and feel of the page was getting disturbed which required all new framework for the BW pages. This was again not at all a viable solution.

Solution: Since the problem was in the URL, so I created URL iview for the BW reports. I mean to say- Login into portal as admin and preview the BW report iview which is not working. After the page loads, right click on that page and select the properties. Copy the complete URL.Now create an URL iview and paste the above copied URL in this new iview. Now use this URL iview in your application and it should work fine.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply