Going BI 7 – Cannot escape a Federated Netweaver portal landscape

With new Business Intelligence version 7, SAP has moved it BEx Web Analyzer to a pure Java framework. This necessitates that there be usage type BI Java, the prerequisite of which is usage type EP. Which means every BI 7 upgrade or installation needs a Netweaver Portal together with KM and Collaboration installed. This has been an interesting way how the landscape has been laid out.
Now it does not really mean that BI Java has to be set up on your primary portal instance. Instead what it means for all practical purposes is that it will almost necessitate setting a separate portal instance. While users will not necessarily know (and should not know) that there is another portal, this additional portal will be real for portal administrators and BI team to manage. The framework for this new portal can (and should) be kept dormant (hidden). The real use of this portal instance should be limited to the use of its underlying J2EE engine to run the BI Query runtime and BEx web analyzer. And probably to use the KM that comes with it for information broadcasting functionality.
In BI 7, The AS ABAP usage type continues to have the BW 3.5 Web Runtime together with IGS for graphics, and is topped off with BI Content Add-on. Which is inclusive of all that is required for web based BEx reporting as people have seen coming out of BW 3.5. Whats new is really the BI Java Usage type that brings all the new added functionality (the IT Scenarios like Enterprise Reporting, Query, and
Analysis) to the fore for the users. For example Analysis Item, Formatted Reporting, Web Printing, PDF Export, etc. Its also required for rendering Webdynpro for Java apps for BI Integrated Planning.
So while technically one could do a “technical” upgrade to BI 7 without the Java engine, any new functionality will need Java (and hance the dormant EP instance).
How is the BI Portal different from the user facing primary portal instance?
Even if your company did not foresee a need for a federated portal, looks like there is no escape from it since in this new architecture, the BI Portal becomes a producer portal and the main portal the consumer portal. Content from the BI producer portal surfaces inside the consumer portal as url iViews, remote role assignment is possible, etc.

You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

AddThis Social Bookmark Button

5 Responses to “Going BI 7 – Cannot escape a Federated Netweaver portal landscape”

  1. What are my options, as far as the SAP GUI are concerned if I have BI7.0?
    SAP GUI 6.4 (What patch level?)
    SAP GUI 7.0 ?

    Thanks for any thoughts.

  2. Very good artical.


  3. Paulo Poinha Says:

    There are other ways to sidestep this issue…. Creating a redirection iview on the main portal which when loaded will redirect to the BI Portal and keep the SSO certificate to avoid user logging on again. It works very well, but we still have to maintain 2 portals using that approach….

  4. it is a good article, provide bi 7.0

  5. Very nice article!

    Thanks for keeping it available.