This Blog describes how different Web Environments and the SAP Enterprise Portal can interoperate.
Different Web Environment could be IBM WebSphere, Microsoft Share Point, BOBJ, CRM WebUI and any simple HTML page that wish to embed some portal content (SAP Portal iView from any kind) in it.
On this blog I will explain how to create hyperlink from BO infoview (BOBJ) to launch a Web template SAP BI 7.0.
Note: The below information is relevant to create interoperability between any external environment and SAP portal and not necessarily only with Business Object Infoview.
While trying to launch for example the following BI query from outside of the portal:
First, we would probably get the Portal Logon Screen and after entering the credentials we are likely to get the loading animation goes on and on in endless loop. The logon screen is not a part of this blog and can be avoided on various ways (defining the desired permissions and Authentication Scheme on the iView or passing SSO cookie and/or passing the credentials on the URL etc.).
The pending loading animation issue in this case is caused since Application Integration engine of the portal is expecting that the main frame that calls it is owned by NetWeaver and by that it expects some properties in Java Scripts which are not available in a simple iFrame.
Fortunately there is documentation for the integration of SAP NW iViews into IBM Web Sphere which is accessible for you:
In this scenario we need to modify a bit your portal. please look at the point 4.2 + 4.2.1.
Restart the portal and follow the description from the document. Especially you need to start the portal using this new
The document is for IBM Web Sphere, but should fit all external portals which are accessing SAP NW from outside.
Now we need to specify a different link in order to launch the BI query since we would like to utilize the new URL alias that we’ve defined in the web.xml file which is called ‘interop’.
The new link should be (for example):
The general structure of the link is:
The above link should work when launched from the Infoview or any other external environment.
And when it does, we see the entire portal environment (top level navigation, detailed navigation etc.) and not only the content area that displays the application. So the next step would be to create a new portal desktop that is assigned only to portal URL alias ‘interop’.
The new desktop will include a copy of the default framework page but the only unhidden part will be the portal content area
– all other parts should be marked as hidden.
The result would be that the hyperlink will display only the desired application in a clean iframe without the portal environment.
Notice: From Enterprise Portal version 7.30 and above the interoperability mode of the portal is coming “out of the box” with the portal which means that no
configuration is needed on portal side and no need to customize any farmeworkpage. The URL interop has a dedicated Desktop and frameworkpage
which does not include the portal navigation parts:
So if you already use portal version 7.30 the interop URL:
Should already work. 🙂