
By integrating SAP NetWeaver BW 7.x with the SAP NetWeaver 2004 (SAP EP 6.0 based on SAP Web AS 6.40 Java), you can use the BEx Web functions from SAP NetWeaver BW 7.x. A BEx Web application in SAP NetWeaver BW 7.x uses the SAP NetWeaver 7.x portal as its infrastructure and is implicitly called as an iView of a SAP NetWeaver 7.x portal. Integration means that an iView and the entire BEx Web application from the SAP NetWeaver 7.x portal are incorporated in SAP EP 6.0.
A SAP NetWeaver portal is used as the required technical infrastructure to display BEx Web applications, queries, and reports. BEx Web applications are displayed as iViews. The URL for a BEx Web application points to the host name and port for the Java stack (J2EE). No direct call is made using the URL of the ABAP stack.
The URL of a BEx Web application in SAP BW 3.5 points to the host name and port of the Internet Communication Manager (ICM) in the ABAP stack.
In order to integrate SAP NetWeaver BW 7.x with the SAP NetWeaver 2004 portal (SAP EP 6.0 based on SAP Web AS 6.40 Java), you need to ensure that the following prerequisites are met:
Other than the general configuration of BEx Web, there are no additional requirements for SAP NetWeaver BW 7.x.
In the SAP NetWeaver 2004 portal (SAP EP 6.0), you can display BEx Web applications, queries, and reports from SAP NetWeaver 7.x.
The iViews are created and maintained using wizards in the Portal Content Studio. For more information about creating iViews using the Portal Content Studio, see Integration Using the Portal Content Studio.
If you select SAP NetWeaver BW as the version, you must use the syntax from SAP NetWeaver. To call a Web template, you therefore have to enter template=<TEMPLATE> (instead of template_id=<TEMPLATE_ID>). More information: BEx Web Application or Query as iView in the Portal.
Once you have created the iView, you can test it by choosing Preview. You can include it in portal roles by using the Portal Content Studio.