BEx Web Setup 

Description

You need the BEx Web to display your BI application in a Web browser, or to use BI integrated planning, information broadcasting, or the PDF-based printing function. The BEx Web from SAP NetWeaver 2004s is based on the technology of the SAP NetWeaver Portal and the J2EE Engine for the SAP NetWeaver Application Server.

The BEx Web setup requires various usage types to be installed. Usage types are the technical components of the SAP software. Usage types determine which system components are required and the roles of these system components in specific scenarios.

For the BEx Web, you require the usage types Business Intelligence (BI) and Application Server ABAP (AS ABAP). These usage types basically correspond to the implementation of the back-end functions of the BI capability in SAP NetWeaver 2004s.

You also require the following usage types for setting up the BEx Web:

●     BI Java components (BI Java)

●     Application Server Java (AS Java)

●     Enterprise Portal (EP)

The usage type Enterprise Portal (EP) corresponds to SAP NetWeaver Portal. However, you do not need a fully installed portal for the BI capability in SAP NetWeaver 2004s; you basically need the runtime environment of the portal only. This is sufficient to display Web pages (URLs) created in BI.

The usage type BI Java Components (BI Java) contains the Web runtime environment for SAP NetWeaver 2004s and thus the functions for enterprise reporting, printing on the Web, PDF export, and so on. This usage type requires the installation of the usage type Application Server Java (AS Java). For more information about possible system configurations, see the Installation and Upgrade Guides in SAP Service Marketplace at service.sap.com/instguidesnw2004s.

General Practices with Migration

For information about setting up the BEx Web, see SAP Note 917950.